Highlighted

VM backup failed with error code -20 (invalid command parameter)

HELLO Smiley Happy

I am not able to backup RHEL VM. It throws invalid command parameter (20) error message.

My Environment is

NBU 8.0
Master Server : WINDOWSMASTER.NET
Media Server  : HPUXMEDIA.NET
Client  : RHELVM.NET (i.e. which needs to back up.)

JOB DETAILS:


Aug 1, 2017 4:03:13 AM - Info bpbrm (pid=15850) RHELVM.NET is the host to backup data from
Aug 1, 2017 4:03:13 AM - Info bpbrm (pid=15850) reading file list for client
Aug 1, 2017 4:03:13 AM - Info bpbrm (pid=15850) start bpfis on client
Aug 1, 2017 4:03:15 AM - Info bpbrm (pid=15850) Starting create snapshot processing
Aug 1, 2017 4:03:16 AM - Info bpfis (pid=15858) Backup started
Aug 1, 2017 4:03:22 AM - Warning bpbrm (pid=15850) from client RHELVM.NET: WRN - Cannot stat /3PAR. Errno = 5: I/O error
Aug 1, 2017 4:03:23 AM - Warning bpbrm (pid=15850) from client RHELVM.NET: WRN - Cannot stat /3PAR. Errno = 5: I/O error
Aug 1, 2017 4:03:24 AM - Warning bpbrm (pid=15850) from RHELVM.NET: WRN - Cannot stat /3PAR. Errno = 5: I/O error
Aug 1, 2017 4:03:24 AM - Critical bpbrm (pid=15850) from client RHELVM.NET: FTL - process_fs_list() failed, status 20
Aug 1, 2017 4:03:24 AM - Info bpfis (pid=15858) done. status: 20
Aug 1, 2017 4:03:24 AM - end VMware: Create Snapshot; elapsed time 8759:59:25
Aug 1, 2017 4:03:24 AM - Info bpfis (pid=15858) done. status: 20: invalid command parameter
Aug 1, 2017 4:03:42 AM - Info bpbrm (pid=15863) Starting delete snapshot processing
Aug 1, 2017 4:03:44 AM - Info bpfis (pid=15875) Backup started
Aug 1, 2017 4:03:44 AM - Warning bpbrm (pid=15863) from client RHELVM.NET: WRN - cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.RHELVM.NET_1501581830.1.0
Aug 1, 2017 4:03:44 AM - Info bpfis (pid=15875) done. status: 4207
Aug 1, 2017 4:03:44 AM - end VMware: Delete Snapshot; elapsed time 8759:59:16
Aug 1, 2017 4:03:44 AM - Info bpfis (pid=15875) done. status: 4207: Could not fetch snapshot metadata or state files
Aug 1, 2017 4:03:50 AM - Info nbjm (pid=11204) starting backup job (jobid=1029) for client RHELVM.NET, policy HPUX_CoE_GRT, schedule Full
Aug 1, 2017 4:03:50 AM - Info nbjm (pid=11204) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1029, request id:{1234567A-7F22-405B-879B-1234A94C29CE})
Aug 1, 2017 4:03:50 AM - requesting resource HPUX_CoE_GRT-stu
Aug 1, 2017 4:03:50 AM - requesting resource WINDOWSMASTER.NET.NBU_CLIENT.MAXJOBS.RHELVM.NET
Aug 1, 2017 4:03:50 AM - requesting resource WINDOWSMASTER.NET.NBU_POLICY.MAXJOBS.HPUX_TEST
Aug 1, 2017 4:03:50 AM - granted resource WINDOWSMASTER.NET.NBU_CLIENT.MAXJOBS.RHELVM.NET
Aug 1, 2017 4:03:50 AM - granted resource WINDOWSMASTER.NET.NBU_POLICY.MAXJOBS.HPUX_TEST
Aug 1, 2017 4:03:50 AM - granted resource MediaID=@aaabA;DiskVolume=ABC_HPUX_CoE_GRT;DiskPool=HPUX_CoE_GRT;Path=ABC_HPUX_CoE_GRT;StorageServer=10.X.X.X;MediaServer=HPUXMEDIA.NET
Aug 1, 2017 4:03:50 AM - granted resource HPUX_CoE_GRT-stu
Aug 1, 2017 4:03:54 AM - estimated 0 kbytes needed
Aug 1, 2017 4:03:54 AM - begin Parent Job
Aug 1, 2017 4:03:54 AM - begin VMware: Start Notify Script
Aug 1, 2017 4:03:59 AM - Info RUNCMD (pid=12920) started
Aug 1, 2017 4:03:59 AM - Info RUNCMD (pid=12920) exiting with status: 0
Operation Status: 0
Aug 1, 2017 4:03:59 AM - end VMware: Start Notify Script; elapsed time 0:00:05
Aug 1, 2017 4:03:59 AM - begin VMware: Step By Condition
Operation Status: 0
Aug 1, 2017 4:03:59 AM - end VMware: Step By Condition; elapsed time 0:00:00
Aug 1, 2017 4:03:59 AM - begin VMware: Read File List
Operation Status: 0
Aug 1, 2017 4:03:59 AM - end VMware: Read File List; elapsed time 0:00:00
Aug 1, 2017 4:03:59 AM - begin VMware: Create Snapshot
Aug 1, 2017 4:04:16 AM - started process bpbrm (pid=15850)
Aug 1, 2017 4:04:28 AM - end writing
Operation Status: 20
Aug 1, 2017 4:04:28 AM - end Parent Job; elapsed time 0:00:34
Aug 1, 2017 4:04:28 AM - begin VMware: Stop On Error
Operation Status: 0
Aug 1, 2017 4:04:28 AM - end VMware: Stop On Error; elapsed time 0:00:00
Aug 1, 2017 4:04:28 AM - begin VMware: Delete Snapshot
Aug 1, 2017 4:04:44 AM - started process bpbrm (pid=15863)
Aug 1, 2017 4:04:48 AM - end writing
Operation Status: 4207
Aug 1, 2017 4:04:48 AM - begin VMware: End Notify Script
Aug 1, 2017 4:04:53 AM - Info RUNCMD (pid=27340) started
Aug 1, 2017 4:04:53 AM - Info RUNCMD (pid=27340) exiting with status: 0
Operation Status: 0
Aug 1, 2017 4:04:53 AM - end VMware: End Notify Script; elapsed time 0:00:05
Operation Status: 20
invalid command parameter (20)

 

 

 

 

Tags (2)
1 Solution

Accepted Solutions
Accepted Solution!

Re: VM backup failed with error code -20 (invalid command parameter)

@PBY

We need more info please...

Which server or client have you configured as VM backup host?
Are you aware that HP-UX media server cannot be VM backup host?

If you look at Components of NetBackup for VMware section in NetBackup for VMware Administrator's Guide  (starting on p. 16), please tell us us which picture on the subsequent 2 pages resembles your backup environment?



 

View solution in original post

13 Replies

Re: VM backup failed with error code -20 (invalid command parameter)

hey

can you share policy details?? what is your transport type? Is this VM having any RDMs.. such details would be nice to have

On that client are you able to run ls -alrt /3PAR 

without any issues ?? as in logs we do see i/o error... uncool Smiley Wink

Accepted Solution!

Re: VM backup failed with error code -20 (invalid command parameter)

@PBY

We need more info please...

Which server or client have you configured as VM backup host?
Are you aware that HP-UX media server cannot be VM backup host?

If you look at Components of NetBackup for VMware section in NetBackup for VMware Administrator's Guide  (starting on p. 16), please tell us us which picture on the subsequent 2 pages resembles your backup environment?



 

View solution in original post

Re: VM backup failed with error code -20 (invalid command parameter)

 I have configured RHEL VM as backup VM host and using HPUX host as Media Server.

I gone through the document, and in my case it is vCenter Server.

I have configured 'vCenter Server' as Virtual Machine server in NBU. 

Re: VM backup failed with error code -20 (invalid command parameter)

If you don't mind - please answer all questions asked by @quebek and myself?

We are really trying to help you but can only do so when we understand the 'full' picture.

Are other backups of VMs on this ESX server and datastore working?

If you are using a VM as backup host, it means you are using hotadd transport mode, right?

Have you confirmed that all requirements for hotadd method are met?

Re: VM backup failed with error code -20 (invalid command parameter)

Hello !
Thanky you Everyone for suggessions.
I have modified policy, by selecting VMware backup host name as My Master Server it worked.

Policy.jpg

 

 

 

 

 

 

 

Re: VM backup failed with error code -20 (invalid command parameter)

Glad we could point you in the right direction. It seems that the backup host was previously set as Backup Media server, which is not supported.

Re: VM backup failed with error code -20 (invalid command parameter)

Now I am not able to do "File Level Recovery", I have already enabled File level recovery option in Policy.
For Restore by selecting "Virtual Machine backup" it shows vdmk file but while selecting "Normal backup" facing error as shown in snapshots below.

 

Policy1.jpgPolicy2.jpgPolicy3.jpg

Re: VM backup failed with error code -20 (invalid command parameter)

Have you checked this doc to see if the Linux Client OS version and filesystem supports file-level restore?

Statement of Support for NetBackup 7.x and 8.x in a Virtual Environment:    http://www.veritas.com/docs/000006177

See this table:
Table 12   VMware guest operating systems supported for file-level recovery

Re: VM backup failed with error code -20 (invalid command parameter)

Thank you @Marianne for replying.

As per document,
NBU 8.0 supports file level recovery of RHEL_7 VM (64-bit with ext4)

and My environment is
NBU 8.0
RHEL VM x86_64bit XFS

as per my knowledge XFS file system is latest. It means that I need to downgrade my RHEL VM to ext4.
Correct me if I am missing anything.

Re: VM backup failed with error code -20 (invalid command parameter)

Firstly, yes, in this particular case... you will have to change file-system if you want working "file-level restore aware" backups.

.

Secondly, Wikipedia describes XFS as having been released in or around 1994, and EXT4 as having been released in or around 2008.

IMO, I don't see a change from XFS to EXT4 as a downgrade, for me it is just a change of file-system, but then that is just me and my own personal opinion.

Why would you yourself personally consider a change from XFS (older) to EXT4 (newer) as a "downgrade"?  Is there perhaps some feature of XFS which has no equivalent in EXT4 but is important (but hopefully not critical) to your RHEL server based solution?

Re: VM backup failed with error code -20 (invalid command parameter)

We are in the same mess with RHEL 7. The Linux/Unix team wants to keep the "vanilla" build that they get from Redhat and since RHEL 7, XFS is default filesystem type.

So, for now, we are using client level backup using Standard policy to provide file level restores. For VM restores, you can still perform a backup using VIP and restore it successfully. The only drawback is that you backup the VM twice and preferably would need to separate the two backup windows.

It would be nice if Veritas added the file restore capability for XFS filesystem, when Symantec wonderfully failed to acknowledge the feature requests for years on the end!

Re: VM backup failed with error code -20 (invalid command parameter)

@PBY

I have moved your restore issue to a new post as this is not related to the backup issue.

Your backup issue that was caused by selecting the HP-UX media server as backup host was solved when you changed it to the Windows master server.

New post:
https://vox.veritas.com/t5/NetBackup/VM-restore-to-client-failure/td-p/836308

 

Re: VM backup failed with error code -20 (invalid command parameter)

@PBY, @X2 - Single File Restore for XFS on RHEL VMs has been a wish-list item for a long while - I would push back on your Veritas Sales and SE to see if support is likely in an upcoming release and if not to request it be added - the more pressure the better... Andrew