Semi-automated Plesk client backup and restore
Also included in the Plesk interface is the ability to backup and restore an individual client account. Because I was migrating multiple sites, I tried to minimize the downtime to each client site. So this is the method that I ultimately used. I would migrate each client’s domains, essentially creating a copy of the old virtual server, then change the DNS to point to the new server when I was sure the everything worked properly. Though as you’ll see, this method was still not without hazards.
To create a client backup, log into the Plesk control panel as the administrator. Click “Clients”, select the client you want to back up, select “Backup”, then “Backup Now”. Leave the default values, taking note of the file name the backup will be saved as, and click the “Backup Now” button. The file will be saved as something like “ineedattention.com_2007.11.25_22.17”.
Note that I did have trouble at this step when trying to save to the local backup repository. Neither my old server nor my new server wanted to create local backups through the control panel. To get around this, I created a temporary domain name on my new virtual server, and noted the FTP login details. Then I created an FTP backup repository on the new server by selecting “FTP Repository” from the Backup Manager screen in the control panel, using the IP address of the new server, and the FTP login information for the temporary domain. Then, I set the same FTP Repository details on the new server. Thus, when I created the backup on the old server, which stored that backup in the FTP Repository (on the new server), the new server checked the same FTP Repository (also on the new server) and then restored that backup file.
To restore that client backup file, you will have to create a client on the new server first, then create the FTP repository as described above, once for each client.
Now, the domain’s files and settings will all be restored. At first it looked like everything was fine, but everything was far from fine.
This time, one of my SSL certificates transferred properly, but the other didn’t. I logged into the certificate control panel and attempted to re-key my certificate entirely, but even still, had some problems. I was pretty frustrated at this point. I emailed GoDaddy technical support and asked for any documentation, knowing that they usually deny you any actual hands on technical support. To my surprise, the technical support offered to migrate the certificate for me if I provided the key files. I provided the key files and they added the certificates. I was pleased with the experience and timeliness of having my certificate restored.
Continue reading: Previous page Next page
3 responses so far ↓
1 Pete // Mar 4, 2008 at 12:53 pm
I am facing this exact problem right now. Upgrading to Fedora Core 7 on a Virtual Go Daddy Server. I know nothing about this stuff at all and I’m thinking I should just forget it. I cannot have things screwed up for 3 months, or even 3 days. I just became aware of the Fedora change option and I do not want to do it. I will stick with the old Fedora 4 thank you very much. I have spent too much time manually finding and changing the “PHP ON” areas of the server code and that was beyond a nightmare. As for starting over with a new server and migrating…. I can’t remember all the stuff I have to migrate. There must be a better way, and why must we change the operating system in the first place?
Terminal codes, shell codes, FTP codes… what’s a regular person to do? Go Daddy should offer a per incident support fee for BIG trouble items like this, not leave us all hanging like Chads in the wind. I give them a 0/10 for this fiasco!
2 Time to ditch GoDaddy? // Mar 12, 2008 at 10:34 pm
[…] a GoDaddy VPS customer, and amateur tutorial author and reviewer, this upset me, so I wrote a note on GoDaddy’s public relations feedback […]
3 DrewryNewsNetwork // Oct 26, 2010 at 10:55 am
Hopefully, everything you said will help me upgrade my server, in making php & mysql 5 work on the VPS!
Leave a Comment