I have seen this go wrong. It will allow you to select different management classes for the DIFF than the FULL, however the FULL's will rebind making this pointless. So if you backed up the FULL with mgmt class "01YEAR" and the DIFF with management class "35DAY", the FULL will rebind to "35DAY" as well. I've seen a lot of FULL backups get lost like this.
You need to keep a separate Full/Diff series for each retention that you want. . I do this by creating a virtualfs called "Filesystem_01YEAR" and point that to the same file system. Let me know if you want more detail. Regards, Shawn ________________________________________________ Shawn Drew Internet [email protected] Sent by: [email protected] 05/04/2011 05:21 PM Please respond to [email protected] To ADSM-L cc Subject Re: [ADSM-L] Re: Policy for NDMP dumps Gee, Norman wrote: > > You can assign a different management class to full and differentials. > I have defined them to different tape storage pools. That would work for storing the different NDMP images in different storage pools. But my experience matches Remco's: each "backup node" command that specifies a different management class will rebind all backups (full or differential) for that node/filespace, including adjusting the retention. I finally gave up trying to use longer retention for full NDMP images (e.g., a year) and shorter retention for differential images (e.g., four weeks). Though I never tried Remco's suggestion of sending the differentials to a different node name with different policy. I have nothing good to say about NDMP. It had its place 15 or 20 years ago, but not today. I'm really hoping I'll be able to replace NDMP for our NetApp backups with SnapDiff-based backups. That should save time and space, should generally perform better, and of particular interest to me, should get rid of long-running single-object transactions that pin the recovery log for insane lengths of time (inevitably filling the recovery log to 90+% and eventually auto-canceling the NDMP job just before if finally completes, wasting 20+ hours of time and terabytes of bandwidth plus sometimes dozens of tapes for TSM DB backups). (Unfortunately for Wanda, SnapDiff is NetApp/N-series only, so it won't help her Celerra backup situation.) -- Hello World. David Bronder - Systems Admin Segmentation Fault ITS-EI, Univ. of Iowa Core dumped, disk trashed, quota filled, soda warm. [email protected] This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
