Installation Robot de sauvegarde
Created: 31 Dec 2012 | 5 comments
bonjour,
j'ai installer backupExec 2010 dans une machine virtuelle , et je veux mon support de sauvegarde soit le robot,mon problème j'ai pas arriver a voir le robot de sauvegarde , comment je fais????
M.Salutations
Discussion Filed Under:
Comments 5 Comments • Jump to latest comment
Symantec does not recommend the use of a VM for the media server. As you have experienced, you would face problems accessing a real device, just like the problem you are facing. See this discussion and the documents that are referenced in it.
Backup Exec 2010 R3 Installed on a VMware vSphere 4 (ESXi 4.1 u1)guest machine | Symantec Connect Community
Hyper-V does not support pass-thru, so you would not be able to attach a tape drive to a Hyper-V VM.
Bonjour,
Je confirme ce que PKH vous a écrit. Le mieux serai d`installer le logiciel dans environnement physique afin que vous puissiez faire vos sauvegarde vers la bandothèque
Cordialement,
ref : http://www.symantec.com/docs/TECH146293
mais je suis en face de cette situation parce que le serveur Physique est endomagée a ce pb j'ai basculer vers machine virtuelle , mais pour instant j'ai pas une sauvegarde des données de ce nouveau serveur
le pb que suite au lien http://www.symantec.com/docs/TECH146293
7) Select the virtual machine that will use the tape device, and click Summary tab > Edit Settings....
8) Click the Hardware tab > Add.. Select SCSI Device from the list of device types and click Next.
-->SCSI Device indisponible
...you need to get the library configured within ESX first before configuring it from vSphere for the VM. The TN above is very misleading, and the ESX host needs to be rebooted too.
Here is the full TN from VMware around this, and check the Additional Information section:
http://kb.vmware.com/selfservice/microsites/search...
The TN you really want to follow is below:
http://www.symantec.com/business/support/index?pag...
Please follow it step-by-step. Be aware that to troubleshoot a SCSI tape library for instance, restarting the VM sometimes doesn't sort things out and you need to restart the ESX host itself! This affects any VMs running on the host unless you Vmotion them all off except for the BE server.
Thanks!
If you find this is a solution, please mark it as such.
Would you like to reply?
Login or Register to post your comment.