Oracle Cloud Infrastructure Documentation

Migrating an Instance from a Local to Remote Boot Volume

Oracle Cloud Infrastructure introduced remote boot volumes November 15, 2017. Remote boot volumes include significant improvements over local boot volumes including lower boot times, encryption of data at rest and in-transit, zero downtime snapshots, improved availability, and more. Instances launched before November 15, 2017 use local boot volumes. Local boot volumes are being deprecated, we recommend that you migrate any instances currently using a local boot volume to a remote boot volume. This topic describes that process.

Limitations and Warnings for Manual Migration

Be aware of the following limitations and warnings when performing a manual migration:

  • Any public IP addresses assigned to your instance from a reserved public pool are retained. Any that were not assigned from a reserved public IP address pool will change. Private IP addresses do not change.
  • MAC addresses, CPUIDs, and other unique hardware identifiers do change during the move. If any applications running on the instance use these identifiers for licensing or other purposes, be sure to take note of this information before moving the instance to help you manage the change.

Prerequisites for Manual Migration

  1. Before moving the instance, document all critical details:

    • The instance's region, availability domain, and fault domain.
    • The instance's display name.
    • All private IP addresses, names, and subnets. Note that the instance can have multiple VNICs, and each VNIC can have multiple secondary IP addresses.
    • All private DNS names. The instance can have multiple VNICs, and each VNIC can have multiple secondary IP addresses. Each private IP address can have a DNS name.
    • Any public IP¬†addresses assigned from a reserved public pool. Note that the instance can have multiple VNICs, and each VNIC can have multiple secondary private IP addresses. Each VNIC and secondary private IP address can have an attached public IP address.
    • Any remote block volumes attached to the instance.
    • Any tags on the instance or attached resources.
  2. Prepare the instance for manual migration:

    • Ensure that any remote block volumes defined in /etc/fstab use the recommended options.
    • Ensure that any File Storage service (NFS) mounts use the nofail option.
    • If you have statically defined any network interfaces belonging to secondary VNICs using their MAC addresses, such as those defined in /etc/sysconfig/network-scripts/ifcfg*, those interfaces will not start due to the change in the MAC address. Remove the static mapping.
    • If you use the Oracle-provided script to configure secondary VNICs, ensure it runs automatically at startup.

Migrating an Instance Manually

After you complete the prerequisites:

  1. Stop any running applications.
  2. Ensure that those applications will not start automatically.


    When the relocated instance starts for the first time, remote block volumes, secondary VNICs, or any resource that relies on them, will not be attached. The absence of these resources can cause application issues.

  3. If your instance has local NVMe storage (dense instances), you must back up this data:
    1. Create and attach one or more remote block volumes to the instance.
    2. Copy the data from the NVMe devices to the remote block volumes.
  4. Unmount any remote block volumes or File Storage service (NFS) mounts.
  5. Back up all remote block volumes. See Overview of Block Volume Backups for more information.
  6. Create a custom image of the instance using the steps described in the Using the Console or Using the API sections of Managing Custom Images.


    Do not generalize or specialize Windows instances.

  7. Terminate the instance:

    Using the Console
    Using the API
    Using the CLI
  8. Create a new instance using the custom image from the terminated instance, see the steps described in the Using the Console or the Using the API sections of Managing Custom Images.
  9. In the launch instance flow, specify the private IP address that was attached to the primary VNIC. If the public IP address was assigned from a reserved IP address pool, be sure to assign the same IP address.
  10. When the instance state changes to RUNNING, Stop the instance.
  11. Recreate any secondary VNICs and secondary IP addresses.
  12. Attach any remote block volumes, see Attaching a Volume for more information.


    This step includes any volumes used to back up local NVMe devices. Copy the data onto the NVMe storage on the new instance, and then detach the volumes.

  13. Start the instance.
  14. Start and test any applications on the instance.
  15. Configure the applications to start automatically, as required.
  16. Recreate the required tags.
  17. (Optional) After you confirm that the instance and applications are healthy, you can delete the volume backups.