Re: BRMS, incremental saves, last saved date.

John,

capital idea!   Gee, I hadn't thought of that (duh!) - thanks for the tip.

On 4/15/05, Jones, John (US) <John.Jones@xxxxxxxxxx> wrote:
> Dunno how BRMS does it, but can't you have your software that's doing
> the saves specify UPDHST(*NO)?  Seems the safest method.
> 
> John A. Jones, CISSP
> Americas Information Security Officer
> Jones Lang LaSalle, Inc.
> V: +1-630-455-2787  F: +1-312-601-1782
> john.jones@xxxxxxxxxx
> 
> -----Original Message-----
> From: rick baird [mailto:rick.baird@xxxxxxxxx]
> Sent: Thursday, April 14, 2005 2:23 PM
> To: Midrange Systems Technical Discussion
> Subject: BRMS, incremental saves, last saved date.
> 
> Hey all,
> 
> does anyone know what BRMS uses to decide whether to save a file on an
> incremental backup?
> 
> In other words, if I do a BRMS weekly full save, and daily incrementals,
> but lets say on wednesday I make a change to a file, and save that file
> to another tap drive or a savefile using SAVOBJ (or
> even SAVOBJBRM).   Does that file get backed up that night on my
> incremental too?  or will it treat the last SAVOBJ as sufficient to not
> save the file?
> 
> in still other words, does BRMS keep track of it's own last save
> date/time or does it use the object's last save date/time?
> 
> The problem I'm going to have is that there are several places in the
> software where a file or files are saved to savfile, not via BRMS.
> These save files could possibly be overwritten later, and BRMS would not
> know about it.
> 
> Thanks,
> 
> Rick
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> moment to review the archives at http://archive.midrange.com/midrange-l.
> 
> This email is for the use of the intended recipient(s) only.  If you have 
> received this email in error, please notify the sender immediately and then 
> delete it.  If you are not the intended recipient, you must not keep, use, 
> disclose, copy or distribute this email without the author's prior 
> permission.  We have taken precautions to minimize the risk of transmitting 
> software viruses, but we advise you to carry out your own virus checks on any 
> attachment to this message.  We cannot accept liability for any loss or 
> damage caused by software viruses.  The information contained in this 
> communication may be confidential and may be subject to the attorney-client 
> privilege. If you are the intended recipient and you do not wish to receive 
> similar electronic messages from us in the future then please respond to the 
> sender to this effect.
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>