Error: invalid backup format Topic is solved

[retronoodle]

I figured it out. For some reason the actual username "dailycha" was different than the backup name. It must have been changed at some point on the old server. I'm on my way!

[richardbenjamin]

* Solution found! I hope this works for someone else.

I was migrating my vesta control panel to a new server so I decided to create a fresh install of VestaCP and migrate the users via the backup system.

After following the migration instructions here: http://vestacp.com/docs/#how-to-migrate ... her-server, the CLI user restore command kept giving me the "invalid backup format".

As a work around, I made a user backup on the "new" VestaCP I created via the gui, then from the command line I swapped out the back up from my old vesta server with the new backup. After that I went to the gui and restored the backup from there. IT WORKED, so far anyway.

[RichBos]

Hi, rather than start a new thread I thought I would post/add here as my issue matches. I hope someone is able to help and advise.

I too am getting the 'invalid backup format' error when trying to restore a .tar file. It was created on an Ubuntu 12.04 ec2 instance and I am trying to restore to an Ubuntu 16.04 ec2 instance. We are migrating as Ubuntu 12.04 is now end of life. Both instances are running VestaCP 0.9.8.

I have tried all the methods advised here but to no avail. I even expanded the .tar archive and recreated it on the Ubuntu 16.04 instance, but no joy :-(

I am using stated location commands for the restore. For example, from within the backup dir (where the archive is located) I am running :

Code: Select all

sudo /usr/local/vesta/bin/v-restore-user admin ./admin.2017-12-18.tar

Running the command gives the error:

Code: Select all

Error: invalid backup format :: ./admin.2017-12-18.tar

Any help or advice from someone who has found a resolution to this (other than those already mentioned) would be most appreciated.

Many thanks.

[RichBos]

Hi, I have managed to resolve this so here is what I discovered if it helps anyone else.

I was specifying the location relative to the dir I was in (i.e ./admin.xxxx.tar). I didn't understand that there needs to be no location specified, it's literally all down to having the .tar file in the correct place (i.e /home/backup).

The revised command that worked (with the .tar in /home/backup) was:

Code: Select all

sudo /usr/local/vesta/bin/v-restore-user admin admin.2017-12-18.tar

Our sites are back up and running happily on Ubuntu 12.04. I needed to make no config changes other than suspending the default domain under the admin account.

[upxbotx]

Hello everyone,

We recently set up a vm web hosting server in order to prepare ourselves for taking down a physical server we have that has been having what seems like hardware issues.

The virtual server is set up with ubuntu, with vesta 0.9.8-17 installed. I copied over the backup tar files over from the old server to the new one, and placed them in the home/backup directory. When I try to use v-restore-user, I get an error saying "Error: invalid backup format ::" followed by the directory path describing the tar file I just tried to use.

I scoured the interwebs and these forums trying to find someone with a similar issue, but I have yet to find a similar situation. I tried:

• - Changing the permissions attributes of the backup folder, the individual tar files, as well as v-restore-user script
  - Using a different tar file
  - Restoring a different user
  - Switching Active User
  - Copying the permission layout of the old server's backup files to the new server
  - Checking spelling on my commands
  - Using grep to find the error message (we found a similar error message within other code, but could not identify the source of our error)

If anyone could help or offer any tips toward getting our users restored it would be greatly appreciated :)

answer for you and all other.
Problem with time on first and second server, if backup was made in future time it makes error.
so you need just change name of file
for example you have admin.2018-01-05_02-20-21.tar
change it to admin.2018-01-05.tar and try again

[imperio]

upxbotx,
Your message is not related to this issue.
And you break the forum rules

Forum rules
Before creating a new topic or reply on the forum you should fill out additional fields "Os" and "Web" in your profile section.
In case of violation, the topic can be closed or response from the support will not be received.

[vesta_mtl]

I had the same issue today, and it was because my backups have started being named with the time as well:

Code: Select all

user.2018-01-10_10-47-52.tar

I therefore renamed it to remove the time:

Code: Select all

mv user.2018-01-10_10-47-52.tar user.2018-01-10.tar

Now, the backup works because the backup filename has the expected suffix (yyyy-mm-dd) and nothing more.

[imperio]

Try to use this
https://github.com/serghey-rodin/vesta/ ... 9d72441fd1
Let me know if this helped

[SampleTacoInundation]

Hi, I have managed to resolve this so here is what I discovered if it helps anyone else.

I was specifying the location relative to the dir I was in (i.e ./admin.xxxx.tar). I didn't understand that there needs to be no location specified, it's literally all down to having the .tar file in the correct place (i.e /home/backup).

The revised command that worked (with the .tar in /home/backup) was:

Code: Select all

sudo /usr/local/vesta/bin/v-restore-user admin admin.2017-12-18.tar

Our sites are back up and running happily on Ubuntu 12.04. I needed to make no config changes other than suspending the default domain under the admin account.

That worked for me!