Cuestión de la delimitación de la plataforma continental entre Nicaragua y

This feature is not supported for MySQL database backups.

•

Step 8: Advanced Options

If you want to configure some additional advanced options - like, Multiple Full Backups etc. click on the Advanced Options button.

Run this backup each time StoreGrid restarts - If you enable this option by checking the checkbox, then this backup schedule will be run every time StoreGrid is restarted or the machine is rebooted irrespective of the actual schedule time of this backup schedule. This is to ensure that any modified or new files created when StoreGrid was down are backed up as soon as possible. In case of the Continuous backup or ‘Run every…’ scheduling options, backups will run each time StoreGrid restarts – by default.

Run this backup immediately after saving this configuration (thereafter, Backups will be scheduled as per the schedule stipulated) - If you enable this option, then this backup schedule will be executed once immediately after you save this backup schedule – even if its not yet ‘time’ as per the schedule. For example if you configure a daily backup at 10.00 AM but you configured the backup at 8.00 AM, then the backup schedule will be run once immediately (8.00 AM) and then as per schedule (eg. daily at 10.00 AM).

Attempt to run this backup every 5 minutes in case of non completion because of a problem (Network error etc.) : If enabled, the user can choose to reschedule this backup every 5/10/15/20/25/30 minutes, whenever an attempted backup is incomplete because of a network error, server crash etc. The number of times the backup will be rescheduled (due to an error) can be configured to be in between 1-5 or unlimited, with the default setting as 5. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the next actual schedule time. Note that this option is enabled by default.

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

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 "Configure/Save Backup” button to activate the backup as per the schedule- on to the configured backup servers.

Troubleshooting Tips

Database names are not listed in the Step 2 of the 'Backup -> Create MySQL Database Backup' page(for windows).

Cause 1: If MySQL Settings for StoreGrid is not configured.

Solution : Configure MySQL settings from "Administration->Advanced Options" menu "MySQL Settings" icon in the left hand side and then check if MySQL database(s) are listed in the "Backup -> Create MySQL Database Backup" page (for windows).

Cause 2 : If MySQL service is not started in the machine.

Solution : Start the MySQL service and then check if MySQL database(s) are listed in the "Backup -> Create MySQL Database Backup" page (for windows).

Cause 3 : When the last time MySQL Settings was saved for mysql server instance port, MySQL Exe path field value was not modified/edited, or may be an older version (MySQL 4) exe path value was entered for the newer version (MySQL 5) port.

Solution : Enter the correct MySQL(version) Exe path value for the mysql server instance port selected.

Cause 4 : mysqldatabase.lst file present in the "<SG_HOME>/plugins/MySQLServer/" folder does not have the database list.

Solution : Check the MySQL version running in the machine (4.x or 5.x). StoreGrid only supports listing MySQL 4.x and 5.x database(s) for backup.

Database names are listed in the Step 2 of the 'Backup -> Create MySQL Database Backup' page, but backup dump is not created.

Cause : Configured username and password in the MySQL settings page may not have access to the database(s) configured for the backup schedule.

Solution : Check if the user name and password entered in the MySQL settings have appropriate permissions to take a backup dump of the database(s).

MySQL Server backups failed after recovering StoreGrid client configurations from backup server through Client Disaster Recovery option.(for Windows)

Cause : MySQL Server details(UserName, Password, PortNumber) are not available in StoreGrid client machine. Solution : In this case, save the MySQL Server details in MySQL Settings[For Windows] page before retrieving client configuration through Disaster Recovery option.

Limitations

1. Databases listed in the "Backup -> Create MySQL Database Backup" page(For Windows) will be for the the last saved MySQL Server instance port in the MySQL Settings.

changes will take effect only for the new mysql database backup schedules created.