Support

Panopticon only tells Akeeba Backup to execute a backup. It is Akeeba Backup controlling everything surrounding the backup, including what happens in case of FTP upload failure.

In the Configuration page of the profile you can set “Fail backup on upload failure” to Yes. This will cause the backup to change its status to Failed if the upload does not run to completion. This means that you have the following cases:

• The upload completes: the backup is set to Complete, everything is fine.
• The upload cannot start at all: the backup is set to Failed, the local files are deleted, there are no remote files.
• The upload fails partway: the backup is set to Failed, the local files are deleted, there might be partially uploaded remote files.

I recommend using SFTP instead of plain FTP and a smaller part size when using a Synology device as the upload target. The part size depends on your downlink speed on the Internet connection hosting Synology. My rule of thumb is 8 MiB for every 10 full Mbps of stable downlink speed. If you have a 28 Mbps downlink, use a part size of 16 MiB. If you have a stable 100 Mbps downlink (e.g. via fiber) use a part size of 80 MiB.

The most critical part, though, is making sure your Synology NAS is on-line at the time of the backup. Some ISPs do maintenance in the early hours, usually between 2am and 4am, when the network traffic is low. I've found out the hard way it's best to avoid uploading to a self-hosted NAS during those hours :)