This option enables Tivoli® Storage Manager to restore configuration information for the pRDM volumes that are associated with a VMware virtual machine, even if the LUNs that were associated with the volumes cannot be found. Because pRDM volumes are not included in virtual machine snapshot, only the configuration information can be restored, and not the data that was on the volumes.
This option does not apply to backups of Microsoft Hyper-V virtual machines.
Supported Clients
This option is valid for Windows and Linux clients that are installed on a vStorage backup server.
Options File
Place this
option in the client options file (dsm.opt),
or specify it as a command-line parameter on the restore
vm command.
Place this option in
the client options file (dsm.opt), in the client
system options file (dsm.sys), or specify it
as a command-line parameter on the restore vm command.
Parameters
- YES
- Specify this value if you must restore a virtual machine that you backed up with -vmprocesswithprdm=yes, and the original LUNs that were mapped by the raw device mappings file cannot be located. This setting causes the client to skip attempts to locate the missing LUNs used by the pRDM volumes, and restore the configuration information (disk labels) that were associated with them. The pRDM volumes are restored as thin-provisioned VMFS VMDKs. You can then use the vSphere client to create the necessary pRDM mappings.
- NO
- Setting -vmnoprdmdisk=no causes restore operations for virtual machines that were backed up with -processvmwithprdm=yes to fail if the original LUNs that were mapped to by the raw device mappings file cannot be located. This value is the default value.
Examples
VMNOPRDMDISKS YESdsmc restore vm vm123 -vmnoprdmdisks=yes- Related information
- Vmprocessvmwithindependent
- Vmprocessvmwithprdm