Unsolved
This post is more than 5 years old
21 Posts
0
8079
Unable to obtain backup status from vProxy after 5 attempts
Hello guys,
Some backups are failing with the following error :
164541 10/01/2017 03:37:45 AM nsrvproxy_save NSR error "vmname": Unable to obtain backup status from vProxy after 5 attempts, failing the backup: Received an HTTP code: 404, libCURL message: "Operation timed out after 1800618 milliseconds with 0 out of -1 bytes received", vProxy message: "Error received from vProxy ="-404: Resource not found: c92f57e4-8c25-4cc4-a081-562b8c39e4dd".
", url: "https://vproxy:9090/api/v1/BackupVmSessions/c92f57e4-8c25-4cc4-a081-562b8c39e4dd", body: " ".
156203 10/01/2017 03:37:51 AM nsrvproxy_save NSR warning "vmname": Unable to download vProxy Session log into file '/nsr/logs/policy/WF/Policy/358869-vmname-2017-10-1-3-37-45.log': Possible wrong vProxy hostname or port, resource path not found. Received an HTTP code: 404, libCURL message: "Operation timed out after 1800618 milliseconds with 0 out of -1 bytes received", url: "https://vproxy:9090/api/v1/BackupVmSessions/c92f57e4-8c25-4cc4-a081-562b8c39e4dd/log".
164546 10/01/2017 03:37:51 AM nsrvproxy_save NSR error vmname: Backup failed.
146000 10/01/2017 03:37:51 AM nsrvproxy_save SYSTEM critical The size of proxied data written has not been set.
142169 10/01/2017 03:37:51 AM nsrvproxy_save NSR warning Save-set ID '399523354' (client 'vcenter': save-set 'vm:5034b93a-c988-b3ef-a823-8a650f5a5421:vcenter') is aborted.
0 10/01/2017 03:37:51 AM nsrmmd NSR error 10/01/17 03:37:51 ddirasm: save set vm:5034b93a-c988-b3ef-a823-8a650f5a5421:vcenter for client vcenter was aborted and removed from volume
Looks like it's a timeout issue but the vProxy is not overloaded and is handling other backups successfully.
In this config, i have :
3 vProxys for around 150 VMs
Max 30 VMs per group
Parallelism set to 15
timeout set to 60
1 hour delay between each VMs group
Any idea what could cause this ?
thanks
Julien
Karthik_N1
25 Posts
0
October 3rd, 2017 02:00
Hi,
Please check if the VM is in "Orphaned state or powered off". Also if VM has been vMotioned to any other host or datastore.
Thanks,
Karthik N
Julien_K
21 Posts
0
October 3rd, 2017 23:00
Hi,
all the VMs are up and running.
Some of them may have been moved to a new datastore but only once, not every day
thanks,
Julien
besal
2 Posts
0
September 25th, 2018 08:00
Hi,
has this problem been resolved?
I get similar errors during VM backups.
NetWorker v9.2.1.0 Build163
8 x vProxies v2.1.1-41_1
1 x Data Domain DD9300 v6.1.2.5-595467 +ECS
Like you mentioned the proxies are working fine. Other backups are done perfectly.
I have one policy/group with 220 VM's and there are:
- 3 with this cancelled error
- 8 others showing hard disk info (closin, queued, percentages)
Although these are shown as failed, in the logs they are successful and I can even
select them for restore without any problems
- 3 others with "Unable to backup virtual disk "Hard disk 2""
regards
Steven Aldenkamp
Julien_K
21 Posts
0
September 27th, 2018 01:00
Hello,
Yes this issue has been resolved with some tuning.
what are your parallelism and inactivity timeout settings for vmware
policies ?
thanks,
Julien
Le mar. 25 sept. 2018 à 17:29, besal a
écrit :
besal
2 Posts
0
September 27th, 2018 07:00
For most actions in the principal VM policy (hotadd) we have 25 parallellism and 30 for inactivity timeout.
For a special nbd policy it's 10 parallellism and 30 for inactivity timeout.
regards
Steven
chrisv.dellemc
1 Message
0
April 9th, 2019 19:00
Hi,
We are having the same issues. Issue started off a back of restoring vms to a different data store due to an SRM failure. Since the restores, we have been getting these type of errors during backups.
I have been also told that the vms contlunally move from data store to data store. ??
Can you explain the relation of the error if the vm have been moved to another host or datastore?