Add a cronjob "0 23 * * * /usr/local/bin/autoxtrabackup"ĭon't create incremental backups.Create the first backup on Sunday at the desired time, let's take 23h for example.Add a cronjob "0 * * * * /usr/local/bin/autoxtrabackup"Ĭreate a full backup on Sunday, take incremental backups all other days.Check /tmp/backuplog ExamplesĬreate incremental backups each hour, and a full backup each 24 hours. The script does not provide standard output. You can also set the settings in the script directly.Ĭopy autoxtrabackup.sh to /usr/local/bin/autoxtrabackup InstallationĬopy nfig to /etc/default/autoxtrabackup and edit the settings This script has been tested on CentOS 6.4 with MariaDB-server-10. This script has been tested on Debian 7 (Wheezy) with Percona-server 5.6. Supported Linux distributions: Debian, Ubuntu, CentOS, RedHatĭependencies: percona-xtrabackup, download from Supported MySQL distributions: MySQL, Percona Server, MariaDB This script uses the innobackupex wrapper for xtrabackup from Percona, included in percona-xtrabackup.Ĭreate full & incremental backups automatically, with configurable retention and compression, and optional e-mail output. Vinchin Backup & Recovery will safely protect the target MySQL database.Automatic MySQL scheduled backups using Percona innobackupex (xtrabackup). Now, you can review all configurations, and submit the backup job. This feature encrypts the data transmission path to prevent your backups from unauthorized access. Database backups can now only be transferred through LAN, and you can choose to enable Encrypted Transmission to improve the security level during that process. Once the retention policy is triggered, data that exceeds the restore point or day limit will automatically be purged for policy compliance.Ĭlick on the Transmission Strategy, you can configure the transport mode of the backup data. If you choose Number of Days as the retention mode, then the backup server will save restore points within a specific number of days. If you choose Number of Restore Points as the retention mode, the backup server will only keep a certain number of full restore points. You can also set up a Retention Policy for the job. There’re 2 data reduction features that you can see in the Data Storage Policy field, which are Data Deduplication and Data Compression.ĭata Deduplication works to exclude duplicated data blocks, and Data Compression will compress the backup data and then save it into backup storage. If you want to set restrictions on the transfer speed of backup, especially when you want to do backups during business hours without affecting the production network too much, you can expand the Speed Controller field, and click on Add Policy to set a max speed for data transport.įor an As Scheduled policy, you can define a start time and end time of the policy within a day, week, or month.įor a Permanent policy, you can simply define a max speed, and once enable it, the transfer speed will always be subject to the policy, no matter when the backup job runs. It’s recommended to combine weekly full backup with daily log backup and incremental backup for high data availability. You can schedule each type of backup to run on a daily, weekly, or monthly basis. If binary logging is not enabled, it needs the database administrator to enable it. If you want to run MySQL log backup, MySQL database needs binary logging enabled. If you choose Backup as Scheduled, Incremental Backup and Log Backup will be the other 2 available options besides regular full backup. In the Schedule field, you can choose to configure the job to Backup as Scheduled or to be a Once-off Backup.įor a Once-off Backup, you can define a start time for a once-off full backup. The Backup Strategies section is where you can flexibly schedule the MySQL backup job with a bunch of features. In the Backup Destination section, select backup storage to save all the backup files, and click on Next. Step 1: Choose a backup source.Īll licensed databases will be shown in the list here, you can select the MySQL database you want to protect, and click on Next. To create a backup job for MySQL, please go to Database Backup > Backup page, here’s an intuitive wizard to guide you through the job creation process. Let’s open and log in the Vinchin Backup Server web console. You can use the software to protect MySQL 5.5~8.0.26 in both physical servers and virtual machines. In this blog, you’ll learn how to schedule an automated MySQL backup job using Vinchin Backup & Recovery in 3 steps. Step 3: Setup the backup plan in detail.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |