Zone Migration Configuration Requirements

Before migrating, you need to consider configuration and host requirements, and package updates.

• Zone state – The zone's state must be installed when you begin the migration. After migration, the state will still be installed on the new host.

• Shared storage – If the zone is not on shared storage, you can use Unified Archives to move the zone, similar to a zone transformation. See About Zone Transformations.

• User authorizations – Migrations must be performed by a user or role that has the Zone Migration and Zone Configuration profiles. You can authorize specific non-root users to perform migrations. See Authorizing Non-Root Users to Perform Non-Global Zone Migrations for more information.

Zone resources – A solaris zone configuration must meet the following resource requirements to be migrated:

device Resource Type

Any device resources must be specified with storage URI. The match property cannot be set.

fs, dataset Resource Types

The fs and dataset resources are not allowed for cold migration because they refer to local file systems or local devices.

npiv:over-hba Resource Type Property

The npiv:over-hba property can only be set if the zone exists on the target system. This setting is bonded to a physical controller number, which is likely not consistent between the source and target systems. However, if the zone configuration exists on the target system before the migration, it is assumed that you have set up the systems so that the controller numbers are consistent and migration should be possible.

rootzpool, zpool Resource Types

The rootzpool and zpool resources must be specified with shared storage resources using iscsi and lu URIs.