bpend_notify.policy.bat not being called
Created: 03 Oct 2012 | 12 comments
Hi,
In some case bpend_notify.policy.bat not beeing called. I tried restarting the net backup services and it starte working fine. Any reason for this? Which service does run this bat file?
Thanks in advance
Veeresh Hosur
Discussion Filed Under:
Comments 12 Comments • Jump to latest comment
What version(s) of NetBackup? What type of backup?
bpend_notify.policy.bat - I presume the "policy" here is actually the name of the policy in question?
Regards Andy
"Have you still got the box it came in?"
I would check/verify as follows:
1. Ensure spelling is 100% correct. Remember that NBU is case sensitive.
2. Check that Windows Explorer did not add .txt extension
3. Verify that there are no "."s in the policy name (e.g. Windows.Clients). "." is allowed in policy name but does play well with NBU notify scripts.
4. Enable bpbkar log on client for detailed troubleshooting.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
also check if this script is placed in <install_path>¥NetBackup¥bin, and if the policy type is MS-Windows.
bpstart_notify and bpend_notify are not called with DB agent's policy types.
Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan
Thanks to all for the reply. To update you all there is no spelling mistake, the bat file is in bin directory. Initially it didn't invoke however when restarted all the services of Netbackup it started working fine. Any reason?
Thanks
Veeresh Hosur
Impossible to say without bpbkar logs.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Hi Maranne,
I am getting the following lines in bpbkar logs while beendnotify is not executed
Seems like the connection was broken before bpend_notify was due to be called.
will restore -- where there is a Will there is a way
Wr,
Thanks for the quick response. But I observe is once I restart the net backup services it bpend_notify.<policy>.bat will be invoked properly. Not getting the reason. Please find the bpbakr logs completely copied below
TCP 10054: Connection reset by peer
Solution
1. Obtain and install the latest Microsoft service pack. There have been significant changes to the TCP/IP stack.
2. Ensure that the network settings are correct (NIC, Hub, Switch, Router, etc.).
3. Ensure that the network settings are correct (the ports are set to full duplex VS half duplex and it is the same across the network. Avoid Auto Sense if possible).
4. Check the timeout settings on the network interface card (NIC) (try increasing the timeout value).
5. Replace the NIC with a different brand or model.
The 10054 error is 'Connection Reset Error'. This is a Microsoft Winsock error. It means that somewhere between the client and the server, the connection was reset. Once the VERITAS software receives this error, it is unable to continue the backup.
This error has been attributed to a variety of causes:
1. A temporary disruption in the network communication (i.e. happens once in a great while)
2. Bad network interface card (NIC) on the client
3. Bad NIC on the server
4. Faulty routers or routers that are not set to the correct duplex
5. Other programs (applications) cause the VERITAS NetBackup connection to drop
will restore -- where there is a Will there is a way
Hi Wr,
Thanks for the reply. Forgot to mention that backup is being run on the same host NBU mediaserver installed. If there is client is involved then I understand it needs communication. Strange thing is once I restart all the services of NBU by bpdown and bpup command it works fine. Any reason for that?
Thanks
Veeresh Hosur
Even on the same machine, server and client talk to each other over standard network ports.
Perhaps there is some clue in the Windows Event Viewer.
will restore -- where there is a Will there is a way
Hi Wr,
Not finding any event raised for this in Event viewer. Any other trouble shooting, to find out the root cause?
Thanks
Veeresh Hosur
Would you like to reply?
Login or Register to post your comment.