2011-04-11 01:08 PM
my customer is using SMSQL in an environment where they snapvault their data manually (without Prot Mgr integration), and they also use snap autodelete. Are there any easy ways to make sure that the most recent SMSQL created backup gets softlocked so that snap autodelete will not remove it when it is in "try" mode? The snapvault snap preserve command will do this, but I'm hoping to avoid writing a script to preserve/unpreserve SMSQL backups after each one is taken. Thanks!
2011-04-12 01:33 PM
This is a tough problem in the sense that ontap dos not care what it deletes and the auto grow function has its own challenges. I think you are stuck with a run after script here. It is a simple enough script however I see your point being that this may require some form of manual intervention in the cases of a failure.