2012-03-23 03:38 AM
We have a snap vault transfer which has failed in the last 2 days, as its lag is now 2 days. If i look at the snapmirror logs, i see error message relating to this snapvault transfer :
Wed Mar 21 12:43:38 PDT filerA:/vol/log22_28/qlog22_28 filerB:/vol/xvs02_sv/qlog22_28 Request (Update)
dst Wed Mar 21 12:43:39 PDT filerA:/vol/log22_28/qlog22_28 filerB:/vol/xvs02_sv/qlog22_28 Abort (destination requested snapshot that does not exist on the source)
It does an retry but still fails. Yesterdays snapvault worked fine.
I did a snapvault status -s command on the destination, and i can see a snapshot for the volume, but when i do it for on the source system, i cannot see a snapshot for the source volume.
ANy advise on this issue.
2012-03-23 04:02 AM
I am out of the office until 25/03/2012.
I am not available from 23rd to 25th March due to Public Holiday in
Bangalore and I will be out of station . Please reach out to Steve
Lee/India/IBM, for any Solution queries in my absence. For any management
queries please reach out to Sundar Subramanian1/India/IBM.
For emergency I can be reachable on Mobile Numbers - 9900111441 /
I Apologies for any Inconvenience and Thanks in Advance for your
Note: This is an automated response to your message "[Products &
Solutions] - snapvault transfer failure" sent on 23/3/12 16:09:09.
This is the only notification you will receive while this person is away.
2012-05-29 02:25 AM
Sounds as if snapshot autodelete threw away your baseline snapshot. You should always disable snapshot autodelete on the source volumes forQSM/SnapVault.
I'm afraid there's nothing you can do if the snapshot is indeed lost on the source side. Your only option is to re-start the SnapVault from scratch
do "snap list <volname>" on the source and destination, and try to find a snapshot with the exact same name on both sides.
2012-09-14 06:17 AM
Hi, is it possible you could provide an example command on what would be required to marry the snapvault back up again? you mention finding a common snapshot between them just wondered how this would form the command once you have this information?
2014-10-28 02:24 AM
I am also seeing this error. "Destination requested snapshot that does not exist on the source"
I am seeing snaps being created both on the source and destination as per my schedules however I am still seeing the error
3 questions I have.
Any advice on this I would appreciate as its doing my nut in!
2014-10-28 02:59 AM
quick howto setup schedule with snapvault
snap sched "sourcevol" 0 0 0 <- normaly schedule deactivated
snapvault snap sched "sourcevol" SV_daily 5@22 <- sv schedule same snapshot name on destination required if the snapshot should be transfered
vol options "destinationvol" nosnap on
snapvault snap sched -x "destinationvol" SV_daily 31@22 <- "-x" option trigger a transfer from source snapshot
snapvault snap sched "destinationvol" SV_weekly 4@so@22 <- creates a snapshot on destination vol without transfering new data from source
2014-10-28 03:50 AM
Many thanks for clarifying that bit of information.
So it looks like as I want to transfer the snapshot I need to ensure the names are kept the same on both source and destination.
One additional question I have is when I delete the schedule from the destination I noticed when I go to the share path
There are still old snapshots located there. How do I remove all of these so I start with a clean slate and I only see my new schedule/s.