LDOM reconfiguration after SB replacement Post: 302855965

6 More Discussions You Might Find Interesting

1. IP Networking

about NTP reconfiguration..

Most services can re-load/re-read their configuration file through the command "service xxxx reload", which is usually implemented by "kill -HUP service_pid" . for NTPD service, "service ntpd restart" and "service ntpd reload" are identical in /etc/rc.d/init.d/ntpd. what's more, "kill -HUP...

2. Red Hat

Force machine reconfiguration

Hi, This may be a dumb question, but here goes. While I have been using Linux for some time, I am wondering if a certain capability exists within Red Hat that I have found within SUSE. Cool stuff you might not know that AutoYast can do ? Part 1 Linux In Novell’s East Region points to...

3. Solaris

Autosys on LDOM

Has anyone configured an Autosys server to run on a Solaris LDOM? I can't think of any obvious reason why there would be a problem with it, but.... Jerry

4. Solaris

ldom and zone

hi, what is the difference between ldom and zone. can we install any other os than sun in ldom. thanks, snj.

5. Solaris

ldom patching

Greetings everyone! I have the task of patching six ldoms and two control domains. I have never done this before and would like to know of any pitfalls or "gotchas" I may encounter. I have been looking online but have found very little about patching ldoms. Thank you all.

6. Solaris

Ldom problem

Hi People, I have been trying to learn solaris ldoms, have created one on a T2000 and get the following error when try to install it off DVD WARNING: /virtual-devices@100/channel-devices@200/disk@1: Communication error with Virtual Disk Server using Port 0. Retrying If anyone could help...

LEARN ABOUT HPUX

vxconfigbackupd

vxconfigbackupd(1M)													       vxconfigbackupd(1M)

NAME

       vxconfigbackupd - disk group configuration backup daemon

SYNOPSIS

       vxconfigbackupd [-l]

DESCRIPTION

       The vxconfigbackupd daemon automatically backs up information about a disk group's new configuration whenever the configuration is changed.

OPTIONS

       -l	 Logs backup daemon activities to the file /etc/vx/cbr/bkdaemonLog.

FILES

       /sbin/init.d/vxvm-recover
		 Startup file for vxconfigbackupd.

       /etc/vx/cbr/bk/dgname.dgid/dgid.dginfo
		 Location of backup file for disk group information.

       /etc/vx/cbr/bk/dgname.dgid/dgid.diskinfo
		 Location of backup file for disk attributes.

       /etc/vx/cbr/bk/dgname.dgid/dgid.binconfig
		 Location of backup file for binary configuration copy.

       /etc/vx/cbr/bk/dgname.dgid/dgid.cfgrec
		 Location of backup file for configuration records in vxprint -m format.

NOTES

       The vxconfigbackup command can be used to back up a disk group's configuration manually at any desired time.

       The  disk  group  configuration	backup and restore utilities do not save any data in the public region. This includes file system or other
       application data that is configured within VxVM objects.

       When a disk group is destroyed, its configuration backup information (including the backup directory) is also removed.  The only  exception
       to this behavior is when the disk group is in the precommit state of restoration.

       The  backup  directory should be large enough to accommodate copies of all the currently imported disk groups. The minimum recommended size
       of the backup directory is P * (N + 1) megabytes, where P is the private region in megabytes (by default, 32MB), and N  is  the	number	of
       disk  groups. The additional P megabytes is required to hold a temporary copy of the disk group configuration when a disk group is imported
       or a configuration change is made.

       The default backup directory is /etc/vx/cbr/bk.	The location of the backup directory can be configured	by  using  the	vxconfigbackup	-l
       backup_directory_path command.

SEE ALSO

       vxconfigbackup(1M), vxconfigrestore(1M)

VxVM 5.0.31.1							    24 Mar 2008 					       vxconfigbackupd(1M)