08-02-2016 09:10 AM - edited 08-02-2016 09:15 AM
I have a backup pointed to a vCenter on another site, I realize that my policy starts and takes too long to start the streams. When I check my vCenter I see many snapshots created before the backup start traffic information. In summary a backup with a maximum time of 02 hours this taking 08 hours, when it ends with error "snapshot error encountered (156)."
Situation my vCenter:
http://i66.tinypic.com/2yn2l94.jpg
My policy freezes at this point.
8/2/2016 12:40:24 PM - Info nbjm(pid=8912) starting backup job (jobid=863222) for client MEDIA_SERVER, policy TESTE_ROD, schedule Diario
8/2/2016 12:40:24 PM - Info nbjm(pid=8912) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=863222, request id:{5E607228-0E23-4F7B-890E-C368050E29EA})
8/2/2016 12:40:24 PM - requesting resource rodsbkp02-hcart2-robot-tld-3
8/2/2016 12:40:24 PM - requesting resource cansbkp03.NBU_POLICY.MAXJOBS.TESTE_ROD
8/2/2016 12:40:24 PM - granted resource cansbkp03.NBU_POLICY.MAXJOBS.TESTE_ROD
8/2/2016 12:40:25 PM - estimated 0 Kbytes needed
8/2/2016 12:40:25 PM - begin Parent Job
8/2/2016 12:40:25 PM - begin Application Resolver, Start Notify Script
8/2/2016 12:40:25 PM - Info RUNCMD(pid=6068) started
8/2/2016 12:40:25 PM - Info RUNCMD(pid=6068) exiting with status: 0
Status 0
8/2/2016 12:40:25 PM - end Application Resolver, Start Notify Script; elapsed time: 0:00:00
8/2/2016 12:40:25 PM - begin Application Resolver, Step By Condition
Status 0
8/2/2016 12:40:25 PM - end Application Resolver, Step By Condition; elapsed time: 0:00:00
8/2/2016 12:40:25 PM - begin Application Resolver, Resolver Discovery
08-02-2016 02:16 PM
snapshot error encountered (156) indicates.. backup job is not even started.. job got failed during the snapshot phase..
what is the error messge that you see for this VM in Vcenter related to sanphost?
08-31-2016 07:04 AM
Hello RamNagalla thanks for the feedback!
In vCenter we did not have an error in creating the snapshot was created started, however he created infinitely many snaps ending to terminate the backup due to failure in the assembly, unfortunately the problem normalized and could not identify the root cause. Thank you as well.
08-31-2016 07:40 AM
We can only hope that you do not wait another 4 weeks to reply....
Seeing that this is a remote location, can you check if firewall ports are open?
NetBackup Network Ports Reference Guide
NetBackup must connect to TCP port 443 to access the vCenter server. NetBackup
can connect to the vCenter server only through this port for information such as the
VM discovery requests, snapshot creation and deletion, and so on.
The backup host must also connect to the TCP port 902 on the ESX/ESXi hosts.
In specific cases, the backup host must also connect to the TCP port 902 on the
ESX/ESXi hosts.