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

Backup Solution: rsnapshot or pleskbackup?

I've got rsnapshot all set up and it's creating the backups like a charm. I'm going to agree with MikePaul99 here that this is probably a better solution than pleskbackup. It's extremely easy to set up and once you have it configured it's totally hands off. Here's a quick how-to to get you up and running.

1. First download the rsnapshot program to your server and install: http://www.rsnapshot.org/downloads.html
I used the RPM version.

2. Once you have rsnapshot installed edit the config file: /etc/rsnapshot.conf
I only had to edit two sections of the conf file.
The first part tells rsnapshot where to store the backups. In my case /backups/ is the path to a second harddrive.
PHP:
###########################
# SNAPSHOT ROOT DIRECTORY #
###########################

# All snapshots will be stored under this root directory.
#
snapshot_root   /backup/.snapshots/
Then further down towards the end of the file we add the directories we want backed up. I'm backing up the following directories: home, etc, usr, var, root, boot
PHP:
# LOCALHOST
backup  /home/	localhost/
backup  /etc/	localhost/
backup  /usr/   localhost/
backup  /var/   localhost/
backup  /root/  localhost/
backup  /boot/  localhost/
That's it for configuration! Just make sure the syntax is right with this command:

rsnapshot configtest


3. Now to automate everything add the following two cron jobs to the root crontab:

0 */4 * * * /usr/bin/rsnapshot hourly

30 23 * * * /usr/bin/rsnapshot daily

This runs the hourly backup every 4 hours and runs the daily backup each day at 11:30PM.

*note: the path to rsnapshot on my system is /usr/bin/rsnapshot, this may differ depending on how you installed it. Make sure your cron job has the correct path to rsnapshot.

All done. Now your system is being backed up every 4 hours. This is a very basic usage of rsnapshot, but there are many more options in the config file. You can read the complete how-to here: http://rsnapshot.org/howto/1.2/rsnapshot-HOWTO.en.html

Brian

Your guide was good one. You might be interested to check http://www.technetra.com/writings/archive/2005/08/20/backups-are-a-snap-with-rsnapshot

Here is my list of folders to backup. What do u think?

# Apache and Plesk services
/etc/

# Users home directories
/home/

# Plesk tree, RoundCube and other custom installations
/usr/local/

# Trac, Rails and other custom installations
/usr/share/

# FTP uploads
/var/ftp/

# Mailman arhives and lists
/var/lib/mailman/

# MySQL dumps taken by Plesk
/var/lib/psa/dumps/

# Emails
/var/qmail/

# Web sites
/var/www/vhosts/
 
Just one quick note. Whatever you backup, I did not saw anyone to restore 100% if an OS fail. Usually when an OS fail, for whatever reason (hacked, libraries, etc) datacenter restore new OS (latest usually) and new PLESK. So the only way to restore in many cases, is to redo all by hand, 1 by 1.
We are in work to finish a PLESK Crash Recovery tool, we hope will be done in 1-2 weeks (all tests was positive) and then to offer this as a service to anyone who get a crash.
So backup in ANY case, what we recommend:
/var/lib/mysql
/var/qmail/
/etc/
/var/ww/vhosts/ (or where it is)
also we use automysqlbackup.sh http://sourceforge.net/projects/automysqlbackup/ to create daily backup of database and also we have our own backup script (http://forum.swsoft.com/showthread.php?p=195911) and seems work ok.

Hope this help.
 
Back
Top