• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Plesk Restore

lainard, please install all available updates. It looks like pleskbackup stored your web files incorrectly (this bug was fixed in update to Plesk 8.0.1), but I may be wrong for sure.
 
i did backup when it was 8.0.1 version

now i want to restore in the same box with update all installed 8.0.1

and i get the error

dns restored
email account restored
account client restored

webfile gone

mysql restored without any table and data all lost

i request plesk support but they give me what a crazy anwser without any solution
 
I have just taken over as Systems Administrator at a hosting company.

They are using plesk Version 8 on Linux.

I have been given the task of restoring the backups that have been previously created.
I have had no experience with Plesk and therefore not having much luck so far.

We do have support with them, however i'm still waiting to hear back from them
So i wanted to see if you guys would help me out in the meantime.

The Backup procedure that is being used is:

Run this command to create backup.

/usr/local/psa/bin/pleskbackup --all /backup/backup_host04-8.0

This creates a file about 6gig.

Then to restore i am trying this:

/usr/local/psa/bin/pleskrestore --create-map /backup/backup_host04-8.0 -map map.txt

creates the map file.. it seems all good... IPs are Correct...

Then i Run:

/usr/local/psa/bin/pleskrestore --restore /backup/backup_host04-8.0 -level all -map map.txt

The error comes back and says
'backup file un-readable'

I changed permissions to 777 to test, made no difference

Can anyone offer another method... or something i'm doing wrong? (Apart from the OS that is currently being used)
The Server is currently on Fedora Core 2...
i want to upgrade to CentOS...
this is the reason for the testing of backups :)

I am rsyncing the backups from the Live server to a Test Server, will this cause any problems to the file?
 
Split backup into 2Gb - 1M parts, named file, file.001, file.00...

It seems like they hit a PHP bug, when file greater then 2Gb is shown as unreadable.

Use multivolume backups.
 
Back
Top