HP3000-L Archives

July 1996, Week 3

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:
Chad Gilles <[log in to unmask]>
Reply To:
Chad Gilles <[log in to unmask]>
Date:
Wed, 17 Jul 1996 08:13:39 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
In article <[log in to unmask]>,, ChipDorm (aka
[log in to unmask]) says...
>
>Does anyone know a simple way to alter the modification dates on Image
>datasets so that all datasets will have the same modification date?
>"touch" does not seem to alter PRIV files.
>
 
Then Mark Landin asked:
 
>Just curious: why do you want all the datasets to have the same date?
 
Then ChipDorm answered:
 
>The usual reason is so that a partial backup will store the entire database.
 
Now comes my .02 worth.
<<PLUG ON>>
        We use Roadrunner from Unison/Tymlabs as our backup utility. It has a
parameter that when set, will store a complete database even if only one
dataset has been modified. We use this on all of our partial backups and it
works perfectly.
<<PLUG OFF>>
        I think other backup utilities ,such as ORbit's backup products,
offer a similar feature. Turbostore might have it as well, if it doesn't then
it should be an enhancement.
--
*************************************
**                                 **
**  Chad Gilles                    **
**  Sr. Software Analyst           **
** ------------------------------- **
**  American United Life           **
**  One American Sq.               **
**  Indianapolis, IN 46206-0368    **
** ------------------------------- **
**  Ph.  317-263-1423              **
**  Fx.  317-263-1956              **
**  EM.  [log in to unmask]        **
**                                 **
*************************************

ATOM RSS1 RSS2