ADSM-L

Re: [ADSM-L] Data Retention Settings: Unintended Consequences

2009-01-28 14:47:51
Subject: Re: [ADSM-L] Data Retention Settings: Unintended Consequences
From: Kelly Lipp <lipp AT STORSERVER DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 28 Jan 2009 12:46:31 -0700
Boy, it sure looks like you'll have three versions forever on this one.

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Nick Laflamme
Sent: Wednesday, January 28, 2009 12:30 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Data Rention Settings: Unintended Consequences

A client's TSM server has the following copygroup settings:

tsm: SERVER1>q copygroup * active f=d

                 Policy Domain Name: OPEN_SYSTEM_ENVIRONMENT
                    Policy Set Name: ACTIVE
                    Mgmt Class Name: BACKUP_SHARK
                    Copy Group Name: STANDARD
                    Copy Group Type: Backup
               Versions Data Exists: 3
              Versions Data Deleted: 3
              Retain Extra Versions: No Limit
                Retain Only Version: 91
<snip>

Because "Versions Data Deleted" is more than 1, and because "Retain
Extra Versions" is set to "No Limit," am I correct in deducing that
TSM will keep three copies of deleted files forever, because "Retain
Only Version" will never become relevant?

Or does TSM use "Retain Only Version" for all versions (copies) once
there isn't an active file? (That's not what the doc says, of course.)

Thanks,
Nick

<Prev in Thread] Current Thread [Next in Thread>