Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

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

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

Error: “backup doesn’t exist” in VestaCP – Resolve it quickly

by | May 31, 2021

While migrating a user to a new server in VestaCP, we may come across the message, “Error: backup admin.2017-02-13.tar doesn’t exist”

As part of our Server Management Services, we assist our customers with several VestaCP queries.

Today, let us discuss the causes and fixes of this error.


How to migrate user to the new server in VestaCP

  1. Initially, we make user backup on the old server. For example, here we use admin as the reference.
    v-backup-user admin
  2. Then we copy the tarball to the new server and place it in the /home/backup directory
    scp /home/backup/admin.2014-01-14.tar new-server:/home/backup/
  3. Finally, we restore backup on the new server
    v-restore-user admin admin.2014-01-14.tar

In case we wish to restore data under another username, we simply rename the archive. If the username doesn’t exist on the server, the account will create automatically.

mv /home/backup/admin.2014-01-14.tar /home/backup/newuser.2014-01-14.tar
v-restore-user newuser newuser.2014-01-14.tar


Fix “Error: backup admin.2017-02-13.tar doesn’t exist

Moving ahead, let us discuss how our Support Techs fix this error for our customers.

When we come across the error, first and foremost, we need to cross-check the permission of the “/home/backup” is under the ownership of the admin user.

We use the ls -al command to list the directory. Then we use the chown command to change the ownership.

ls -al /home/backup
chown admin:admin /home/backup

If the permission is intact, we need to verify if there is a symlink from /home/backup and /backup.

In case it is not, we run the command below:

ln -s /home/backup /backup

Once done, we need to ensure that the backup file exists in the /home/backup directory.

Suppose it is not, then we need to move the backup inside the /home/backup directory.

For instance, suppose the file is in the user home directory, then we use the command below to move the file:

mv /home/USERNAME/backup_file.tar /home/backup/

[Failed to solve the error? We are available 24*7]



To conclude, the Error: “backup doesn’t exist” in VestaCP occurs while migrating a user to a new server. Today, we saw how our Support Techs resolve it.


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.