Re: Versions deleted
2015-10-04 17:42:39
Hi Dave.....
Here's a short description of the Version Data Deleted parameter:
The maximum number of different backup versions that the server retains
for files and directories that have been erased from a workstation. The
server ignores this parameter while the file or directory remains on the
workstation.
If users erase a file or directory from their client nodes, then the next
time
a full incremental backup is run, the server changes the active backup
version to inactive. The oldest versions that are more than the number
specified by this parameter then expire, and the server deletes them the
next time expiration processing runs.
The expiration date for the remaining versions is based on the Retain Extra
Versions and Retain Only Version parameters.
Have a nice day
Clarence Beukes
IT Specialist (Storage Solutions)
IBM Product Support Services
Tel : +2711 302 5333 Fax : +2711 302 8209
Mobile : +2782 573 5665
"The success of men never lies in falling, but in falling and rising up
again."
"Miller, Dave" <dave.miller AT BHS DOT ORG> on 06/29/99 06:46:55 PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Clarence Beukes/South Africa/IBM)
Subject: Versions deleted
I'm confused about how the VERSIONS DATA DELETED paramater works.
If the backup copy group specifies
Versions Data Exists 30
Versions Data Deleted 1
Retain Extra Versions 30
Retain Only Version 30
And the following takes place
6/29/99 file dave.oracle.dump.Tue is created and bound to this mgmt_class,
during the nightly incremental.
6/30/99 file dave.oracle.dump.Tue is deleted.
7/6/99 file dave.oracle.dump.Tue is created again and bound to this
mgmt_class,
during the nightly incremental.
What will be the availability of the file created on 6/29?
|
|
|