Jon – Another update for you.  I wound up opening a ticket with Symantec this weekend to troubleshoot this issue further.

 

No surprise, there are some bugs in v7.0 pertaining to vStorage that will be addressed in v7.1 (due to be released in August 2010).  This is a documented bug, see the following articles:

http://seer.entsupport.symantec.com/docs/347447.htm

http://seer.entsupport.symantec.com/docs/346839.htm            

 

As a work around to perform the restore, support had me delete my credentials for the vCenter server and add credentials for the individual ESX host which allowed me to perform the restore.  They said this issue also worked in the reverse scenario where you have already specified credentials for the individual ESX servers (so you would have to delete them and add the vCenter server.)

 

Try deleting your credentials for the ESX server leaving only the vCenter credentials.  That might fix your issue.

 

FYI – You might also ensure you use the FQDN for the vCenter and ESX servers throughout your configuration.  In a lab that I have this working in, I had used FQDN throughout and it worked fine.  Using the short name in another environment  caused this issue for me.

 

Additionally, make sure the user you are using to interface with vCenter/ESX has the appropriate permissions.  You might try and just give the user full administrator access propagated down through the data center and then start tightening the permissions if this resolves the issue.

 

Best of luck,

Tom

 

 

 

Joh – Interesting… I’m doing testing in a lab and now getting your same error.

 

Comparing my logs from an environment that works to one that is failing… in the bpVMutil log:

 

The line immediately following:

SetTimeoutsAndLogging: vmcloglevel=0

 

Should read:

get_vSphere_VMs: Processing datacenter XXXX

 

However, I’m now also getting:

                vmwareLogger: CreateVirtualMachine: SYM_VMC_ERROR:  FAILED_TO_GET_HOST_MOR

 

I’m continue to research… will let you know if I find anything.

 

-Tom

 

 

 

 

Thanks Tom,  I’ll double check my networking (I’m using local hosts files), but I think that’s all setup fine.  Hopefully my case with Symantec will lead somewhere.

 

Cheers,

Jon

 

 

 

John – I’ve been “playing” with vStorage quite a bit. 

 

Regarding the restore to alternate location, I’ve been able to restore to an alternate location but with some issues (see my post here: https://www-secure.symantec.com/connect/forums/virtual-machine-recovery-issues).

 

Couple things to check:

1.       Make sure you are restoring to your VM Backup Host

2.       Make sure your DNS (forward and reverse) resolves the hostname of the vCenter and all ESX hosts

3.       Make sure your VM Backup host can ping the vCenter and all ESX hosts

 

-Tom

My Website: http://www.tcpdump.com

 

 

 

 

 

 

Hello all,

I continue to find new vStorage API backup nuances for Netbackup 7 (most recently discover vCenter crendentails are insufficient to backup lab manager deployed VM’s,  you need to run as root on the ESX servers themselves). 

 

Now I’ve noticed that if you backup a client using ESX Server credentials,  instead of vCenter credentials,  restoring to an alternate location fails.

 

What happens is:

1)      The backup completes normally

2)       Select the guest image for restore, and the backup server as the destination client, and start the Virtual Machine Recovery wizard

3)      Select “Alternate Location” on the first screen, and then “Next”

4)      The next screen hangs trying to populate the Datstore and Resource Pool dropdown menus (needed to perform the alternate location restore)

 

Anyone know if  this expected or is there a timeout/etc that needs to be adjusted?  I have checked the bpvmutil logs, and I see the following errors:

 

-          SYM_VMC_ERROR: FAILED_TO_GET_MOR_BY_NAME

-          bpVMutil main: EXIT STATUS 11: system call failed

-          vmcGetObjDetails for HostRoot failed with status 14

 

Thanks,
Jon

 

====================================================================================

La version française suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential information, and the Bank of

Canada does not waive any related rights. Any distribution, use, or copying of this

email or the information it contains by other than the intended recipient is

unauthorized. If you received this email in error please delete it immediately from

your system and notify the sender promptly by email that you have done so. 

------------------------------------------------------------------------------------

Le présent courriel peut contenir de l'information privilégiée ou confidentielle.

La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion,

utilisation ou copie de ce courriel ou des renseignements qu'il contient par une

personne autre que le ou les destinataires désignés est interdite. Si vous recevez

ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à

l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre

ordinateur toute copie du courriel reçu.

_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

====================================================================================

La version française suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential information, and the Bank of

Canada does not waive any related rights. Any distribution, use, or copying of this

email or the information it contains by other than the intended recipient is

unauthorized. If you received this email in error please delete it immediately from

your system and notify the sender promptly by email that you have done so. 

------------------------------------------------------------------------------------

Le présent courriel peut contenir de l'information privilégiée ou confidentielle.

La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion,

utilisation ou copie de ce courriel ou des renseignements qu'il contient par une

personne autre que le ou les destinataires désignés est interdite. Si vous recevez

ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à

l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre

ordinateur toute copie du courriel reçu.