cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Windows file level backup failed with error code (20) invalid command parameter

Hi Folks,

I get the following error on my Windows File Level backup policy:

Error Message
=============
From status
----------------

(20) invalid command parameter

Detailed Job:
-----------------

8 Oct, 2020 8:14:07 PM - Info bpbrm (pid=36537) sql141-bkp is the host to backup data from

8 Oct, 2020 8:14:07 PM - Info bpbrm (pid=36537) reading file list for client

8 Oct, 2020 8:14:08 PM - Info bpbrm (pid=36537) accelerator enabled

8 Oct, 2020 8:14:10 PM - Info bpbrm (pid=36537) There is no complete backup image match with track journal, a regular full backup will be performed.

8 Oct, 2020 8:14:12 PM - Info bpbrm (pid=36537) starting bpbkar on client

8 Oct, 2020 8:14:13 PM - Info bpbkar (pid=5332) Backup started

8 Oct, 2020 8:14:13 PM - Info bpbrm (pid=36537) bptm pid: 36687

8 Oct, 2020 8:14:13 PM - Info bpbkar (pid=5332) change time comparison:<enabled>

8 Oct, 2020 8:14:13 PM - Info bpbkar (pid=5332) accelerator enabled backup, archive bit processing:<disabled>

8 Oct, 2020 8:14:14 PM - Info bptm (pid=36687) start

8 Oct, 2020 8:14:14 PM - Info bptm (pid=36687) using 262144 data buffer size

8 Oct, 2020 8:14:14 PM - Info bptm (pid=36687) using 30 data buffers

8 Oct, 2020 8:14:16 PM - Info bptm (pid=36687) start backup

8 Oct, 2020 8:14:18 PM - Info bpbkar (pid=5332) will attempt to use change journal data for <C:\>

8 Oct, 2020 8:14:18 PM - Info bpbkar (pid=5332) will attempt to use change journal data for <D:\>

8 Oct, 2020 8:14:18 PM - Info bpbkar (pid=5332) not using change journal data for <System State:\>: not supported for non-local volumes / file systems

8 Oct, 2020 8:14:18 PM - Info bpbkar (pid=5332) not using change journal data for <_BACKUP_SPECIAL_OBJECTS AFTER System StateSmiley Embarassed: not supported for non-local volumes / file systems

8 Oct, 2020 8:14:19 PM - Info bptm (pid=36687) backup child process is pid 36756

8 Oct, 2020 8:15:15 PM - Info bpbkar (pid=5332) not using change journal data for <C:\>: unable to locate change journal data

8 Oct, 2020 8:16:15 PM - Info bpbkar (pid=5332) 5000 entries sent to bpdbm

8 Oct, 2020 8:16:52 PM - Info bpbkar (pid=5332) 10000 entries sent to bpdbm

8 Oct, 2020 8:17:58 PM - Info bpbkar (pid=5332) 15000 entries sent to bpdbm

8 Oct, 2020 8:18:14 PM - Info nbjm (pid=5936) starting backup job (jobid=660746) for client sql141-bkp, policy VM-FS, schedule Daily

8 Oct, 2020 8:18:14 PM - Info nbjm (pid=5936) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=660746, request id:{E001A05A-41D0-486B-BA29-ACD73C6512D3})

8 Oct, 2020 8:18:14 PM - requesting resource  stu_disk_bak2

8 Oct, 2020 8:18:14 PM - requesting resource  bak1.NBU_CLIENT.MAXJOBS.sql141-bkp

8 Oct, 2020 8:18:14 PM - granted resource  bak1.NBU_CLIENT.MAXJOBS.sql141-bkp

8 Oct, 2020 8:18:14 PM - granted resource  MediaID=@aaaae;DiskVolume=PureDiskVolume;DiskPool=dp_disk_bak2;Path=PureDiskVolume;StorageServer=bak2;MediaServer=bak2

8 Oct, 2020 8:18:14 PM - granted resource  stu_disk_bak2

8 Oct, 2020 8:18:14 PM - estimated 0 kbytes needed

8 Oct, 2020 8:18:14 PM - Info nbjm (pid=5936) started backup (backupid=sql141-bkp_1601381894) job for client sql141-bkp, policy VM-FS, schedule Daily on storage unit stu_disk_bak2

8 Oct, 2020 8:18:26 PM - started process bpbrm (pid=36537)

8 Oct, 2020 8:18:32 PM - connecting

8 Oct, 2020 8:18:34 PM - connected; connect time: 0:00:00

8 Oct, 2020 8:18:41 PM - begin writing

8 Oct, 2020 8:19:05 PM - Info bpbkar (pid=5332) 20000 entries sent to bpdbm

8 Oct, 2020 8:19:29 PM - Info bpbkar (pid=5332) 25000 entries sent to bpdbm

8 Oct, 2020 8:19:54 PM - Info bpbkar (pid=5332) 30000 entries sent to bpdbm

8 Oct, 2020 8:20:15 PM - Info bpbkar (pid=5332) 35000 entries sent to bpdbm

8 Oct, 2020 8:21:26 PM - Info bpbkar (pid=5332) 40000 entries sent to bpdbm

8 Oct, 2020 8:22:26 PM - Info bpbkar (pid=5332) 45000 entries sent to bpdbm

8 Oct, 2020 8:22:39 PM - Info bpbkar (pid=5332) accelerator sent 26957405184 bytes out of 26900562944 bytes to server, optimization 0.0%

8 Oct, 2020 8:22:43 PM - Error bptm (pid=36687) media manager terminated by parent process

8 Oct, 2020 8:22:50 PM - Info bak2 (pid=36687) StorageServer=PureDisk:bak2; Report=PDDO Stats (multi-threaded stream used) for (bak2): scanned: 26271142 KB, CR sent: 57881 KB, CR sent over FC: 0 KB, dedup: 99.8%, cache disabled

8 Oct, 2020 8:22:51 PM - Info bpbkar (pid=5332) done. status: 20: invalid command parameter

8 Oct, 2020 8:23:07 PM - Info bpbrm (pid=44443) Starting delete snapshot processing

8 Oct, 2020 8:23:11 PM - Info bpfis (pid=5532) Backup started

8 Oct, 2020 8:23:11 PM - Warning bpbrm (pid=44443) from client sql141-bkp: cannot open D:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.sql141-bkp_1601381894.1.0

8 Oct, 2020 8:23:11 PM - Info bpfis (pid=5532) done. status: 4207

8 Oct, 2020 8:23:11 PM - Info bpfis (pid=5532) done. status: 4207: Could not fetch snapshot metadata or state files

8 Oct, 2020 8:27:13 PM - end writing; write time: 0:08:32

invalid command parameter  (20)

For your information below is our current schedule:

Daily – Differential Incremental

Weekly – Full Backup

Thanks in advance for answer

3 Replies
Highlighted

Re: Windows file level backup failed with error code (20) invalid command parameter

Hey

What is the client OS, NBU version on it. Can you please share same information for master/media server?

What is this policy type? VMWare or MS-Windows? If VMWare what are the transports allowed...

On media server i would have enabled logging for bptm verbose = 3 and on client bpbkar same verbosity... and retry

did it ever worked? if so what has changed?

 

Highlighted

Re: Windows file level backup failed with error code (20) invalid command parameter

We see that bpbkar reported the status 20: Info bpbkar (pid=5332) done. status: 20: invalid command parameter So, I would like to the client's bpbkar log first.
Highlighted

Re: Windows file level backup failed with error code (20) invalid command parameter

If this is happening regularly on all backups of that one box, it might be worth a casual question to the server team (or end user if they have admin access) just to check and see if anyone has been cancelling that, "annoying bpbkar32.exe process that keeps running and using all the server resources when we're doing SQL maintenance." There's certainly other things it could be (back-rev version issues, accelerator issues, client filesystem issues, etc.) but sometimes it's worth spending an email to check on the simple ones first. =) The client-side bpbkar log will tell you for sure (although you might have to up the verbosity) what's going on though. Other things you can try to narrow it down some : 1) Set the filesystems to run sequentially to see if it's a particular one having the issues or if they all fail. 2) Run a full backup with a rescan to correct accelerator issues. 3) Bring the NBU client version up to the level of the Media Server (which hopefully already matches your Master's version of NBU) & see if the issue still happens.