10-31-2008
The syntax for cloning a zone will be:
# zoneadm -z new-zone clone [-m method] method_params
Cloning a zone is analogous to installing a zone. That is, you first must configure the new zone using the zonecfg command. Once you have the new zone in the configured state you can use clone to set up the zone root instead of installing. This allows all
customizations (configuration, pkgs, etc.) from the source zone to be directly instantiated in the new zone. The new zone will be left in the sys-unconfigured state even though the source zone is likely to be fully configured. The source zone must be halted while the clone is running.
The zoneadm command will be enhanced to perform additional verification when cloning. Appropriate warnings and errors will be printed if the new zone and source zone are configured inappropriately.
The -m option specifies the method used to clone the source. The default and initial -m method will be “copy”. This will copy the data from the source zone (specified as the method_param) zonepath to the new-zone zonepath (implemented using cpio as with the move sub-command).
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Need some advice and guidance for this UNIX beginner. Due to downsizing I have inherited the SysAdmin duties..(sigh). Please excuse and forgive me if I use the wrong terms below....
Situation:
We have UNIX ( Solaris 7/8/9( it varies) on Sun Ultra 10's) servers located at several global... (1 Reply)
Discussion started by: HikerLT
1 Replies
2. Solaris
Hi Every,
I would like to know some questions on Zones???
1.what are types of zones we can install in global zone???
2.Exact difference between sparce root and whole root???
3.can we change the ip address of a running zone???
4.how to find our in which zone we are running and how many... (8 Replies)
Discussion started by: tirupathiraju_t
8 Replies
3. UNIX for Advanced & Expert Users
I have several Solaris 8,9 and 10 servers.
I need to refresh them and avoid doing any OS upgrades. I may have to apply patches when I am done due to the new hardware.
My current servers have internal disk and my new target servers (same processor types) will have only SAN storage. Once the... (0 Replies)
Discussion started by: zzqv9p
0 Replies
4. Solaris
Dear All,
I have been trying to move my existing Solaris Installation (x86, 10/08) to a bigger HDD.
So I created a 22 cylinder boot partition and used the rest of the space for a Solaris2 partition. Then I created slices same size like on my current disk.
I copied all files with cpio and... (3 Replies)
Discussion started by: BigT79
3 Replies
5. Solaris
Hello and let me say at first, thank you for viewing this problem I have.
From the top!
Where I work, we have a Dell PowerEdge T300 X86 system running Solaris 10 8/07 s10x_u4wos_12b X86, and we realized, if this machine went down, we would be in trouble. So to fix that situation, I took it... (5 Replies)
Discussion started by: nitrolinux
5 Replies
6. Solaris
Hello,
What is the best method to use to clone a Solaris 10 machine with zones, to ensure all software and config can be easily installed on new hardware?
Thank You (4 Replies)
Discussion started by: da2013
4 Replies
7. Solaris
Hi All
Kindly let me know how can I move Solaris 10 OS running update 10 on physical machine to another machine solaris zone running Solaris 10 update 11 (2 Replies)
Discussion started by: amity
2 Replies
8. Solaris
Hello all, this is my first time posting here. Where I work we have multiple servers (x3-2's) running Solaris 10u11 with 2 drives configured as RAID0, 300GB per. There are 4-6 open slots for drives to clone to.
Past attempts to clone/backup these drives has failed. One of the machines is... (1 Reply)
Discussion started by: eprlsguy
1 Replies
9. Solaris
Hi all,
I am trying to use archiveadm to backup/clone an existing Solaris11.4 system.
However, i failed at media creation with the error -> "Media can only be created from archives containing root-only data"
root@xxx:/mnt/opt/software# zpool list
NAME SIZE ALLOC FREE CAP DEDUP ... (6 Replies)
Discussion started by: javanoob
6 Replies
LEARN ABOUT OPENSOLARIS
lx
lx(5) Standards, Environments, and Macros lx(5)
NAME
lx - Linux branded zone
DESCRIPTION
The lx brand uses the branded zones framework described in brands(5) to enable Linux binary applications to run unmodified on a machine
with a Solaris Operating System kernel.
The lx brand includes the tools necessary to install a CentOS 3.x or Red Hat Enterprise Linux 3.x distribution inside a non-global zone.
The brand supports the execution of 32-bit Linux applications on x86/x64 machines running the Solaris system in either 32-bit or 64-bit
mode.
Supported Linux Distributions
The lx brand emulates the system call interfaces provided by the Linux 2.4.21 kernel, as modified by Red Hat in the RHEL 3.x distributions.
This kernel provides the system call interfaces consumed by the glibc version 2.3.2 released by Red Hat.
In addition, the lx brand partially emulates the Linux /dev and /proc interfaces.
Configuration and Administration
The lx brand supports the whole root non-global zone model. All of the required linux packages are installed into the private file systems
of the zone.
The zonecfg(1M) utility is used to configure an lx branded zone. Once a branded zone has been installed, that zone's brand cannot be
changed or removed. The zoneadm(1M) utility is used to report the zone's brand type and administer the zone. The zlogin(1) utility is used
to log in to the zone.
Application Support
The lx zone only supports user-level Linux applications. You cannot use Linux device drivers, Linux kernel modules, or Linux file systems
from inside an lx zone.
You cannot add any non-standard Solaris devices to a Linux zone. Any attempt to do so will result in a zone that zonecfg(1M) will refuse to
verify.
You cannot run Solaris applications inside an lx zone. Solaris debugging tools such as DTrace (see dtrace(1M)) and mdb (see mdb(1)) can be
applied to Linux processes executing inside the zone, but the tools themselves must be running in the global zone. Any core files generated
are produced in the Solaris format, and such files can only be debugged with Solaris tools.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWlxr, SUNWlxu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
mdb(1), zlogin(1), zonename(1), dtrace(1M), zoneadm(1M), zonecfg(1M), brands(5), zones(5), lx_systrace(7D)
SunOS 5.11 19 Sep 2006 lx(5)