Backup & Recovery

 View Only

  • 1.  Problem with Backup Exec 2010 and VMware agent

    Posted Aug 18, 2010 12:51 PM

    I am using a fully patched Backup Exec server to test the VMware agent for backing up VM's. Here is what is happening:

    1. Backup Exec requests a snapshot

    2. I can see the snapshot getting created in vCenter

    3. Then vCenter mounts the original vmdk file as another disk to the backup server( I have no idea why it does this )

    4. Backup exec backs up the vmdk file

    5. The backup completes normally in backup exec but in vCenter I see this error:

    Remove snapshot

    Unable to access file

    <unspecified filename> since it

    is locked

    I have the backup exec RAWS installed on the VM. Anyone else run into this? Its pretty maddening and Symantec says they will not give support on trialware.



  • 2.  RE: Problem with Backup Exec 2010 and VMware agent

    Posted Feb 25, 2011 12:39 PM

    Hello,

    I have just run into the exact same problem.  I see that there is a technote on symantec for this now.  The workaround is to "disable GRT" backups.

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

    I was just wondering how you removed the snapshot.  Because when I try to remove it from VI client using a delet all it cimpletes succesfully, but actually leaves all the snapshots there and the vmx file still points to the delta that BE2010 created.

    I was going to VMKFS -i to clone the delta into a new base disk and point the VM to that.

    Any other ideas at all?

    Cheers!

    Graham.



  • 3.  RE: Problem with Backup Exec 2010 and VMware agent

    Posted Feb 25, 2011 12:56 PM

    I would say that the problem is that the GRT require the use of  vDR installed and configured so you may use backup exec to do incremental backups and restore single files, that is why it try to mount the disk.

    Do this:

    1) remove the GRT from the policy

    2) delete all the jobs created by the policy

    3) recreate the jobs

    4) run a test backup.

    to remove the snaphost try this:

    http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/



  • 4.  RE: Problem with Backup Exec 2010 and VMware agent

    Posted Feb 25, 2011 01:18 PM

    Thanks very much Ill give it a go.

    Cheers!



  • 5.  RE: Problem with Backup Exec 2010 and VMware agent

    Posted Feb 25, 2011 02:10 PM

    BTW thought that the Best practice from symantec to use GRT in a VM enviroment could be useful:

    Best practices for Backup Exec 2010 Agent for VMware Virtual Infrastructure

    Best practices include tips and recommendations to help you effectively use Backup Exec 2010 Agent for VMware Virtual Infrastructure (Agent for VMware). For more information about the Agent for VMware, see the Backup Exec 2010 Administrator's Guide.

    The following best practices help you use the Agent for VMware effectively:

    • Install the Backup Exec Remote Agent for Windows Systems on any virtual machines on which you want to use Backup Exec's Granular Recovery Technology (GRT).


    • To use GRT when you create a restore job, do the following:

      • Expand the network bios name of the virtual machine.


      • Select the individual drives, files, and folders that you want to restore.



  • You cannot select individual drives, folders, and files from the virtual machines that appear when you expand VMware vCenter and ESX Servers.


  • If you select the vCenter or the ESX server as a backup resource, all virtual machines are backed up. For a recurring job, any virtual machines that you add after the job is created are included in the backup.


  • If you select to back up the vCenter or the ESX server, the backup job does not include the following:

    • Configuration files for the vCenter or the ESX server


    • Physical Raw Disk Mapping (RDM) devices


    • Independent disks



  • Perform a weekly full backup. This schedule is the default for the VMware policy.


  • Back up to a disk device instead of a tape device.


  • Ensure that the VMware Converter is installed on the media server if you want to restore backup sets that were created with Backup Exec 12.5 for Windows Servers.


  • Ensure that only one VSS Provider is installed on Guest virtual machines. The VMware VSS Provider and the Symantec VSS Provider cannot reside on the same Guest virtual machine.


  • To use Granular Recovery Technology for individual items from Microsoft Active Directory, Exchange, or SQL, do the following:

    • Install VMware tools on the guest virtual machine.


    • Install the Remote Agent for Windows Systems on the guest virtual machine. You must install the VMware tools before you install the Remote Agent for Windows Systems.


    • Ensure that you have a valid license for each application that you want to protect.


    • Ensure that the credentials for the guest virtual machine are valid for the application you want to protect.


    • Use the same requirements for backing up Microsoft Exchange on a physical machine when you back up Exchange on a virtual machine.


    • Create separate backup jobs for file servers and application or database servers. When you create file server backup jobs, be sure to uncheck the options on the Virtual Machine Application Granular Recovery Technology Settings dialog box.



    • /apps/media/inquira/resources /resources


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



  • 6.  RE: Problem with Backup Exec 2010 and VMware agent

    Posted Feb 28, 2011 09:18 AM

    Thanks mate that’s useful – I have both the vmware VSS and the Symantec VSS on the same VM. I Wonder if thats the issue.

    Cheers!

    Graham.



  • 7.  RE: Problem with Backup Exec 2010 and VMware agent

    Posted Feb 28, 2011 10:20 AM

    Basically BEX try to use VSS on Exchange,SQL and AD ...but you have to consider that by default BEX use only the VSS software by Symantec or by Micorosoft or any VSS Hardware si Vmware is not used.

    I would anyway try to "force" BEX using the Microsoft VSS to avoid any "confusion" .

    For backing up the VM Symantec use VAAI so it is not at windows VSS level.

    Alex