cancel
Showing results for 
Search instead for 
Did you mean: 

Snapshot error 156 for vmbackups in Veritas

manura13
Level 3

Hi !!!!

   while taken vm backup it shows 156 error.

Earlier we are using ESX5.0 now we upgrade to 5.1 then only shows error

Error Msg.

09/14/2013 08:18:38 - granted resource  R00012
09/14/2013 08:18:38 - granted resource  IBM.ULT3580-TD5.000
09/14/2013 08:18:38 - granted resource  drdmzvc01-hcart2-robot-tld-0
09/14/2013 08:18:38 - estimated 0 kbytes needed
09/14/2013 08:18:38 - begin Parent Job
09/14/2013 08:18:38 - begin Flash Backup Windows: Start Notify Script
09/14/2013 08:18:38 - Info RUNCMD (pid=22311) started
09/14/2013 08:18:38 - Info RUNCMD (pid=22311) exiting with status: 0
Operation Status: 0
09/14/2013 08:18:38 - end Flash Backup Windows: Start Notify Script; elapsed time 0:00:00
09/14/2013 08:18:38 - begin Flash Backup Windows: Step By Condition
Operation Status: 0
09/14/2013 08:18:38 - end Flash Backup Windows: Step By Condition; elapsed time 0:00:00
09/14/2013 08:18:38 - begin Flash Backup Windows: Read File List
Operation Status: 0
09/14/2013 08:18:38 - end Flash Backup Windows: Read File List; elapsed time 0:00:00
09/14/2013 08:18:38 - begin Flash Backup Windows: Create Snapshot
09/14/2013 08:18:39 - Info bpbrm (pid=7700) DrOwa01 is the host to backup data from
09/14/2013 08:18:39 - Info bpbrm (pid=7700) reading file list from client
09/14/2013 08:18:39 - Info bpbrm (pid=7700) start bpfis on client
09/14/2013 08:18:39 - Info bpbrm (pid=7700) Starting create snapshot processing
09/14/2013 08:18:39 - started process bpbrm (pid=7700)
09/14/2013 08:18:40 - Info bpfis (pid=9104) Backup started
09/14/2013 08:18:40 - snapshot backup of client DrOwa01 using method VMware
09/14/2013 08:20:54 - Critical bpbrm (pid=7700) from client DrOwa01: FTL - VMware snapshot failed: SYM_VMC_TASK_REACHED_ERROR_STATE
09/14/2013 08:20:54 - Critical bpbrm (pid=7700) from client DrOwa01: FTL - VMware error received: Unable to communicate with the remote host, since it is disconnected.
09/14/2013 08:20:54 - Critical bpbrm (pid=7700) from client DrOwa01: FTL - snapshot processing failed, status 156
09/14/2013 08:20:54 - Critical bpbrm (pid=7700) from client DrOwa01: FTL - snapshot creation failed, status 156
09/14/2013 08:20:54 - Warning bpbrm (pid=7700) from client DrOwa01: WRN - ALL_LOCAL_DRIVES is not frozen
09/14/2013 08:20:54 - Info bpfis (pid=9104) done. status: 156
09/14/2013 08:20:54 - end Flash Backup Windows: Create Snapshot; elapsed time 0:02:16
09/14/2013 08:20:54 - Info bpfis (pid=0) done. status: 156: snapshot error encountered
09/14/2013 08:20:54 - end writing
Operation Status: 156
09/14/2013 08:20:54 - end Parent Job; elapsed time 0:02:16
09/14/2013 08:20:54 - begin Flash Backup Windows: Stop On Error
Operation Status: 0
09/14/2013 08:20:54 - end Flash Backup Windows: Stop On Error; elapsed time 0:00:00
09/14/2013 08:20:54 - begin Flash Backup Windows: Delete Snapshot
09/14/2013 08:20:54 - started process bpbrm (pid=8960)
09/14/2013 08:20:55 - Info bpbrm (pid=8960) Starting delete snapshot processing
09/14/2013 08:20:55 - Info bpfis (pid=0) Snapshot will not be deleted
09/14/2013 08:20:56 - Info bpfis (pid=8724) Backup started
09/14/2013 08:20:56 - Critical bpbrm (pid=8960) from client DrOwa01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.DrOwa01_1379126918.1.0
09/14/2013 08:20:56 - Info bpfis (pid=8724) done. status: 1542
09/14/2013 08:20:56 - end Flash Backup Windows: Delete Snapshot; elapsed time 0:00:02
09/14/2013 08:20:56 - Info bpfis (pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations
09/14/2013 08:20:56 - end writing
Operation Status: 1542
09/14/2013 08:20:56 - begin Flash Backup Windows: End Notify Script
09/14/2013 08:20:56 - Info RUNCMD (pid=22482) started
09/14/2013 08:20:56 - Info RUNCMD (pid=22482) exiting with status: 0
Operation Status: 0
09/14/2013 08:20:56 - end Flash Backup Windows: End Notify Script; elapsed time 0:00:00
Operation Status: 156
snapshot error encountered  (156)
 
Any body suggest
 
Thanks
Manu
8 REPLIES 8

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

09/14/2013 08:20:54 - Critical bpbrm (pid=7700) from client DrOwa01: FTL - VMware snapshot failed: SYM_VMC_TASK_REACHED_ERROR_STATE

 

see the below discussion and tech note.. looks like you are also having the same type of issue

https://www-secure.symantec.com/connect/forums/issue-backing-vmware-windows2008-server-machine#comme...

http://www.symantec.com/business/support/index?page=content&id=TECH154085

 

Marianne
Level 6
Partner    VIP    Accredited Certified

You forgot to mention NBU 7.5 patch level?

vSphere 5.1 is supported as from NetBackup 7.5.0.5

See http://www.symantec.com/docs/TECH127089

Mr_Khan
Level 4
Partner Accredited

look at the following link for possible causes for status 156. You will find it helpful.

http://www.symantec.com/business/support/index?page=content&id=HOWTO44492

 

NBU35
Level 6

check If Master, media, proxy host are at NBU 7.5 version.

check and paste Bpfis logs, 

Also  try the backup after disabling the quiescing of machine from policy

manura13
Level 3

Thanks All..

 

   Problem cleared after update the patches 7.5.0.5

manura13
Level 3

Hi !!!!

Any one help to trouble this issue..

Master Linux

Client Win2003 32bit

NB 7.5.0.6

backuptype -flashbackup-windows

while take back up it shows 50error..

10/25/2013 06:10:30 - Info nbjm (pid=28953) starting backup job (jobid=16368) for client extftp01, policy extftp01_fs, schedule Thursday
10/25/2013 06:10:30 - estimated 0 kbytes needed
10/25/2013 06:10:30 - Info nbjm (pid=28953) started backup (backupid=extftp01_1382661630) job for client Drextftp01, policy Drextftp01_fs, schedule Thursday on storage unit drnbapp01-hcart2-robot-tld-0
10/25/2013 06:10:30 - started process bpbrm (pid=24185)
10/25/2013 06:10:31 - Info bpbrm (pid=24185) starting bptm
10/25/2013 06:10:31 - Info bpbrm (pid=24185) Started media manager using bpcd successfully
10/25/2013 06:10:31 - Info bpbrm (pid=24185) Drextftp01 is the host to backup data from
10/25/2013 06:10:31 - Info bpbrm (pid=24185) telling media manager to start backup on client
10/25/2013 06:10:31 - Info bptm (pid=24189) using 262144 data buffer size
10/25/2013 06:10:31 - Info bptm (pid=24189) using 64 data buffers
10/25/2013 06:10:31 - Info bptm (pid=24189) start backup
10/25/2013 06:10:31 - Info bptm (pid=24189) Waiting for mount of media id R00011 (copy 1) on server drnbapp01.
10/25/2013 06:10:31 - Info bpbrm (pid=24185) spawning a brm child process
10/25/2013 06:10:31 - Info bpbrm (pid=24185) child pid: 24200
10/25/2013 06:10:32 - Info bpbrm (pid=24185) sending bpsched msg: CONNECTING TO CLIENT FOR Drextftp01_1382661630
10/25/2013 06:10:32 - Info bpbrm (pid=24185) start bpbkar on client
10/25/2013 06:10:32 - mounting R00011
10/25/2013 06:10:32 - connecting
10/25/2013 06:10:32 - connected; connect time: 0:00:00
10/25/2013 06:10:34 - Info bpbkar (pid=5860) Backup started
10/25/2013 06:10:34 - Info bpbrm (pid=24185) Sending the file list to the client
10/25/2013 06:10:34 - Error bpbrm (pid=24200) from client Drextftp01: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification
10/25/2013 06:10:34 - Critical bpbrm (pid=24200) unexpected termination of client Drextftp01
10/25/2013 06:10:34 - Error bpbrm (pid=24200) could not send server status message
10/25/2013 06:10:35 - Critical bpbrm (pid=24200) unexpected termination of client Drextftp01
10/25/2013 06:10:35 - Info bpbrm (pid=24185) sending message to media manager: STOP BACKUP Drextftp01_1382661630
10/25/2013 06:10:35 - Info bpbrm (pid=24185) media manager for backup id Drextftp01_1382661630 exited with status 150: termination requested by administrator
10/25/2013 06:10:35 - end writing
client process aborted  (50)

 

Any body suggest
 
Thanks
Manu


 

DG-2005
Level 5

10/25/2013 06:10:34 - Error bpbrm (pid=24200) from client Drextftp01: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification

 

Check the VSS writers on the box

vssadmin list writers

 

make sure all are in a good state.

manura13
Level 3

Hi!!!

  If we excute this vssadmin list writers

it shows this ..


C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {d59364d9-4cca-409f-ac20-e86950f583c5}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {143cf871-26b9-491d-a017-a9fc7aed13e5}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {0275bd71-b1b3-449a-b38e-ed088e4842a3}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {6de473a8-8e60-476f-93ae-de2c68468c21}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {47fca605-f8d2-4950-9670-bf33971ddff0}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {1b4ed865-f752-497e-b735-7d5e6d39dc0c}
   State: [1] Stable
   Last error: No error

Writer name: 'Removable Storage Manager'
   Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
   Writer Instance Id: {edcc66ab-9dd8-400f-8c6e-fc0ff439c1a9}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {97629e3f-131c-4b26-bc97-c1ab6fd6a1cb}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {fc94f057-287e-4267-ab27-aff6a9e7a234}
   State: [1] Stable
   Last error: No error

 

Thanks
Manu