Error connecting to VM disk for backups

[MKRT]

I need some help with the following errors:

V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:

This is a new install of 2010 and I an trying to backup the VMDKs for several Virtual Machines on ESXi 4.1 vshpere. 

I am able to create the jobs, browse the VMDK list.  I've tried backup through vsphere and also directly from ESXi with the same results.   The credentials I use are good with full root.

The ESXi servers connect to an iSCSI share where I store the VMDK but I would assume that the BES should backup the files though the Datastore access on each server.   

Regardless, any ideas as to what is causing the issue?

[Striker_303]

Have you tried this: http://www.symantec.com/docs/TECH129572

Also have you updated to BE 2010 R2 with all updates?

[Munir2Fast]

Hi,

Sorry but Backup exec does not support backups of free version for VMWare ESXi server, you need to have minimum lincense installed for it to work correctly.

Please got through the below link for the same :

http://www.symantec.com/docs/TECH135343

Let me know if you have any more questions...

[MKRT]

I am using an ESXi4.1 licensed through vsphere.    With 4.1, backups should be handled by the storage APIs.   The article above makes mention of ver 3.x that did not have this feature available but should be supported in 4.1.  

The server 2008 issue does not come into play since I am not backing up that OS.  

The other suggestions about ID permissions should not be an issue since I tried the backup with essentially the 'root' id.  

If this is an issue with ESX vs ESXi that is suprising since the product documentation states that it is supported.    http://eval.symantec.com/mktginfo/enterprise/fact_sheets/b-be2010_agent_vmware_virtual_infrastructure.en-us.pdf  It states esx 3.5 and vsphere hosts. 

Symantec tech support will not provide 'pre sales' tech support.  But I am also not going to recommend a product when the demo fails.  

We are no fortune 500 company, but I don't understand why symantec wouldn't want to bend over backwards to answer the questions of a potential new customer. 

[ZeRoC00L]

Does your Backup Exec Media server has got access to the iSCSI LUNs ?

You can try to use NBD, wich uses the 'normal' network to backup, but will be slower than SAN mode.

[teiva-boy]

You need to talk to your reseller to speak to your Symantec sales person.  That sales person has an engineer that can assist in getting your Proof of Concept (POC) off the ground and working.

Though as mentioned, you may want to start with NBD first to see if that works, if that fails, it could be a permissions thing.

You did share out your LUN from your SAN to BE too right?  Of course making sure to turn off automount within Windows Server first!!!!!

[MKRT]

In this install, the Media server would not have access to the SAN with the Virtual disks. 

I tried the NBD option and it also failed with the same message.  

Is having the BES media server on the Same san the only way to get a backup?  What if I am pulling data from multiple SANs?  Would I then need a direct connection to each?  

Also, I've tried going through the sales rep, but they have no technical knowledge.   The 'engineer' they tried to get me in contact with will not speak to me without a service contract #.

[teiva-boy]

There is an account Manager that is based in your region, and he/she has a Systems Engineer that also lives in the region.  They are 100% sales focused, and dont give a damn about service contracts.  They are paid based on new sales.  If they want money, they will help you.  You are not asking the right questions, or talking to the wrong people.

Tell them you are in a POC, and you want to speak to a Pre-sales SE for assistance.  

[teiva-boy]

The media server has to have access to the SAN if you want to do SAN based backups.  If not, then you are using NBD, and you need network access to the vcenter host and esx hosts.

[ZeRoC00L]

In order to make a fast SAN based backup, yes the backup exec media server needs access to the SAN.

Can you post the full log of an NBD backup, this should normally work fine ?

[Colin_Weaver]

Also do you have any Independent or Phyisical RDM (RAW) disks in the VM's you are backing up as there are limitations on backing up Vms containing disks of this type.

[Ben_L_]

What is the OS of the VM's you are trying to backup? 

If they are 2008 or 2008 R2 you may want to check out this technote.

http://www.symantec.com/docs/TECH135858

[MKRT]

The backups would be all VMDK, no RAW access.  

I do not want SAN based backups. So NBD would be the way, but I hit the same error.  

Here is the Sanitized log:

Job Log: BEX_FREYA_00024.xmlJob Log for Backup 00003



      Completed status: Failed    See error(s)
      Expand AllCollapse All

      Job Information
Job server: FREYA
Job name: Backup 00003
Job started: Wednesday, January 05, 2011 at 12:47:34 PM
Job type: Backup
Job Log: BEX_FREYA_00024.xml


Drive and media mount requested: 1/5/2011 12:47:34 PM
No appendable media could be mounted.
Switching to overwrite operation on scratch media.


      Device and Media Information
Drive and media information from media mount: 1/5/2011 12:47:35 PM
Drive Name: Backup-to-Disk Folder 0001
Media Label: B2D000001
Media GUID: {b7217ae6-531b-41ee-852b-2d29e4b79d81}
Overwrite Protected Until: 2/2/2011 12:47:35 PM
Appendable Until: 1/11/2011 12:47:35 PM
Targeted Media Set Name: Keep Data for 4 Weeks

All Media Used
 B2D000001

 IMG000024

 IMG000025

 IMG000026



      Job Operation - Backup
            Backup Options
Media operation - Append to media, overwrite if no appendable media is available.

Compression Type: Hardware [if available, otherwise none]

Encryption Type: None

WARNING: The option 'Verify after backup completes' was not selected.

Performing a verify operation to make sure that media can be read after the backup has completed is recommended.




            Server - FREYA
                  Set Information -
                  VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\varda
                        Backup Set Information
V-79-57344-38726 - Backup Exec failed to connect to virtual machine '\(DC)ha-datacenter(DC)\vm\varda' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.

Family Name: "Media created 1/5/2011 12:47:34 PM"
Backup of "VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\varda"
Backup set #1 on storage media #1
Backup set description: "Backup 00003"
Backup Method: Full - Back up virtual machines
The option to enable the restore of individual files and folders from a virtual machine backup was selected for this backup.
The Remote Agent for Windows Systems must be installed on the virtual machine to use Granular Recovery Technology to restore data.



Backup started on 1/5/2011 at 12:48:10 PM.
Backup Set Detail Information
Media Label: IMG000024
GRT backup set folder: C:\backups\IMG000024
V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:

Backup completed on 1/5/2011 at 12:48:21 PM.
Backup Set Summary
Backed up 0 files in 0 directories.
Backed up 1 virtual machines
Backed up 0 virtual machine disks
Processed 24,847 bytes in  11 seconds.
Throughput rate: 0.129 MB/min
Compression Type: None





            Server - FREYA
                  Set Information -
                  VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\VMware Data
                  Recovery
                        Backup Set Information
Family Name: "Media created 1/5/2011 12:47:34 PM"
Backup of "VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\VMware Data Recovery"
Backup set #1 on storage media #1
Backup set description: "Backup 00003"
Backup Method: Full - Back up virtual machines
The option to enable the restore of individual files and folders from a virtual machine backup was selected for this backup.
The Remote Agent for Windows Systems must be installed on the virtual machine to use Granular Recovery Technology to restore data.



Backup started on 1/5/2011 at 12:48:33 PM.
Backup Set Detail Information
Media Label: IMG000025
GRT backup set folder: C:\backups\IMG000025
V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:

Backup completed on 1/5/2011 at 12:48:38 PM.
Backup Set Summary
Backed up 0 files in 0 directories.
Backed up 1 virtual machines
Backed up 0 virtual machine disks
Processed 23,304 bytes in  5 seconds.
Throughput rate: 0.267 MB/min
Compression Type: None





            Server - FREYA
                  Set Information -
                  VMVCB::\\storm.domain.com\VCGuestVm\(DC)domain(DC)\vm\2003
                  test1
                        Backup Set Information
V-79-57344-38726 - Backup Exec failed to connect to virtual machine '\(DC)domain(DC)\vm\2003 test1' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.

Family Name: "Media created 1/5/2011 12:47:34 PM"
Backup of "VMVCB::\\storm.domain.com\VCGuestVm\(DC)domain(DC)\vm\2003 test1"
Backup set #1 on storage media #1
Backup set description: "Backup 00003"
Backup Method: Full - Back up virtual machines
The option to enable the restore of individual files and folders from a virtual machine backup was selected for this backup.
The Remote Agent for Windows Systems must be installed on the virtual machine to use Granular Recovery Technology to restore data.



Backup started on 1/5/2011 at 12:49:19 PM.
Backup Set Detail Information
Media Label: IMG000026
GRT backup set folder: C:\backups\IMG000026
V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:

Backup completed on 1/5/2011 at 12:49:30 PM.
Backup Set Summary
Backed up 0 files in 0 directories.
Backed up 1 virtual machines
Backed up 0 virtual machine disks
Processed 23,986 bytes in  11 seconds.
Throughput rate: 0.125 MB/min
Compression Type: None






      Job Completion Status
Job ended: Wednesday, January 05, 2011 at 12:49:31 PM
Completed status: Failed
Final error: 0xe000848c - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-33932


      Errors
      Click an error below to locate it in the job log
Backup- VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\vardaV-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:
Backup- VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\VMware Data RecoveryV-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:
Backup- VMVCB::\\storm.domain.com\VCGuestVm\(DC)domain(DC)\vm\2003 test1V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:


      Exceptions
      Click an exception below to locate it in the job log
Backup- VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\vardaV-79-57344-38726 - Backup Exec failed to connect to virtual machine '\(DC)ha-datacenter(DC)\vm\varda' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.

Backup- VMVCB::\\storm.domain.com\VCGuestVm\(DC)domain(DC)\vm\2003 test1V-79-57344-38726 - Backup Exec failed to connect to virtual machine '\(DC)domain(DC)\vm\2003 test1' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.

[Ben_L_]

Can you go into the job properties and under the VMware section, uncheck the box for GRT then click the Edit button (still in the VMware section) and uncheck the 3 check boxes there as well.  Then attempt to run the backup again?

[MKRT]

It again failed using the above config from Ben I.. 

Here is the output log:

Job Log: BEX_FREYA_00026.xmlJob Log for Backup 00003



      Completed status: Failed    See error(s)
      Expand AllCollapse All

      Job Information
Job server: FREYA
Job name: Backup 00003
Job started: Thursday, January 06, 2011 at 11:07:43 AM
Job type: Backup
Job Log: BEX_FREYA_00026.xml


Drive and media mount requested: 1/6/2011 11:07:43 AM
No appendable media could be mounted.
Switching to overwrite operation on scratch media.


      Device and Media Information
Drive and media information from media mount: 1/6/2011 11:07:43 AM
Drive Name: Backup-to-Disk Folder 0001
Media Label: B2D000001
Media GUID: {b7217ae6-531b-41ee-852b-2d29e4b79d81}
Overwrite Protected Until: 2/3/2011 11:07:43 AM
Appendable Until: 1/12/2011 11:07:43 AM
Targeted Media Set Name: Keep Data for 4 Weeks

All Media Used
 B2D000001

 IMG000027

 IMG000028

 IMG000029



      Job Operation - Backup
            Backup Options
Media operation - Append to media, overwrite if no appendable media is available.

Compression Type: Hardware [if available, otherwise none]

Encryption Type: None

WARNING: The option 'Verify after backup completes' was not selected.

Performing a verify operation to make sure that media can be read after the backup has completed is recommended.




            Server - FREYA
                  Set Information -
                  VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\varda
                        Backup Set Information
V-79-57344-38726 - Backup Exec failed to connect to virtual machine '\(DC)ha-datacenter(DC)\vm\varda' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.

Family Name: "Media created 1/6/2011 11:07:43 AM"
Backup of "VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\varda"
Backup set #1 on storage media #1
Backup set description: "Backup 00003"
Backup Method: Full - Back up virtual machines
The option to enable the restore of individual files and folders from a virtual machine backup was selected for this backup.
The Remote Agent for Windows Systems must be installed on the virtual machine to use Granular Recovery Technology to restore data.



Backup started on 1/6/2011 at 11:08:17 AM.
Backup Set Detail Information
Media Label: IMG000027
GRT backup set folder: C:\backups\IMG000027
V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:

Backup completed on 1/6/2011 at 11:08:26 AM.
Backup Set Summary
Backed up 0 files in 0 directories.
Backed up 1 virtual machines
Backed up 0 virtual machine disks
Processed 24,847 bytes in  9 seconds.
Throughput rate: 0.158 MB/min
Compression Type: None





            Server - FREYA
                  Set Information -
                  VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\VMware Data
                  Recovery
                        Backup Set Information
Family Name: "Media created 1/6/2011 11:07:43 AM"
Backup of "VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\VMware Data Recovery"
Backup set #1 on storage media #1
Backup set description: "Backup 00003"
Backup Method: Full - Back up virtual machines
The option to enable the restore of individual files and folders from a virtual machine backup was selected for this backup.
The Remote Agent for Windows Systems must be installed on the virtual machine to use Granular Recovery Technology to restore data.



Backup started on 1/6/2011 at 11:08:38 AM.
Backup Set Detail Information
Media Label: IMG000028
GRT backup set folder: C:\backups\IMG000028
V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:

Backup completed on 1/6/2011 at 11:08:43 AM.
Backup Set Summary
Backed up 0 files in 0 directories.
Backed up 1 virtual machines
Backed up 0 virtual machine disks
Processed 23,304 bytes in  5 seconds.
Throughput rate: 0.267 MB/min
Compression Type: None





            Server - FREYA
                  Set Information -
                  VMVCB::\\storm.mydomain.com\VCGuestVm\(DC)mydomain(DC)\vm\2003
                  test1
                        Backup Set Information
V-79-57344-38726 - Backup Exec failed to connect to virtual machine '\(DC)mydomain(DC)\vm\2003 test1' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.

Family Name: "Media created 1/6/2011 11:07:43 AM"
Backup of "VMVCB::\\storm.mydomain.com\VCGuestVm\(DC)mydomain(DC)\vm\2003 test1"
Backup set #1 on storage media #1
Backup set description: "Backup 00003"
Backup Method: Full - Back up virtual machines
The option to enable the restore of individual files and folders from a virtual machine backup was selected for this backup.
The Remote Agent for Windows Systems must be installed on the virtual machine to use Granular Recovery Technology to restore data.



Backup started on 1/6/2011 at 11:09:23 AM.
Backup Set Detail Information
Media Label: IMG000029
GRT backup set folder: C:\backups\IMG000029
V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:

Backup completed on 1/6/2011 at 11:09:34 AM.
Backup Set Summary
Backed up 0 files in 0 directories.
Backed up 1 virtual machines
Backed up 0 virtual machine disks
Processed 24,075 bytes in  11 seconds.
Throughput rate: 0.125 MB/min
Compression Type: None






      Job Completion Status
Job ended: Thursday, January 06, 2011 at 11:09:34 AM
Completed status: Failed
Final error: 0xe000848c - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-33932


      Errors
      Click an error below to locate it in the job log
Backup- VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\vardaV-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:
Backup- VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\VMware Data RecoveryV-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:
Backup- VMVCB::\\storm.mydomain.com\VCGuestVm\(DC)mydomain(DC)\vm\2003 test1V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error:


      Exceptions
      Click an exception below to locate it in the job log
Backup- VMVCB::\\opvm2\VCGuestVm\(DC)ha-datacenter(DC)\vm\vardaV-79-57344-38726 - Backup Exec failed to connect to virtual machine '\(DC)ha-datacenter(DC)\vm\varda' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.

Backup- VMVCB::\\storm.mydomain.com\VCGuestVm\(DC)mydomain(DC)\vm\2003 test1V-79-57344-38726 - Backup Exec failed to connect to virtual machine '\(DC)mydomain(DC)\vm\2003 test1' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.

[ZeRoC00L]

Have you seen this aricle:

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

Troubleshooting / Solution
1. Verify the media server can see the SAN disks and they are not marked as OFFLINE.
2. Ping the ESX Host by name from the media server.  Verify the media server can resolve the name and IP of the ESX host correctly.
3. Create a new user account and give it administrator rights in vCenter or the ESX host and attempt the backup again using the new user account.

[MKRT]

Yes I have seen that article.  And this goes back to my original question.   Does the Media Server need to have a connection to the SAN in order to backup the VMDKs?    We have multiple SANs, some are isolated such that the Media server can not connect to that subnet. 

The MEdia server will not have access to the SAN.   Can the symantec product back up the VMDKs through vsphere?  

[ZeRoC00L]

Yes, but with the option NBD, so the backup will go over the network.

[MKRT]

Well then I'm back at the beginning. 

I am using NBD trying to backup over the network and getting the above errors. 

[kp-nuts]

...and couldn't figure it out for ages.  This link helped find the cause of the problem I had.  However, I couldn't reinstall using the method that was suggested on this link, so I ran \BE\WinNT\Install\BE32\Install\Media\Symantec Backup Exec for Windows Servers.msi from the Backup exec install DVD and re-installed the option again from here.  After this I was able to back up my VM's