NetBackup for Microsoft Exchange Server backup fails with status 130 on an Exchange Server 2013 client

NetBackup for Microsoft Exchange Server backup fails with status 130 on an Exchange Server 2013 client

Article: 100010573
Last Published: 2020-03-23
Ratings: 11 7
Product(s): NetBackup

Problem

NetBackup for Microsoft Exchange Server backup fails with status 130 on an Exchange 2013 or higher client.
 

Error Message

Consult the bpfis log for evidence of the following:

10:53:13.725 [2908.6024] <2> onlfi_vfms_logf: INF - INF - GetExtendedDatabaseStatus returned 80004003 -> 0
10:53:13.725 [2908.6024] <2> onlfi_vfms_logf: INF - INF - [EseE14::CreateExcludes]   ### GetExtendedDatabaseStatus("my_exchange_host") failed ... 0x80004003.

10:53:14.490 [2908.6024] <2> onlfi_vfms_logf: INF - [EseE14::GetTargetDatabaseCopyStatus]  machine:my_exchange_host  database:my_exchange_database  targetSite:null  options:0x8  flags:0  count:0
10:53:14.958 [2908.6024] <2> onlfi_vfms_logf: INF - GetTargetDatabaseCopyStatus returned 80004003
10:53:14.958 [2908.6024] <2> onlfi_vfms_logf: INF - Error (0x80004003) !!! EseE14::GetTargetDatabaseCopyStatus("my_exchange_host ", "my_exchange_database ") failed
10:53:14.958 [2908.6024] <2> onlfi_vfms_logf: INF - [ESE_AttachToDLE]  Fail to get database copy information. Abort the backup (0xe000038d) !!!!!

10:53:14.973 [2908.6024] <2> onlfi_vfms_logf: INF - Extended status = 130:1:Error attempting to find volumes to snap.
10:53:14.973 [2908.6024] <16> bpfis main: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130
 

Cause

This problem can arise if the following file has been modified, deleted, or renamed:

\Program Files\Veritas\NetBackup\bin\monad.exe.config

 

Solution

To recover the file, perform one of the following:

  • Attempt a repair installation of the client software
  • Uninstall and reinstall the client software
  • Copy the file from another NetBackup Exchange client of the same version.  This can be done safely, as the information in the file is not host specific.
  • If the file has been renamed, rename it back to monad.exe.config, and make it "Read Only"

 

Was this content helpful?