Linux RN Limitations

Recovery Nodes running Linux have the following limitations:

•

To support booting of Recovery Nodes (RN) for RHEL 5.x servers, you must download the appropriate version of Xen‑compatible kernel packages and install them on the Protected Nodes (PN) before enrolling or attempting to build the RNs for such clients. The installed Xen kernel will not be an active kernel on the PN; instead, that kernel will be used to boot the RNs. For more information, go to Install kernel‑xen RPM package.

•	The filesystem format is required to be set in the Protection Node Configuration for each RN disk to ensure that onQ protection starts correctly.

•	For RHEL 5.x, the root disk partition (/) must be set to Format (file system type) parameter ext3 for the RN to boot correctly. The enrollment procedure, outlined in (Linux) Enroll protected nodes, accounts for this limitation.

•	After upgrading the onQ to 3.6, you need to do the following to upgrade your Linux nodes:

•	For 32-bit Linux nodes, after performing an automatically upgrade you must restart protection twice to upgrade the client services.

•	For 64‑bit Linux nodes, the client services will not automatically upgrade; therefore, you must run the install.py utility as outlined in (Linux) Update node software.

•	Linux PNs may return 256 code during an auto-upgrade. If you encounter this error, restart (stop/start) protection to re-initiate the auto-upgrade.

•	Network Manger on RHEL 5.9 (Tikanga) is required to be turned off to have self-test work correctly. Similar action need be taken if Kudzu services are running on the RHEL 5.x versions.

•	BMR and incremental failback for Linux nodes are not supported in this release.

v3.6 SP1