Chapter 35

Moving and Migrating lx Branded Zones (Tasks)

This chapter describes how to:

• Move an existing lx branded zone to a new location on the same machine

• Validate what will happen in an lx branded zone migration before the actual migration is performed.

• Migrate an existing lx branded zone to a new machine.

Moving an lx Branded Zone

This procedure is used to move a zone to a new location on the same system by changing the zonepath. The zone must be halted. The new zonepath must be on a local file system. The normal zonepath criteria described in Resource and Property Types apply.

How to Move a Zone

1. Become superuser, or assume the Primary Administrator role.

   Roles are described in "Using the Solaris Management Tools With RBAC (Task Map)" in System Administration Guide: Basic Administration.

2. Halt the zone to be moved, db-zone in this procedure.

   global# zoneadm -z db-zone halt

   
   

3. Use the zoneadm command with the move subcommand to move the zone to a new zonepath, /export/zones/db-zone.

   global# zoneadm -z db-zone move /export/zones/db-zone

   
   

4. Verify the path.

   global# zoneadm list -iv ID NAME STATUS PATH BRAND 0 global running / native - lx-zone installed /export/home/lx-zone lx - db-zone installed /export/zones/db-zone lx

   
   

Migrating an lx Branded Zone to a Different Machine

You can do a trial run of a zone migration before you actually move the zone to a different machine. For more information, see About Validating a Zone Migration Before the Migration Is Performed.

Note that the trial run does not validate the processor type, so you must verify that the target machine is running a supported processor.

About Migrating an lx Branded Zone

The zonecfg and zoneadm commands can be used to migrate an existing non-global zone from one system to another. The zone is halted and detached from its current host. The zonepath is moved to the target host, where it is attached.

The following requirements apply to lx branded zone migration:

• The global zone on the target system must be running the same Solaris release as the original host.

• To ensure that the zone will run properly, the target system must have the same versions of the required operating system packages and patches that were installed on the original host.

• The brand must be the same on the original host and on the target system.

• The target system must have one of the following supported i686 processor types:

  • Intel

    • Pentium Pro

    • Pentium II

    • Pentium III

    • Celeron

    • Xeon

    • Pentium 4

    • Pentium M

    • Pentium D

    • Pentium Extreme Edition

    • Core

    • Core 2

    AMD

    • Opteron

    • Athlon XP

    • Athlon 64

    • Athlon 64 X2

    • Athlon FX

    • Duron

    • Sempron

    • Turion 64

    • Turion 64 X2