if a media server crashes, what happens to the catalog database?

[daydok]

i understand that procedures need to be followed if de-commissioning a media server, but what happens if it just crashes, and netbackup looks for it? will the catalog crash, and halt ALL backup operations? (assuming more than one media server is present in the domain). thanks for any input.

 

[Stumpr]

From VERITAS admin manuals:

NetBackup 5.0

SERVER_CONNECT_TIMEOUT specifies the number of seconds that the master server
waits before timing out when connecting to a media server. Default: Timeout period is 30
seconds.
You can add this option to the /usr/openv/netbackup/bp.conf file on NetBackup
master servers.
The following example permits a timeout of 60 seconds:
SERVER_CONNECT_TIMEOUT = 60


NetBackup 4.5
SLAVE_CONNECT_TIMEOUT
Specifies the number of seconds that the master server waits before timing out when
connecting to a media server. Default: Timeout period is 30 seconds.
You can add this option to the /usr/openv/netbackup/bp.conf file on NetBackup
master servers.
The following example permits a timeout of 60 seconds:
SLAVE_CONNECT_TIMEOUT = 60

 

[daydok]

thanks stumpr. so what happens when i set the timeout to 60 seconds, and the media server is still out (does not reply)? does that halt the backup schedule for that particular media server (and all clients attached to it), or does it corrupt the entire catalog, halting ALL jobs by the master server?