05-06-2011 12:17 PM
I have 4 out of the 12 child processes continuing to fail on the first run of the backus. I am using Replication Manager to copy the Exchange database. It was working fine for the first few weeks. Now 4 out of the 12 is failing but still completing successfully at the 2nd attempt. Just hoping we can run this successfully on the First attempt. Here are some logs.
(74) client timed out waiting for bpstart_notify to complete
Example of one of the details:
05/05/2011 01:00:56 - requesting resource snpmedia01-ltog3-robot-tld-1
05/05/2011 01:00:56 - requesting resource su29357.NBU_CLIENT.MAXJOBS.snpmedia01.corporate.smud.org
05/05/2011 01:00:56 - requesting resource su29357.NBU_POLICY.MAXJOBS.Exchange_2010_DAGs
05/05/2011 01:00:57 - Waiting for scan drive stop HPULTRIUM-LTOG3-06, Media server: snpmedia01
05/05/2011 01:00:58 - granted resource su29357.NBU_CLIENT.MAXJOBS.snpmedia01.corporate.smud.org
05/05/2011 01:00:58 - granted resource su29357.NBU_POLICY.MAXJOBS.Exchange_2010_DAGs
05/05/2011 01:00:58 - granted resource H02340
05/05/2011 01:00:58 - granted resource HPULTRIUM-LTOG3-06
05/05/2011 01:00:58 - granted resource snpmedia01-ltog3-robot-tld-1
05/05/2011 01:00:58 - estimated 109818558 kbytes needed
05/05/2011 01:01:00 - started process bpbrm (pid=6212)
05/05/2011 01:01:02 - connecting
05/05/2011 01:01:02 - connected; connect time: 0:00:00
05/05/2011 04:01:05 - Error bpbrm (pid=6212) from client snpmedia01.corporate.smud.org: ERR - bpstart_notify timed out
05/05/2011 04:01:06 - Error bpbrm (pid=6212) could not send server status message
05/05/2011 04:01:08 - end writing
client timed out waiting for bpstart_notify to complete (74)
05-09-2011 12:26 AM
Hi,
The error is an indication that the script (bpstart) did not finish with in the set timeout. The fact that it works on second attempt should be an indication that your script is working fine. To avoid the error, adjust the timeout to a higher value.