Need help?

Our experts have had an average response time of 12.14 minutes in September 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

How to start the System and Autoftp backup manually in SolusVM?

by | Jul 28, 2021

Wondering ‘how to start Backup manually in SolusVM?’ We can help you with this!

Here at Bobcares, we handle similar requests from our customers as a part of our Server Management Services.

Today let’s see how our Support Engineers help to start backup manually for our SolusVM customers.


Start Backup manually in SolusVM

SolusVM provides two backup methods. They are,

  • System Backup
  • Auto FTP Backup

Today, let’s discuss these two backups and how to start them manually in SolusVM.


System Backup

In SolusVM, System backup is a feature focused on backup the database and database configuration of the Master server.

The system backup contains:

  • Database backup
  • /usr/local/solusvm/includes/solusvm.conf : The configuration file

Here the SolusVM create the backup and transfer it to the FTP storage.


Start the System Backup manually in SolusVM

Let’s see how to initiate system backup manually in SolusVM.

  1. Firstly, access the Master server via SSH.
  2. Then to start the system backup manually, run the following command:
php /usr/local/solusvm/system/systembackup.php


After that, we need to check the status of the backup by checking the System logs of the backup if the system backup is configured using the FTP method.

If you notice the following error in the log, it means that the process is already running.

/usr/local/solusvm/tmp/ already exists

So we need to wait till the backup process completes. Else, we have to remove all auto FTP backup processes, file, and then restart the backup process again.


Auto FTP Backup

In SolusVM, the Auto FTP Backup is a solution for automated VPS backups. It is configured per node.


How to configure Auto FTP backup?

  1. Firstly, login to SolusVM.

SolusVM admin panel >> Nodes >> List >> (Select the node that wish to backup)>> Auto FTP Backup

2. Then, Under the FTP Server Settings :

Select the FTP server from the Profile option. Also specify the details like IP or Hostname, Username, Password, Port, and Directory.

3. Tick the checkbox Passive in the FTP Server Settings page.

4. Then under Backup Settings, tick the checkbox Enabled to allow backup.

5. Also, we can change the other backup settings according to our requirements.

6. Finally, click Update


Start the Autoftp backup manually in SolusVM

Now, let’s see how to initiate Autoftp backup manually in SolusVM.

  1. Firstly, access the Slave server via SSH.
  2. Then to start the Autoftp backup manually, run the following command:
php /usr/local/solusvm/includes/autoftpbackup.php

For verbose output, run the below command:

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

[Need any assistance with SolusVM queries? We can help you]


In short, today we saw the steps followed by our Support Techs to start Backup manually in SolusVM.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.