Restart FTP backups On SolusVM Slaves

Sometimes if an error happens when FTP Backups are running on a SolusVM slave your FTP Backups will get stuck until you restart the FTP backup service. When SolusVM backups run, SolusVM creates an image of the server whilst it’s still running. Then it places that image into a dump file where it stays whilst it is uploaded to your backup server.

If the upload is interrupted then the image will stay in the dump file and take up space. You should remove this file and follow the below to restart the SolusVM backups.

Stop FTP Backups

First, let’s remove the PID file that the server uses to run backups. Once you remove this file backups will stop.

rm -rf /usr/local/solusvm/tmp/ftpbackup.pid

Restart Backups

Then you need to restart the FTP backup program again by issuing the below command;

php /usr/local/solusvm/includes/autoftpbackup.php

If you see errors you can run this command with debugging to find out what is causing them;

php /usr/local/solusvm/includes/autoftpbackup.php --mode=all --debug=1

You can restore SolusVM Backups by using the dedicated restore script that is shipped with SoluVM. Depending on the type of backup it might be faster to restore the server manually rather than using the restore script. See how to Restore SolusVM Backups from the command line for further information.

How was this article? – Forcing SolusVM backups to run on a SolusVM slave

Click to rate this post!

[Total: 34 Average: 5]

Spread the love