Sponsored Content
Full Discussion: live upgrade SUN cluster
Operating Systems Solaris live upgrade SUN cluster Post 302557978 by DukeNuke2 on Thursday 22nd of September 2011 12:07:37 PM
 

8 More Discussions You Might Find Interesting

1. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

2. Solaris

Live upgrade Issue

Hi, I upgraded solaris 10 x86 from update 3 to update 7 with zones installed n UFS file system . The global zone was updated but the non global zone still shows update 3 what could be the reason for this and how can i update the local zones to update 7 (0 Replies)
Discussion started by: fugitive
0 Replies

3. Solaris

Sun Live Upgrade - lucreate fails

Hi, I currently have one BE and would like to create an ABE. # lustatus BE_name Complete Active ActiveOnReboot CopyStatus ------------------------------------------------------------------------ coolthreads yes yes yes - But... (3 Replies)
Discussion started by: pgarousi
3 Replies

4. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

5. Solaris

Live upgrade question

I want to basically update an ABE that someone created a few months back. I'm sure stuff has changed since it was made, and I was going to delete it and create a new one. But from what I'm looking at, the lumake appears like it would be a faster approach. I want to use live upgrade to... (0 Replies)
Discussion started by: BG_JrAdmin
0 Replies

6. Emergency UNIX and Linux Support

Live Upgrade Query

I am upgrading Solaris-9 Update-7 to Solaris-9 Update-9 through live upgrade. I am able to create another boot environment and have OS DVD inside server. But i am confused for, what command/path should I give for luupgrade. OS DVD is mounted on /mnt Boot environments are Solaris9old (Active now)... (2 Replies)
Discussion started by: solaris_1977
2 Replies

7. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

8. Solaris

Live upgrade first steps

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
ludelete(1M)															      ludelete(1M)

NAME
ludelete - delete a boot environment SYNOPSIS
/usr/sbin/ludelete [-l error_log] [-o outfile] BE_name [-X] DESCRIPTION
The ludelete command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See live_upgrade(5) for a description of the Live Upgrade feature. The ludelete command deletes all records associated with a boot environment (BE) on all defined complete BEs. A complete BE is one that is not participating in an lucreate(1M), luupgrade(1M), or lucompare(1M) operation. Use lustatus(1M) to determine a BE's status. You can delete neither the current BE, nor the BE that will become current upon the next reboot. Also, you cannot delete a BE that has file systems mounted with lumount(1M) or mount(1M). ludelete does not alter any files on the BE being deleted. The ludelete command requires root privileges. OPTIONS
The ludelete command has the following options: -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -o outfile All command output is sent to outfile, in addition to where it is sent in your current environment. -X Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version number of the DTD file. OPERANDS
BE_name Name of the BE to be deleted. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
/etc/lutab list of BEs on the system /usr/share/lib/xml/dtd/lu_cli.dtd.<num> Live Upgrade DTD (see -X option) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWluu | +-----------------------------+-----------------------------+ SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure- name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 24 Jan 2002 ludelete(1M)
All times are GMT -4. The time now is 07:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy