Facebook
Twittermad_inventor
New Pleskian
- Server operating system version
- Microsoft Windows Server 2022
- Plesk version and microupdate number
- Plesk Obsidian Version 18.0.68
Hi, I hope this helps fellow Plesk users on a Windows web server.
After my 7-year-old server died, I realized too late that its HDD wasn’t defragging properly—clear signs it was about to fail. Thankfully, I back up my Plesk settings and websites daily using the Backup Manager and download the ZIP file to my local PC.
When setting up my new IONOS server, I encountered the 2GB restore limit issue, as well as the upload restriction—my backup ZIP was 2.8GB due to hosting 30 sites.
Plesk wouldn’t let me use the file transfer option in the control panel either, as the ZIP was too large.
Everything—sites, settings, and configurations—was restored perfectly. Without this workaround, you’d think the ZIP was corrupt (as WinZip and Windows ZIP often report), which can be a heart-stopping moment.
I hope this helps someone! The IONOS engineers found it useful, and now I’m back up and running with a happy client base.
I keep client emails hosted separately with IONOS and use their MX setup. This way, if the web server ever fails, emails remain unaffected, reducing stress. I learned this the hard way after previously running Exchange on the same web server—when it went down, everything went down!
Best regards,
Anthony (APBTECHNOLOGY)
After my 7-year-old server died, I realized too late that its HDD wasn’t defragging properly—clear signs it was about to fail. Thankfully, I back up my Plesk settings and websites daily using the Backup Manager and download the ZIP file to my local PC.
When setting up my new IONOS server, I encountered the 2GB restore limit issue, as well as the upload restriction—my backup ZIP was 2.8GB due to hosting 30 sites.
Plesk wouldn’t let me use the file transfer option in the control panel either, as the ZIP was too large.
Here’s how I worked around it:
- My new IONOS server was set up, and I had my backup ZIP stored locally.
- I used ZIPWARE (this was key!) to extract the contents into a folder on my PC. Other tools, including Windows ZIP and WinZip, kept saying the file was corrupt.
- I then created a new ZIP archive using Windows’ built-in ZIP utility.
- Uploaded this new ZIP via FTP to my server.
- On the server (via Remote Desktop), I extracted the contents using Windows ZIP.
- Moved all extracted data into the Vhost/Plesk/Backup folder.
- Logged into Plesk, and there it was—the backup from two days ago!
- Hit Restore and let it do its thing while grabbing a brew. ☕
Success!
Everything—sites, settings, and configurations—was restored perfectly. Without this workaround, you’d think the ZIP was corrupt (as WinZip and Windows ZIP often report), which can be a heart-stopping moment.
I hope this helps someone! The IONOS engineers found it useful, and now I’m back up and running with a happy client base.
Extra tip:
I keep client emails hosted separately with IONOS and use their MX setup. This way, if the web server ever fails, emails remain unaffected, reducing stress. I learned this the hard way after previously running Exchange on the same web server—when it went down, everything went down!
Best regards,
Anthony (APBTECHNOLOGY)
