Skip to main content

You do not have access rights to this file

Thread needs solution

27/02/2017

Hi,

I previously used vmWare Backup v9 in my vSphere 5.1 environment. I have now upgraded this to vSphere 6.5 and so was very keen to seen and start working with AB12u3.

Much to my disappointment, i've had a few issues. I've tried very hard to work this through with the Acronis support team, but i've been waiting for an answer now for nearly two weeks now. I'm hoping someone on the forum will be able to assist.

It's not a very complex setup, couple of hosts, couple of netapp SAN's, management server running AB12u3. vCenter is an appliance. I have deployed AB12 as a virtual appliance to each host of the vCenter. I used the necessary Administrator Password and the appliances have been installed and are powered on.

ANY backup that I attempt to perform, the snapshot is fine and then, part way through the backup, I get the error, "You do not have access rights to this file".

If I browse the datastore, from the vCenter, using the same credentials as those used when deploying the virtual appliance from the Acronis Management Console and those used to log into the Acronis Backup Management Console. I can even copy the ???-vss_manifests199.zip from the datastore to another location, but the backups continue to fail with this error.

I have attached a copy of the error log that I get on screen.

Any help would be appreciated, I am not really getting anywhere with Acronis Support, I am hoping someone may have had this issue and resolved it.

Many thanks in advance.

Dave S. Chunilal

 

Attachment Size
error_24022017.txt 3.64 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Dave,

The error shown in the attached log file typically indicates DNS issues in network: the machine which has Agent for VMware (Windows or appliance) installed cannot resolve the ESXi hosts names to IP addresses even if the vCenter hostname is accessible properly. Note that the ESXi hosts addresses which appears under vCenter from vSphere client (e.g. how these hosts were added to vCenter) must be properly resolved to IP from each agent side which is configured to work with this vCenter.

The solution for this problem would be to configure DNS server address on appliances side: open appliance console from vSphere client -> check networking -> set DNS server address. After that you can switch to command prompt to confirm that name resolution works properly via Ctrl+Shift+F2/F1 (switch back to GUI via Alt+F1/F2) and issuing "ping [esxihost_name]" . An alternative solution would be to add corresponding IP/name combination into /etc/hosts file on appliance side: you can enable SSH access to appliance via "/bin/sshd" command and then connect to it via WinSCP tool (login/pass = root/root) in order to edit local files on appliance.

Thank you.

27/02/2017

Hi Vastly,

One thing I forgot to mention is that if I install an Agent on the VM, then the backup is successful? So could this still be a DNS issue?

Regards

Dave S. Chunilal

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Dave,

In case agent is installed inside the VM the backup flow is independent from the vSphere infrastructure so here DNS is not an issue, since the agent inside VM doesn't need to resolve the DNS names of the ESXi hosts at all. My comment was only about the name resolution from Agent for VMware (appliance) side.

Thank you.