Views:

Summary



Snapvault backup if failing with errors in the job log relating to 'destination temporarily quiesced'.

Symptoms



The job log reports:

10.112.95.130 6/4/2007 9:37:01am SNBSVH_240N Task 4 NDMP_LOG: id(0), type(NDMP_LOG_ERROR), text(destination is temporarily quiesced)

10.112.95.130 6/4/2007 9:37:01am SNBSVH_240N Task 4 NDMP_LOG: id(0), type(), text(NDMP_SVS_NOTIFY_TRANSFER_BACKUP operation failed. Error(542113797, NDMP_SV_RPL_PRE_XFER); Rseq(0))

 



Resolution



Issues like this have been observed when a snapvault transaction attempts to rollback. Usually this is a temporary condition, however a filer may experience extended (or permanent) quiesced qtrees when a snapvault transaction rolls back and a low resource condition (out of memory and out of space) occurs.

The first thing to check is if you are experiencing any "out of resource" conditions. Check the Filer's syslog for any volumes experiencing trouble writing snapshots, check for any messages in the DPX job log and the Filer's syslog for any reference to low/out of memory errors, and also check that your aggregates are not filled up. If you have any low resource conditions pending, please clean these up first before trying to troubleshoot the quiesced volume error.

The following are suggested guidelines only -- If these don't help, then it will be necessary to call your Network Appliance technical support representative to explain the cause and possible fixes for your quiesced volume.

To troubleshoot the quiesced volume error:

  • Try to place the affected volume "offline", wait a few minutes, bring it back "online", and then re-try the backup. The idea here is to force Ontap to clean up all pending transactions for this volume, and then bring it back online.
     
  • Removing the affected volume and re-creating it will eliminate the problem; however in this case, you will need to force a new OSSV base backup of all hosts sending data into this volume (see Recommendations for Performing New BEX Advanced Recovery Base Backup Jobs for additional help).
     
  • You can also try deleting the affected qtrees, however this will also require running a new base Block backup of affected hosts.
     
  • Rebooting the Filer can also clear up this condition. This may be necessary if you are experiencing out of memory errors and you cannot find out or explain why.

Note that deleting snapshots within the volume does not directly help alleviate this quiesced condition. However, deleting snapshots from the volume is one way to clear up space if the root cause was a low disk condition.