2012-01-08 07:57 AM
folks. I need to remove a snapvault relations ship. Key here is that there is no relationship and was a typo when setting up the snapsched. no qtree exists for this relation ship and I wish to remove it
Thi smessage is taken from the log output of sv-smvi as it would return a error code 21 as it would led me to beleive is due to the fact the line below does not exists as a relation ship but is a pain in the side some place where I need to remove it as mentioned was fat fingered when inititally configuring.
SnapVault relationship found (additional) (primary = uschisan01:/vol/DS_DT_101/, secondary = uschivsan01:/vol/dt_backup_sv/DS_DT_102_q)
Output of snapvault status:
uschivsan01> snapvault status
Snapvault is ON.
Source Destination State Lag Status
uschisan01:/vol/DS_DT_101/ uschivsan01:/vol/dt_backup_sv/DS_DT_101_q Snapvaulted 37:44:46 Idle
uschisan02:/vol/DS_DT_201/ uschivsan01:/vol/dt_backup_sv/DS_DT_201_q Snapvaulted 36:15:31 Idle
Also from the system manager you can see from attached screen shot that the qtree does not exist -
Is it in the schedule do I need to destroy the schedule and re create it? How do I remove it?
Also when i run the snapvault destination command on each filer it does not show either.
2012-01-09 01:44 AM
Can you try stopping the incorrect snapvault entry on the snapvault destination filer?
snapvault stop /vol/dt_backup_sv/DS_DT_102_q
This should remove any registry information left behind.
2012-01-09 09:54 PM
can you jump into the cli of your destination filer and type qtree show. Does the destination qtree exist ? double check that the qtree does not exist
Then check on your volume uschivsan01:/vol/dt_backup_sv for the snapvault snapshot, if it still exists delete the snapshot and then the relationship should disappear ?
2012-07-26 07:13 AM
I would try to recreate the missing qtree and then do a snapvault stop, so it can delete the destination qtree and remove the snapvault relationship from the registry.