Reading the fine manual, it states:

IMPORTANT:
Before rebooting or stopping the Linux or Windows server, you must manually shut down all the stores on the
Deduplication Store system and Media Agent system. Failing to do so may result in a corrupted store and data
loss.
Perform the following steps to shut down a store:
1. On the Media Agent system, to shut down the deduplication services on Linux and Windows, run the following
command:
<DP_Home_Dir>\DPDClientUtils -shutdown <DP_Data_Dir>\Config\client\SdfsProxyPort.conf
Example: DPDClientUtils -shutdown C:\ProgramData\OmniBack\Config\client\SdfsProxyPort.conf
DPDClientUtils is an internal Data Protector utility and the output isn't displayed.
2. On the Deduplication server, to shutdown the Deduplication Store, run the following command: DPDUtils -shutd
own_all

So I considered to write a systemd unit for Linux to do that. However I discovered that there is already a unit named /usr/lib/systemd/system/dp_dedup.service:

# systemctl cat dp_dedup.service
# /usr/lib/systemd/system/dp_dedup.service
[Unit]
 Description=DP Deduplication Store Startup and Shutdown Service
 After=omni.service network.target

[Service]
 Type=simple
 RemainAfterExit=yes
 ExecStart=/bin/bash /opt/omni/sbin/dp_dedup_start.sh
 ExecStop=/bin/bash /opt/omni/sbin/dp_dedup_stop.sh
 TimeoutStartSec=10min
 TimeoutStopSec=10min
 [Install]
 WantedBy=multi-user.target

So I inspected those shell scripts:

# cat /opt/omni/sbin/dp_dedup_start.sh
#!/bin/bash
DT=`date "+%d.%m.%Y %T"`
echo "${DT}: Starting dp_dedup.service">> /var/opt/omni/log/dp_dedup.log
exit 0


# cat /opt/omni/sbin/dp_dedup_stop.sh
#!/bin/bash
DT=`date "+%d.%m.%Y %T"`
echo "${DT}: Stopping dp_dedup.service">> /var/opt/omni/log/dp_dedup.log
/opt/omni/lbin/DPDUtils.exe -shutdown_all -skipTimeCheck
DPDClientUtilsPath="/opt/omni/lbin/DPDClientUtils"
if [ -e "$DPDClientUtilsPath" ]; then
 echo "${DT}: Stopping client proxies">> /var/opt/omni/log/dp_dedup.log
 /opt/omni/lbin/DPDClientUtils -shutdown /etc/opt/omni/client/SdfsProxyPort.conf
fi
rm -rf /etc/opt/omni/client/SdfsProxyPort*
rm -rf /etc/opt/omni/client/pfconfig.json
exit 0

So the start script actually does not start anything, and the stop script deletes the file used as parameter.

I wonder: How is the deduplication store started, and how is the parameter file created?

Do I have to configure a start/stop mechanism for deduplication store at all?