Oracle Cloud Infrastructure Documentation

Manage Migrations

This topic describes how to create and manage a migration.

Caution

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

About Migrations

A migration represents the end-to-end workflow of moving an application from a source environment to Oracle Cloud Infrastructure. Each migration moves a single application from a specified source to a specified compartment in Oracle Cloud Infrastructure.

To perform a migration:

  1. Create a migration source by specifying the source environment and providing credentials for Classic Migration Service to access the source environment. Classic Migration Service discovers the resources in the source environment.
  2. Select the application that you want to migrate. Applications that can be migrated are listed on the Applications page for each source. Before you start the migration, you must provide application-specific information including a name for the migrated application in the target environment and user credentials to access the application in the source environment. Classic Migration Service uses this information to access the application and export the complete domain configuration along with data sources and other dependencies. Classic Migration Service uses this information to access the application and discover application artifacts and dependencies. For example, Classic Migration Service accesses the Oracle Java WebLogic Server domain configuration and its data sources.
  3. Create a migration. To create a migration, select a source environment and then select the application in that source environment that you want to migrate. After creating a migration, wait for Classic Migration Service to complete the create migration work request associated with this task. The process of migrating the application to the target environment has not started, at this point.
  4. Provide configuration information about the application in the target environment. Classic Migration Service migrates the application to the target environment only after you provide this information. Use the Configure Migration wizard to specify information about the target environment and the application that you are migrating. The information that you must provide varies depending on the type of application that you are migrating.
  5. Start the migration. Classic Migration Service migrates the specified application from the source environment to Oracle Cloud Infrastructure.

The name of the migrated application is the same as its name in its source environment. If there are any dependencies, such as an associated database system, then Classic Migration Service creates an Oracle Cloud Infrastructure Database System. To name the database system, Classic Migration Service appends db to the name of the application. For example, if you want to migrate an Oracle Java Cloud Service application named MyApp in the source environment, then Classic Migration Service creates the application with the same name, MyApp, in Oracle Cloud Infrastructure and the associated database system is named MyAppdb.

A migration is successful when:

  • The target service instance is started and is healthy.
  • The service instance has been configured with all the dependencies required by the application.
  • The application has been deployed to the service instance and is reported to be in a healthy state.

After a migration completes successfully, ensure that you validate the behavior of the application in terms of its business logic. Classic Migration Service does not perform this validation.

If the migration fails, then examine the work request errors and logs to diagnose the issues. After resolving the issues, you can restart the migration.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy written by an administrator, whether you are using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you do not have permission or are unauthorized, then confirm with your administrator the type of access you have and in which you should work.

If you are new to policies, then see Getting Started with Policies and Common Policies. If you want to dig deeper into writing policies for Classic Migration Service API resources, then see Manage Service Access and Security.

Tagging Migrations

You can add tags to your resources to help you organize them according to your business needs. You can add tags at the time you create a resource, or you can update the resource later with the desired tags. For general information about applying tags, see Resource Tags.

Using the Console

To start a migration

You can start a migration only after you've provided the configuration information for the target environment. When you start a migration, Classic Migration Service migrates the application and its dependencies to Oracle Cloud Infrastructure.

After providing configuration information for the target environment, you can start the migration whenever you are ready. Classic Migration Service validates the details you have provided while creating and configuring the migration. You can migrate the application only after the validation is complete. The migration is in the ready state when the validation is complete. You can now start the migration.

While configuring the migration, if you selected the option to start the migration, then no further action is required. Classic Migration Service updates the migration with the configuration information that you have provided for the target environment, and then migrates the application.

  1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click Sources in the Classic Migration section to display the Sources in compartment page and a list of sources in the compartment.
  2. Click Migrations to view the list of migrations and their status.
  3. Click the migration that you're interested in.
  4. Click Start on the migration details page.

The status of the migration changes to migrating. The Work Requests page appears and displays the status of the migrate application work request. To track the progress of the operation, you can monitor the associated work request. For more information, see Viewing the State of a Work Request. When this work request is processed successfully, Classic Migration Service creates the required resources in the target environment and the status of the migration changes to migration succeeded.

If the migration fails, the status of the migration changes to Migration failed. You can look at the logs and errors for the migrate application work request to troubleshoot the issues. After resolving the issues, you can restart the migration whenever you are ready.

To delete a migration

If you have migrated the application or for any other reason if you no longer require a migration, then you can delete the relevant migration. When you delete a migration, it does not delete any resources that Classic Migration Service had created while migrating the application.

You can delete a migration, irrespective of its state. If any work request is being processed for the migration that you are deleting, then the associated work requests are canceled and the migration is deleted.

  1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click Sources in the Classic Migration section to display the Sources in compartment page and a list of sources in the compartment.
  2. Click Migrations to view the list of migration and their status.
  3. Find the migration that you're interested in.
  4. Click the Actions icon (three dots), and then click Delete.
    A confirmation message is displayed.
  5. If you are sure that you want to delete the migration, click Delete.
To manage tags for a migration

  1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click Sources in the Classic Migration section to display the Sources in compartment page and a list of sources in the compartment.
  2. Click the migration that you're interested in.
  3. Click the Tags tab to view or edit the existing tags. Or click Apply tag(s) to add new ones.

For more information, see Resource Tags.

To move a migration to a different compartment

You can move a migration from one compartment to another. For more information, see Moving Resources to a Different Compartment.

  1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click Sources in the Classic Migration section to display the Sources in compartment page and a list of sources in the compartment.
  2. On the Classic Migration Service page, click Migrations.
  3. Find the migration in the list. Click the Actions icon (three dots), and then click Move Resource.
  4. Choose the destination compartment from the list.
  5. Click Move Resource.