It means they can restore a file from last week without bothering a support team or sysadmins. Plesk backups are useful for end users and site owners who want to manage their own backups. A dump of the psa database is not safe, you need a config only backup. If you need to rebuild a server but dont have the plesk config you might be screwed even if you have the files and databases. Plesk config only backups are super important. you will see the success or failure message in the right side of the message box. To choose a dump from your local computer in select Upload and click Browse. I prefer to keep it simple just to have a cron thats rsyncs account by account to a remote server, make sure you have a decent set of exclusions to skip session files, logs and file cache directories you know are safe to skip. Locate the name of the database you wish to upload or restore the backup from your local machine. If you do snapshot with ZFS make sure you are using zfs send to get a copy to a remote server in case of real disaster. It took me a few minutes to realise it, but Plesk’s backups are essentially MIMEd and gzipped.
I know that Plesk 8.6 have a backup utility (Parallels Plesk Control Panel 8.6 for Linux/Unix Backup and Restore Utilities Administrators Guide) But I have some unclear doubts: 1.
You can only restore backups made in Plesk Onyx 17.0 and later. When restoring from a backup file, you can restore all data contained in the backup, or select individual objects to be restored (for example, a particular site, all databases, and so on).
Plesk backups how to#
After many tries and support tickets, I am configuring a new server, with Suse 11 and Plesk 9.2. This topic explains how to restore data from a backup in Plesk. For some reason, we wanted one file back out of a backup. I have a CentOS 64bit server with Plesk Panel 8.6. I dont use any file system snapshot features, as it limits the pool of people with the skills to recover, in my use case that can be the limiting factor. I won’t repeat my frequent anti-Plesk rant, but suffice to say: it’s a pain. Wanted to get some advice on files to exclude for plesk backups, we dont want our backups growing exponetially with unwanted files. That you can also keep point in time dumps ( I do last 3 hourly, last 3 daily and last 3 weekly) in case you need an older copy the databases. As an added bonus you can dump the databases from the replica server with no performance impact on the primary server or sites. For the databases setup MySQL (Mariadb) replication, I put this first as most important! Then you can have a live copy on a different server, so if the primary goes bang there is close to zero data loss from the databases.
0 kommentar(er)
