04-06-2019
After re-reading your post I realized that my original response was, incorrect for what you needed.
I'm not sure about the possibility of creating another
zpool from a standalone rpool. I doubt it's even possible.
To create a zpool, you need a separate disk, you are
able to create a zfs dataset from the rpool but not recommended.
As for the alternative BE to apply patches to, I believe lucreate
makes/has a pre-defined directory which it places the alternative
BEs'.
Let me know if you where able to get this resolved as this
will help solaris admins alike.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
what are the typical steps used by system adminstrators while applying an application patch upgrade (1 Reply)
Discussion started by: ramky79
1 Replies
2. Solaris
Attempting to patch several servers using live upgrade
Release: Oracle Solaris 10 8/11 s10x_u10wos_17b X86
Error I'm receiving is in the message in the log below
tail -15 /var/svc/log/rc6.log
Legacy init script "/etc/rc0.d/K50pppd" exited with return code 0.
Executing legacy init... (5 Replies)
Discussion started by: Siralos
5 Replies
3. Solaris
What are the Pre-installation steps for patching on Solaris servers in real time ?
:confused: (6 Replies)
Discussion started by: vijaykrishna
6 Replies
4. Solaris
I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade.
Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less... (7 Replies)
Discussion started by: solaris_1977
7 Replies
5. Solaris
Hello Guys,
I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me.
The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade?
1. before creating the new boot environment? or
2. after creating... (1 Reply)
Discussion started by: cjashu
1 Replies
6. Solaris
Hello,
I was assigned some Solaris machines and need to patch them to N-1, where N is the latest OS realease, which means, upgrade till one version before the latest one.
I do not now a lot about Solaris. What I only know is that need to make use of live upgrade and be careful with VxVM... (4 Replies)
Discussion started by: feroccimx
4 Replies
7. Solaris
Hi all,
I would like to ask what will be the best practice for the following setup
/ - c0t0d0s0 - current BE (named First)
/ - c0t0d1s0 - alternate BE (name Second)
i have a non-global zone with zonepath in /zones/myzone
/mnt/opt - c0t0d2s6 (shared between the 2 BE)... (3 Replies)
Discussion started by: javanoob
3 Replies
LEARN ABOUT SUSE
crm_diff
CRM_DIFF(8) [FIXME: manual] CRM_DIFF(8)
NAME
crm_diff - identify changes to the cluster configuration and apply patches to the configuration files
SYNOPSIS
crm_diff [-?|-V] [-o filename] [-O string] [-p filename] [-n filename] [-N string]
DESCRIPTION
The crm_diff command assists in creating and applying XML patches. This can be useful for visualizing the changes between two versions of
the cluster configuration or saving changes so they can be applied at a later time using cibadmin.
OPTIONS
--help, -?
Print a help message.
--original filename, -o filename
Specify the original file against which to diff or apply patches.
--new filename, -n filename
Specify the name of the new file.
--original-string string, -O string
Specify the original string against which to diff or apply patches.
--new-string string, -N string
Specify the new string.
--patch filename, -p filename
Apply a patch to the original XML. Always use with -o.
--cib, -c
Compare or patch the inputs as a CIB. Always specify the base version with -o and provide either the patch file or the second version
with -p or -n, respectively.
--stdin, -s
Read the inputs from stdin.
EXAMPLES
Use crm_diff to determine the differences between various CIB configuration files and to create patches. By means of patches, easily reuse
configuration parts without having to use the cibadmin command on every single one of them.
1. Obtain the two different configuration files by running cibadmin on the two cluster setups to compare:
cibadmin -Q > cib1.xml
cibadmin -Q > cib2.xml
2. Determine whether to diff the entire files against each other or compare just a subset of the configurations.
3. To print the difference between the files to stdout, use the following command:
crm_diff -o cib1.xml -n cib2.xml
4. To print the difference between the files to a file and create a patch, use the following command:
crm_diff -o cib1.xml -n cib2.xml > patch.xml
5. Apply the patch to the original file:
crm_diff -o cib1.xml -p patch.xml
FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.
SEE ALSO
???
AUTHOR
crm_diff was written by Andrew Beekhof.
[FIXME: source] 07/05/2010 CRM_DIFF(8)