Managed Object - Datastore

Property of
ComputeResource, Datacenter, DatastoreEventArgument, DatastoreMountPathDatastorePair, DatastoreSummary, HostConfigInfo, HostDatastoreBrowser, HostDatastoreBrowserSearchResults, HostDatastoreSystem, HostResignatureRescanResult, HostSystem, InvalidDatastore, IORMNotSupportedHostOnDatastore, OvfResourceMap, RDMNotSupportedOnDatastore, UnsupportedDatastore, VAppCloneSpec, VAppCloneSpecResourceMap, VirtualApp, VirtualDeviceFileBackingInfo, VirtualMachine, VirtualMachineRelocateSpec, VirtualMachineRelocateSpecDiskLocator, VirtualMachineUsageOnDatastore
Parameter to
ConfigureDatastoreIORM_Task, CreateImportSpec, ExpandVmfsDatastore, ExtendVmfsDatastore, QueryAvailableDisksForVmfs, QueryVmfsDatastoreExpandOptions, QueryVmfsDatastoreExtendOptions, RemoveDatastore, UpdateLocalSwapDatastore
Returned by
CreateLocalDatastore, CreateNasDatastore, CreateVmfsDatastore, ExpandVmfsDatastore, ExtendVmfsDatastore
Extends
ManagedEntity
See also
DatastoreCapability, DatastoreHostMount, DatastoreInfo, DatastoreMountPathDatastorePair, DatastoreSummary, HostDatastoreBrowser, StorageIORMInfo, UpdateVirtualMachineFilesResult, VirtualMachine


Managed Object Description

Represents a storage location for virtual machine files. A storage location can be a VMFS volume, a directory on Network Attached Storage, or a local file system path.

A datastore is platform-independent and host-independent. Therefore, datastores do not change when the virtual machines they contain are moved between hosts. The scope of a datastore is a datacenter; the datastore is uniquely named within the datacenter.

Any reference to a virtual machine or file accessed by any host within the datacenter must use a datastore path. A datastore path has the form "[<datastore>] <path>", where <datastore> is the datastore name, and <path> is a slash-delimited path from the root of the datastore. An example datastore path is "[storage] path/to/config.vmx".

You may use the following characters in a path, but not in a datastore name: slash (/), backslash (\), and percent (%).

All references to files in the VIM API are implicitly done using datastore paths.

When a client creates a virtual machine, it may specify the name of the datastore, omitting the path; the system, meaning VirtualCenter or the host, automatically assigns filenames and creates directories on the given datastore. For example, specifying My_Datastore as a location for a virtual machine called MyVm results in a datastore location of My_Datastore\MyVm\MyVm.vmx.

Datastores are configured per host. As part of host configuration, a HostSystem can be configured to mount a set of network drives. Multiple hosts may be configured to point to the same storage location. There exists only one Datastore object per Datacenter, for each such shared location. Each Datastore object keeps a reference to the set of hosts that have mounted the datastore. A Datastore object can be removed only if no hosts currently have the datastore mounted.

Thus, managing datastores is done both at the host level and the datacenter level. Each host is configured explicitly with the set of datastores it can access. At the datacenter, a view of the datastores across the datacenter is shown.

Properties

Name Type Description
browserManagedObjectReference
to a HostDatastoreBrowser

DatastoreBrowser used to browse this datastore.
capabilityDatastoreCapability

Capabilities of this datastore.
host*DatastoreHostMount[]

Hosts attached to this datastore.
infoDatastoreInfo

Specific information about the datastore.
iormConfiguration*StorageIORMInfo

Configuration of storage I/O resource management for the datastore. Currently we only support storage I/O resource management on VMFS volumes of a datastore.

This configuration may not be available if the datastore is not accessible from any host, or if the datastore does not have VMFS volume. The configuration can be modified using the method ConfigureDatastoreIORM_Task

Since vSphere API 4.1
summaryDatastoreSummary

Global properties of the datastore.
vm*ManagedObjectReference[]
to a VirtualMachine[]

Virtual machines stored on this datastore.
Properties inherited from ManagedEntity
alarmActionsEnabled, configIssue, configStatus, customValue, declaredAlarmState, disabledMethod, effectiveRole, name, overallStatus, parent, permission, recentTask, tag, triggeredAlarmState
Properties inherited from ExtensibleManagedObject
availableField, value
*May not be present

Methods

Methods defined in this Managed Object
DestroyDatastore, RefreshDatastore, RefreshDatastoreStorageInfo, RenameDatastore, UpdateVirtualMachineFiles_Task
Methods inherited from ManagedEntity
Destroy_Task, Reload, Rename_Task
Methods inherited from ExtensibleManagedObject
setCustomValue

DestroyDatastore

Deprecated. As of VI API 2.5 do not use this method. This method throws ResourceInUse. Datastores are automatically removed when no longer in use, so this method is unnecessary.

Removes a datastore. A datastore can be removed only if it is not currently used by any host or virtual machine.
Required Privileges
Datastore.Delete

Parameters

NameTypeDescription
_thisManagedObjectReference A reference to the Datastore used to make the method call.

Return Value

Type Description
None

Faults

Type Description
ResourceInUseThrown if one or more hosts or virtual machines are configured to use the datastore.
RuntimeFaultThrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error.

Show WSDL type definition



RefreshDatastore

Explicitly refreshes free-space and capacity values in summary and info.
Required Privileges
System.Read

Parameters

NameTypeDescription
_thisManagedObjectReference A reference to the Datastore used to make the method call.

Return Value

Type Description
None

Faults

Type Description
HostConfigFaultThrown if unable to get the current system information for the datastore.
NotFoundThrown if the datastore or its underlying volume is not found.
RuntimeFaultThrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error.

Show WSDL type definition



RefreshDatastoreStorageInfo

Refreshes all storage related information including free-space, capacity, and detailed usage of virtual machines. Updated values are available in summary and info.
Required Privileges
System.Read
Since
vSphere API 4.0

Parameters

NameTypeDescription
_thisManagedObjectReference A reference to the Datastore used to make the method call.

Return Value

Type Description
None

Faults

Type Description
RuntimeFaultThrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error.

Show WSDL type definition



RenameDatastore

Deprecated. As of vSphere API 4.0, use Rename_Task.

Renames a datastore.
Required Privileges
Datastore.Rename

Parameters

NameTypeDescription
_thisManagedObjectReference A reference to the Datastore used to make the method call.
newNamexsd:string

The new name to assign to the datastore.

Return Value

Type Description
None

Faults

Type Description
DuplicateNameThrown if another datastore in this datacenter already has the same name.
InvalidNameThrown if the name is not a valid datastore name.
RuntimeFaultThrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error.

Show WSDL type definition



UpdateVirtualMachineFiles_Task

Update file paths embedded in virtual machine files on the datastore. This can be called after the file system corresponding to the datastore has been resignatured or remounted.

This method is only supported by vCenter server.

While this operation is in progress, it is important that users do not initiate any operations that might read or write to any files on the datastore, such as registering a virtual machine with files residing on the datastore, or performing any virtual disk operations on any files in the datastore. These operations can potentially cause spurious file update failures, while at the same time they can prevent virtual machine files from being updated correctly.

If users intend to update multiple datastores using this method, it is strongly advised that the users do not initiate any operations that might read or write to files on any of the datastores, until all of them have been updated. The files of a single virtual machine can reside on multiple datastores, and thus all the involved datastores should be updated, before the virtual machine is considered updated completely.

Required Privileges
Datastore.UpdateVirtualMachineFiles
Since
vSphere API 4.1

Parameters

NameTypeDescription
_thisManagedObjectReference A reference to the Datastore used to make the method call.
mountPathDatastoreMappingDatastoreMountPathDatastorePair[]

Old mount path to datastore mapping.

Return Value

Type Description
ManagedObjectReference
to a Task
This method returns a Task object with which to monitor the operation. The result property in the Task contains an UpdateVirtualMachineFilesResult object, upon success, which is a list of virtual machines files the server has attempted to update but failed to update. When there are too many failed files, only a subset of failed files will be returned.

Faults

Type Description
InvalidArgumentThrown if old mount path is mapped to more than one datastores, or if any of the datastore being mapped can not be found.
InvalidDatastoreThrown if the operation cannot be performed due to some error with the datastore; typically a specific subclass of the fault is reported.
NotSupportedThrown if all hosts attached to this datastore do not support updating virtual machine files.
PlatformConfigFaultThrown if any error related to platform occurs during the operation.
ResourceInUseThrown if there exists a registered virtual machine in the volume.
RuntimeFaultThrown if any type of runtime fault is thrown that is not covered by the other faults; for example, a communication error.
TaskInProgressThrown if the datastore is busy, for example, while another task is updating the datastore after volume resignaturing or remounting.