Oracle Solaris System Administration (MOSC)

MOSC Banner

Best practise for managing orphaned beadms

in Oracle Solaris System Administration (MOSC) 2 commentsAnswered ✓

Hi we have had to move some native zones between global zones during hardware failures. I have noticed there some orphaned beadms not associated with the current running boot env on the global zone it is running on.

I have looked around for recommendations on tidying these and not really found very much yet.Is anyone aware of any docs on best practise for managing boot envs on non-global zones.

Do I just use beadm destroy -o whilst the zone is running and if I do this will it cause an issue if I want to move the zone back over onto the old global zone - or will it just create a new beadm and associate it with the new global zone when imported?

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