Oracle® VM Server for SPARC 3.3 Administration Guide

Exit Print View

Updated: October 2015

Migrating a Domain

You can use the ldm migrate-domain command to initiate the migration of a domain from one host machine to another host machine.

Note - If you migrate a domain, any named resources that you assigned by using the cid and mblock properties are dropped. Instead, the domain uses anonymous resources on the target system.

For information about migrating an active domain while it continues to run, see Migrating an Active Domain. For information about migrating a bound or inactive domain, see Migrating Bound or Inactive Domains.

For information about the migration options and operands, see the ldm(1M) man page.

Note - After a domain migration completes, save a new configuration to the SP of both the source and target systems. As a result, the state of the migrated domain is correct if either the source or target system undergoes a power cycle.

Performing a Dry Run

When you provide the –n option to the ldm migrate-domain command, migration checks are performed but the domain is not migrated. Any requirement that is not satisfied is reported as an error. The dry run results enable you to correct any configuration errors before you attempt an actual migration.

Note - Because of the dynamic nature of logical domains, a dry run could succeed and an actual migration fail, and vice versa.

Performing Non-Interactive Migrations

Use the SSL certificate method to perform non-interactive migration operations. Although the use of the legacy ldm migrate-domain -p filename command to initiate a non-interactive migration operation is deprecated, you can still use it.

    The file name you specify as an argument to the –p option must have the following characteristics:

  • The first line of the file must contain the password.

  • The password must be plain text.

  • The password must not exceed 256 characters in length.

A newline character at the end of the password and all lines that follow the first line are ignored.

The file in which you store the target machine's password must be properly secured. If you plan to store passwords in this manner, ensure that the file permissions are set so that only the root owner or a privileged user can read or write the file (400 or 600).