Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Issue with backing up from VMWare Windows2008 server machine

Created: 20 Sep 2012 • Updated: 26 Sep 2012 | 2 comments
This issue has been solved. See solution.

Hi All,

I am moving over from the old netbackup 6.5 to 7.5 and am trying to iron out some of the issues before turning off the old system.

I have a policy which backs up all VMware hosts.  It does most of them without too much bother but gets stuck with a few.  It seems to get stuck when doing the snapshot in VMWare I have searched the forum and have tried the solution to issues which I thought were the same but not getting anything.  There are other machines in the policy which seems to work ok.  I have compared the details on the host sides and can't see anything outstanding.

I would be very greatful if anyone could shed any light on this at all.

I have put in the output from the job description please let me know if any other information would be helpful.

 

Thanks

James

 

09/20/2012 12:05:09 - Info nbjm (pid=15397) starting backup job (jobid=43374) for client sqa-nbuopsc-gl, policy PL_GL_DISK_V_ALL, schedule Daily_Diff

09/20/2012 12:05:09 - Info nbjm (pid=15397) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=43374, request id:{0B0D8810-0313-11E2-93AC-2C2A7044ADBA})

09/20/2012 12:05:09 - requesting resource stu_disk_sqa-nbumaster-gl-02

09/20/2012 12:05:09 - requesting resource sqa-nbumaster-gl-02.NBU_CLIENT.MAXJOBS.sqa-nbuopsc-gl

09/20/2012 12:05:09 - requesting resource sqa-nbumaster-gl-02.NBU_POLICY.MAXJOBS.PL_GL_DISK_V_ALL

09/20/2012 12:05:09 - granted resource  sqa-nbumaster-gl-02.NBU_CLIENT.MAXJOBS.sqa-nbuopsc-gl

09/20/2012 12:05:09 - granted resource  sqa-nbumaster-gl-02.NBU_POLICY.MAXJOBS.PL_GL_DISK_V_ALL

09/20/2012 12:05:09 - granted resource  MediaID=@aaaaf;DiskVolume=PureDiskVolume;DiskPool=dp_disk_sqa-nbumaster-gl-02;Path=PureDiskVolume;StorageServer=sqa-nbumaster-gl-02;MediaServer=sqa-nbumaster-gl-02

09/20/2012 12:05:09 - granted resource  stu_disk_sqa-nbumaster-gl-02

09/20/2012 12:05:10 - estimated 0 kbytes needed

09/20/2012 12:05:10 - begin Parent Job

09/20/2012 12:05:10 - begin VMware: Start Notify Script

09/20/2012 12:05:10 - Info RUNCMD (pid=12696) started

09/20/2012 12:05:10 - Info RUNCMD (pid=12696) exiting with status: 0

Operation Status: 0

09/20/2012 12:05:10 - end VMware: Start Notify Script; elapsed time 0:00:00

09/20/2012 12:05:10 - begin VMware: Step By Condition

Operation Status: 0

09/20/2012 12:05:10 - end VMware: Step By Condition; elapsed time 0:00:00

09/20/2012 12:05:10 - begin VMware: Read File List

Operation Status: 0

09/20/2012 12:05:10 - end VMware: Read File List; elapsed time 0:00:00

09/20/2012 12:05:10 - begin VMware: Create Snapshot

09/20/2012 12:05:11 - Info bpbrm (pid=12705) sqa-nbuopsc-gl is the host to backup data from

09/20/2012 12:05:11 - Info bpbrm (pid=12705) reading file list from client

09/20/2012 12:05:11 - Info bpbrm (pid=12705) start bpfis on client

09/20/2012 12:05:11 - begin Create Snapshot

09/20/2012 12:05:11 - Info bpfis (pid=12712) Backup started

09/20/2012 12:05:11 - started process bpbrm (pid=12705)

09/20/2012 12:05:12 - snapshot backup of client sqa-nbuopsc-gl using method VMware_v2

09/20/2012 12:08:20 - Critical bpbrm (pid=12705) from client sqa-nbuopsc-gl: FTL - VMware snapshot failed: SYM_VMC_TASK_REACHED_ERROR_STATE

09/20/2012 12:08:20 - Critical bpbrm (pid=12705) from client sqa-nbuopsc-gl: FTL - VMware error received: A snapshot operation cannot be performed.

09/20/2012 12:08:20 - Critical bpbrm (pid=12705) from client sqa-nbuopsc-gl: FTL - snapshot creation failed, status 156

09/20/2012 12:08:20 - Warning bpbrm (pid=12705) from client sqa-nbuopsc-gl: WRN - ALL_LOCAL_DRIVES is not frozen

09/20/2012 12:08:20 - Info bpfis (pid=12712) done. status: 156

09/20/2012 12:08:20 - end VMware: Create Snapshot; elapsed time 0:03:10

09/20/2012 12:08:20 - Info bpfis (pid=0) done. status: 156: snapshot error encountered

09/20/2012 12:08:20 - end writing

Operation Status: 156

09/20/2012 12:08:20 - end Parent Job; elapsed time 0:03:10

09/20/2012 12:08:20 - begin VMware: Stop On Error

Operation Status: 0

09/20/2012 12:08:20 - end VMware: Stop On Error; elapsed time 0:00:00

09/20/2012 12:08:20 - begin VMware: Delete Snapshot

09/20/2012 12:08:21 - begin Delete Snapshot

09/20/2012 12:08:21 - Info bpfis (pid=0) Snapshot will not be deleted

09/20/2012 12:08:21 - Info bpfis (pid=12958) Backup started

09/20/2012 12:08:21 - Critical bpbrm (pid=12950) from client sqa-nbuopsc-gl: FTL - cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.sqa-nbuopsc-gl_1348139109.1.0

09/20/2012 12:08:21 - Info bpfis (pid=12958) done. status: 1542

09/20/2012 12:08:21 - end Delete Snapshot; elapsed time 0:00:00

09/20/2012 12:08:21 - Info bpfis (pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations

09/20/2012 12:08:21 - started process bpbrm (pid=12950)

09/20/2012 12:08:21 - end writing

Operation Status: 1542

09/20/2012 12:08:21 - end VMware: Delete Snapshot; elapsed time 0:00:01

Operation Status: 156

09/20/2012 12:08:21 - end Create Snapshot; elapsed time 0:03:10

snapshot error encountered  (156)

09/20/2012 13:23:36 - job 43374 was restarted as job 43380

Comments 2 CommentsJump to latest comment

Will Restore's picture

Article URL http://www.symantec.com/docs/TECH154085

 

Cause

The message, its cause, and workarounds are discussed in the following VMware knowledge base article:

Unable to use Snapshots or perform a backup on virtual machines configured with bus-sharing
http://kb.vmware.com/kb/1006392

VMware does not support snapshots of virtual machines configured for bus-sharing.  This means the virtual machine cannot be protecting using the vStorage API.

 

Solution

These virtual machines are configured in such a way that they can have snapshots created. You may need to back these up with a NetBackup client installed in the guest operating system rather than using the VMware Agent

 

Will Restore -- where there is a Will there is a way

SOLUTION
Jammes's picture

Thanks, managed to get the issue resolved.  It seems there was an old snapshot file in VSphere.  Once removed it backed up ok.