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

General server backup before Plesk updates and component updates

Giorgio1

New Pleskian
Hi, I'm using Plesk 12.0.18 Update #32 on CentOS 6.5. I would like to know which is the right way to backup all the server content and configuration before applying an update of Plesk or a component update.

Of course, this backup should be usable if something goes wrong after an update.

Untill now I had not problem using Plesk and maintaining it updated but... you never know..!

Thanks for any suggestion.
 
Thank you for your answer. So, if I understood correctly, in case of a server backup created by using the feature in the Plesk panel, I can't for example "downgrade" to the 12.0.18 Update #32 if I updated the system to Plesk 12.0.8 Update #33 and something gone in the wrong way. In that case I lose, for example, the previous version of MySQL. Is that correct?
 
Thank you for your answer. So, if I understood correctly, in case of a server backup created by using the feature in the Plesk panel, I can't for example "downgrade" to the 12.0.18 Update #32 if I updated the system to Plesk 12.0.8 Update #33 and something gone in the wrong way. In that case I lose, for example, the previous version of MySQL. Is that correct?
No. Ples backup does not contain system of Plesk system files and packages.
 
Hi Giorgio!

This is my solution for my VPS Ubuntu 14.04.1 LTS + Plesk 12
- Idera ServerBackup Free for incremental backup;
- Idera HotCopy + dd command (disk duplicator) for weekly snapshot without reboot (live system).

You'll need a FTP account to storage the backups.

- http://wiki.r1soft.com/display/ServerBackup/Server Backup Free
(instruction and download http://www.howdididothat.info/2013/...e-to-backup-a-ubuntu-system-to-a-nfs-storage/ (With this you will have ServerBackup Free and HotCopy too)

How to use Idera HotCopy?
It's very very simple. From bash:
- cd /tmp
- dd if=/dev/zero of=zerofillfile bs=1M
- rm zerofillfile

Now lunch Idera HotCopy. From bash:
- mkdir /mnt/snapshot
- cd /mnt/snapshot
- hcp -m /mnt/snapshot /dev/sda1 (partition to snapshot)
- umount /dev/hcp1

Now you can lunch DD command (this is valid to storage in FTP remote space)
- dd if=/dev/hcp1 | gzip -c | ssh account_ftp@ftp_address "cat > /path_to_ftp_storage/Current_Date_Snapshot.img.gz"

At the end, you'll be able to remove the /dev/hcp1. From bash:
- hcp -r /dev/hcp1

*** IMPORTANT ***
For the first time (and every time you'll upgrade the kernel on the server), you'll need to DD the MBR of the disk. Reboot your server from a live CD or Rescue Mode (I'm VPS OVH Customer). From the bash:
- dd if=/dev/sda of=/home/mbr.img bs=512 count=1 (Remember to copy mbr.img to FTP backup storage)

How to restore?
It's very very simple too. From live CD (or Rescue Mode).
- umount /dev/sda1 (IMPORTANT: the partition to restore must be unmounted)
- ssh account_ftp@ftp_address "cat /path_to_ftp_storage/Current_Date_Snapshot.img.gz" | gunzip -c | dd of=/dev/sda1

Now you'll need to restore Boot loader:
- dd if=/path_on_ftp_storage/mbr.img of=/dev/sda bs=446 count=1 (the boot loader is only the first 446 byte of MBR)

Reboot and enjoy!

That's all! Totally free!
 
Back
Top