• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Don't use pleskbackup ... Use PleskX.pl

M

madcat

Guest
Hello. I recently went through a nightmare trying to migrate some of the domains of a particular client from a Plesk 8.2 machine to a Plesk 8.1 machine, because the 8.2 machine was running very low on disk space. The Plesk 8.2 machine is running CentOS 5, the Plesk 8.1 machine is running CentOS 4.6.

I initially tried to use /usr/local/psa/bin/pleskbackup to create backups. It told me one of the domains I was trying to backup didn't exist, even though it did and was up and working just fine. (I cut-and-pasted, so it wasn't a typo). So I skipped that one, and copied the rest of the backup files to the 8.1 machine.

Once I tried to restore the backups on the 8.1 machine, I ended up with a whole bunch of Python spew error messages. *Very* long story short, I ended up finding this little carefully hidden gem: http://download1.parallels.com/Plesk/Plesk8.1/Extensions/backup-agent-8.1.0.tar

This utility creates plesk backups that are compatible with the /usr/local/psa/bin/pleskrestore tool ... and it has one added advantage over the regular backup / restore tools ... IT DOESN'T ****!

My $0.02

PS: When using /usr/local/psa/bin/pleskbackup, I recomend that you always create your own map files (since --create-map is broken) and always use "-level domains" if you're trying to add domains into an existing client, and do the domains one by one. If you try to create a large backup file with all the domains, and/or use "-level clients" the restore utility will WIPE OUT the entire client, including all their domains, and replace them with the ones in the backup file.
 
Hey ... they stared out the work S-U-C-K ... WTF? It's not like it's a swear word.
 
Back
Top