DPA services will not automatically start after reboot of Linux server.

Data Protection Advisor (DPA) services fail to start automatically on restart of O/S for Linux system which use systemd init process such as RHEL 7 and above or SUSE 12 and above.
This is seen when DPA is installed on a non root or mounted filesystem.

The cause of this issue is not known at this time.

At times the systemd process will not convert init.d entries to service files as systemd will first attempt to start services before mounting filesystems on remote mount points.  If DPA is installed on a filesystem which is a remote mount point then the DPA services will not start due to this.

To resolve this a systemd service file can be created to allow the O/S can start the DPA services.

Gather the following information from both the APP and DS servers in the environment:

systemctl | grep .mount

This will display a list of mounted filesystems. Find the filesystem where DPA install, which should similar to the below:
 

opt-data.mount - /opt/data

Active: active (mounted) since Tue 2017-07-18 18:00:43 MSK; 5min ago

Process: 742 ExecMount=/bin/mount -n -t xfs -o defaults /dev/disk/by-uuid/4d04e118-0d0a-49d4-b626-e58d1bb82a29 /opt/data (code=exited, status=0/SUCCESS)

The following commands will determine where the DPA init files are:
find / -name 'datasvc' -print
find / -name 'agentsvc' -print
find / -name 'applnsvc' -print

This command will return a path and in most cases it is either /etc/rc.d or /etc/init.d.

With this data the following systemd service files can be created:
datasvc.service
applnsvc.service
agentsvc.service

Note the above names must be used for these files and that they are simply text files.  Below has further information on the content required in each of these files: datasvc.service

Within the datasvc.service file on the DS system the SourcePath, ExecStart and ExecStop will need to be set to the datasvc location on the system.  For the After=network-online.target add the mount point at the end for the mount point where DPA is installed which was gathered from the systemctl status |grep .mount command.

[Unit]
SourcePath=/etc/init.d/datasvc
Description=EMC DPA Datastore Service
After=network-online.target opt-data.mount

[Service]
Type=forking
Restart=no
RemainAfterExit=yes
ExecStart=/etc/init.d/datasvc start
ExecStop=/etc/init.d/datasvc stop

[Install]
WantedBy=multi-user.target

applnsvc.service
Within the applnsvc.service file on the APP server make the SourcePath, ExecStart and ExecStop set to the applnsvc location on the system.  For the After=network-online.target add the mount point at the end for the mount point where DPA is installed which was gathered from the systemctl status |grep .mount command.

[Unit]
SourcePath=/etc/init.d/applnsvc
Description=EMC DPA Application Service
After=network-online.target opt-emc-dpa.mount

[Service]
Type=forking
Restart=no
RemainAfterExit=yes
ExecStart=/etc/init.d/applnsvc start
ExecStop=/etc/init.d/applnsvc stop

[Install]
WantedBy=multi-user.target


agentsvc.service
Within the agentsvc.service file on both the APP and DS servers the SourcePath, ExecStart and ExecStop set to the agentsvc location on the system.  For the After=network-online.target add the mount point at the end for the mount point where DPA is installed which was gathered from the systemctl status |grep .mount command.  You will need to make an agent.service file for both the APP agent and the DS agent.

[Unit]
SourcePath=/etc/init.d/agentsvc
Description=EMC DPA Agent Service
After=network-online.target opt-emc-dpa.mount

[Service]
Type=forking
Restart=no
RemainAfterExit=yes
ExecStart=/etc/init.d/agentsvc start
ExecStop=/etc/init.d/agentsvc stop

[Install]
WantedBy=multi-user.target

After creating these files copy the datasvc.service and the agentsvc.service files to the DS server under the /etc/systemd/system directory and the applnsvc.services and agentsvc.service to the /etc/systemd/system directory on the APP server. Once all the files have been copied complete the below steps in order:

1. Stop the DPA services on both the APP and DS servers.
2. Run the following commands on the DS server:
systemctl enable datasvc.service
systemctl enable agentsvc.service

systemctl start datasvc.service
systemctl start agentsvc.service

3. Run the following commands on the APP server:
systemctl enable applnsvc.service
systemctl enable agentsvc.service

systemctl start applnsvc.service
systemctl start agentsvc.service

4. Check DPA services status to ensure they are now running.
5. Reboot the APP then DS server.
6. Run the following command to confirm if services started with systemd:
DS server
systemctl status datasvc.service
systemctl status agentsvc.service

APP server
systemctl status applnsvc.service
systemctl status agentsvc.service

7. Check DPA services status with dpa svc status command.
8. If the DPA services did not start review the three files (datasvc.service, applnsvc.service, agentsvc.service) for errors.
9. After correcting the errors test again by following steps 1 - 7.