Trouble Migrating

[mike08]

Actually /backup should be a symlink for /home/backup as a default vesta installation

[skurudo]

Actually /backup should be a symlink for /home/backup as a default vesta installation

In newer version from 14 afaik you can choose, where your back will be.
Symlink to /home/backup optional

[jonkratz]

Looking at the Vesta code, I found:

/usr/local/vesta/func/main.sh line 6:

Code: Select all

BACKUP='/backup'

Thanks so much, Russell!

As of version 0.9.8-15 this was still required to fix the issue for me.

[skurudo]

As of version 0.9.8-15 this was still required to fix the issue for me.

All will be fixed and warm, and soft ;-)
What do you mean exactly, symlink?

[mehargags]

I'm again for the second time having the same problem of Backup set not being valid .
Moving out from an old to new server, both servers run the same version of Latest Vesta, only that new one runs Debian 8 and old one runs debian 7

I copied backup to /root/ -> fail
then copied it to /backup -> fail
then copied it to /home/backup -> failed again

Can't make out whats the problem.

is there a way I can check what "format of the $backup parameter" is being used on old server so I can match them both and restore my set from old server to new one?

[skurudo]

I'Can't make out whats the problem.
is there a way I can check what "format of the $backup parameter" is being used on old server so I can match them both and restore my set from old server to new one?

SERVER -> CONFIGURING SERVER -> BACKUP -> Directory
in newer version -- /backup

And something like this:

Code: Select all

cd /backup
v-restore-user admin your-arc

[mehargags]

cd /backup
v-restore-user admin your-arc

As I said Skurudo, I did try with the archive in /bakcup, it still throws me error :

Code: Select all

Error: backup /backup/admin.2016-01017.tar is not valid

I think the problem is somewhere in the TAR compression module. The compression is not recognized by the new server.

[skurudo]

I think the problem is somewhere in the TAR compression module. The compression is not recognized by the new server.

The problem is, then you need to think. I was not able to repeat from Debain 7 -> Debian 8.

[mehargags]

I was not able to repeat from Debain 7 -> Debian 8.

Means ? you were not able to Restore from a Debian 7 system to a Debian 8 ? is that what you mean?
please clear!

[skurudo]

I was not able to repeat from Debain 7 -> Debian 8.

Means ? you were not able to Restore from a Debian 7 system to a Debian 8 ? is that what you mean?
please clear!

Restored nice,
backup from Debain 7 and restore on Debian 8.