Flashbackup - Status Code 156

Hello all,

Would anyone be able to offer any help on failed backups for a 'FlashBackup-Windows' policy?

Client OS: Windows Server 2008 R2
NetBackup client: v7.5.0.6

Media Server OS: Windows Server 2008 R2
NetBackup v7.5.0.6
Policy type: FlashBackup-Windows

Flashbackups have newly been introduced into the environment for one server to backup one specific drive (size = 1.5 TB).  They are set to backup to Tape (LT04 tape drive) have been failing with Status Code 156.  Below I've included a snip from the Job Details in NetBackup Admin Console.

2/10/2014 3:11:16 AM - begin Flash Backup Windows, Start Notify Script

2/10/2014 3:11:16 AM - Info RUNCMD(pid=18208) started            
2/10/2014 3:11:16 AM - Info RUNCMD(pid=18208) exiting with status: 0         
Status 0
2/10/2014 3:11:16 AM - end Flash Backup Windows, Start Notify Script; elapsed time: 00:00:00
2/10/2014 3:11:16 AM - begin Flash Backup Windows, Step By Condition
Status 0
2/10/2014 3:11:16 AM - end Flash Backup Windows, Step By Condition; elapsed time: 00:00:00
2/1/2014 3:11:16 AM - begin Flash Backup Windows, Read File List
Status 0
2/10/2014 3:11:16 AM - end Flash Backup Windows, Read File List; elapsed time: 00:00:00
2/10/2014 3:11:16 AM - begin Flash Backup Windows, Create Snapshot
2/10/2014 3:11:16 AM - started process bpbrm (18215)
2/10/2014 3:11:16 AM - started
2/10/2014 3:11:19 AM - Info bpbrm(pid=18215) someserver.server.net is the host to backup data from     
2/10/2014 3:11:19 AM - Info bpbrm(pid=18215) reading file list from client        
2/10/2014 3:11:19 AM - Info bpbrm(pid=18215) start bpfis on client         
2/10/2014 3:11:19 AM - Info bpbrm(pid=18215) Starting create snapshot processing         
2/10/2014 3:11:21 AM - Info bpfis(pid=5480) Backup started           
2/10/2014 3:31:39 AM - Critical bpbrm(pid=18215) from client someserver.server.net: FTL - snapshot processing failed, status 156   
2/10/2014 3:31:39 AM - Critical bpbrm(pid=18215) from client someserver.server.net: FTL - snapshot creation failed, status 156   
2/10/2014 3:31:39 AM - Warning bpbrm(pid=18215) from client someserver.server.net: WRN - \\.\R:\ is not frozen    
2/10/2014 3:31:39 AM - Info bpfis(pid=5480) done. status: 156          
2/10/2014 3:31:39 AM - end Flash Backup Windows, Create Snapshot; elapsed time: 00:20:23
2/10/2014 3:31:39 AM - Info bpfis(pid=0) done. status: 156: snapshot error encountered       
2/10/2014 3:31:39 AM - end writing
Status 156
2/10/2014 3:31:39 AM - end Parent Job; elapsed time: 00:20:23
2/10/2014 3:31:39 AM - begin Flash Backup Windows, Stop On Error
Status 0
2/10/2014 3:31:39 AM - end Flash Backup Windows, Stop On Error; elapsed time: 00:00:00
2/10/2014 3:31:39 AM - begin Flash Backup Windows, Delete Snapshot
2/10/2014 3:31:39 AM - started process bpbrm (19152)
2/10/2014 3:31:42 AM - Info bpbrm(pid=19152) Starting delete snapshot processing         
2/10/2014 3:31:42 AM - Info bpfis(pid=0) Snapshot will not be deleted        
2/10/2014 3:31:46 AM - Info bpfis(pid=1264) Backup started           
2/10/2014 3:31:46 AM - Critical bpbrm(pid=19152) from someserver.server.net: FTL - cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.someserver.server.net_1392117147.1.0    
2/10/2014 3:31:46 AM - Info bpfis(pid=1264) done. status: 1542          
2/10/2014 3:31:46 AM - end Flash Backup Windows, Delete Snapshot; elapsed time: 00:00:07
2/10/2014 3:31:46 AM - Info bpfis(pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations
2/10/2014 3:31:46 AM - end writing
Status 1542
2/10/2014 3:31:46 AM - end operation
2/10/2014 3:31:46 AM - begin Flash Backup Windows, End Notify Script
2/10/2014 3:31:46 AM - Info RUNCMD(pid=19159) started            
2/10/2014 3:31:46 AM - Info RUNCMD(pid=19159) exiting with status: 0         
Status 0
2/10/2014 3:31:46 AM - end Flash Backup Windows, End Notify Script; elapsed time: 00:00:00
Status 156
2/10/2014 3:31:46 AM - end operation
snapshot error encountered(156)

 

You'll notcice from 3:11AM to 3:31AM there is no activity

2/10/2014 3:11:21 AM - Info bpfis(pid=5480) Backup started
2/10/2014 3:31:39 AM - Critical bpbrm(pid=18215) from client someserver.server.net: FTL - snapshot processing failed, status 156   

Any sugestions would be appreciated.

Thanks

5 Replies

Please check if the follwing

Please check if the follwing services are running on the windows client server and set to start automatic.

VSS (Volume Shadow Copy)

Also check the "event logs" are share if you find any error message for taking or deleting the snapshot. If I am thinking right, your server may be using other snapshot service available & its having some issue while accessing the snapshot. 

Check using this command the number of snapshot providers on your server - vssadmin list writers

 

Highlighted

Hello Yogesh - thanks for

Hello Yogesh - thanks for your reply.

VSS service

VSS is set to Manual, why would have to be set to start automatic?  This Microsoft KB article suggests leaving it set to Manual http://technet.microsoft.com/en-us/library/ee264206(v=ws.10).aspx

Event Log

Event log (Application) shows a VSS error (note: modifed a little):

Source:        VSS
Date:          2/10/2014 3:11:30 AM
Event ID:      12289
 
Level:         Error
Computer:      someserver.server.net
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{########-####-####-####-############} - ################,0x########,################,0,################,####,[0]).  hr = 0x8007012e, The volume is too fragmented to complete this operation.


vssadmin list providers: 

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {removed}
   Version: 1.0.0.7
 
Thanks,

"The volume is too fragmented

"The volume is too fragmented to complete this operation." NBU relies on VSS to take a snapshot of the drive but VSS seems to be failing with the message that you see in Event Viewer log. I must admit that this is the first time that I have seen a snapshot attempt failing with this message. Probably best to deal with this issue first of all? An online defrag tool may be a good idea.

Thank you Marianne - system

Thank you Marianne - system owners have been advised to defragment that drive.  I will provide an update on whether that helped.

Moved:

4201 Hyper-V: Stop On Error