Greetings,
I was given a pointer that the snapshots are still on the destination. It turned out that some of the qtree relationships did not get deleted and cleaned up. After I manually deleted the snapshots that were used as part of the nightly baseline, the old relationships went away.
Thanks,
Jeff
On Fri, May 11, 2012 at 5:40 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We retired a SV primary volume and I need to keep the destination SV volume around until the snapshots age out. The backups are done via command line/cron/snapvault snap sched setups. They are not managed by DFM/PM or any other package.
I did a snapvault stop on the destination which seems to have worked fine. I verified that the destination qtree is gone. I also did a snapvault release on the primary and a snapvault snap unsched on both primary and secondary. I've even rebooted the destination filer which would have the effect of stopping and starting snapvault.
The primary shows no trace of the former relationship. The secondary got rid of everything, but some of the destinations still show up in the snapvault status output. I need to figure out how to clean these up. Here is the output of a snapvault -l of one of the destination qtrees:
Snapvault secondary is ON.
Source: source:/vol/carmel2/test Destination: destination:/vol/carmel2_i/test Status: Idle Progress: - State: Unknown Lag: - Mirror Timestamp: - Base Snapshot: - Current Transfer Type: - Current Transfer Error: - Contents: - Last Transfer Type: Update Last Transfer Size: 8 KB Last Transfer Duration: 00:00:06 Last Transfer From: source:/vol/carmel2/test
Thanks,
Jeff
Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611