Forum Discussion

Bharath_Achar's avatar
Bharath_Achar
Level 6
10 years ago

VMware backup failing with status snapshot error encountered (156)

Hi Experts,

Please help me troubleshooting this failure:

NBU master server -

swvmnb01    SunOS(5.10)    UNIX    Master Server    7.6.0.2    Connected

 

01/21/2015 23:54:00 - Info nbjm (pid=11361) starting backup job (jobid=123604) for client swv222.groups.com, policy 3S-IMP-VIP-LEGP02, schedule Full
01/21/2015 23:54:00 - Info nbjm (pid=11361) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=123604, request id:{0FFFE316-A1FB-11E4-81D4-001E680F6D54})
01/21/2015 23:54:00 - requesting resource 3S-DSSU-VM-GRP-swvMNB03
01/21/2015 23:54:00 - requesting resource swvmnb01.NBU_CLIENT.MAXJOBS.swv222.groups.com
01/21/2015 23:54:00 - granted resource  swvmnb01.NBU_CLIENT.MAXJOBS.swv222.groups.com
01/21/2015 23:54:00 - granted resource  MediaID=@aaaae;Path=G:\;MediaServer=swvmnb03
01/21/2015 23:54:00 - granted resource  swvMNB03-DSSU-VM-1
01/21/2015 23:54:00 - estimated 0 kbytes needed
01/21/2015 23:54:00 - begin Parent Job
01/21/2015 23:54:00 - begin Application Snapshot: Step By Condition
Operation Status: 0
01/21/2015 23:54:00 - end Application Snapshot: Step By Condition; elapsed time 0:00:00
01/21/2015 23:54:00 - begin Application Snapshot: Read File List
Operation Status: 0
01/21/2015 23:54:00 - end Application Snapshot: Read File List; elapsed time 0:00:00
01/21/2015 23:54:00 - begin Application Snapshot: Create Snapshot
01/21/2015 23:54:01 - started process bpbrm (pid=10340)
01/21/2015 23:54:07 - Info bpbrm (pid=10340) swv222.groups.com is the host to backup data from
01/21/2015 23:54:07 - Info bpbrm (pid=10340) reading file list for client
01/21/2015 23:54:07 - Info bpbrm (pid=10340) start bpfis on client
01/21/2015 23:54:09 - Info bpbrm (pid=10340) Starting create snapshot processing
01/21/2015 23:54:11 - Info bpfis (pid=11240) Backup started
01/21/2015 23:54:11 - snapshot backup of client swv222.groups.com using method VMware_v2
01/21/2015 23:56:52 - Critical bpbrm (pid=10340) from client swv222.groups.com: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error
01/21/2015 23:56:52 - Critical bpbrm (pid=10340) from client swv222.groups.com: FTL - VMware error received: fault.GenericVmConfigFault.summary
01/21/2015 23:56:53 - Critical bpbrm (pid=10340) from client swv222.groups.com: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
01/21/2015 23:56:53 - Critical bpbrm (pid=10340) from client swv222.groups.com: FTL - 
01/21/2015 23:56:53 - Critical bpbrm (pid=10340) from client swv222.groups.com: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
01/21/2015 23:56:53 - Critical bpbrm (pid=10340) from client swv222.groups.com: FTL - 
01/21/2015 23:56:53 - Critical bpbrm (pid=10340) from client swv222.groups.com: FTL - snapshot processing failed, status 156
01/21/2015 23:56:53 - Critical bpbrm (pid=10340) from client swv222.groups.com: FTL - snapshot creation failed, status 156
01/21/2015 23:56:53 - Warning bpbrm (pid=10340) from client swv222.groups.com: WRN - ALL_LOCAL_DRIVES is not frozen
01/21/2015 23:56:53 - Info bpfis (pid=11240) done. status: 156
01/21/2015 23:56:53 - end Application Snapshot: Create Snapshot; elapsed time 0:02:53
01/21/2015 23:56:53 - Info bpfis (pid=11240) done. status: 156: snapshot error encountered
01/21/2015 23:56:53 - end writing
Operation Status: 156
01/21/2015 23:56:53 - end Parent Job; elapsed time 0:02:53
01/21/2015 23:56:53 - begin Application Snapshot: Stop On Error
Operation Status: 0
01/21/2015 23:56:53 - end Application Snapshot: Stop On Error; elapsed time 0:00:00
01/21/2015 23:56:53 - begin Application Snapshot: Cleanup Resources
Operation Status: -9999
01/21/2015 23:56:53 - end Application Snapshot: Cleanup Resources; elapsed time 0:00:00
01/21/2015 23:56:53 - begin Application Snapshot: Delete Snapshot
01/21/2015 23:56:54 - started process bpbrm (pid=6896)
01/21/2015 23:57:01 - Info bpbrm (pid=6896) Starting delete snapshot processing
01/21/2015 23:57:04 - Info bpfis (pid=10956) Backup started
01/21/2015 23:57:04 - Critical bpbrm (pid=6896) from client swv222.groups.com: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.swv222.groups.com_1421906040.1.0
01/21/2015 23:57:04 - Info bpfis (pid=10956) done. status: 4207
01/21/2015 23:57:04 - end Application Snapshot: Delete Snapshot; elapsed time 0:00:11
01/21/2015 23:57:04 - Info bpfis (pid=10956) done. status: 4207: Could not fetch snapshot metadata or state files
01/21/2015 23:57:04 - end writing
Operation Status: 4207
Operation Status: 156
snapshot error encountered  (156)

 

7.6
Backing Up
Backup and Recovery
Basics
Best Practice
NetBackup
Rules
Solaris
Tip-How to
Troubleshooting
  • RamNagalla's avatar
    RamNagalla
    10 years ago

    i dont thinks this esxi version is supported by netbackup 7.6

    does it ever make successfull backup?

    see the below compatablity..

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

9 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    Did you see this?

    VMware error received: fault.GenericVmConfigFault.summary

    Have you tested snapshot for swv222 from VMware?

    I would firstly get VM admin involved to test snapshot from their side and check VMware logs for errors.

  • Bharath_Achar's avatar
    Bharath_Achar
    Level 6
    10 years ago

    Hi,

     

    VM version is 4.

    I have asked the VM admin to test the snapshot.

     

    Regards,

    Bharath

  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    10 years ago

    If the VM is a windows machine, check if there is any VSS or Volsnap errors/warnings in the system and application event log. Also do a vssadmin list writers from an elevated prompt to see if there any writer there shas a status other than stable/no error

  • NBU35's avatar
    NBU35
    Level 6
    10 years ago

    If Vmware console is able to generate the snapshot , then from backup policy >> advanced options>> disable quiescing and retry the backup.

    Also check for the VSS writers state as per Michael's recommendation by Vssadmin list writers and check if they are stable or not.

    also check if your backup host is virtual machine, then any disk of failing vm is still attched to it, if yes then remove that disk.

    is there any application like SQL, exchange, sharepoint installed in the VM ?

    As suggested by Riaan, kindly share the bpfis & vxms logs

     

  • RamNagalla's avatar
    RamNagalla
    Moderator
    10 years ago

    hi Bharath,

    when you say VM version is 4.is that the VM hardware version?

    if yes, its too old to get backup using 7.6.0.2

    did you select the Block level incrmental backup option in policy VMware tab, if yes, please un select it and try the backup.

    what is your Vcetner and Esxi vertions?

     

  • Bharath_Achar's avatar
    Bharath_Achar
    Level 6
    10 years ago

    Hello All,

     

    I see that VMware tool is out of date on this VM, hence i requested  VM admin to update it first.

     

    Hi Ram,

    ESX/ESXi version is 3.5

  • RamNagalla's avatar
    RamNagalla
    Moderator
    10 years ago

    i dont thinks this esxi version is supported by netbackup 7.6

    does it ever make successfull backup?

    see the below compatablity..

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

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    10 years ago

    In version 7.5 ESX 3.5 update to was supported with limited support (and what limits there were was unclear). In 7.6 its not listed anywhere, so I would say unsupported. Rather just backup in guest and don't waste time on this.