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.

•	onQ Portal enforces specific filesystem requirements:

•	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 any Linux PN, you must protect both / and /boot and any other mount points that contain the necessary software to boot the RN.

•	(RHEL 7.0 PNs) The Format (file system type) parameter for the boot partition (/boot) must be set to ext3. If you choose to protect the xfs file system, the Format (file system type) parameter for this volume must be set to ext4.

•	(RHEL 6.x/RHEL 7.0 PNs) If you choose to protect the xfs file system, the Format (file system type) parameter for this volume must be set to ext4.

•	(RHEL 5.x PNs) The Format (file system type) parameter for the root partition (/) must be set to ext3.

•	(Agent‑less Linux PNs) Cannot protect xfs volumes. Use ext2, ext3, and ext4 as /boot or data volumes.

•	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.

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

v3.8 SP1 HF1