Zone Migration and Various Host Configurations

Observe the following guidelines concerning the source host and target host of a zone migration:

• If you are migrating a zone to an identical system and all storage references use a storage URI that is accessible by both hosts, the migrated configuration should be compatible without changes. If the target system is not identical, you must modify the configuration on the target system after migrationto suit the new system.

• If the zone storage is local, you cannot use the zoneadm migrate command. You can instead do one of the following:

  • Remove local storage devices from the zone configuration if they are not needed for booting, and then use zoneadm migrate.

  • Convert the storage to shared as described in How to Move a Zone to a Shared Storage Configuration, and then use zoneadm migrate.

  • Archive the zone and redeploy on the new system instead of migrating as described in Archiving and Moving Non-Global Zones That Are Not Using Shared Storage.

• If you configure the zone on the target host before migration, the target host's version of the zone configuration is used to boot the zone.

• If you do not configure the zone on the target host before migration, the zone configuration is exported from the source host and imported on the target host. The user performing the migration must have the Zone Configuration rights profile and solaris.zone.config authorization to create zone configurations on the target host. See Authorizing Non-Root Users to Perform Non-Global Zone Migrations for more information.