Bug 2188593

1. Proposed title of this feature request
-----------------------------------------

[RFE] Include NetBackup's systemd unit files in rear rescue environment and start the services automatically.

2. Who is the customer behind the request?
------------------------------------------

This information will be attached as private comment after the BZ is created.

3. What is the nature and description of the request?
-----------------------------------------------------

The customer successfully uses rear and NetBackup 10.1.1 on RHEL 8. They try to validate this solution for RHEL 9 as it's an important part of their disaster recovery strategy.

In RHEL 8 NetBackup 10.1.1 installs init-scripts in `/etc/init.d/*`. These are included in the rear rescue environment when creating the rear ISO. When the customer creates the REAR ISO they are able to see all NBU /etc/init.d files and the service is automatically started.

On RHEL 9 however NetBackup 10.1.1 installs systemd service unit files instead of /etc/init.d files. Creating the rear ISO recovery environment, these files are not included. Booting the recovery ISO, the systemd service unit files are missing in the rescue environment.

Looking upstream at [0] it seems that rear takes care of files in /etc/init.d only but ignores systemd unit files.

4. Why does the customer need this? (List the business requirements here)
-------------------------------------------------------------------------

- NetBackup >= 10.1.1 on RHEL 9 uses systemd unit files instead of init-scripts in `/etc/init.d/*`
- The feature is an important part in the customers disaster recovery strategy.
- The missing feature is preventing the adoption of RHEL 9 in the customer's infrastructure.

5. How would the customer like to achieve this? (List the functional requirements here)

- When creating the rear recovery ISO the systemd unit files, needed to start the NetBackup services automatically after boot, should be getting included in the rear rescue ISO.
- When the RHEL 9 machine boots into the rear rescue environment using the ISO previously created the NetBackup services should start automatically.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

6.1. Install RHEL 9.1
6.2. Install Netbackup >= 10.1.1
6.3. Install rear, configure it, and create rescue ISO
6.4. Boot rear ISO
6.5. Check whether NetBackup services are started automatically

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
The customer would like to see this feature in RHEL 9.3.

9. Is the sales team involved in this request and do they have any additional input?
The sales team is currently not involved.

10. List any affected packages or components.
- rear
- NetBackup >= 10.1.1 (see [1] for reference)

11. Would the customer be able to assist in testing this functionality if implemented?
Yes.

Additional Information
----------------------

The customer is able to bring up the NetBackup services manually in the rear rescue environment running the following commands. However this is not convenient as it's adding several manual steps to the disaster recovery process for first level support:

~~~
/usr/openv/netbackup/bin/vnetd -standalone
/usr/openv/netbackup/bin/bpcd -standalone
/opt/VRTSpbx/bin/pbx_exchange
~~~

[0] https://github.com/rear/rear/blob/master/usr/share/rear/rescue/NBU/default/450_prepare_netbackup.sh

[1] https://download.veritas.com/resources/content/live/OSVC/100046000/100046445/en_US/nbu_100_scl.html?__gda__=1682113924_284c2b4b6c279132d4597b7ff56be943#operating_systems-red_hat_enterprise_linux