1. Support
  2. Knowledge base
  3. 100012439

NetBackup for Microsoft Exchange Server DAG fails with Status Code 130 when a database passive copy is missing

Article: 100012439
Last Published: 2017-12-20
Ratings: 1 1
Product(s): NetBackup & Alta Data Protection

Problem

NetBackup for Microsoft Exchange Server DAG fails with Status Code 130 when a database passive copy is missing; "GetTargetDatabaseCopyStatus" doesn't return the database in a Healthy status.

Error Message

Detail Status:
03/04/2014 10:31:37 - Info bpfis (pid=36508) Backup started 
03/04/2014 10:31:46 - Critical bpbrm (pid=4652) from client EXCHANGENODE: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit 
03/04/2014 10:31:46 - Critical bpbrm (pid=4652) from client EXCHANGENODE: FTL - 
03/04/2014 10:31:46 - Critical bpbrm (pid=4652) from client EXCHANGENODE: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit 
03/04/2014 10:31:46 - Critical bpbrm (pid=4652) from client EXCHANGENODE: FTL - 
03/04/2014 10:31:46 - Critical bpbrm (pid=4652) from client EXCHANGENODE: FTL - snapshot processing failed, status 156 
03/04/2014 10:31:46 - Critical bpbrm (pid=4652) from client EXCHANGENODE: FTL - snapshot creation failed - Error attempting to gather metadata., status 130 
03/04/2014 10:31:46 - Info bpbrm (pid=4652) DB_BACKUP_STATUS is 156 
03/04/2014 10:31:46 - Warning bpbrm (pid=4652) from client EXCHANGENODE: WRN - NEW_STREAM0 is not frozen 
03/04/2014 10:31:46 - Warning bpbrm (pid=4652) from client EXCHANGENODE: WRN - Microsoft Information Store:\DB02 is not frozen 
03/04/2014 10:31:46 - Info bpfis (pid=36508) done. status: 130 
03/04/2014 10:31:46 - Info bpfis (pid=36508) done. status: 130: system error occurred 
bpfis:
10:31:45.343 [36508.28748] <2> onlfi_vfms_logf: INF - Status FS_NO_MORE (0x2000FE07) calling DetermineHandlePassThruChangeDir path 'User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store\EXCHANGENODE\DB02' in SHADOW::ChangeDir
10:31:45.343 [36508.28748] <2> onlfi_vfms_logf: INF - INF -  v_beds::V_FindNext() EXIT Name: bRC:false LastError:0xFFFFFE07:0xa000fe07 (2684419591)
10:31:45.436 [36508.28748] <2> onlfi_vfms_logf: INF - INF -  v_beds::V_FindNext() EXIT Name: bRC:false LastError:0xFFFFFE1B:0xa000fe1b (2684419611)
10:31:45.561 [36508.28748] <2> onlfi_vfms_logf: INF - ERR - vss__add: No mounted Exchange databases were found during the enumeration of <Microsoft Information Store:\DB02>.
10:31:45.842 [36508.28748] <2> onlfi_vfms_logf: INF - [EseE14::GetTargetDatabaseCopyStatus]  machine:EXCHANGENODE  database:DB02  targetSite:null  options:0x8  flags:0  count:0
10:31:45.935 [36508.28748] <2> onlfi_vfms_logf: INF - EseE14::GetTargetDatabaseCopyStatus(OUT) ... dag:No, status:"Offline", active:"", passive:"", healthy:No, mdb:Yes, cas:, clustered:No
10:31:45.935 [36508.28748] <2> onlfi_vfms_logf: INF - [MountOrDismountStore] - Mount/Dismount = TRUE, machine = dagname, sg = DB02, db =  snaped = TRUE, GetJustDbs = FALSE, check_only = TRUE, enable_rest = FALSE, isCCRClust = FALSE, is Cluster = FALSE
10:31:45.967 [36508.28748] <2> onlfi_vfms_logf: INF - [MountOrDismountStore] - GetDatabases returned 0 databases ... you may need to kill monad.exe if there are databases in the storage group
10:31:46.591 [36508.28748] <2> onlfi_vfms_logf: INF - INF - ShadowCopy Writer Table
10:31:46.591 [36508.28748] <2> onlfi_vfms_logf: INF - Status ERROR_NO_DATA (0x000000E8) accessing Writer Metdata map in SHADOW::GenerateWriterMetadataDocumentStreams
10:31:46.591 [36508.28748] <2> onlfi_vfms_logf: INF - Status FS_WRITER_METADATA_FAILURE (0xE000FEC9) generating Writer Metadata Document stream in SHADOW::ReadVcb
10:31:46.591 [36508.28748] <2> onlfi_vfms_logf: INF - ERR - EnumerateForLocalMetaData: FS_ReadObj(1) Failed! (0xE000FEC9:A failure occurred accessing the Writer metadata.
)
10:31:46.606 [36508.28748] <2> onlfi_vfms_logf: INF - INF - EnumerateForLocalMetaData exiting.
10:31:46.606 [36508.28748] <2> onlfi_vfms_logf: INF - VSS_Writer_freeze_commit: snapshot create failed

Cause

The issue is caused by bad values returned from the Exchange Server environment via Exchange Management Shell.

get-MailboxDatabase -Identity <mailbox_db_name> | foreach -Process {$_.DatabaseCopies.Count}

Get-MailboxDatabaseCopyStatus -identity 'mailbox_db_name' -Local
 

Solution

In some cases the issue is resolved by rebooting the Exchange server(s).

Was this content helpful?

Article Languages