Summary
A SnapVault backup fails and an error displays indicating initialize cannot be applied if destination is a mirror." To resolve this issue, use the snapvault stop command as described in the NetApp support site (BURT 115152). "
Symptoms
The failure occurs if a volume containing a SnapVaulted secondary qtree is destroyed and a new volume with the same name is created. The subsequent SnapVault to the same secondary qtree may fail with the error message:
initialize cannot be applied if destination is a mirror
SnapVault backup fails and the backup log displays the following errors. The errors display for each primary volume backed up.
SNBSVH_236J Task 4 being run as BASE because SV relationship does not exist
SNBSVH_240N Task 4 NDMP_LOG:id (0),type (NDMP_LOG_ERROR), text (initialize cannot be applied if destination is a mirror)
SNBSVH_240N Task 4 NDMP_LOG:id (0), type(), text (NDMP_SVS_NOTIFY_CREATE_RELATIONSHIP operation failed. Error (542113801, NDMP_SV_RPL_VOL_STATE) ;Rseq (14))
SNBSVH_968E Create relationship (/vol/server101/[SERVER101]SERVER101@12C0DE79AE6811DAB42A001143DAC5EF) failed with exception: 501
Resolution
For information on this issue and for the workaround, refer to the NetApp support site (BURT 115152) :
support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=115152
As the above document explains, perform a snapvault stop for each instance that is failing. Obtain the qtree name from the backup log on the "create relationship" failure lines. In the above example, this is:
SNBSVH_968E Create relationship (/vol/server101/[SERVER101]SERVER101@12C0DE79AE6811DAB42A001143DAC5EF) failed with exception: <EXCEPTION CATEGORY = "BEXEXCEPTION"> <CODE>501</CODE> </EXCEPTION>
The snapvault stop command based on this is:
Snapvault stop -f /vol/server101/[SERVER101]SERVER101@12C0DE79AE6811DAB42A001143DAC5EF
Note: While the snapvault stop command performs additional cleanup, it displays an error message as there is nothing to delete.
Snapvault configuration for the qtree has been deleted.
Could not delete qtree: destination qtree does not exist.
After you use this command, the backup runs successfully.