HP Ignite-UX manual Best practices

Page 19

16.Create archive directories for cluster nodes

Log into the virtual service for the package and create archive directories for all cluster nodes.

#cd /var/opt/ignite/recovery/archives

#mkdir -p sgiux3 sgiux4 sgiux5 sgiux6

#chown bin:bin *

#cd /

17.Add clients and create recovery archives

Add all cluster nodes as clients and then create recovery archives for each inactive node (not running the ha-iuxpackage). From each node, execute the following:

# /opt/ignite/bin/add_new_client \

–s[ha-iux virtual hostname or IP]

From each inactive node, create a recovery archive. These can run in parallel using the virtual server IP. When they all complete, the package can be moved to another node to allow archive creation for the last node.

#/opt/ignite/bin/make_net_recovery -x inc_entire=vg00 \

–s[ha-iux virtual hostname or IP]

Best practices

Upgrading Ignite-UX

To upgrade the version of Ignite-UX on the cluster, you will need to swinstall the newer version on each node one at a time. The Serviceguard package must be running on the node that is updating. This swinstall will execute pkg_rec_depot when necessary. After the last node is updated, the customizations from step 15 will need to be re-applied.

Inactive cluster nodes and swverify

On nodes that are not running the Ignite Serviceguard package, swverify of IGNITE will fail.

This is expected due to /var/opt/ignite, /etc/opt/ignite, and /opt/ignite/boot being set up for exclusive access.

Other depots under shared file systems

If there are other SD depots under shared file systems such as /var/opt/ignite, they will need to be registered on each cluster node individually while the Ignite package is running on that node, or registered by Serviceguard when the Ignite package starts. To manage from Serviceguard, The swreg commands can be added to the /etc/cmcluster/ha-iux/nfs.cntl customer_defined_run_cmds and customer_defined_halt_cmds similar to the handling

of the /var/opt/ignite/depots/recovery_cmds depot. When you swinstall from these depots, be sure to use the virtual hostname or IP for the Ignite Serviceguard package.

19

Page 18 Page 20
Image 19
Page 18 Page 20
Contents Table of Contents Configuring an Ignite-UX server under HP ServiceguardFor more information About this document Advantage of running Ignite-UX under ServiceguardSetting up Ignite-UX to run under Serviceguard Serviceguard packages and scriptsPage Create logical volumes for the shared file systems MWC Create mount points for the shared file systemsAdd 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 Etc/cmcluster/ha-iux/hanfs.sh Etc/cmcluster/ha-iux/nfs.cntl Create package config and scriptsPage Add the new package to the cluster on the first node Copy completed package directory to all nodesBring 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 Edit scripts on all cluster nodes for NFS client mounts Booting from the cluster using /etc/bootptabManaging recovery images for cluster nodes For more information
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