Nick Howitt wrote:

Do you need to do a "modprobe synosnap"? If you do, you'll need to do it permanently. To do that add a file to /etc/sysconfig/modules with its name ending in ".modules" and put the one line command in it.

Made the file as suggested above and then I read that you need to do chmod 755 on it to make it executable

Thanks again you are awesome

Von Royce Wallace wrote:
Not sure after I reboot

Probably not unless you make file I suggested.

Well it works now

after doing a sudo modprobe synosnap

Not sure after I reboot

Do you need to do a "modprobe synosnap"? If you do, you'll need to do it permanently. To do that add a file to /etc/sysconfig/modules with its name ending in ".modules" and put the one line command in it.

Per messages log

Dec 13 10:58:23 vonwallace synology-backupd: ABB backup service starts
Dec 13 11:04:22 vonwallace systemd-modules-load: Failed to find module 'synosnap'
Dec 13 11:04:23 vonwallace synology-backupd: ABB backup service starts

Systemd unit files seem to normally go into /usr/lib/systemd/system but systemd has a hierarchy or overrides so what you have may be OK. To start it and have it starting on boot, either longhand:

systemctl enable synology-active-backup-business-linux-service

systemctl start synology-active-backup-business-linux-service

or shorthand:

systemctl enable synology-active-backup-business-linux-service --now

I am thinking clearos has a different service method

[root@vonwallace system]# pwd
/etc/systemd/system

ls

synology-active-backup-business-linux-service.service



this is the above service file

[Unit]
Description=ActiveBackup Daemon

[Service]
Type=forking
PIDFile=/var/run/synology-backupd.pid
WorkingDirectory=/opt/Synology/ActiveBackupforBusiness/bin/
ExecStart=/opt/Synology/ActiveBackupforBusiness/bin/synology-backupd
ExecReload=/bin/kill -HUP $MAINPID
ExecStop=/bin/kill -QUIT $MAINPID
KillMode=process
Restart=on-failure

[Install]
WantedBy=multi-user.target

How do I get this to run on clearos