ADSM-L

Re: Exactly when DO backup versions expire?

1998-09-23 16:02:21
Subject: Re: Exactly when DO backup versions expire?
From: Dan Curtis <vndob569 AT US.IBM DOT COM>
Date: Wed, 23 Sep 1998 16:02:21 -0400
Hello

 Retain extra versions refers to versions of a file that have an ACTIVE
version. It is measured from the
day that the version becomes an INACTIVE version. Thus if you keep 5 versions
and retain extra is set for 30 days and
the file changes between each daily back up you should see this type of
behaviour.

1 ACTIVE version (retained until a new backup is taken or the file is
deleted/excluded)
1 INACTIVE version with a shelf life of 30 days
1 INACTIVE version with a shelf life of 29 days
1 INACTIVE version with a shelf life of 28 days
1 INACTIVE version with a shelf life of 27 days

Assuming you leave today for a 3 month sabbatical (90 days) and expiration runs
every day. When you return
you will have.

1 ACTIVE version

The next day after the file has changed again you get

1 ACTIVE version
1 INACTIVE version with a shelf life of 30 days

Using the first part of the example and deleting/excluding the file instead of
going to Tibet you have the following after the next back up
if your versions data deleted is 1 and retain only versions is 60.

1 INACTIVE version with a shelf life of 60 (this is the formerly ACTIVE version)

Or skipping the above illustration the timers run from the time the version
(physical file in ADSM storage) enters the state that the parameter
measures. This has also been covered in responses to what happens when you
delete a file from a database product that is unique due to
a time stamp as part of the name. The file does not actually get deleted from
ADSM storage until the retain extra versions runs its course.

 Hope this helps
  Daniel