Oracle Solaris Cluster (MOSC)

MOSC Banner

Zone migration (via update-on-attach) from clustered to standalone systems (and vice versa)

edited Apr 9, 2015 9:35AM in Oracle Solaris Cluster (MOSC) 4 commentsAnswered ✓

Hello Experts,

Scenario #1: Zone migration from clustered to standalone systems

We are having a couple of S10 sparse root Zones running (as local Zone nodes) on SC 3.3u2. These Zones do not host any cluster service. We are asked to migrate them via update-on-attach to standalone systems (not running SC software).

Problem:  some SC 3.3u2 packages (w/ SUNW_PKG_ALLZONES=true) are directly installed on the Zones

Following questions:

Q1: Do I understand it correctly that the update-on-attach on the standalone system (# zoneadm –z <ZONE> attach -U) will not be able to uninstall these packages ?

Q2: I guess that forcing the update-on-attach (# zoneadm –z <ZONE> attach -U –F), editing the pkginfo files (SUNW_PKG_ALLZONES=false), removing SC packages (# pkgrm <CLUSTER PACKAGES>) and adopting /etc/nsswitch.conf is not a supported solution. Can update-on-attach be used or is there another supported method for the Zone migration ?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center