Expiration not working...like I thought it would

[droach]

I have my STANDARD Copy Group defined like this:

Policy Policy Mgmt Copy Versions Versions Retain Retain
Domain Set Name Class Group Data Data Extra Only
Name Name Name Exists Deleted Versions Version
--------- --------- --------- --------- -------- -------- -------- -------
STANDARD ACTIVE STANDARD STANDARD 62 62 62 62
STANDARD STANDARD EXTRA STANDARD 62 62 62 62
STANDARD STANDARD STANDARD STANDARD 62 62 62 62

And have this decomissioned node with its filespaces:

tsm: MYSERVER007_SERVER1>q node MYSERVER049
Node Name Platform Policy Domain Days Since Days Since Locked?
Name Last Acce- Password
ss Set
------------------------- -------- -------------- ---------- ---------- -------
MYSERVER049 WinNT STANDARD 336 492 No

tsm: MYSERVER007_SERVER1>q files MYSERVER049
Node Name Filespace FSID Platform Filespace Is Files- Capacity Pct
Name Type pace (MB) Util
Unicode?
--------------- ----------- ---- -------- --------- --------- ----------- -----
MYSERVER049 SYSTEM 1 WinNT SYSTEM Yes 0.0 0.0
SERVICES
MYSERVER049 SYSTEM 2 WinNT SYSTEM Yes 0.0 0.0
STATE
MYSERVER049 \\MYSERVER04- 3 WinNT NTFS Yes 69,884.3 10.7
9\c$
MYSERVER049 ASR 4 WinNT NTFS Yes 0.0 0.0

When I decomission a TSM client (server) I was not manually deleting the client filespaces. I thought that expiration would eventually purge them after the client quit checking in with the TSM server for nn number of days.

Is there a way to configure TSM to automatically purge filespaces?

Thanks,
Daryl

 

[rore]

Hi,
What do you mean for "I decomission a TSM client ". What did you do to achieve that?

For TSM you have just stopped to take backups. Basically, the node and its data is there because you have version retention. At least the active version is there.

There is no automatically purge. But you can do it manually with 'delete filespace node_name *'. After that you can remove the node.

Rudy

 

[droach]

Thanks for the reply Rore,

When I say decomission I just mean that the client has been shutdown. I don't "tell" TSM that anything has happened to the node.

I would like the filespaces to remain until the expiration date and then purge themselves automatically.

 

[dennis_in_texas]

If you exclude EVERYTHING (or include NOTHING?) on the client, and then run a final backup, the data should expire based on your retention policies. Make sure you have the Inactive Copies setting in the retention policy the way you want it. This setting can throw you a curve ball...

Depending on the number of files you have on the client, this final backup could take a while, because it has to notify the backup server to mark everything associated with the client for Expiration. Don't forget to exclude SystemState, etc.

 

[droach]

Thanks Dennis_in_Texas, I will give that a try.

 

[dennis_in_texas]

Hey Droach!!

You live in Cut and Shoot? I work near Greenspoint and the big airport, in Houston. Small world...

d_i_t