NetBackup Exchange status code 1542

Exchange 2007 CCR, NetBackup 7.5 policy is configured to backup from the passive node.

Backups for the cluster fail with code 1542:

An existing snapshot is no longer valid and cannot be mounted for subsequent operations(1542)

The detailed status shows something like:

29/10/2013 08:11:19 - Info nbjm(pid=4464) starting backup job (jobid=1731878) for client exch-cluster, policy EXCH_CLUSTER_SG5, schedule Daily_Full  
29/10/2013 08:11:19 - Info nbjm(pid=4464) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1731878, request id:{CB0B27C8-A3AF-4176-B14A-2E76AC254B65})  
29/10/2013 08:11:19 - requesting resource Adv_Disk_Group
29/10/2013 08:11:19 - requesting resource bgen-uwe10.NBU_CLIENT.MAXJOBS.exch-cluster
29/10/2013 08:11:19 - requesting resource bgen-uwe10.NBU_POLICY.MAXJOBS.EXCH-CLUSTER_SG5
29/10/2013 08:11:19 - granted resource bgen-uwe10.NBU_CLIENT.MAXJOBS.exch-cluster
29/10/2013 08:11:19 - granted resource bgen-uwe10.NBU_POLICY.MAXJOBS.EXCH-CLUSTER_SG5
29/10/2013 08:11:19 - granted resource MediaID=@aaaai;DiskVolume=D:\;DiskPool=nbu2_adv_d;Path=D:\;StorageServer=nbu2;MediaServer=nbu2
29/10/2013 08:11:19 - granted resource nbu2_adv_d
29/10/2013 08:11:19 - estimated 1175018 Kbytes needed
29/10/2013 08:11:19 - begin Parent Job
29/10/2013 08:11:19 - begin Snapshot, Start Notify Script
29/10/2013 08:11:19 - Info RUNCMD(pid=9740) started            
29/10/2013 08:11:19 - Info RUNCMD(pid=9740) exiting with status: 0         
Status 0
29/10/2013 08:11:19 - end Snapshot, Start Notify Script; elapsed time: 00:00:00
29/10/2013 08:11:19 - begin Snapshot, Step By Condition
Status 0
29/10/2013 08:11:19 - end Snapshot, Step By Condition; elapsed time: 00:00:00
29/10/2013 08:11:19 - begin Snapshot, Read File List
Status 0
29/10/2013 08:11:19 - end Snapshot, Read File List; elapsed time: 00:00:00
29/10/2013 08:11:19 - begin Snapshot, Create Snapshot
29/10/2013 08:11:19 - started
29/10/2013 08:11:21 - started process bpbrm (3352)
29/10/2013 08:11:30 - Info bpbrm(pid=3352) exch-cluster is the host to backup data from     
29/10/2013 08:11:30 - Info bpbrm(pid=3352) reading file list from client        
29/10/2013 08:11:30 - Info bpbrm(pid=3352) start bpfis on client         
29/10/2013 08:11:30 - Info bpbrm(pid=3352) Starting create snapshot processing         
29/10/2013 08:11:32 - Info bpfis(pid=9564) Backup started           
29/10/2013 08:11:48 - Info bpbrm(pid=3352) from client exch-nodeb: TRV - Redirecting snapshot backup to server (exch-nodeb)  
29/10/2013 08:11:48 - Info bpbrm(pid=3352) Read redirected snapshot host egen-mbx2b from client egen-mbx02INF - BACKUP_HOST=exch-nodeb   
29/10/2013 08:11:49 - Info bpfis(pid=9564) done. status: 0          
29/10/2013 08:11:49 - end Snapshot, Create Snapshot; elapsed time: 00:00:30
29/10/2013 08:11:50 - Info bpbrm(pid=3352) Starting delete snapshot processing         
29/10/2013 08:11:50 - Info bpfis(pid=9564) Deleting Snapshot exch-nodeb_1383034279 for client exch-nodeb       
29/10/2013 08:11:53 - Info bpfis(pid=4336) Backup started           
29/10/2013 08:11:53 - Critical bpbrm(pid=3352) from client exch-nodeb: FTL - cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.egen-mbx02_1383034279.1.0    
29/10/2013 08:11:54 - Info bpfis(pid=4336) done. status: 1542          
29/10/2013 08:11:54 - end Parent Job; elapsed time: 00:00:35
29/10/2013 08:11:54 - Info bpbrm(pid=3352) start bpfis on client         
29/10/2013 08:11:54 - Info bpbrm(pid=3352) Starting create snapshot processing         
29/10/2013 08:11:56 - Info bpfis(pid=7460) Backup started           
29/10/2013 08:12:07 - Critical bpbrm(pid=3352) from client exch-nodeb: FTL - snapshot processing failed, status 156   
29/10/2013 08:12:07 - Critical bpbrm(pid=3352) from client exch-nodeb: FTL - snapshot creation failed - SNAPSHOT_NOTIFICATION::SnapshotPrepare failed., status 130
29/10/2013 08:12:07 - end writing
Status 130
29/10/2013 08:12:07 - end operation
29/10/2013 08:12:07 - begin Snapshot, Stop On Error
Status 0
29/10/2013 08:12:07 - end Snapshot, Stop On Error; elapsed time: 00:00:00
29/10/2013 08:12:07 - begin Snapshot, Delete Snapshot
29/10/2013 08:12:08 - Warning bpbrm(pid=3352) from client exch-nodeb: WRN - NEW_STREAM0 is not frozen    
29/10/2013 08:12:08 - Warning bpbrm(pid=3352) from client exch-nodeb: WRN - Microsoft Information Store:\SG5 - PF (C2) is not frozen
29/10/2013 08:12:08 - Info bpfis(pid=7460) done. status: 130          
29/10/2013 08:12:08 - end Snapshot, Delete Snapshot; elapsed time: 00:00:01
29/10/2013 08:12:08 - Info bpfis(pid=0) done. status: 130: system error occurred       
29/10/2013 08:12:09 - started process bpbrm (6604)
29/10/2013 08:12:15 - Info bpbrm(pid=6604) Starting delete snapshot processing         
29/10/2013 08:12:15 - Info bpfis(pid=0) Snapshot will not be deleted        
29/10/2013 08:12:17 - Info bpfis(pid=8916) Backup started           
29/10/2013 08:12:17 - Critical bpbrm(pid=6604) from client exch-nodeb: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.egen-mbx02_1383034279.1.0      
29/10/2013 08:12:18 - Info bpfis(pid=8916) done. status: 1542          
29/10/2013 08:12:18 - end operation
29/10/2013 08:12:18 - Info bpfis(pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations
29/10/2013 08:12:18 - end writing
Status 1542
29/10/2013 08:12:18 - end operation
29/10/2013 08:12:18 - begin Snapshot, End Notify Script
29/10/2013 08:12:18 - Info RUNCMD(pid=7804) started            
29/10/2013 08:12:18 - Info RUNCMD(pid=7804) exiting with status: 0         
Status 0
29/10/2013 08:12:18 - end Snapshot, End Notify Script; elapsed time: 00:00:00
Status 1542
29/10/2013 08:12:18 - end operation
An existing snapshot is no longer valid and cannot be mounted for subsequent operations(1542)

Check the VSS writer status on the passive node using the command:

vssadmin list writer

It should say “Stable” and “No error” but if it looks like this:

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {b5fc018e-3ae9-4e87-8637-766ed6dde1bb}
   State: [9] Failed
   Last error: Not responding

then there’s your problem.

You should also find the following error in the Application event log:

Log Name:      Application
Source:        VSS
Date:          29/10/2013 08:12:07
Event ID:      12301
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      exch-nodeb.rcmtech.co.uk
Description:
Volume Shadow Copy Service error: Writer Microsoft Exchange Writer did not respond to a GatherWriterStatus call. 

Operation:
   Gather writers' status
   Executing Asynchronous Operation

Context:
   Current State: GatherWriterStatus

Reboot the passive node to clear the VSS error and retry the backups.

This entry was posted in Exchange, NetBackup and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s