What is the expected behaviour when:
- NBU master crashes and reboots (or is brought online on failover node in a cluser)
- NBU master is stopped forcefully (I believe bp.kill is used) and then restarted (on the same node, or on failover node in a cluster)
- NBU master is stopped cleanly (if such option exists) and then restarted (I don't believe this is applicable to a cluster as I don't THINK there is anyway to configure VCS NBU agent to cleanly stop NBU master)
Whenever NBU master has been restarted in our environment (a VCS cluster), we see:
a. All jobs are killed so they have to restart from scratch.
b. Jobs are not killed cleanly so in particular for SAP backups, the Oracle database is left in backup mode, meaning when the backup is restarted it fails.
So I am hoping there is someway to cleanly stop the NBU master (preferably integrated into the VCS cluster) so that:
- Ideally the backup jobs do not stop, so that the media servers just buffers information about files being backed up so that this can be transferred to NBU master when it comes back up (with some timeout, so if NBU master doesn't come backup, the backup job fails). Alternatively the backup could pause (with timeout) until NBU master returns
- If there is some reason 1 cannot be done, then jobs should be killed cleanly, so that databases are not left in backup mode.
I did look in the "admin volume 1" guide and this says when shutting down NBU "make sure that no jobs are running", but this will never be the case in our environment, so for example there are 32 active jobs at the moment and we could potentially have over 100 active jobs, and in the docs, I coudn't find any guidance as to what you do if you have jobs running.
Mike