Is there a recommended process for handling more than 250+ snapshots in Protection Manager? Specifically transitioning a Protection Manager Dataset to a new volume for SnapManager for Exchange/SQL SnapVaults? I understand this would be a manual process.
In this environment the requirement is to maintain a year worth of snapshots - although I have recommended 6 months of Daily, 6 months of Weekly, etc..(Max of 250).
Therefore I need to develop a process for gracefully transitioning to a new volume. In my testing I've found that if I remove the destination SV volume, and then 'Conform' the dataset, it will create a new volume from the resource pool and continue the SV relationship. I then have to issue a 'dfbm primary dir relinquish <ID>' to stop OnCommand/PM errors about unable to remove SnapVault relationship.
At this point, I've noticed that I still retain the ability to restore from the previous volume through the restore button in OnCommand/PM.
Do I need to also remove the relationship from PM via 'dfpm dataset relinquish <ID>'? Would that prevent the previous snapshots from being seen during a restore operation?
SME/SMSQL => Created OnCommand/PM dataset
PRI_FILER1 => SEC_FILER1
SME jobs create local snapshots (7 days)
SME causes OnCommand/PM SnapVault update.
Once backup volume reaches 250 snapshots, the relationship needs to be moved to a new volume while retaining the ability to restore from the old backup volume.
(?) Remove Destination Volume from Dataset
(?) Release Volume with 'dfbm primary dir relinquish <ID>'
(?) Conform Dataset to SnapVault to new Volume
(?) Continue process until total of 3 volumes, 1 active SV. Remove oldest Volume once snapshots in 2 recent volumes totals 356 days.
(?) Break SV relationship between PRI and old SV volume (?) - Would this affect restore in PM?
462 moreThan255 Back up 468 snapvaulted idle 0.1 mpo-vsim13:/noVolLang/two mpo-vsim14:/noVolLang/two
462 moreThan255 Back up 470 snapvaulted idle 0.1 mpo-vsim13:/noVolLang/one mpo-vsim14:/noVolLang/one
462 moreThan255 Back up 472 snapvaulted idle 0.1 mpo-vsim13:/noVolLang/- mpo-sim14:/noVolLang/moreThan255_mposim13_noVolLang
Now the steps to get new secondary volume created:
Relinquish the relationships using dfpm dataset relinquish cli so that PM stops scheduling the relationships anymore
Remove the secondary volume usings dfpm dataset remove cli, this way the old secondary volume where we reached 250 snapshot is removed and a new secondary volume is created with re-baseline from primary.
This way you still have the relationship between your primary and old secondary( though this is not a requirement for PM to restore, also PM will no more update this relationship).
dfbm primary dir relinquish removes the entry from the database, but the next snapvault monitoring cycle will rediscover it again. Whereas dfpm dataset relinquish will make the dataset to relinquish its control over it like
scheduling the same
doing conformance check on the same
Using dfbm will lead to dataset showing redundant relationship error.
dfpm dataset remove, removes the secondary volume from the dataset. Then conformance kicks in and finds that there is a primary and no secondary but as per the protection policy this needs one. So it goes head and provisions and new secondary volume and does the re-baseline from primary.
Is there a NetApp Management Console GUI process for when the user removes a destination volume from the dataset?
What I've found is that removing the destination volume in the NMC PM GUI (Backup - SnapVault), causes the conform process to create a new volume.
However the customer still sees an error logged about "SnapVault Relationship Delete Failed" - some because of too many snapshots, and some because of PATH error. To stop those from reoccuring, I've had to use the dfbm primary dir relinquish command to remove the relationship. The relationship disappears from the dfpm command.
In 2 years, the customer logged 300,000 error events for "SnapVault Relationship Delete Failed"!
Re: OnCommand Protection Manager SV solution for more than 250 snapshots