Data Object Description

Properties

Name	Type	Description
changeId*	xsd:string	The change ID of the virtual disk for the corresponding snapshot or virtual machine. This can be used to track incremental changes to a virtual disk. See QueryChangedDiskAreas. *Since* vSphere API 4.0
compatibilityMode*	xsd:string	The compatibility mode of the raw disk mapping (RDM). This must be specified when a new virtual disk with an RDM backing is created. On subsequent virtual machine reconfigurations, this property should be handled as follows, depending on the version of the host: On ESX Server 2.5, the compatibility mode of an RDM backing is a characteristic of the virtual machine's configuration. When reconfiguring a virtual machine that currently uses a virtual disk backed by an RDM, the compatibility mode of that backing may be modified. When reconfiguring a virtual machine to add an existing virtual disk backed by an RDM, the compatibility mode of that backing may be specified. If left unspecified it defaults to "physicalMode". On ESX Server 3.x, the compatibility mode of an RDM backing is a characteristic of the RDM itself. Once the RDM is created, its compatibility mode cannot be changed by reconfiguring the virtual machine. When reconfiguring a virtual machine to add an existing virtual disk backed by an RDM, the compatibility mode of that backing must be left unspecified. See VirtualDiskCompatibilityMode
contentId*	xsd:string	Content ID of the virtual disk file, if available. A content ID indicates the logical contents of the disk backing and its parents. This property is only guaranteed to be up to date if this disk backing is not currently being written to by any virtual machine. The only supported operation is comparing if two content IDs are equal or not. The guarantee provided by the content ID is that if two disk backings have the same content ID and are not currently being written to, then reads issued from the guest operating system to those disk backings will return the same data. *Since* vSphere API 4.0
deviceName*	xsd:string	The host-specific device the LUN is being accessed through. If the target LUN is not available on the host then it is empty. For example, this could happen if it has accidentally been masked out.
diskMode*	xsd:string	The disk mode. Valid values are: persistent independent_persistent independent_nonpersistent nonpersistent undoable append Disk modes are only supported when the raw disk mapping is using virtual compatibility mode. See VirtualDiskMode
lunUuid*	xsd:string	Unique identifier of the LUN accessed by the raw disk mapping.
parent*	VirtualDiskRawDiskMappingVer1BackingInfo	The parent of this virtual disk file, if this is a delta disk backing. This will be unset if this is not a delta disk backing. A delta disk backing is a way to preserve a virtual disk backing at some point in time. A delta disk backing is a file backing which in turn points to the original virtual disk backing (the parent). After a delta disk backing is added, all writes go to the delta disk backing. All reads first try the delta disk backing and then try the parent backing if needed. A delta disk backing can be added to a disk either implicitly during snapshot operations, or explicitly during create or reconfigure of the virtual machine. Note that the type of the backing is consistent throughout the chain; any new delta disk backing which is added is of the same type as the original disk . Also note that since the parent backing is not being written to, it is possible that the parent backing may be shared among multiple disks belonging to multiple virtual machines. During virtual machine creation and reconfiguration this property is only checked if the VirtualDeviceConfigSpec specifies an add operation with a create file operation. In this case, a new delta disk backing is created which points to the parent disk backing. Only the fileName property is important; all other properties will be ignored. The parent backing is assumed to exist and will not be recursively created. Only raw disk mappings in virtual compatibility mode can have parents. This property may only be set if deltaDiskBackingsSupported is true. *Since* vSphere API 4.0
uuid*	xsd:string	Disk UUID for the virtual disk, if available. Disk UUID is not available if the raw disk mapping is in physical compatibility mode. *Since* VI API 2.5
Properties inherited from VirtualDeviceFileBackingInfo
datastore, fileName
Properties inherited from VirtualDeviceBackingInfo
None
Properties inherited from DynamicData
dynamicProperty, dynamicType

Name

Type

Description

changeId*

xsd:string

The change ID of the virtual disk for the corresponding snapshot or virtual machine. This can be used to track incremental changes to a virtual disk. See QueryChangedDiskAreas.

Since vSphere API 4.0

compatibilityMode*

xsd:string

The compatibility mode of the raw disk mapping (RDM). This must be specified when a new virtual disk with an RDM backing is created. On subsequent virtual machine reconfigurations, this property should be handled as follows, depending on the version of the host:

On ESX Server 2.5, the compatibility mode of an RDM backing is a characteristic of the virtual machine's configuration. When reconfiguring a virtual machine that currently uses a virtual disk backed by an RDM, the compatibility mode of that backing may be modified. When reconfiguring a virtual machine to add an existing virtual disk backed by an RDM, the compatibility mode of that backing may be specified. If left unspecified it defaults to "physicalMode".

On ESX Server 3.x, the compatibility mode of an RDM backing is a characteristic of the RDM itself. Once the RDM is created, its compatibility mode cannot be changed by reconfiguring the virtual machine. When reconfiguring a virtual machine to add an existing virtual disk backed by an RDM, the compatibility mode of that backing must be left unspecified.

See VirtualDiskCompatibilityMode

contentId*

xsd:string

Content ID of the virtual disk file, if available.

A content ID indicates the logical contents of the disk backing and its parents.

This property is only guaranteed to be up to date if this disk backing is not currently being written to by any virtual machine.

The only supported operation is comparing if two content IDs are equal or not. The guarantee provided by the content ID is that if two disk backings have the same content ID and are not currently being written to, then reads issued from the guest operating system to those disk backings will return the same data.

Since vSphere API 4.0

deviceName*

xsd:string

The host-specific device the LUN is being accessed through. If the target LUN is not available on the host then it is empty. For example, this could happen if it has accidentally been masked out.

diskMode*

xsd:string

The disk mode. Valid values are:

Disk modes are only supported when the raw disk mapping is using virtual compatibility mode.
See VirtualDiskMode

lunUuid*

xsd:string

Unique identifier of the LUN accessed by the raw disk mapping.

parent*

VirtualDiskRawDiskMappingVer1BackingInfo

The parent of this virtual disk file, if this is a delta disk backing. This will be unset if this is not a delta disk backing.

A delta disk backing is a way to preserve a virtual disk backing at some point in time. A delta disk backing is a file backing which in turn points to the original virtual disk backing (the parent). After a delta disk backing is added, all writes go to the delta disk backing. All reads first try the delta disk backing and then try the parent backing if needed.

A delta disk backing can be added to a disk either implicitly during snapshot operations, or explicitly during create or reconfigure of the virtual machine.

Note that the type of the backing is consistent throughout the chain; any new delta disk backing which is added is of the same type as the original disk . Also note that since the parent backing is not being written to, it is possible that the parent backing may be shared among multiple disks belonging to multiple virtual machines.

During virtual machine creation and reconfiguration this property is only checked if the VirtualDeviceConfigSpec specifies an add operation with a create file operation. In this case, a new delta disk backing is created which points to the parent disk backing. Only the fileName property is important; all other properties will be ignored. The parent backing is assumed to exist and will not be recursively created.

Only raw disk mappings in virtual compatibility mode can have parents.

This property may only be set if deltaDiskBackingsSupported is true.

Since vSphere API 4.0

uuid*

xsd:string

Disk UUID for the virtual disk, if available. Disk UUID is not available if the raw disk mapping is in physical compatibility mode.

Since VI API 2.5

Properties inherited from VirtualDeviceFileBackingInfo

datastore, fileName

Properties inherited from VirtualDeviceBackingInfo

None

Properties inherited from DynamicData

dynamicProperty, dynamicType

Need not be set

Show WSDL type definition

         <complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vim25="urn:vim25" name="VirtualDiskRawDiskMappingVer1BackingInfo">
            <complexContent>
               <extension base="vim25:VirtualDeviceFileBackingInfo">
                  <sequence>
                     <element name="lunUuid" type="xsd:string" minOccurs="0"/>
                     <element name="deviceName" type="xsd:string" minOccurs="0"/>
                     <element name="compatibilityMode" type="xsd:string" minOccurs="0"/>
                     <element name="diskMode" type="xsd:string" minOccurs="0"/>
                     <element name="uuid" type="xsd:string" minOccurs="0"/>
                     <element name="contentId" type="xsd:string" minOccurs="0"/>
                     <element name="changeId" type="xsd:string" minOccurs="0"/>
                     <element name="parent" type="vim25:VirtualDiskRawDiskMappingVer1BackingInfo" minOccurs="0"/>
                  </sequence>
               </extension>
            </complexContent>
         </complexType>

Data Object - VirtualDiskRawDiskMappingVer1BackingInfo

Data Object Description