Skip to main content

ESXi 6.5 and vcenter 6.5 support for agentless backup

Forum Member
Posts: 5
Comments: 26

after upgrading from esxi 6 to 6.5 the acronis esx appliances crashed. so i decided to update acronis to the latest 10.7 build 50058 and redeploy the appliance. unfortunately this had never been finished.

so my question is, when will there be a fix? atm i'm not able to backup any vm agentlessly.

Forum Star
Posts: 22
Comments: 2534

Top

Hi,

Support for vSphere 6.5 in Acronis Backup Advanced 11.7 is planned for future updates (internal ID: ABR-103674). The currently available builds do not support it officially (some functionality may work though).

Thank you.

Forum Member
Posts: 5
Comments: 26

Top

is it possible to get a ftf of the latest developer build? i cannot downgrade to esx 6.

whats the username and password i use to add machine to ams when the appliance is deployed manually?

ok never mind. after rebooting the appliance vcenter creds got accepted.

Forum Star
Posts: 22
Comments: 2534

Top

Hi,

There are no builds of 11.7 which have specific fixes for vSphere 6.5 support yet. What we know won't work for sure is 1) backup/recovery of a VM which has new NVME controller attached; 2) appliances deployment from AMS. Other than that backup and recovery of VMs should work including usage of Windows based Agent for VMware (alternative to appliance).

If you add appliance manually to AMS then username/password would be root/root or you can also use the vCenter/ESXi credentials configured in appliance GUI. 

Thank you.

Forum Member
Posts: 5
Comments: 26

Top

manual deployment fo the appliance only works when deploying from url. local file doesn't work.

Beginner
Posts: 0
Comments: 1

Top

I have been facing the same problems.  Here is what I have found out so far.

1. Imported the Backup Agent VM into Fusion on my MAC and exported it again.  This allowed me to import the new OVF into vCenter 6.5

2. I have (2) Vmware backup agents deployed, which have succesfully registered each of my ESXi hosts

3. I have added (1) VMware backup agent to my AMS using the host credentials, but cannot get the other VMware backup agent registered because AMS says that ID is already registered.

4. I have not been able to take any agentless backups because the backups will fail.  I cannot really get much support because 11.7 doesn't support vSphere 6.5 yet.

I currently have agents deployed to all my workstations and servers, but it still leaves my ESXi hosts vulnerable.

Beginner
Posts: 0
Comments: 1

Top

Hi,

 

we made an updgrade of ESXi 6.0 to 6.5. At this time ESXI6.5 is not new. Why it takes so long by Acronis to deliver a new Acronis Backaup Advanced for VMware which supports ESXi 6.5? A company who is actual in time didn't need so much time to ship a new version for actual Software. At which time I can expect a version für ESXi 6-5?

Kindly regards,

 

Martin Mühlhan

Forum Star
Posts: 22
Comments: 2534

Top

Hi Martin,

We're currently in process of preparing a new version of Acronis Backup Advanced: v12 - this version is x64 bit based and therefore won't have problems supporting vSphere 6.5. Some info on the reasons: vSphere 6.5 can be supported only by certain VMware VDDK versions which are all provided by VMware only in x64 bit format - hence the difficulty to support vSphere 6.5 in Acronis Backup v11.7 which is fully x32 bit.

The new v12 is planned to be released in the end of May and after that v11.7 will be supported in maintenance mode (no new features - only bug fixes/critical updates).

We can also provide a workaround for 11.7 on demand - there is a special x64 bit appliance (with certain limitations though) - you can request it from our support team by referring to the following internal KB article ID: 59602 .

Thank you.

Beginner
Posts: 0
Comments: 2

Top

Just tried to upgrade my acronis appliance and failed. Any news on this? ESXi 6.5 has been releasen in November 2016 and still no update?

My ticket is already open for 1 hour, without answer from support :-(

 

Cheers

MrBeta

Beginner
Posts: 0
Comments: 2

Top

Allright here is a easy workaround:

Have an old ESXi Host (<6.5) and deploy appliance to this host. Connect to appliance via vSphere Client and change Name, ESXi-Host and IP if needed. Shutdown appliance and migrate to new host. Start appliance and recheck if it is connected to new host and visible in AMS.

Enjoy backup as before :-)