NDMP backups and versioning

[Xeroid]

Hi all,

I seem to have a problem with the backup of our IBM SAN.
We do a full backup in the weekend and the other days a differential.
The full backup is bound to an other mgmtclass via this command:
"backup node node_name volume_name mg=nas_mgmt_2v mode=full"
The diff uses this command:
"backup node node_name volume_name mode=diff"

The default mgmtclass(as used by diff) is nas_mgmt_15v: vere = 15; verd=1; keep all on No Limit
nas_mgmt_2v: vere = 2; verd=1; keep all on No Limit

I have implemented this 3 weeks ago and would expect to have +- 17 different nas objects, however I only got 5 when I do "q occ" of the nas node. And I got 4 entries when I do "q nasbackup ... begind=-20".

Does anyone know what I am missing here?
The TSM server does see those backups of diff and full as different versions or as different files?
I use tsm server 6.1.

Thanks a lot!

 

[TonyB]

hmm...it does look reasonable - however I use rete and reto instead of vere and verd...

Here's some output from my environment, which admittedly doesn't use diffs:

TYPE     CLASS_NAME                        VEREXISTS   VERDELETED   RETEXTRA   RETONLY   SERIALIZATION   DESTINATION                     
-------  --------------------------------  ----------  -----------  ---------  --------  --------------  --------------------------------
Backup   AD_BACKUPS                        NOLIMIT     NOLIMIT      60         60        SHRSTATIC       IMAGES                          


tsm>select ll_name, state, class_name, count(ll_name) from backups where node_name='XXX' group by ll_name, state, class_name

   LL_NAME: IMAGE
     STATE: ACTIVE_VERSION
CLASS_NAME: AD_BACKUPS
Unnamed[4]: 1

   LL_NAME: IMAGE
     STATE: INACTIVE_VERSION
CLASS_NAME: AD_BACKUPS
Unnamed[4]: 60

   LL_NAME: TOC
     STATE: ACTIVE_VERSION
CLASS_NAME: AD_BACKUPS
Unnamed[4]: 61

 

[Xeroid]

Thanks for your reply!

Think I found something interesting on the IBM page:

"Full and incremental NDMP filespace backups fall under the same management
class, and cannot be backed up using separate management classes."

Also it seems that IF a full backup is expired, which has still some dependent diff backups that are not expired, TSM is keeping it until also those diffs are expired.

Very important in my case and this means I can go back to my previous setup.