• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Plesk installation backup

Franco

Regular Pleskian
Hello,
in view of upgrading to Plesk to 17.8 I would like to backup the Plesk installation (but not the entire server) for a potential rollback. What's the way to proceed? I have seen a lot of information on how to backup subscriptions and the entire server, but could not find any mention about Plesk itself. Can someone give me some indications, please?

Regards
Franco
 
I don't think this is feasible.
On Digital Ocean I would take a server snapshot beforehand, but you don't provide information on where your server is hosted so... no idea!
 
Thank you all for the hint and that's what I did.

However, I find it weird that one has to and restore and entire server in case a Plesk update goes bad. Why not a dedicated backup procedure like one does for subscriptions? Is there something I don't understand?
 
I don't see the point personally. I've yet to see an upgrade get botched so bad that it wasn't recoverable. Even if you do roll back - you're likely to just hit the same issue again, and staying on outdated software isn't really an option either.
 
Hi Mark,
it's not because it's called Plesk that it won't ever fail. I am old enough to have watched and lived several disasters in IT, and coming from unexpected angles (otherwise they could be prevented). If it happens and there seem to be no way around it the thing to do is a restore. Afterwards you have the time to analyse what happened without letting your users down too long and hopefuly find a solution before attempting it again.
But the point is that all these upgrade procedures offered by Plesk and other experts all start with a backup (as it should be). They say snapshot or full server backup; to me a full server backup does not sound right for a Plesk upgrade, but that's what they say, don't they?

A rollback for Plesk? Forgive my ignorance, but what is it and how does it work?

Cheers
Franco
 
Don't you think you'd waste more time doing a restore versus just spending the time to resolve the issue? I like to time my updates on any production system to be right after a scheduled full backup is done. Never needed it. May just be luck - If there was a way to backup panel only, I don't think I'd waste the additional storage space personally.
 
Back
Top