Greetings,
I posted a couple of weeks ago about snapvault relationships not going away. It turned out the snapvault stop had not cleaned up all the associated snapshots on the destination used for qtrees.
Since that time I have had a similar problem on multiple filers. The problem seems to be that snapvault stop doesn't actually do anything in 8.1. I upgraded one of the filers from 8.0.1P1 to 8.1 GA. I was able to get the SV stop to work at 8.0.1, but it hasn't worked once since I've upgraded. One of my other filers is doing the same thing.
Ultimately after multiple SV stop attempts (at least 5), rebooting the filer, then doing more multiple SV stops, I was able to get some of them to lose the SV lock. I've got a call open for this but haven't received any useful information from it. This is an example of the error message I get.
isolation> snap delete former_mofab isolation(0118075592)_former_mofab_root-dst.0 Snapshot isolation(0118075592)_former_mofab_root-dst.0 is busy because of LUN clone, snapmirror, sync mirror, volume clone, snap restore, dump, CIFS share, volume copy, ndmp, WORM volume, SIS Clone
The snapvault stop was the first thing run. Nothing else was done until after it completed. Everything else is cleaned up. The schedules, relationships, etc. A snapvault status doesn't show a source because that has already been cleaned up. The volumes are not part of a mirror and this snapshot is the only special snapshot in the volume. I've also taken the volume offline and brought it back online but that doesn't help either.
Is there some magic recipe at 8.1 to make SV stop work? I can't keep rebooting filers and spending 30 minutes per volume doing multiple stops and snap delete attempts.
Thanks,
Jeff
Greetings,
I think I may have found a way through this.
A point of quick clarification though. When I said SV stop wasn't working, it was deleting the qtree data, it just wasn't removing the SV snapshot and releasing the relationship. A snapvault status still showed it as a snapvault relationship and it showed up on my out of date backup reports.
I have found that if I get a system console from the RLM, and run a snapvault stop -f as the advanced user, this seems to work. It did not work as a regular user from the system console or via a ssh command including a "priv set advanced ; snapvault stop -f xxxxx". I've used this syntax on other things previously and it has worked.
Jeff
On Wed, May 30, 2012 at 1:01 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
I posted a couple of weeks ago about snapvault relationships not going away. It turned out the snapvault stop had not cleaned up all the associated snapshots on the destination used for qtrees.
Since that time I have had a similar problem on multiple filers. The problem seems to be that snapvault stop doesn't actually do anything in 8.1. I upgraded one of the filers from 8.0.1P1 to 8.1 GA. I was able to get the SV stop to work at 8.0.1, but it hasn't worked once since I've upgraded. One of my other filers is doing the same thing.
Ultimately after multiple SV stop attempts (at least 5), rebooting the filer, then doing more multiple SV stops, I was able to get some of them to lose the SV lock. I've got a call open for this but haven't received any useful information from it. This is an example of the error message I get.
isolation> snap delete former_mofab isolation(0118075592)_former_mofab_root-dst.0 Snapshot isolation(0118075592)_former_mofab_root-dst.0 is busy because of LUN clone, snapmirror, sync mirror, volume clone, snap restore, dump, CIFS share, volume copy, ndmp, WORM volume, SIS Clone
The snapvault stop was the first thing run. Nothing else was done until after it completed. Everything else is cleaned up. The schedules, relationships, etc. A snapvault status doesn't show a source because that has already been cleaned up. The volumes are not part of a mirror and this snapshot is the only special snapshot in the volume. I've also taken the volume offline and brought it back online but that doesn't help either.
Is there some magic recipe at 8.1 to make SV stop work? I can't keep rebooting filers and spending 30 minutes per volume doing multiple stops and snap delete attempts.
Thanks,
Jeff
Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
-
Jeff Cleverley