Direkt zum Inhalt

Replacing Acronis Backup for VMware v9 with Acronis Backup 12.5

Thread needs solution

Just wondered why Acronis think this is a sensible thing to do when Acronis Backup for VMware is the better VMware solution and as yet Acronis Backup 12.5 cannot properly handle the backup archives created by Acronis Backup for VMware?

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

Hi Andrew,

While Acronis Backup for VMware is indeed a great product, the core architectural specifics of it do not allow us to properly evolve this project and include more functionality (keep it up-to-date at least) into it. For example it lacks vSphere 6.5 support and it's technically nearly impossible to make it happen with this product, because it's 32-bit, while for proper vSphere 6.5 support 64-bit architecture is required. Recovery from archives created by Acronis Backup for VMware via Acronis Backup 12.5 is also limited because if these core differences, but still full VM and/or files/folders recovery is possible (not application-level though).

Also we're planning to implement "all-in-one appliance" concept with Acronis Backup 12.5 (planned for the next update, coming by the end of this year) so that deployment of this version would be as easy as it is with Acronis Backup for VMware.

Thank you.