Tommojunior
MIS
Hi,
I'm running 4.5MP3 on hpux. We are looking to use the bpstart_notify and bpend_notify scripts to perform our own scripted and sql backups of some large oracle backups.
Some of these "hot" or "cold" pre script can last upto five hours, so I've set BPSTART_NOTIFY to 32767 (max allowed) in bp.conf on the master.
I've successfully ran some "sample" bpstart_notify scripts with just a simple "sleep 1000" inside and all looks good.
NOW TO THE POINT!:
The supplied (standard) bpstart_notify script which is in goodies has a warning about long scripts holding up the start of other clients policies:
# If this script will not complete within a few seconds, you should set
# the BPSTART_TIMEOUT in the /usr/openv/netbackup/bp.conf file on the server.
# You should also be aware that the time taken by this script will delay
# the initiation of other client's backups".
To put this to the test, I started my "sleep 1000" policy and then started another policy on another client and even another policy on the same client. All appears fine, no issues to date (they DONT wait for the "sleep 1000" script or policy to complete)
Is the warning a load of cobblers, or is there some other side-effect I need to be aware of? Its likely that I'll be running many of these pre-scripts across dozens of servers.
All thoughts welcome!
Cheers,
Tommojunior
I'm running 4.5MP3 on hpux. We are looking to use the bpstart_notify and bpend_notify scripts to perform our own scripted and sql backups of some large oracle backups.
Some of these "hot" or "cold" pre script can last upto five hours, so I've set BPSTART_NOTIFY to 32767 (max allowed) in bp.conf on the master.
I've successfully ran some "sample" bpstart_notify scripts with just a simple "sleep 1000" inside and all looks good.
NOW TO THE POINT!:
The supplied (standard) bpstart_notify script which is in goodies has a warning about long scripts holding up the start of other clients policies:
# If this script will not complete within a few seconds, you should set
# the BPSTART_TIMEOUT in the /usr/openv/netbackup/bp.conf file on the server.
# You should also be aware that the time taken by this script will delay
# the initiation of other client's backups".
To put this to the test, I started my "sleep 1000" policy and then started another policy on another client and even another policy on the same client. All appears fine, no issues to date (they DONT wait for the "sleep 1000" script or policy to complete)
Is the warning a load of cobblers, or is there some other side-effect I need to be aware of? Its likely that I'll be running many of these pre-scripts across dozens of servers.
All thoughts welcome!
Cheers,
Tommojunior