Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !
WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure. Join the pilot program today!
Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
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.
thanks for posting that script. I'm fairly new to all this so please bear with me.
I have been running your script successfully for over a week without error. It is called via a cron job using:
sh /usr/backupScripts/mybackup.sh
and runs at 4am every day.
Last night, my server went down. When I woke up in the AM I couldn't access it via the http, ftp, ssh or ping. I figured out how to boot into rescue mode and restart the server in normal mode. it was my first time doing that but it went smoothly.
After doign some research i my log files, I realized that the server went down at 4:01am. Its pretty clear that the process running knocked it down.
I'm just trying to figure out how to prevent this from happening again. Any thoughts?
Also, does this script stop any services before backup to prevent failures?
Originally posted by fishnyc22 After doign some research i my log files, I realized that the server went down at 4:01am. Its pretty clear that the process running knocked it down.
Hmm, I haven't run into that so I'm unable to offer a solution.
Perhaps others can help.
As far as I know pleskbackup doesn't stop anything with the current backup command.
Check the knowlegebase for pleskbackup for additional commands to add. Until you resolve the problem perhaps you should run the script manually to see what happens.
Wish I could offer more help. In the interim, I will try to find answers for you as well.
Originally posted by Cranky
In Plesk 8 they changed the backup engine completely by dropping psadump/psarestore and replacing it with Plesk Backup Manager which is based on the much more efficient Plesk Migration Manager engine.
Is that a joke? PMM is the biggest piece of **** I have ever used. 1 domain restoration caused me 1 week (pretty much all day) server repairs. I WILL NEVER USE PMM EVER AGAIN.
The error is sent via email to the server administrator.
You've got to go to the scheduled backup and click the 'OK' button to get it to stop. When the backup runs next time, or a new backup runs, it keeps doing it until you click the 'OK' button. It continues to run the same backup until you click it.