TSM NDMP retention driving me crazy!

Gerry123

Newcomer
Joined
May 9, 2007
Messages
2
Reaction score
0
Points
0
Hi guys,

I am having an absolute nightmare trying to get a simple backup of a NSeries volume to work via 'backup node' command from TSM server. Basically the issue is it doesn't seem to want to follow the Management class defined for the node as far as retention goes.

Whatever I do, the backups keep expiring and falling off the radar after 7 days. There has to be an obvious reason, but I can't for the life of me see it, I was hoping someone else might be able to.

I am running backups as below :

FULL
backup node stgnode01 /vol/test_vol1 toc=yes mode=full mgmtclass=nasmc wait=yes (This runs on 1st and the 16th of the month)

DIFFERENTIAL
backup node stgnode01 /vol/test_vol1 toc=yes mode=differential mgmtclass=nasmc wait=yes (This runs every day except the 1st and the 16th of the month)

My management class definition is below :
tsm: TSMSERVER1>q co NASPD ACTIVE NASMC f=d

Policy Domain Name: NASPD
Policy Set Name: ACTIVE
Mgmt Class Name: NASMC
Copy Group Name: STANDARD
Copy Group Type: Backup
Versions Data Exists: 104
Versions Data Deleted: 104
Retain Extra Versions: 104
Retain Only Version: 0
Copy Mode: Modified
Copy Serialization: Shared Static
Copy Frequency: 0
Copy Destination: DISKPOOL
Table of Contents (TOC) Destination: NASTOCPOOL
Last Update by (administrator): ADMIN
Last Update Date/Time: 03-06-2009 10:16:20
Managing profile:
Changes Pending: No

If I run 'show versions STGNODE01 *' all previous versions are shown under correct management class, however a 'q nasbackup stgnode01 *' only displays 7 days?

Any ideas?
 
Well, colour me embarrassed :redface:

Thanks very much for the prompt response, I'll slink away now!
 
Back
Top