If you use archive -deletefiles you can incorporate step 3 and use that as a checkpoint that 1. Files are actually archived before they are deleted and 2. That files are deleted after they are archived. Good Luck. Mary V
-----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2003 3:31 PM To: [EMAIL PROTECTED] Subject: Re: Special Filesystem Backup Is the usage cycle discrete enough such that you can work in the backup (or archive) before they empty it? That is, do you plan to implement something like this: 1) fill 2) backup (or archive) - file system does not change during the operation 3) empty 4) repeat from (1) In this case, you probably could use archive with RETVER=NOLIMIT in the copygroup. Assuming that the file system is emptied between archive operations, each archive copy would represent a unique file. Alternatively, you could use backup with copygroup settings like this: VEREXISTS=NOLIMIT VERDELETED=NOLIMIT RETEXTRA=NOLIMIT RETONLY=NOLIMIT Incremental backup will not create any duplicate backup versions, so you'll have a full history of every file (as each file existed at the time the file system was backed up). If the file is deleted, the backup version will become inactive, but will still be kept forever due to the VERDELETED and RETEXTRA/RETONLY settings. Do either of these capture the spirit of what you are looking for? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Theresa Sarver <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07/18/2003 12:51 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: Special Filesystem Backup Hi Andy; Thanks for the response. Unfortunately no, it's not quite that simple. This is a 100GB filesystem, containing large mainframe files. The mainframe folks fill up this filesystem, then empty it, then fill it again. I need to keep 1 copy of every single file ever belonging to this filesystem whether or not it is active. Which is why I setup an Archive...but that doesn't seem to be correct either. Thanks for the help! Theresa >>> [EMAIL PROTECTED] 07/18/03 01:55PM >>> Theresa, what I am reading into your question is that you have a requirement to maintain only a single backup version of each file in this file system. In other words, the backup file space should reflect only the current state of the actual file system (as of the time the backup is taken). Is this an accurate summary? In this case, you could use a copygroup with settings like this: VEREXISTS=1 VERDELETED=0 RETEXTRA=0 RETONLY=0 The above settings assume the following: - If someone deletes a file from the file system, you no longer require a backup version for that file. The potential problem here is that if the deletion was erroneous, then your window for restoring that file will be somewhere between 0 and 24 hours (i.e. you'll have up to the time of the next backup to restore the file). - Similarly, if someone changes a file on the file system, then decides they need to get the prior version of the file back, your restore window is as described above. This is one reason why I advocate configuring TSM by thinking in terms of your RESTORE needs, not backup needs. If my assessment above isn't quite right, perhaps you could describe the restore needs? That might be useful in fine-tuning the policy settings. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Theresa Sarver <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07/18/2003 07:18 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Special Filesystem Backup Hi all; I have a filesystem that requires only 1 copy of the data on tape. This data however, needs to be kept more/less forever. FYI...The rest of the filesystems in this PD/PS/MC have the retention of 5/1/30/60. I tried setting up an archive copy group for just this filesystem, however, that is backing up (archiving) the entire filesystem everyday - instead of only new files. Is there something that I can do to make it only archive new files? Or do I just need to setup a backup copygroup with the retention of 1/1/-/- for this lone filesystem? If so, is there any way around creating an entirely new PD, PS, MC for this 1 filesystem? Thanks in advance for the help! Theresa
