Problem

STATUS CODE 150: Backups fail with a NetBackup Status Code 150 (termination requested by administrator), despite no administrator intervention, after a client is moved from an old master server to a new master server.

Solution
Overview: Backups fail with a NetBackup Status Code 150 (termination requested by administrator), despite no administrator intervention, after a client is moved from an old master server to a new master server. Troubleshooting: Enable the bpbrm and bptm log files on the media server, and the bpbkar log file on the client server. Log files: A review of the bpbrm and bptm log files (on the media server) and the bpbkar log file on the client shows the backup job going active and the backup image in the process of being transferred from bpbkar to bptm when the problem occurs. The bptm log shows the media mounted and positioned and received data from the only/one stream in the MPX group.
16:10:18.148 [1452.3324] <4> write_backup: begin writing backup id <backupid>_1165874934, copy 1, fragment 1, to media id ABC123 on drive index 0 16:10:18.148 [1452.3324] <2> signal_parent: set bpbrm media ready event (pid = 3744) 16:10:18.148 [1452.3324] <2> write_data: ndmp_dup_max_frag is set to 0 16:10:18.148 [1452.3324] <2> write_data: twin_index: 0 active: 1 dont_process: 0 wrote_backup_hdr: 0 finished_buff: 0 saved_cindex: 0 twin_is_disk 0 delay_brm: 0 16:10:18.945 [1452.3324] <2> write_data: absolute block position prior to writing backup header(s) is 8, copy 1 16:10:18.945 [1452.3324] <2> io_write_back_header: drive index 0, <backupid>_1165874934, file num = 3, mpx_headers = 0, copy 1 16:10:18.945 [1452.3324] <2> write_data: completed writing backup header, start writing data when first buffer is available, copy 1 16:10:18.945 [1452.3324] <2> write_data: first write, twin_index: 0 cindex: 0 dont_process: 1 wrote_backup_hdr: 1 finished_buff: 0 16:10:18.945 [1452.3324] <2> write_data: received first buffer (65536 bytes), begin writing data

The bptm log then reports that it's waiting for its child to exit, writes the empty backup header, and exits with a NetBackup Status Code 150.
16:14:26.128 [1452.3324] <2> wait_for_sigcld: waiting for child 2876 to exit, timeout is 3600 16:14:26.128 [1452.3324] <2> io_terminate_tape: writing empty backup header,

drive index 0, copy 1 16:14:26.128 [1452.3324] <2> io_terminate_tape: reposition to previous tapemark and rewrite header <==SNIP==> 16:14:59.895 [1452.3324] <2> mm_terminate: EXITING with status 150

Bpbrm receives a status 150 from bptm and passes it to bpbkar.

16:15:04.723 16:15:04.723 150 16:15:04.723 16:15:04.723 16:15:04.723 150 [3744.3160] <2> bpbrm readline: exit_status = 150 [3744.3160] <2> bpbrm readline: child exit abnormal - status = [3744.3160] <2> bpbrm kill_child_process_Ex: start [3744.3160] <2> bpbrm wait_for_child: start [3744.3160] <2> inform_client_of_status: INF - Server status =

Bpbkar detects the loss of data socket when bptm exits, and reports it as being reset externally. Bpbkar exits with a status 14.
4:14:26.101 PM: [2608.5820] <4> bpio::read_string: INF - read non-blocking message of length 1 4:14:27.148 PM: [2608.5820] <4> ov_log::OVLoop: Timestamp 4:15:04.835 PM: [2608.5820] <16> dtcp_write: TCP - failure: send socket (900) (TCP 10054: Connection reset by peer) 4:15:04.835 PM: [2608.5820] <16> dtcp_write: TCP - failure: attempted to send 32768 bytes 4:15:04.835 PM: [2608.5820] <4> tar_base::V_vTarMsgW: INF - tar message received from tar_backup::backup_data_state 4:15:04.835 PM: [2608.5820] <2> tar_base::V_vTarMsgW: FTL - tar file write error (10054) 4:15:04.835 PM: [2608.5820] <2> ov_log::V_GlobalLog: INF - HrESEBackupClose: Microsoft Information Store = 0x00000000 4:15:04.835 PM: [2608.5820] <2> tar_base::V_vTarMsgW: INF - Client completed sending data for backup 4:15:04.835 PM: [2608.5820] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 14: file write failed 4:15:04.835 PM: [2608.5820] <2> tar_base::V_vTarMsgW: WRN - Abnormal backup status, Exchange Transaction Logs were not truncated

Finally, bpbrm reports status 150 to the master server.

16:15:13.286 [3744.3160] <2> bpbrm Exit: client backup EXIT STATUS 150: termination requested by administrator

Reason: The old master server will ask for a report drive on the media server and finds out that a job is running and is not listed in his EMM database. It will send an abort signal to the media server to cancel the job. Resolution: When the client was moved to the new master server, the master server was successfully added to the client server list of servers, and set as the current master server. The old master server, however, remained in the client's server list. By removing the old master server from the client's server list, backups were able to complete successfully.

Problem
STATSU CODE 150: Backups are terminated with a NetBackup Status Code 150 (Termination requested by administrator) when no administrator has terminated the job.

Error
termination requested by administrator

Solution
Overview: Scheduled backups fail almost instantly upon starting. Running the backups manually after the failure yields a successful backup. Troubleshooting: Enable the bpsched log file on the master server. Log files: The bpsched log file on the master server shows the following message:
00:05:43.001 [3752.3460] <2> send_runQ_msg_list: main_sched suspending--possible hang condition 00:05:43.001 [3752.3460] <2> send_runQ_msg_list: queue full, suspending process 1 00:05:43.188 [3752.3460] <2> send_runQ_msg_list: unsuspending process 1 00:08:02.077 [3752.3460] <2> ?: <clientname> exited with status 150 (termination requested by administrator) 00:08:02.218 [3752.3460] <16> log_in_errorDB: backup of client <clientname> exited with status 150 (termination requested by administrator)

Resolution: Check for the MsgQ size registry key under

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion.

If the key is not present, do the following: Note: A reboot of the master server is required. 1. Stop all NetBackup services 2. Add a REG_DWORD value to the above registry path and enter MsgQ size as the value name 3. Edit the above key and set the Base value to Decimal 4. Insert 512 under the Value data field and click OK

5. Reboot the computer By default, this value is 64.This value can be as low as 1 and no higher than 1024, but it is recommended not to go lower than the default value. Note: If the system experiences performance issues (e.g. sluggishness, etc.) after the implementation of this key, please revert the changes to the registry.