Skip to main content

Acronis Cyber Protect 15 Crashes Connection to ESXi Datastore

Thread needs solution

Can anyone shed some light on why ACP15 might kill my ESXi datastore connection in this scenario?

Here's the setup:

HOST:          ESXi v6.0.0 w/ NFS datastore mount to NAS, controlled by vSphere v6.0.0
STORAGE:  Seagate 2-Bay NAS with SMB & NFS services enabled
VM:              Win10 w/ ACP15 default installation, with SMB mapped drive for the backup

 

Here's the scenario: (VM runs normal when ACP15 is not performing the backup)

I installed ACP15 in the Win10 VM selecting the default settings & after configuring ACP15 through the Web console to backup the VM to the mapped drive, when the backup initially starts the ESXi host maintains connection to the datastore just fine & I'm still able to work within the VM. Upon the backup reaching ~20% I lose response to the VM, PINGs to the VM come back as "Request timed out.", & the ESXi host loses connection to the datastore on the NAS which can be verified through vSphere. The only way to recover is for me to reboot the NAS.

Communication to the NAS is never lost during this time as I'm still able to log into it, enable/disable services, & reboot through the web interface. ACP15 is running both server/agent in the same VM (which I'm suspecting might be a reason). Upon rebooting the NAS, ESXi is able to reconnect to the datastore & I can restart the VM without issue. I only have the 1 VM running as this is a test environment before deploying to other VMs.

 

Has anyone experienced this problem or does anyone have any idea what might be the cause of the problem? I've thought about installing ACP15 on my Win7 physical machine & just install the agent on the Win10 VM to see if that works but I only have the single ACP15 license to wasn't sure if I could do that without having to purchase another license.

Any info may be helpful.

0 Users found this helpful

Well, just in case someone has the same issue, here's what my fix was for this problem... the only "Backup Location" that actually worked was to use SFTP. Once I used that option, the backup worked just fine.

SMB, NFS, regular \\server notation .... wouldn't work but I put in "sftp://server:/share" & voila. Weird that *that* was the only thing that worked for me but would love to know if someone else was able to get it to work using a different setup.