HP Ignite-UX manual

Page 4

∙File systems to export - only the active cluster node has exported file systems

Procedure to set up Ignite under Serviceguard

1.Create an LVM volume group to manage the shared file systems

This volume group will contain /etc/opt/ignite, /opt/ignite/boot, and /var/opt/ignite. This must be on a RAID array and must be accessible by each of the other cluster nodes. You must have approximately 1 GB of free disk space available in /opt/ignite/boot. For this example, we have a 104 GB disk.

If you use a location other than /var/opt/ignite to store archives on the Ignite server, you will need to change these instructions so your custom location is available via NFS as part of this package. If your archives are stored outside the cluster, using a highly available Ignite package in a Serviceguard cluster does not improve the availability of your archives - if the archive server is down, you will not be able to perform any recoveries.

Execute the following on the first cluster node.

# diskinfo /dev/rdsk/c13t0d2

SCSI describe of /dev/rdsk/c13t0d2: vendor: COMPAQ

product id: HSV111 (C)COMPAQ type: direct access size: 104857600 Kbytes

bytes per sector: 512

#

#mkdir /dev/vg01

#chmod 755 /dev/vg01

#mknod /dev/vg01/group c 64 0x010000

For the mknod command, the major number is always 64 and the hexadecimal minor number has the form 0xhh0000 where hh must be unique to the volume group you are creating. You must use the same minor number for the volume group on all the nodes. You need to determine in advance what minor number is available on all cluster members for this new volume group by reviewing what has been used on all cluster members. Once you determine what minor number is available, use it instead of the 0x010000 value used in the example.

#chmod 640 /dev/vg01/group

#pvcreate -f /dev/rdsk/c13t0d2

Physical volume "/dev/rdsk/c13t0d2" has been successfully created.

#vgcreate -s 16 /dev/vg01 /dev/dsk/c13t0d2 Increased the number of physical extents per physical volume to 6399.

Volume group "/dev/vg01" has been successfully created. Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf

4

Page 3 Page 5
Image 4
Page 3 Page 5
Contents Configuring an Ignite-UX server under HP Serviceguard Table of ContentsFor more information Advantage of running Ignite-UX under Serviceguard Setting up Ignite-UX to run under ServiceguardServiceguard packages and scripts About this documentPage Create logical volumes for the shared file systems Create mount points for the shared file systems MWCAdd the -soption to /usr/lbin/tftpd Import volume group data on all cluster nodes Configure group for exclusive access and exportCopy NFS toolkit cluster scripts in place Create package config and scripts Etc/cmcluster/ha-iux/hanfs.sh Etc/cmcluster/ha-iux/nfs.cntlPage Copy completed package directory to all nodes Add the new package to the cluster on the first nodeBring up the package on each node and install Ignite-UX Page Execute pkgrecdepot on the first node only Page Objects /var/opt/ignite/depots/recoverycmds Page Update the Ignite server IP address Best practices Booting from the cluster using /etc/bootptab Managing recovery images for cluster nodesFor more information Edit scripts on all cluster nodes for NFS client mounts
Related manuals
Manual 9 pages 7.38 Kb

Ignite-UX specifications

HP Ignite-UX is a sophisticated system recovery tool developed for the HP-UX operating system. It plays a vital role in ensuring that HP-UX environments can be efficiently restored to a known good state in the event of a system failure, corruption, or mishap. The tool provides administrators with a user-friendly interface and comprehensive features that enable them to quickly deploy, recover, and maintain HP-UX systems.

One of the defining features of HP Ignite-UX is its ability to create system recovery archives. These archives can encapsulate a fully configured HP-UX system, including both the operating system and installed applications. This allows for quick restoration of systems to their exact configurations when necessary, saving both time and resources. Additionally, Ignite-UX supports network-based installations, making it possible to deploy systems remotely, which is particularly advantageous for organizations with multiple servers spread out across different locations.

Another significant aspect of Ignite-UX is its integration with the HP-UX Model. The tool leverages the underlying technologies of HP-UX, such as LVM (Logical Volume Management) and filesystem structures, to ensure that recovery processes are both efficient and reliable. By working closely with these features, Ignite-UX can handle complex restoration tasks with minimal user intervention. This ability to interact seamlessly with other HP-UX components reinforces its reputation as a critical utility for system administrators.

Ignite-UX is designed to be flexible and adaptable, catering to a variety of use cases. It supports creation of bootable recovery media on different formats, including DVD, USB, and network images, enabling easy access during disaster recovery scenarios. Furthermore, the tool includes a set of advanced diagnostics to help troubleshoot issues, providing detailed logs and reports to assist administrators in identifying root causes of system failures.

Security is also a top priority for HP Ignite-UX. The tool ensures that backups are securely encrypted, safeguarding sensitive data against unauthorized access during the restore process.

In conclusion, HP Ignite-UX stands out as a robust solution for system recovery and management within HP-UX environments. With its comprehensive features, including system recovery archives, network-based installations, seamless integration with HP-UX technologies, flexible media options, and strong security measures, Ignite-UX is an invaluable asset for organizations looking to enhance their system reliability and minimize downtime.
Top Page Image Contents