Forum Discussion

ElGringo's avatar
ElGringo
Level 6
16 years ago

VCB snapshot failed for file level backup

Hello,

 

I've a issue only when I try to backup VM machine

DiffInc using file level crash but FullVM work properly !

My configuration :

NBU 6.5.3 runing on Windows 2003 R2 X64 SP2

VCB 1.5

ESX 3.5

EMC CX3-40

Storage Foundation Basic 5.1

 

18:38:52.886 [6048.7000] <2> onlfi_vfms_logf: --- End of file C:\WINDOWS\TEMP\VfMS-06048233768795332000000000004-a07000
18:38:52.886 [6048.7000] <2> onlfi_vfms_logf: --- Dumping file C:\WINDOWS\TEMP\VfMS-06048233768795332000000000005-a07000 (stderr):
18:38:52.886 [6048.7000] <2> onlfi_vfms_logf: --- End of file C:\WINDOWS\TEMP\VfMS-06048233768795332000000000005-a07000
18:38:52.886 [6048.7000] <2> onlfi_vfms_logf: do_cmd: Command failed ""C:\Program Files (x86)\VMware\VMware Consolidated Backup Framework\\vcbMounter.exe" -h virtualcenter.mipih.net -u "netbackupadmin" -p ************ -c "C:\Program Files (x86)\VMware\VMware Consolidated Backup Framework\\vmName.cache" -a ipaddr:2003testnb.mipih.net -t file -L 6 -r "i:\mnt\2003testnb.mipih.net" -M 1 -F 0 -m nbd" <NUL >C:\WINDOWS\TEMP\VfMS-06048233768795332000000000004-a07000 2>C:\WINDOWS\TEMP\VfMS-06048233768795332000000000005-a07000
18:38:54.886 [6048.7000] <4> delete_mount_point: Deleted mount point C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_ALL_LOCAL_DRIVES_6048
18:38:54.886 [6048.7000] <32> onlfi_freeze_fim_fs: VfMS error 11; see following messages:
18:38:54.886 [6048.7000] <32> onlfi_freeze_fim_fs: Fatal method error was reported
18:38:54.886 [6048.7000] <32> onlfi_freeze_fim_fs: vfm_freeze: method: VMware, type: FIM, function: VMware_freeze
18:38:54.886 [6048.7000] <32> onlfi_freeze_fim_fs: VfMS method error 5; see following message:
18:38:54.886 [6048.7000] <32> onlfi_freeze_fim_fs: VMware_freeze: Snapshot create failed for 2003testnb.mipih.net on virtualcenter.mipih.net
18:38:54.886 [6048.7000] <32> onlfi_freeze: VfMS error 11; see following messages:
18:38:54.886 [6048.7000] <32> onlfi_freeze: Fatal method error was reported
18:38:54.886 [6048.7000] <32> onlfi_freeze: vfm_freeze: method: VMware, type: FIM, function: VMware_freeze
18:38:54.886 [6048.7000] <32> onlfi_freeze: VfMS method error 5; see following message:
18:38:54.886 [6048.7000] <32> onlfi_freeze: VMware_freeze: Snapshot create failed for 2003testnb.mipih.net on virtualcenter.mipih.net
18:38:54.886 [6048.7000] <16> bpfis: FTL - snapshot creation failed, status 156
18:38:54.886 [6048.7000] <4> onlfi_thaw: Thawing ALL_LOCAL_DRIVES using snapshot method VMware.

 

Thx for any help,

 

 

 

7.1.x and Earlier
Backup and Recovery
NetBackup
  • ElGringo's avatar
    ElGringo
    16 years ago

    Yes,

     

    This is a known issue on restoring flashbackup image stored on PureDisk.

    Symantec support can provides an EEB patch that solve this issue. Or you have to wait for NBU 6.5.4 which will include the patch.

     

    Best Regards.

10 Replies

Sort By
  • Santosh_Kalugad's avatar
    Santosh_Kalugad
    Level 4
    16 years ago

    In the attribute of the backup policy go to snapshot client option. Under configuration paramater there is option called Virtual machine backup. Here select 2 option (mapped to Full VM) and then try to take backup of VM. Mapped to full VM will give backup incremental VM.

     

    Thanks

    Santosh

  • ElGringo's avatar
    ElGringo
    Level 6
    16 years ago

    Hello,

     

    I 've already try to backup using backup mode 2 (mapped FullVM) it's OK, BUT it doesn't solve my issue. Because I wan't to backup using level 3 ( Mapped fullVM and file for incr)...

     

    Thx for any help.

     

    Best regards

  • Pravs's avatar
    Pravs
    Level 4
    16 years ago

    1.see what's written in this file C:\WINDOWS\TEMP\VfMS-06048233768795332000000000005-a07000 (stderr)

    2. do_cmd is failing. it might be because of command_length limitation. I can't see any good reason here to fail. can you compare do_cmd  (for vcbMounter.exe) for other options (say type 0) and see what's the difference. If you can't do by your own, call support and let them know, what's the problem.

     

    ~

    Praveen

  • Status_Code_0's avatar
    Status_Code_0
    Level 4
    16 years ago

    Has there been any update to this case?  I have the same issue and any updates would be helpful.


    Thanks.

     

     

  • schmaustech's avatar
    schmaustech
    Level 5
    16 years ago

    Create the following directory on the proxy server:

     

    C:\Program Files\VERITAS\Netbackup\logs\bpfis

     

    Run the job that fails with status 156.  Post the log created in that directory.

     

    Regards,

     

    Benjamin Schmaus

  • policeman51's avatar
    policeman51
    Level 4
    16 years ago

    Have you had any progress with this.

    We have the same exact issue, almost the same configuration except my NBU 6.5.3.1 runing on Windows 2003 SP2. 

    I've tried option 2 and 3 under the snapshot settings and the differentials always fail, but the fulls work. 

    The diffs fail on our Windows 2008 VM, which Netbackup says that should be fixed with update 6.5.4, http://communities.vmware.com/thread/155543

    But we have 2 Exchange 2007 VMs that just started failing on the differentials, not sure why, they were working fine.

  • ElGringo's avatar
    ElGringo
    Level 6
    16 years ago

    Yes,

     

    This is a known issue on restoring flashbackup image stored on PureDisk.

    Symantec support can provides an EEB patch that solve this issue. Or you have to wait for NBU 6.5.4 which will include the patch.

     

    Best Regards.

  • Pravs's avatar
    Pravs
    Level 4
    16 years ago
    @ policeman51 if you are talking abour this thread http://communities.vmware.com/thread/155543 and symantec ET : 1370521 then we provided an EEB for 6.5.2 and exceptional support for the 2008 VM in NBU 6.5.3.

    What I feel you guys are having a altogether different problem. If the mapping for these volumes fails get the bpbkar and bpfis atleast. and perhaps you might be seeing Event viewer errors on proxy at the back-up. This should be the first place to start.