HP3000-L Archives

September 2001, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Tue, 25 Sep 2001 12:06:25 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
X-no-Archive:yes
Bob wrote:
> I need to force selected file sets to be stored on partial
> backups regardless of whether or not they have been modified since the
last
> full backup date.  Any ideas?

How about a store list, preferably kept in an indirect file? If these are
known files or file sets, then either explicit lists of filenames, or
appropriately wildcarded arguments, ought to get you exactly the files you
need.

One important caveat is, that if you go with explicit filesets, and someone
adds a new file to this application, that file will not get picked up.
Whereas, if you go with wildcards, and someone adds a file that fits the
wildcard, but this is not a file you want backed up, you get it anyway. So,
this requires some attention. It's not set it and forget it. But I cannot
imagine a solution that could be guaranteed to be bullet-proof.

My own bias is that using MPEX to change the modified date loses some
important information, when the file was actually modified. Sure, you would
have the files on backup tape, but you wouldn't know for sure which copy of
the file was the same as or different from another. If one tape, or several
tapes in a row, proved bad, you could never be sure that the copy you
recovered from a good tape was a good copy.

Greg Stigers
http://www.cgiusa.com

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2