Backups fails with Error: invalid command parameter (20)

Backups fails with Error: invalid command parameter (20)

Article: 100046251
Last Published: 2019-09-12
Ratings: 0 0
Product(s): NetBackup

Problem

All Backup fails with Error: invalid command parameter (20)

Error Message

invalid command parameter (20)

Cause

“BPSTART_TIMEOUT =” had incorrect value in bp.conf file on Media Server.

 

Job Details:

Sep 10, 2019 3:28:20 PM - Info bpbrm (pid=338042) starting bpbkar on client

Sep 10, 2019 3:28:20 PM - Info bpbkar (pid=0) done. status: 20: invalid command parameter

Sep 10, 2019 3:28:20 PM - Info bpbkar (pid=0) done. status: 20: invalid command parameter

Sep 10, 2019 3:28:37 PM - Info nbjm (pid=4774) starting backup job (jobid=1126) for client netbackup, policy master_test, schedule daily

Sep 10, 2019 3:28:37 PM - Info nbjm (pid=4774) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1126, request id:{9A9B830E-D39C-11E9-AAD6-5BC49A3EE8AC})

Sep 10, 2019 3:28:37 PM - requesting resource  stu_disk_appliance

Sep 10, 2019 3:28:37 PM - requesting resource  netbackup.NBU_CLIENT.MAXJOBS.netbackup

Sep 10, 2019 3:28:37 PM - granted resource  netbackup.NBU_CLIENT.MAXJOBS.netbackup

Sep 10, 2019 3:28:37 PM - granted resource  MediaID=@aaaac;DiskVolume=PureDiskVolume;DiskPool=dp_disk_appliance;Path=PureDiskVolume;StorageServer=appliance;MediaServer=appliance

Sep 10, 2019 3:28:37 PM - granted resource  stu_disk_appliance

Sep 10, 2019 3:28:37 PM - estimated 0 kbytes needed

Sep 10, 2019 3:28:37 PM - Info nbjm (pid=4774) started backup (backupid=netbackup_1568100517) job for client netbackup, policy master_testing, schedule daily on storage unit stu_disk_appliance

Sep 10, 2019 3:28:43 PM - started process bpbrm (pid=338042)

Sep 10, 2019 3:28:44 PM - connecting

Sep 10, 2019 3:28:45 PM - connected; connect time: 0:00:00

Sep 10, 2019 3:28:45 PM - end writing

Sep 10, 2019 3:44:04 PM - job 1126 was restarted as job 1127

invalid command parameter (20)

bpcd logs:

15:28:12.845 [9830] <2> process_requests: child_args[5] = -jm

15:28:12.845 [9830] <2> process_requests: Before execvp of command

15:28:12.846 [9829] <2> VssAtManager::~freeManager: ---- EXITING ----

15:28:12.849 [4377] <2> daemon_check_for_zombies: waited for 1 child processes including: 9829

15:28:43.080 [4377] <4> is_remote_host_connect_disabled: Failed to read key from bp.conf, errorcode:227. LEGACY_SERVICES_LOOPBACK_ONLY is not defined, using default.

15:28:43.080 [4377] <2> bpcd main: accept sock = 3

15:28:43.082 [10111] <2> daemon_proxy_proto: Preparing to do daemon protocol for (10.20.8.9:13782 <- 10.20.8.9:39033)

15:28:43.082 [10111] <2> is_connection_INBOUND: non-proxy, localhost connection

15:28:43.082 [10111] <2> is_connection_INBOUND: Connection-Is-INBOUND:[FALSE]

15:28:43.082 [10111] <2> is_connection_INBOUND: non-proxy, localhost connection

15:28:43.083 [10111] <2> is_connection_INBOUND: Connection-Is-INBOUND:[FALSE]

15:28:43.083 [10111] <2> ReadKeyfile: keyfile /usr/openv/netbackup/keyfile does not exist
 

 

Solution

1.       Go to Media Server

2.       Check bp.conf file and make sure that “BPSTART_TIMEOUT=” key has correct value.

NOTE: The default timeout is 300 seconds (5 minutes)

3.       If the value of “BPSTART_TIMEOUT=” is incorrect, correct it or if not needed, remove it from bp.conf file.

4.       Re-run the backup and check if issue persist.

Was this content helpful?