NetBackup Exchange 2013 snapshots will fail, reporting status code 130, if any database is dismounted.

  • Article ID:100010172
  • Modified Date:
  • Product(s):


Exchange 2013 snapshot will fail with status 130 (system error occured) reported if any of the databases are dismounted.


In Exchange 2013, the Microsoft Exchange writer's metadata XML includes the dismounted database along with other databases.  When Netbackup enumerates this metadata XML file to find out the volumes to snap, the volumes of the dismounted database are added to the snapshot set.  This will cause the Microsoft Exchange VSS writer to go into Retryable state and the snapshot will fail with error code 130 reported.


Veritas Corporation has acknowledged that the above-mentioned issue (Etrack 3277388) is present in the current version(s) of the product(s) mentioned in this article. Veritas Corporation is committed to product quality and satisfied customers.  This issue was tentatively scheduled to be addressed in the following release:

  • NetBackup 7.5 Maintenance Release 7 (

When NetBackup is released, please access the following link for download and readme information:

Please note that Veritas Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Veritas's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Make sure all the databases are mounted prior to running the backup.

Reference: Please check the Microsoft article below in the section What does it mean when I receive a VSS_E_WRITERERROR_RETRYABLE error message during a BackupPrepare event?

Alternately, the dismounted database can be added to the exclude list, or specify the databases to be backed up individually in the backup selection list.

If none of these workarounds are unfeasible, please contact Veritas technical support, referencing this document ID and Etrack 3277388 to obtain a fix for this issue.

Applies To

Issue is seen in Exchange 2013 standalone as well as DAG.

This issue was originally reported on Netbackup, which was the first version to support Exchange 2013.

Was this content helpful?

Get Support