• 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.

Issue Backup Restore Job takes Sites offline

dannray

New Pleskian
Hi,

Is it normal when you do a large backup restore job for it to restart PHP or take all other sites offline temporarily?

Thanks
 
It does this on one of these two events:
- You have clicked the checkbox that during the restore the site shall be offline.
- The load is so high compared to the capabilities of the server that the site takes so long to respond that it reaches a timeout and appears to be offline.
 
Hi Peter,

Thanks for the reply, is there any way to avoid this?

When the restore was taking place it seemed like all the sites on the server were pointing to the login or default index.html screen like the apache config or Nginx config were broken.

I had to rebuild the web using Plesk repair web -y to fix this.

Thanks
 
A restore also reconfigures all webserver configuration files. This process can take several minutes, depending on the number of configuration files that need to be created. The process first deletes all such files and then restores the files for each subscription separately. It is correct that during this phase the web server points all traffic to the default page, because the web server does not know the virtual hosts yet. This is an unavoidable behavior. I can think of ways how this could be done better, e.g. create all new config files in a shadow directory and then move them into their destination all at once, but currently it's a one by one algorithm.

It is normally not necessary to run a "plesk repair web" on it. This will only reconfigure the server again. Instead, when the issue occurs, look into the system with
# ps aux | grep mng
or
# ps aux | config
which will reveal the ongoing reconfiguration processes.
 
Back
Top