Show / Hide Table of Contents

Class UpdateDrProtectionGroupMemberVolumeGroupDetails

Update properties for a volume group member.

Inheritance
object
UpdateDrProtectionGroupMemberDetails
UpdateDrProtectionGroupMemberVolumeGroupDetails
Inherited Members
UpdateDrProtectionGroupMemberDetails.MemberId
object.Equals(object)
object.Equals(object, object)
object.GetHashCode()
object.GetType()
object.MemberwiseClone()
object.ReferenceEquals(object, object)
object.ToString()
Namespace: Oci.DisasterrecoveryService.Models
Assembly: OCI.DotNetSDK.Disasterrecovery.dll
Syntax
public class UpdateDrProtectionGroupMemberVolumeGroupDetails : UpdateDrProtectionGroupMemberDetails

Properties

CommonDestinationKey

Declaration
[JsonProperty(PropertyName = "commonDestinationKey")]
public UpdateVaultAndEncryptionKeyDetails CommonDestinationKey { get; set; }
Property Value
Type Description
UpdateVaultAndEncryptionKeyDetails

DestinationBackupPolicyId

Declaration
[JsonProperty(PropertyName = "destinationBackupPolicyId")]
public string DestinationBackupPolicyId { get; set; }
Property Value
Type Description
string

The OCID of the backup policy to use in the destination region. This policy will be used to create backups for this volume group after it moves the destination region.
Example: ocid1.volumebackuppolicy.oc1..uniqueID

SourceVolumeToDestinationEncryptionKeyMappings

Declaration
[JsonProperty(PropertyName = "sourceVolumeToDestinationEncryptionKeyMappings")]
public List<UpdateSourceVolumeToDestinationEncryptionKeyMappingDetails> SourceVolumeToDestinationEncryptionKeyMappings { get; set; }
Property Value
Type Description
List<UpdateSourceVolumeToDestinationEncryptionKeyMappingDetails>

A list of mappings between source volume IDs in the volume group and customer-managed encryption keys in the destination region which will be used to encrypt the volume after it moves to the destination region.
If you add the entry for source volumes and its corresponding vault and encryption keys here, you can not use 'commonDestinationKey' for encrypting all volumes with common encryption key. Similarly, if you specify common vault and encryption key using 'commonDestinationKey', you cannot specify vaults and encryption keys individually for each volume using 'sourceVolumeToDestinationEncryptionKeyMappings'.
An entry for each volume in volume group should be added in this list. The encryption key will not be updated for the volumes that are part of volume group but missing in this list.

In this article
Back to top