There are two instances when you would use VMDEPLOY INIT with VM:Backup.
VMDEPLOY name INIT
is used when deploying the product for the first time.
Specifies that a new server is being deployed. The process places a set of default configuration files and a startup PROFILE EXEC file on the disk. The LOCAL tag in the VMSERVER NAMES file entry (typically VMBACKUP’s 191) defines the disk for the files. The disks that are defined on the DEPLOY tag are populated with product materials.
INIT creates the following files on VMBACKUP’s LOCAL disk:
VMDEPLOY name INIT ALTERNATE
is used when migrating VM:Backup from AIM to the Mainframe VM Product Manager.
VMDEPLOY verifies all minidisks and then makes necessary changes. Each disk is checked for correct size and block size. Minidisks that have errors are flagged with a message. Fix any problems reported with the minidisks and then rerun the preceding VMDEPLOY command. If all minidisks are correct, then VMDEPLOY loads the code. Because the new VM:Backup code is deployed to the ALTERNATE series of minidisks, your current release remains intact. VMDEPLOY also creates a backup copy of the original PROFILE EXEC on the VMBACKUP 191 as PROFILE OLDEXEC.