Direkt zum Inhalt

P2V Recovery in VMWare: Using virtual appliance and bootable media vs virtual appliance and AMS

Thread needs solution

Is there anything I'm losing in the quality of the recovery of a backup of a physical PC to a new VMware virtual machine if I perform the recovery using a new blank VM I created and booted using Acronis bootable media vs recovering it using the AMS console and targeting a new vm and let Acronis create the VM and recover it? In other words, does the AMS console method perform any steps the other method does not 

I ask because I'm seeing performance problems because the AMS console -> virtual appliance recovery method is routing all of the data through a single Acronis virtual appliance and I have 13 ESXi hosts and 140 backups to recover/convert and I cannot choose the acronis appliance(s) (I have 5).

Thanks

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi,

Both methods practically do the same thing. The main drawback from using bootable media method is that you'll have to create VM beforehand and configure it to boot from the bootable media, while when doing recovery via virtual appliance, the new VM (target for recovery) is created automatically so using appliance method should be more convenient.

Note that you can directly select the agent (appliance) which will be performing recovery into VM - to do this, simply choose required appliance from the list of "Machine to browse from...", while browsing the archive for recovery in Backups -> Locations section of web console. The agent which performs the browsing will be also performing the recovery (e.g. all the traffic will go through it).

Thank you.