ADSM-L

Using different policies to nightly and weekly backups.

1998-01-20 23:43:47
Subject: Using different policies to nightly and weekly backups.
From: Gary Bromley <Gary.Bromley AT ASPECT.COM DOT AU>
Date: Wed, 21 Jan 1998 15:43:47 +1100
Dear ADSMers,
I have a requirement for nightly incremental backups to be retained for
14 days and weekly full backups for 3 months (90 days). I have tried
using a weekly & nightly policy set with the same management class, each
having a standard copy group with the following parameters (I used 2
days and 7 days for a test) :-
TEST_DOM    ACTIVE    TEST_MGMT STANDARD  No Limit No Limit        2
2
TEST_DOM    NIGHTLY   TEST_MGMT STANDARD  No Limit No Limit        2
2 mode=modified
TEST_DOM    WEEKLY    TEST_MGMT STANDARD  No Limit No Limit        7
7 mode=absolute

Using a test program to cycle through the days, 2 days after the weekly
backup the weekly version expires.
The sequence goes like this :-
        count=1
        set_date (day of the month = count)
        activate policy test_dom weekly
        while [ count -le 4 ]
        do
                set_date
                start_server
                dsmc incremental /test
                stop_server
                let count=count+1
        done      

        set_date
        start_server
        activate policy test_dom weekly
        dsmc incremental /test
        activate policy test_dom nightly
        stop_server
        let count=count+1

        while [ count -le 12 ]
        do
                set_date
                start_server
                dsmc incremental /test
                stop_server
                let count=count+1
        done   

According to the help text when the active policy is changed, files are
rebound when :

·You change the management class for the file by specifying a different
management class in an INCLUDE statement. 
        ADSM continues to manage the backups based on the old management
class until you run another backup.

·Your ADSM administrator deletes the management class from your active
policy set. 
        ADSM uses the default management class to manage the backup
versions when you back up the file again.

·Your ADSM administrator assigns your client node to a different policy
domain and the active policy set in that domain does not have a
management class with the same name. 
        ADSM uses the default management class for the new policy domain
to manage the backup versions.

Since none of the above is true, I would expect none of the files to be
rebound. The backup report does not show any rebound files, but the
versions are still expiring.

Does anybody know why.

Version 2 Server and Client using shared memory.

Regards
Gary

----------------------------------------------------------------
Gary Bromley
Gary Bromley
Aspect Computing Pty Ltd
Tel : +61 (0)3 9230 2222
Fax : +61 (0)3 9818 1320
Email : Gary.Bromley AT aspect.com DOT au
<Prev in Thread] Current Thread [Next in Thread>