Summary
A DPX Block backup fails because the qtrees on the backup destination are in a quiescing state. The NetApp qtrees never return to an idle state after many hours or days. The NetApp storage system attempts to resolve itself and pull from a snapshot to perform the rollback. If it is not able to resolve itself and access the associated snapshot, the following error displays: Cannot connect to source filer.
Symptoms
- When performing snapvault status on the NetApp storage system, the qtrees are in a quiescing state
Source Destination State Lag Status
X.X.X.232:APPS-CV.EXCH_GROUP.1349146800 netapp1:/vol/SS_EXCH_BU/[EXCH_GROUP]EX-DAG@APPS_ Snapvaulted 252:10:17 Quiescing
- On the NetApp secondary backup destination, check the SnapMirror.log file to see if the following error is present: Cannot connect to source filer.
dst Sun Oct 7 00:33:14 EDT EX4:{C612B547}.EXCH_GROUP.1348455600 netapp1:/vol/SS_EXCH_BU/[EXCH_GROUP]EX4@{C612B547} Rollback_start
dst Sun Oct 7 00:33:16 EDT EX4:{FEFCC452}.EXCH_GROUP.1348455600 netapp1:/vol/SS_EXCH_BU/[EXCH_GROUP]EX4@{FEFCC452} Rollback_start
dst Sun Oct 7 00:33:18 EDT EX1:{A8CF117F}.EXCH_GROUP.1348369200 netapp1:/vol/SS_EXCH_BU/[EXCH_GROUP]EX1@{A8CF117F} Rollback_failed (cannot connect to source filer)
dst Sun Oct 7 00:33:21 EDT EX2:{28E1D612}.EXCH_GROUP.1348455600 netapp1:/vol/SS_EXCH_BU/[EXCH_GROUP]EX2@{28E1D612} Rollback_failed (cannot connect to source filer)
Resolution
Connect to the NetApp secondary destination and attempt to ping itself through FQDN and short name for all interfaces. If it is resolving to the wrong IP or the system is not alive, check the DNS servers configured for the NetApp storage system or the /etc/host file.