HP Ignite-UX manual For more information, Booting from the cluster using /etc/bootptab

Page 20

Booting from the cluster using /etc/bootptab

All bootptab entries must be maintained on the active cluster node, as this copy is linked to the shared version /etc/opt/ignite/bootptab. The local copies of /etc/bootptab on the inactive cluster nodes must not contain entries for clients that will be booting from the Ignite server.

Edit scripts on all cluster nodes for NFS client mounts

The /etc/dfs/dfstab file is not used in this configuration; the Serviceguard control scripts will export all file systems. Edit all cluster nodes’ control scripts to include NFS exports for recovery clients. In our case, /etc/cmcluster/ha-iux/hanfs.sh(from the NFS toolkit template) has the following:

#NFS: Specifies all exported NFS directories with share options. The

#directories must be defined in the mounted file system FS list specified

#in the control script. These variables are used by the command "share"

#to share the file systems and the command "unshare" to unshare the file systems.

#Example: XFS[0]="-o ro /pkg1"

#Example: XFS[1]="/pkg2"

#XFS[0]=""

XFS[0]="-o anon=2 /var/opt/ignite/data" XFS[1]="-o anon=2 /var/opt/ignite/clients" XFS[2]="-o sec=sys,anon=2,rw=sgiux3.fc.hp.com:sgiux4.fc.hp.com:sgiux5.fc.hp.com: sgiux6.fc.hp.com /var/opt/ignite/recovery/archives"

When using the Ignite UI or commands, always use the virtual server hostname and IP for the package

If you don't, you will have problems when running on other nodes, since Ignite stores the server IP in its config files.

Managing recovery images for cluster nodes

Recovery images for the individual cluster nodes can be created and restored as well, providing at least one cluster node remains running throughout the process. Always do this for nodes that are inactive. For example, if a package is running on node1, you can run make_net_recovery on node2 and also re-ignite node2 from the cluster itself. Again, always use the virtual server hostname and IP address.

For more information

The following relevant documents are available online at the HP Technical Documentation website at HP Business Support Center:

20

Page 19 Page 21
Image 20
Page 19 Page 21
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 Copy NFS toolkit cluster scripts in place Configure group for exclusive access and exportImport volume group data on all cluster nodes 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