SnapProtect – Best Practices – MySQL iDataAgent

Table of Contents

Planning a Backup

When you create subclients for a database, you can create a complete backup of the database by backing up these subclients.

  • If you create a group of selected subclients for the database, you must back up all of these subclients to create a complete backup.
  • If you create separate subclients for the log files, and if these subclients are not included with the subclients that are defined for databases or subsets, then the subclients for these files must also be backed up to create a complete backup.

Creating Subclients

As a best practice, it is recommended that you create separate subclients to back up data that undergo frequent changes.

For example, if the EXAMPLE and USERS dbspaces undergo frequent changes, you can create a separate subclient for each tablespace.

Example:

  • User-defined subclient: Test1

    Content: EXAMPLE

  • User-defined subclient: Test2

    Content: USERS

Create a separate user-defined subclient for the log files on the client.

Distributing the client data using subclients as recommended above, can help improve backup performance by organizing the workload on the client into logical groupings.

Subclient Content

We recommend that you add only a few small databases to each subclient and add larger databases into separate subclients. On a restart condition, the system backs up all of the databases in the subclient from the beginning. In that case, you do not want a large database that has completed its backup successfully to be backed up again because a smaller one has caused a restart to occur.

Reconfiguring Default Subclient Content

We recommend that you do not re-configure the content of a default subclient because this would disable its capability to serve as a catch-all entity for client data. As a result, some data will not get backed up or scanned.

Changing Storage Policies

If you change a storage policy for a default subclient, and you want to restore to a point in time prior to the change (that is, restore from a previous storage policy), perform a full backup of the database as soon as possible. Data from the old storage policy is not considered to be the most recent cycle. When the storage policy exceeds its retention period, it is pruned.

MySQL Database Backup

The MySQL database is a system database that is created when the MySQL Server is installed. The database contains all of the metadata information, such as database access permissions, user information, and so on, that is used to manage the MySQL Server. Therefore, it is important that you back up this database often.

MySQL database names must be in English for backup operations to complete successfully.

MySQL Server Restore

Before you restore a master server, stop any replication processes between the master and slaves. After the master server is restored, make sure that the replication is online on the proxy server.