AROVA supports the following run-time configuration changes:

    • Adding independent VMs from a particular project to an existing Domain
      New independent VMs can be added to existing Protected Domains without restrictions. VM belongs to the same project as other Protected Domain’s VMs. Select an existing Protected Domain, navigate to the Independent Protected VMs tab, click the 'START PROTECTION' button, select the VM(s), and submit a task to initiate protection. AROVA will check VM’s protection eligibility, and if it is eligible, automatically create secondary disks, create CG and start replication for each VM’s disks. If failover must be executed while the VM is in Initial Sync, this VM is skipped on failover.
    • Stop protection for an independent protected VM
      Select the Protected Domain, choose the VM, and click the 'STOP PROTECTION' button. AROVA will then remove the VM from the Protected Domain, stop replication for each VM disk, delete the corresponding Consistency Group, and remove the secondary disks.
    • Adding a dependent VM to an existing Domain and RG
      Select the Domain and RG, then select a new VM for protection. AROVA will check VM’s protection eligibility (including RG’s VMs scope and zones and exceeding maximum number of disks in RG’s CG), and if it is eligible, automatically create secondary disks, add disks to corresponding CG and start replication for each VM’s disk. Starting VM protection does not impact protection of other VMs. If failover must be executed while the VM is in Initial Sync, this VM is skipped on failover.
    • Stop protection for a dependent protected VM
      Select the Domain and RG, then select the VM and click the ‘STOP PROTECTION’ button. AROVA will remove VM from the Protected Domain and RG, stop replication for each VM’s disk, remove disks from corresponding CG and delete secondary disks.
    • Changing the VM properties of a independent protected VM or dependent VM
      AROVA seamlessly supports property change of protected VMs. AROVA cannot control properties while being changed in Google Console, it periodically fetches VM’s properties and scans for any VM’s property change. Then AROVA updates CDB accordingly. AROVA does not check properties, dependencies, and compatibility between regions. It is the user’s responsibility to update properties correctly.
    • Changing VM disk properties
      AROVA does not handle protected VM’s disk properties. AROVA follows GCE that copies the properties from the primary disk to the secondary disk only once, when the secondary disk is created. If a user modifies the primary disk's label, guest OS features, or other properties after the secondary disk is created, then Compute Engine doesn't replicate those changes to the secondary disk. https://cloud.google.com/compute/docs/disks/async-pd/configure#create_a_secondary_disk
    • Hot-add disk to an independent protected VM
      A new/existing disk can be attached to an independent protected VM while protection is running. This is handled by AROVA seamlessly. No additional user actions are required. AROVA will assign the newly attached disk to the VM’s CG. Disk scope zonal/regional and specific zones must match VM’s existing disk(s) scope and zones exactly. PDAR takes care of it and rejects adding disk if it breaks this rule. If the attached disk breaks this rule, AROVA will stop VM protection and send appropriate notification. AROVA “notices” add disk events through periodic scanning of protected VM's properties.
    • Hot-remove disk from an independent protected VM
      If a disk is removed from an independent protected VM, AROVA will stop its replication, remove it from VM’s CG and delete the secondary disk. AROVA “notices” this event through periodic scanning of VM's properties.


Note: All configuration changes are saved in the AROVA ACD/CDB and replicated to the secondary region.

Also see:

View: Protection

View: Support for VMs with Disk Encryption