Problems related to installing and updating Ignite-UX

Related problems include:

Cleaning up old Ignite-UX software when an update didn’t match what was already on the system

Needing to ignite and recover an HP-UX release that Ignite-UX no longer supports

Needing to move back to an earlier version of Ignite-UX

Identifying the source from which Ignite-UX was installed

A change in the name of the full product bundle in version C.7.0 and later

Mismatched filesets after updating to version C.7.0 or later

Cleaning up after an update (if needed)

If you select different Ignite-UX bundles for update than were previously installed, you can end up with a mix of old and new software on the system. This situation causes problems when you try to run the make_tape_recovery (1M) and make_net_recovery (1M) commands. Both commands check the local system to ensure that Ignite-UX does not have mixed-revision filesets before allowing the command to run. Mixed-revision filesets will cause the command to end in error, and a recovery archive will not be created. If you accidentally create this scenario, you can clean up the older software using the swremove (1M) command, or you can add newer software using the swinstall (1M) command.

For example, assume you installed the Ignite-UX-11-11bundle from version C.7.2.x. A few months later you realize you need to support HP-UX 11i v2. Using your current OE media, you install the Ignite-UX-11-23bundle. However, the newer media contains Ignite-UX version C.7.3.x. The second installation results in mixed versions of Ignite-UX. To correct this situation, you can either remove the Ignite-UX-11-11bundle (assuming you no longer need to support HP- UX 11i v1), or you can install the C.7.3x version of the Ignite-UX-11-11bundle.

Dealing with obsolete HP-UX releases

When Hewlett-Packard stops supporting an HP-UX release, the OS-specific bundle for that release is removed from Ignite-UX. For example, in December 2005, Ignite-IA-11-22was removed from Ignite-UX C.6.5.x. In September 2004, Ignite-UX-10-20was removed from Ignite-UX C.6.0.x. In September 2007, Ignite-UX-11-00was removed from Ignite-UX C.7.3.x. To determine support for a specific release, refer to the Supported Versions of Ignite-UXdocument at http://www.docs.hp.com/en/IUX/supportinfo.html.

If your work environment requires continued support for an unsupported HP-UX release, you will need to maintain more than one Ignite-UX server. One server must remain on the last version of Ignite-UX to support the HP-UX release you need (e.g., Ignite-UX B.5.4.x for HP-UX 10.20). The other Ignite-UX server can continue to move forward with newer versions of Ignite-UX in order to support new hardware, features2, and revisions of HP-UX.

2For example, using the HP-UX 11i v2 September 2004 OE or later requires you to use Ignite-UX version C.6.0.x or later on your Ignite-UX server. Using VxVM 4.1 on clients requires you to run at least Ignite-UX version C.6.3.x.

6

Page 6
Image 6
HP manual Problems related to installing and updating Ignite-UX, Cleaning up after an update if needed

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.