Adept Backup Solution - Configure Database MySQL Backup Schedule How to configure a MySQL Database Backup. Overview.

Transcription

1 201 Datavoice House, PO Box 267, Stellenbosch, Elektron Avenue, Technopark, Tel: Stellenbosch, 7600 Fax: Adept Internet (Pty) Ltd. Reg. no: 1984/01310/07 VAT No: Adept Backup Solution - Configure Database MySQL Backup Schedule How to configure a MySQL Database Backup Overview. StoreGrid supports full and incremental back-ups of MySQL databases. The database(s) is dumped locally on the client side. If a full backup is done the full dump will be sent to the Adept Internet backup server(s) whereas if a incremental backup is done only the differences between the last back-up and the current one will be sent to the Adept Internet backup server(s). In both backup types a full back-up will be done on the local client to allow for the compare to create the incremental back-up for the Adept Internet backup server(s). Requirements Supported Windows, Linux MySQL 4.0 and later The StoreGrid service needs to run as a root (Linux) or System / Administrator (Windows) user. MySQL root user login details. MySQL Backup Linux Requirements By default, StoreGrid checks for 'mysql' under '/var/lib' folder in the system during the installation process. StoreGrid uses the internal MySQLDump utility (mysqldump) to backup MySQL Database(s) in the Linux machines. MySQL Backup Windows Requirements By default, StoreGrid uses the internal MySQLDump utility (mysqldump.exe) to backup MySQL Database(s) and it uses the MySQL Exe (mysql.exe) to list the database names in the Backup Schedule setup. MySQL Backup Schedule Configuration Pre-Schedule Configuration. Before a MySQL backup can be configured in StoreGrid, you should configure the MySQL settings through "Settings->Advanced Options" and click on the "MySQL Settings" icon in the left hand side. Without the correct values for MySQL settings, StoreGrid will not be able to list the databases to be configured for backups in.

2 Ubuntu / Redhat / CentOS 2

3 3 Windows MySQL Backup Schedule Configuration. To configure the MySQL backup Schedule from the main screen go to Backup -> Add Plugin Backups : MySQL Step 1: Schedule Name The first step in configuring a backup is to give a name for the backup schedule. The backup schedule name will uniquely identify the backup. While restoring your backup data, you need to choose the data to be restored using its schedule name. Only [a-z][a-z][0-9][ - _ ] characters are allowed in the Backup Name Step 2: Select Database(s) Select the databases that need to be backed up as a part of this schedule. Select All Databases for this schedule If "Select All Databases for this Schedule" option is chosen, it will include all the databases present in the MySQL server. If a new database is later added to the MySQL Server, it will be automatically included in this backup schedule. Let me manually choose databases If "Let me manually choose databases" option is chosen, then any databases can be selected for backup. Icon

4 4 If a new database is later added to the MySQL Server, it will not be automatically included in this backup schedule. Step 3: Set Basic Configuration Backup Type This is the type of Backup Required. Adept Internet Suggest that a backup be kept on the "Same Machine" and "Remote Server", to allow for fast restores when a file was deleted. The remote server will be used in the case where the PC / Server had a failure or was stolen. NOTE: Retention policies will not apply for a local backup. The Retention policies configured for this backup schedule will work only if the backup data is migrated into a backup server (seed backup). Remote Server - Select this option if you want the backup data to be transferred to a backup server directly when the backup schedule runs. Select Backup Server : This is the list of peers/backup servers in which the backup data can be stored. Once the backup server is selected, you cannot change the server name. In case the backup server name or IP address is to be changed in future, you can change it from the Seed Backup Migration page. The client will run the backup to the selected backup server. Test connectivity - Before you select the backup server for this backup schedule, you can check the connectivity to backup server. It also checks the different settings configured in the backup server for this client and confirms if this client can backup to the chosen backup server or not. Encryption Icon The backup will be encrypted with the password and cannot be recovered without the password. Please keep

5 5 passwords in a safe place. Saving the password on the same computer that are backup is not recommended. Retention Policies (Optional) StoreGrid provides the retention feature where backups of multiple versions of a file can be maintain at the backup server. StoreGrid cleans up the version files in the backup server based on two major retention policies:

6 6 1. Version-Based Retention - Retains multiple version files in the backup server based on the version file count.

7 7 2. Time-Based Retention - Retains multiple version files in the backup up server based on the age of the version files. Step 4: Scheduling (Decide When To Backup) This field has the following options from which any one can be chosen.

8 8 Step 5: Additional Full Backups Typically, you would do a full backup the first time you backup your data and thereafter only do incremental backups. However, like in a typical enterprise scenario, if you want to run full backups periodically and run the incremental backups in between two full backups, then you can configure the scheduling for how to run the full backups here. For Run Every Few Hours and Run Daily backups, the Additional Full Backup settings will allow you to configure daily/weekly/monthly additional full backups. For weekly backups, only Monthly additional full backups are possible. For Run Once Only backup, you cannot configure additional full backups. Additionally you can specify the maximum number of full backups that need to be stored in the server. For example if you configured a weekly backup and additionally if you configure a monthly full backup, then StoreGrid will take a full backup the first time and then weekly do an incremental backup. The next month, StoreGrid will do a new full backup and subsequently run the weekly incremental backup over this full backup. After 6 months you will have 6 separate full backups in the backup server along with weekly incremental versions under each of the 6 full backups. If your policy is to retain only backup data for 6 months, then you can configure "Store maximum of 6 full backups" here. On the 7th month, StoreGrid, after finishing the 7th full backup, will delete the first full backup along with its weekly incremental backups thus retaining always the last 6 month backups.

9 9 Advanced Options (Optional) If you want to configure some additional advanced options - like, CPU utilization, Compression settings, etc. click on the Advanced Options button. Saving the configured backup Once all the MySQL Server database(s) to be backed up are chosen and the configuration options are set, you simply need to click on the "Save Backup" button to activate the backup as per the schedule- on to the configured backup servers.

10 10 Icon A warning will come up after the save. Read this warning carefully. Limitations 1. Databases listed in the "Backup -> Plugin Backups -> MySQL" page(for Windows) will be for the the last saved MySQL Server instance port in the MySQL Settings. 2. Backup Report/View Backup/Edit Backup UI pages does not provide the details like MySQL Server name, port etc.