ADSM-L

[no subject]

2015-10-04 17:50:04
Mark,
hope this helps. It is in RTF...
 

Versions (file exists)

This option defines how many backup versions of a file are to be retained while the file exists on the client workstation. For example, if Version exists is set to 3, then the three most recent unique versions of the file will be retained. When a new backup copy is made (defined by Frequency), the oldest version is deleted and replaced by the new version.

Options for this field are from 1 to 9999.

Related fields: Retain Days (extra copies)

Versions (file deleted)

This option defines how many backup versions of a file are to be retained once the original file has been deleted from the client workstation. For example, if Versions deleted is set to 1, then when the original file is deleted from the client workstation, all but the most recent backup version is also automatically deleted by ADSM.

Options for this field are from 1 to 9999.

Related fields: Retain Days (last copy)

Retain days (extra copies)

This option defines how many days to retain old backup versions. For example, if Versions (file exists) is set to 3, then the three most recent unique versions of a file will be retained. The retention of these versions is further controlled by the Retain days (extra copies) field. If this option is set to 180, all copies but the most recent version of the file will be automatically expired then the versions become 180 days old. In other words, if the file is not modified for over 180 days, only the most recent version will be maintained.

Options for this field are from 0 to 9999 or NOLIMIT.

Related fields: Versions (file exists)

Retain Days (last copy)

This option defines the number of days to retain the last backup version of a file. For example, if Versions (file deleted) is set to 1, then only the most recent version of the file will be retained once the original file is deleted off of the client workstation. The retention of this version is further controlled by the Retain Days (last copy) option. If this option is set to 60, the last backup version will be automatically expired after sixty days. In other words, if you delete a file from your workstation, the most recent backup version of that file will be available for restore for another 60 days.

Options for this field are from 0 to 9999.

Related fields: Versions (file deleted)

Retain Days (archive)

This option defines how many days an archive copy is to be retained. Archive copies differ from backup copies in that there is no version control. A file may have an unlimited number of archive copies. Archive is intended for vital records retention. For example, retain financial data for 7 years, retain patent information for an unlimited amount of time, retain geophysical data for 20 years, etc.

Options for this field are from 0 to 9999 or NOLIMIT.

cheers Ian
-----Original Message-----
From: Remeta, Mark <MRemeta AT SELIGMANDATA DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
Date: 18 December 1998 15:56
Subject: Simple Question

>I am a bit confused about management classes. Specifically the number of
>backup versions to keep.
>I understand that versions data exists specifies the number of
>'inactive' copies to keep but then what does retain extra versions do.
>They seem to contradict each other. Does one override the other. If I
>say keep 3 extra versions and keep inactive copies 30 days, does that
>mean that any inactive copies kept longer than 30 days will be deleted
>even if there are less than 3 extra versions and visa-versa
>
>Thanks in advance,
>
>Mark Remeta
------=_NextPart_000_001F_01BE2AA7.A050AFA0-- =======================================================================
<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=