Re: backup retention
2001-12-07 08:59:59
We do it like this:
Backup Copy Groups : ENT02 ACTIVE STANDARD STANDARD
Policy Domain Name ENT02
Policy Set Name ACTIVE
Mgmt Class Name STANDARD
Copy Group Name STANDARD
Versions Data Exists NOLIMIT
Versions Data Deleted 2
Retain Extra Versions 33
Retain Only Version 365
Copy Mode MODIFIED
Copy Serialization SHRSTATIC
Copy Frequency 0
Copy Destination DISKPOOL_DRM
Last Update Date/Time 2001-03-07 13:55:05.000000
Last Update by (administrator) ADMIN
Managing profile -
By setting versions data exists to nolimit the factor which limits how lond
versions are kept becomes retain extra.
Hope that helps,
Cory
>>> cookde AT BP DOT COM 12/06/01 08:49PM >>>
it is your "versions data exists" says keep only two copies...
Works like this...
Versions Data Exists : how many copies to keep as long as the file exists on
the client
only keep inactive versions for up to Retain Extra number of days
Versions Data Deleted : upon deletion of the file from the client,
immediately reduce the number of versions down to this
any copies other than the latest inactive copy goes away when they
reach Retain Extra number of days old
Retain Only : keep the last copy of a file for this number of days
DOMAIN Grace Period : If the management class associated with a backed up
copy of a file doesn't exist any more, this is how long that piece of data
will be retained. (kind of a home for the lost)
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- backup retention, Rob Schroeder
- Re: backup retention, Rob Schroeder
- Re: backup retention, Rushforth, Tim
- Re: backup retention, Gabriel Wiley
- Re: backup retention, Cook, Dwight E (SAIC)
- Re: backup retention, Seay, Paul
- Re: backup retention, Seay, Paul
- Re: backup retention,
Cory Heikel <=
- Re: backup retention, Remeta, Mark
|
|
|