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:
Michael Berkowitz <[log in to unmask]>
Reply To:
Michael Berkowitz <[log in to unmask]>
Date:
Tue, 25 Sep 2001 10:24:50 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
Bob Sorenson writes

Exactly my dilemma!  It's a mix--some files regardless of when they were
modified and some files stored by modify date.  For several reasons, two
separate backups are not feasible now.  I've written a job that will run
every Sunday at 1:00 a.m. with the "Rename solution".  This way, if we need
to know if the file was truly modified or not, we can be pretty certain (not
full-proof, I admit).  If it was "modified" during the time my job ran, it
probably wasn't really changed because we don't have any other processes
running then
----------------------------------------------------
An alternative might be a different backup program.  We use BackPack
(formerly RoadRunner) from ROC software.  Here's how to do what you want.

SELECT ("FILES YOU WANT SOMETIMES" WHERE MODDATE>=somedate)
SELECT "FILES YOU ALWAYS WANT"
STORE TO *T
/GO

No plug, just a user.

Mike Berkowitz
Guess? Inc.

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

ATOM RSS1 RSS2