Under Construction
hmc rmviosbk
Available: from 1.9.2.0 (V10R1M1010)
With the command “hmc rmviosbk“ you can delete virtual I/O server backups from the HMC hard drive:
hmc rmviosbk [-v] <hmc> <backup_selections>
The backup to be deleted must be specified as the only argument. For example, if the following backups currently exist on the HMC hmc01,
$ hmc lsviosbk hmc01
NAME TYPE SIZE SYS_NAME VIOS_NAME LAST_MODIFIED
cfgbackup.tar.gz viosioconfig 0.007 ms03 ms03-vio2 05/10/2024 08:57:41
fullbackup.tar vios 3558.838 ms03 ms03-vio1 04/30/2024 12:05:00
fullbackup.tar vios 6255.049 ms03 ms03-vio2 05/02/2024 08:56:55
$
and the backup cfgbackup.tar.gz of virtual I/O server ms03-vio2 should be deleted, then the name of the backup can simply be specified as an argument:
$ hmc rmviosbk hmc01 cfgbackup.tar.gz
$
Since there is only one backup with this name, the name is sufficient. However, if the fullbackup.tar of virtual I/O server ms03-vio2 is to be deleted, the name alone is not sufficient:
$ hmc rmviosbk hmc01 fullbackup.tar
hmc01: lsviosbk
USAGE:
hmc rmviosbk [-v] <hmc> <backup_selections>
ERROR: 'fullbackup.tar' matches more than one backup:
did you mean: fullbackup.tar
did you mean: fullbackup.tar
$
There are two backups named fullbackup.tar, one for ms03-vio1 and one for ms03-vio2. Therefore, the name alone is not enough to clearly select the desired backup.
The problem can be solved by simply specifying the name of the virtual I/O server (see selections):
$ hmc rmviosbk hmc01 fullbackup.tar,ms03-vio2
$
Alternatively, you could have specified size=6255.049 as an argument, since there is only one backup with this size:
$ hmc rmviosbk hmc01 size=6255.049
$
Instead of selecting the backup to be deleted using many selections, it is often easier to use the analogous command “vios rmviosbk”.