Author: "GSHEPPAR@CUUKMAIL" <guy_sheppard AT UK.CU DOT COM>
Date: Mon, 25 Jan 1999 09:49:09 EST
To: I1017261@IBMMAIL IBMMAIL -I1017261 *ibmmail.I1017261 Dear All, No responses yet - Please help The current retention requirements I'm working to are keep backups for 28 days - Simple enough. The b
Author: "Lambelet,Rene,VEVEY,FC-SIL/INF." <Rene.Lambelet AT NESTLE DOT COM>
Date: Mon, 25 Jan 1999 16:08:44 +0100
Hello, I would advise to use Archive and not Backup function for such different retention periods. Just define corresponding management classes and code them appropriately in the archive command. Reg
Author: Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>
Date: Mon, 25 Jan 1999 10:38:05 -0500
are [Further similar requirements deleted] This sort of question has been raised a number of times in the past on this mailing list, and the consensus answer that emerged was to use ADSM archive faci
Author: "Thomas A. La Porte" <tlaporte AT ANIM.DREAMWORKS DOT COM>
Date: Mon, 25 Jan 1999 08:13:02 -0800
You can only use management classes to implement different retention policies for different files. You can not implement different retention policies for the same file without using the archive comma
I agree with Rene, have them archive it ! just make some management classes like 1yrarch, 5yrarch, whateveryrarch set the archive copygroup's retention period to keep the data for the indicated perio
Author: Simon Watson <Simon.S.Watson AT OPENMAIL.FIC32.BSPSER.SIMIS DOT COM>
Date: Tue, 26 Jan 1999 07:15:08 +0800
Guy, I would keep my BACKUPS the same and do a specific ARCHIVE of the relevant files which need to be stored for specific periods of time. You would need different ARCHIVE management classes for eac