MariaDB Database Backup
Before taking database backup for your MariaDB database server, a lightweight agent needs to be installed on the database server, please refer to Agents for how to install agents on your database servers.
After the agents had been installed and licensed for database backup, please follow the below steps to create database backup job.
Configure Application
After the installation of Vinchin physical backup agent on the MariaDB database server, please open Vinchin Backup Server web console and go to Resources > Infrastructure > Agents & Client page, find the target agent, click on Options, and then select Application to configure application settings for database backup.
Click on the Configure Application button to configure the application settings.
In the Application Type dropdown list, please select MariaDB and then click on Next.
In the Applications Settings screen, please configure the following settings.
In the CNF File Location field, please type in the file path of the MariaDB cnf file. Providing database administrator username and password.
Vinchin provides two authentication modes: tcp/ip authentication and sock file authentication. If connecting to MySQL via tcp/ip authentication, the default IP address is 127.0.0.1, default port is 3306 (please fill in the IP address and port based on the actual situation). If connecting to MariaDB via sock file authentication, the default hostname is localhost, and the sock file path is filled in according to the actual situation. Leave the IP Address and Port number with the default value and click on OK to complete the application configuration.
When the MariaDB application is successfully configured, you should be able to create backup jobs for the MariaDB database server.
Before Backing up MariaDB Database
If you want to run MariaDB log backup, the MariaDB database needs binary logging enabled. You can check with the below command from the MariaDB database command line interface.
show variables like ‘%log_bin%’;
If you got log_bin value as on, which means binary logging is enabled.
If binary logging is not enabled, it needs the database administrator to enable it.
Create Backup Job
Step 1: Backup Source
First, select the backup source from the left column, then select the MariaDB database instance you wish to backup, in the right column will show which instance you selected, click on Next to step 2.
Step 2: Backup Destination
A backup destination (backup storage) should be associated with this backup job.
In the Target Storage dropdown list, the storage belonging to the selected backup node can be selected.
In the Target Node dropdown list, you can select a backup node on which you want the backup data to be processed and stored.
Step 3: Backup Strategies
In the General Strategy includes Schedule, Throttling Policy, Data Storage Policy, and Retention Policy.
In the Schedule field, you can configure the schedule of the backup job. You can configure the job as a Backup as Scheduled job or a Once-off Backup job.
For a Once-off backup job, the job will only run for once, and only full backup will be performed. You only have to appoint a time of when to start the backup job, in the Time Schedule field.
For backup job type, you can schedule Full Backup, Incremental Backup, and Log Backup. Here we take these three Backups as an Example. Please set the backup mode and backup schedule as per your actual demands, then please click on Next to continue.
Throttling Policy is optional. It can be used to limit the transmission speed during database backup if needed.
There are 3 options in the Data Storage Policy section, Data Deduplication, Data Compression, and Data Encryption. By enabling Data Compression and Data Deduplication, the backup data will be deduplicated and compressed before saving it into backup storage. By enabling Data Encryption, the backup data will be encrypted in the backup storage.
For the retention policy of the database backup, there are 2 retention modes, retain the database backups according to the Number of Restore Points or Number of Days.
For the retention mode Number of Restore Points, the restore points will be counted as full restore points, including the incremental backups and log backups dependent on this full backup.
For retention mode Number of Days, Vinchin Backup Server will save the restore points within the specified number of days.
When the retention policy is triggered, the outdated restore points will be purged to comply with the retention policy.
In the transmission Strategy, you can choose to enable Encrypted Transfer for data safety. The backup data will be transferred through LAN.
The Script configuration is disabled by default. Enabling it allows you to configure scripts to run before and after backups. Before backup script: Executes before the database backup, such as disabling database operations. After backup script: Executes after the database backup completes, such as re-enabling database operations.
In the Security Strategy it indcluding WORM Protection and Integrity Check. Once enable the WORM Protection (Write Once Read Many), the backup points cannot be modified or deleted before expiration, and their retention period can only be extended. The default protection period is 7 days, with a configurable range of 1 to 9999 days.
Integrity Check before performing incremental backup (if the check period is exceeded) verifies the health of thebackup point by checking part of thesource data information in the backupdata. You can select the Check Schedule and can task Redo or Terminate action when backup points are abnormal.
Advanced Strategy including Performance Optimization, Retry strategy and Overload Protection.
Processing threads and source-side compression can be configured in the Performance Optimization. Processing threads: Supports multi-threaded processing, with a default of 1 thread and a maximum of 16 threads. Source-side compression: Compresses data before transmission to reduce network bandwidth consumption and transmission latency.
when the network fluctuates, can reconnect to the current network by setting the number of Retry Attempts and Retry interval to reduce the factors that cause job failures due to network fluctuations.
Automatic Retry for Operation Exceptions, When enabled, if an operation excepetion occurs during job execution, it will re-execute according to the configured retry strategy This mechanism reduces task failures caused by RPC remote call exceptions.
After enabling Job Retry, if an objects exception occurs during job execution, it will re-execute according to the configured retry staategy.Reduce redundant backups caused by failed backups of some objects when retrying other successful backup objects, improving task efficiency.
After enabling Overload Protection, if resource limits are configured on a backup node, backup tasks running on that node will operate within those constraints. By default, backup tasks are subject to resource limits. For tasks with higher priority, enabling this setting allows them to bypass node resource restrictions.
Step 4: Review & Confirm
After completing the above-mentioned settings, you can review and confirm the settings on one screen.
A job name can be specified for identification of the database backup job, and by clicking on the Submit button to create the backup job.