VslmMigrateSpec
Base specification of moving or copying a virtual storage object.
{
"_typeName": "string",
"backingSpec": {
"_typeName": "string",
"datastore": {
"_typeName": "string",
"type": "string",
"value": "string"
},
"path": "string"
},
"profile": [
{
"_typeName": "string"
}
],
"consolidate": false,
"disksCrypto": {
"_typeName": "string",
"parent": "DiskCryptoSpec Object",
"crypto": {
"_typeName": "string"
}
},
"service": {
"_typeName": "string",
"instanceUuid": "string",
"url": "string",
"credential": {
"_typeName": "string"
},
"sslThumbprint": "string",
"sslCertificate": "string"
}
}
Specification of the backings of the target virtual storage object.
Virtual storage object Profile requirement.
If unset, the default behavior will apply.
Flag indicates any delta disk backings will be consolidated during clone/migration.
Cloning of linked clone disks always require consolidation.
Disk chain crypto information.
If unset and if profile contains an encryption iofilter and if source VStorageObject is unencrypted, then disksCrypto will be of type CryptoSpecEncrypt, and filled with keyId that is automatically generated and keyProviderId that is the default kms cluster. During the migration, the object will be encrypted. If unset and if profile is a default policy and if source VStorageObject is unenrypted, then disksCrypto is treated as CryptoSpecNoOp. During migration, no cryptographic change. If unset and if profile contains an encryption iofilter and if source VStorageObject is encrypted, then disksCrypto is treated as CryptoSpecNoOp. During migration, no cryptographic change. If unset and if profile is a default policy and if source VStorageObject is encrypted, then disksCrypto is treated as CryptoSpecDecrypt, during migration, the object will be decrypted. To recrypt the disk during migration, disksCrypto has to be present.
The service endpoint of vCenter where the FCD should be located.
If not specified the current vCenter service is used.
Since: vSphere API Release 8.0.3.0