Oracle Cloud Infrastructure Documentation

Setting Instance Availability During Maintenance Events

When the underlying infrastructure for a compute instance needs to undergo planned maintenance or recover from an unexpected failure, Oracle Cloud Infrastructure automatically attempts to recover the instance by migrating it to healthy hardware.

For virtual machine (VM) instances, when applicable, Oracle Cloud Infrastructure live migrates supported VM instances from the physical VM host that needs maintenance to a healthy VM host with minimal disruption to running instances. If you do not want your instances live migrated, you can choose to receive a notification for the maintenance event. After you receive the notification, you have 14 days to reboot migrate your instance. The instance is only live migrated if you do not reboot the instance before the due date. If the instance can't be live migrated, reboot migration (for standard VM shapes) or rebuild in place (for dense I/O VM shapes) is used instead.

After a migration, by default the instance is recovered to the same lifecycle state as before the maintenance event. If you have an alternate process to recover the instance after a reboot migration, you can optionally configure the instance to remain stopped after the maintenance is complete. You can then restart the instance on your own schedule.

For permissions, see Required IAM Policy for Working with Instances.

  • You can use the Console to configure live migration options and the lifecycle state of instances after a migration.

    Configuring Live Migration

    1. On the Compute list page, select the instance that you want to work with. If you need help finding the list page, see Listing Instances.
    2. Select More Actions, and then select Edit.
    3. Select Show advanced options, and then select the Availability configuration tab.
    4. In the Live migration section, select an option:
      • Let Oracle Cloud Infrastructure select the best migration option: Select this option to let Oracle Cloud Infrastructure select the best option to migrate the instance to a healthy physical VM host if an underlying infrastructure component needs to undergo maintenance.
      • Use live migration if possible: Select this option to have the instance live migrated to a healthy physical VM host without any notification or disruption. If live migration isn't successful, reboot migration is used. Some shapes don't support live migration.
      • Opt-out: Select this option to have a notification sent for the maintenance event. The instance is live migrated if you don't proactively reboot the instance before the due date.
    5. Select Save changes.

    Configuring the Lifecycle State

    1. On the Compute list page, select the instance that you want to work with. If you need help finding the list page, see Listing Instances.
    2. Select More Actions, and then select Edit.
    3. Select Show advanced options, and then select the Availability configuration tab.
    4. For the Restore instance lifecycle state after infrastructure maintenance checkbox, select an option:
      • To reboot a running instance after it's recovered, select the checkbox.
      • To recover the instance in the stopped state, clear the checkbox.
    5. Select Save changes.

  • Use the instance update command and required parameters to update an instance:

    oci compute instance update --from-json <file://path/to/file.json>

    <file://path/to/file.json> is the path to a JSON file that defines the instance details. For information about how to generate an example of the JSON file, see Advanced JSON Options.

    For a complete list of flags and variable options for the Compute Service CLI commands, see the command line reference for Compute.

  • For information about using the API and signing requests, see REST API documentation and Security Credentials. For information about SDKs, see SDKs and the CLI.

    Use this API operation to edit the maintenance recovery action for an instance: