Symantec Backup Exec Vmware plugin
Created: 09 Feb 2012 | 8 comments
Hi,
I was wondering has anyone on these forums manage to successfully use the Symantec Backup Exec Vmware plugin? I have installed the plugin (v2.0.259.0) in vSphere client (v4.1.0) and logged into the backup server using domain admin credentials. Unfortunately it does not display any Protected machines. I have the Agent for VMWare installed on Backup Exec 2010 R3. I found the installation documenation to be quite limited.
Any suggestions greatly appreciated.
Thanks,
Eoin
Discussion Filed Under:
Comments
Make sure BE system logon account have all required rights
Add BE system logon account to Admin group on ESX
http://www.symantec.com/docs/TECH129645
and use them same to login
I have verified that the BE
Thanks for the suggestion. have verified that the BE system logon account has already been added to Admin group in vCenter and it still doesn't see any jobs.
Hi Eoin
1-You need to connect to the respective ESX or Vcenter on Vshpere plugin from where you have backed up those VMs. I.E. Just make sure you login to Vsphere client via ESX credentials if you have taken backups via ESX from backup selection list OR login to Vsphere client via Vcenter credentials if you have taken backups via Vcenter from backup selection list.
2-Make sure that you are connecting to same media server from where you have backed up the VMs via AVVI.
3-You should be able to view the AVVI backed up VMs status even though you have connected media server via a user having only backup operator rights. HOwever for validation and autorecovery, you would need extra admin credentials.
If this response answers your concern, please mark it as a "solution"
Hi RahulG, Thanks for
Hi RahulG,
Thanks for the info! I tried step 1 mentioned in your post, but when I log into vCenter using the same account used in Backup Exec to back up the vmdks I still can't see any jobs.
When you log onto Backup Exec through vCenter, which account should I use?
Thanks
I think the nomenclature is
I think the nomenclature is getting mixed up here, or perhaps expectations.
Typically you have an account that has backup permissions or use root in your vCenter environment.
This account, when you go into BackupExec and create a selection list or job, is what you would use when you add the vCenter host into the selection list via IP or FQDN
Watch this video, it explains 98% of what you want to do!
http://www.youtube.com/watch?v=Se-5OtXMZUk
The other 2%, is the fact they didn't show you how to add the vCenter server in the first place, so that you can browse it. Just right click there, and you can add it.
There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."
Hi Eoin
Please go through the below steps and verify if you have followed all of them:
1-Backup VMs ( via ESX or Vcenter from teh selection list ) using AVVI option.
2-Symantec Backup Exec Vmware plugin needs to be installed on the server where you have vShpere client installed as Symantec Backup Exec Vmware plugin sits inside the vShpere client.
3-After you install Symantec Backup Exec Vmware plugin, relaunch the vShpere client and login using ESX or Vcenter credentials. (NOTE: If you have backed up VMs via ESX in the backup job then you have to login to vShpere client through your ESX credentials BUT If you have backed up VMs via Vcenter in the backup job then you have to login to vShpere client through your Vcenter credentials). So you need to login to vShpere client using the same credentials which you have used while backing up your VMs in backup job.
4-Then go to Symantec Backup Exec Vmware plugin and login to the same media server (using IP or netbios name or FQDN) using your system logon account.
5-Once to connect to media server, you should be able to see all the VMs which were backed up from that media server.
Please let me know if you hav any queries.
If this response answers your concern, please mark it as a "solution"
Hi Eoin
were the above steps useful? did it resolve the issue?
If this response answers your concern, please mark it as a "solution"
Hi RahulG, I've only managed
Hi RahulG,
I've only managed to try some of the steps, which have not been successful yet. My colleague is looking after this now so I'll update when he gets back to me.
Thanks.
Would you like to reply?
Login or Register to post your comment.