NetBackup status code: 1542

[peprice216]

I have a problem with backing up my exchange server which keeps giving me this error, ( An existing snapshot is no longer valid and cannot be mounted for subsequent operations (1542). it has been running fine all of a sudden started giving me this error code.

I have tried deleting the snapshot and creating a new policy for this exchange snapshot but still no success keeps giving me the same error code (1542)

CMDS used to remove snapshot but I never see anything there any how.

1.  This command displays any active snapshots created by bpfis.
    <install_path>\NetBackup\bin\bpfis query
2.  This command will delete the snapshots
    <install_path>\NetBackup\bin\bpfis delete -id snapshot_id
3.  Check VSS writers status using vssadmin list writers

Can anyone help please.

[Marianne]

Please share all relevant info:

NBU version on Exchange server (or servers in case of a DAG)

Windows version on Exchange server(s)

Exchange version

Output of 'vssadmin list writers' on Exchange server(s)

[peprice216]

Exchange 2010 DAG snapshot vss 

10/03/2017 09:48:03 - Info nbjm(pid=7340) starting backup job (jobid=396988) for client xxx231xxx, policy Exchange_Snapshot, schedule Fri_Exch_Backup
10/03/2017 09:48:03 - Info nbjm(pid=7340) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=396988, request id:{)
10/03/2017 09:48:03 - requesting resource backupmachine-hcart2-robot-tld-0
10/03/2017 09:48:03 - requesting resource backupmachinie.nbu.NBU_CLIENT.MAXJOBS.clientmachine
10/03/2017 09:48:03 - requesting resource backupmachine.nbu.NBU_POLICY.MAXJOBS_Exchange_Snapshot
10/03/2017 09:48:06 - granted resource backupmachine.nbu.NBU_CLIENT.MAXJOBS.clientserver
10/03/2017 09:48:06 - granted resource backupmachine.nbu.NBU_POLICY.MAXJOBS._Exchange_Snapshot
10/03/2017 09:48:06 - granted resource O0932
10/03/2017 09:48:06 - granted resource HP.ULTRIUM5-SCSI.007
10/03/2017 09:48:06 - granted resource backupmachine-hcart2-robot-tld-0
10/03/2017 09:48:06 - estimated 0 Kbytes needed
10/03/2017 09:48:06 - begin Parent Job
10/03/2017 09:48:06 - begin Snapshot, Start Notify Script
10/03/2017 09:48:06 - Info RUNCMD(pid=1076) started
10/03/2017 09:48:06 - Info RUNCMD(pid=1076) exiting with status: 0
Status 0
10/03/2017 09:48:06 - end Snapshot, Start Notify Script; elapsed time: 00:00:00
10/03/2017 09:48:06 - begin Snapshot, Step By Condition
Status 0
10/03/2017 09:48:06 - end Snapshot, Step By Condition; elapsed time: 00:00:00
10/03/2017 09:48:06 - begin Snapshot, Stream Discovery
Status 0
10/03/2017 09:48:06 - end Snapshot, Stream Discovery; elapsed time: 00:00:00
10/03/2017 09:48:06 - begin Snapshot, Read File List
Status 0
10/03/2017 09:48:06 - end Snapshot, Read File List; elapsed time: 00:00:00
10/03/2017 09:48:06 - begin Snapshot, Create Snapshot
10/03/2017 09:48:06 - started
10/03/2017 09:48:07 - started process bpbrm (10764)
10/03/2017 09:48:16 - Info bpbrm(pid=10764) backupclient4 is the host to backup data from
10/03/2017 09:48:16 - Info bpbrm(pid=10764) reading file list from client
10/03/2017 09:48:16 - Info bpbrm(pid=10764) start bpfis on client
10/03/2017 09:48:16 - Info bpbrm(pid=10764) Starting create snapshot processing
10/03/2017 09:48:20 - Info bpfis(pid=8664) Backup started
10/03/2017 09:48:22 - Critical bpbrm(pid=10764) from client ClientMachine: FTL - snapshot preparation failed - Unable to determine Exchange version., status 72
10/03/2017 09:48:22 - Warning bpbrm(pid=10764) from client ClientMachine: WRN - NEW_STREAM0 is not frozen
10/03/2017 09:48:22 - Warning bpbrm(pid=10764) from client ClientMachine: WRN - Microsoft Information Store:\ is not frozen
10/03/2017 09:48:22 - Info bpfis(pid=8664) done. status: 72
10/03/2017 09:48:22 - end Snapshot, Create Snapshot; elapsed time: 00:00:16
10/03/2017 09:48:22 - Info bpfis(pid=0) done. status: 72: the client type is incorrect in the configuration database
10/03/2017 09:48:22 - end writing
Status 72
10/03/2017 09:48:22 - end Parent Job; elapsed time: 00:00:16
10/03/2017 09:48:22 - begin Snapshot, Stop On Error
Status 0
10/03/2017 09:48:22 - end Snapshot, Stop On Error; elapsed time: 00:00:00
10/03/2017 09:48:22 - begin Snapshot, Delete Snapshot
10/03/2017 09:48:22 - started process bpbrm (12704)
10/03/2017 09:48:30 - Info bpbrm(pid=12704) Starting delete snapshot processing
10/03/2017 09:48:35 - Info bpfis(pid=19584) Backup started
10/03/2017 09:48:35 - Critical bpbrm(pid=12704) from client ClientMachine: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.ClientMachine_1489139286.1.0
10/03/2017 09:48:36 - Info bpfis(pid=19584) done. status: 1542
10/03/2017 09:48:36 - end Snapshot, Delete Snapshot; elapsed time: 00:00:14
10/03/2017 09:48:36 - Info bpfis(pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations
10/03/2017 09:48:36 - end writing
Status 1542
10/03/2017 09:48:36 - end Parent Job; elapsed time: 00:00:30
10/03/2017 09:48:36 - begin Snapshot, End Notify Script
10/03/2017 09:48:36 - Info RUNCMD(pid=3188) started
10/03/2017 09:48:37 - Info RUNCMD(pid=3188) exiting with status: 0
Status 0
10/03/2017 09:48:37 - end Snapshot, End Notify Script; elapsed time: 00:00:01
Status 1542
10/03/2017 09:48:37 - end operation
An existing snapshot is no longer valid and cannot be mounted for subsequent operations(1542)

[GeForce123]

I know this usually isn't an 'answer' and sometimes it's not allowed depending on your environment but have you tried to reboot the server? I've seen this issue be resolved after a reboot.

[Lowell_Palecek]

You didn't answer the NetBackup version, but that's probably not your problem.

When you get an error, look at the first error, not the last one.

When you bpbrm reports an error from the client, look at the client log, in this case bpfis:

10/03/2017 09:48:22 - Critical bpbrm(pid=10764) from client ClientMachine: FTL - snapshot preparation failed - Unable to determine Exchange version., status 72

This is really fundamental. Something is wrong in your Exchange access on the client. What changed - firewall, host credentials for the client, etc.?

Besides a bpfis log, a related log that may give a clue is from a BEDS component called monad. That's what executes Exchange PowerShell. (I'm not sure the problem is in PowerShell - the bpfis log will help determine whether we need to look there.) We have a TechNote on how to download Microsoft's DebugView to capture the monad log.

[Lowell_Palecek]

There are two bpfis processes executed on every VSS backup, one to create the snapshot and communicate with the VSS API, and the other to clean up after the backup is done. This comes from the 'bpfis delete' process:

10/03/2017 09:48:35 - Critical bpbrm(pid=12704) from client ClientMachine: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.ClientMachine_1489139286.1.0

We call this the 'state file' for the snapshot. The bpfis create process creates it. Every other bpfis process uses it to get oriented. The bpfis delete process can't find the file because the create process failed before creating it.

[Marianne]

You say that Exchange is 'Exchange 2010 DAG '?

But your Backup Selection seems to be Microsoft Information Store:\ ?
Which is for Standalone Exch?

Has anyone changed the Backup Selection in the policy?
Or have Exch Admins made changes to Exchange?

[Lowell_Palecek]

I don't think the following indicates what the top-level backup selection had been. Even with a DAG, "Microsoft Information Store" appears withing the hierarchy.

10/03/2017 09:48:22 - Warning bpbrm(pid=10764) from client ClientMachine: WRN - Microsoft Information Store:\ is not frozen

The error 72 just above this line is serious. Why can't NetBackup determine the Exchange version? Perhaps it can't find Exchange at all on the system.

A verbose bpfis log will show the input file list, and it will also show details of the Exchange environment that it can see. It will also answer the as-yet unanswered question, what level of NetBackup, although NetBackup has supported Exchange 2010 since version 7.0.