Backup Sets

About Backup Sets

The backup set is a grouping mechanism that simplifies and optimizes backing up MySQL databases, and tables that are accessible for a MySQL server or is a part of MySQL cluster. It lets an administrator define a set of backup policies (what, how, where and when) to automatically schedule different backup runs.

All ZMC actions (backup, restore, reporting, and monitoring) are performed in the context of backup sets.

A backup set cannot include more than one MySQL server, unless those servers form a cluster. A backup set can include one or more databases. When selecting individual tables as backup sources, you must select a single database, then the tables it contains. A single backup set cannot contain tables from multiple databases.

Multiple backup sets are useful for protecting a large number of systems with different backup requirements, but many organizations with less complex backup requirements can define a single backup set to meet their needs. For example, on a network that includes several databases with high transaction rate along with other databases that change more slowly, you would probably want to create one backup set for the more active databases, and another backup set for the less active ones.


What a Backup Set Contains

A backup set is defined by the following properties:


Besides being unique, the name must consist of alphanumeric characters. Dashes (-) and underline (_) characters are also allowed.
Type and Name of MySQL host: Identifies the MySQL server (identified by DNS name or IP) or cluster being backed up, and the database(s), or table(s) within in a database to back up.
The destination directory where the backups will be stored until they are expired by the retention datespecified by the retention policy.
Specifies the backup cycle policies used when automatically generating backup schedules.
Specifies the backup method to use and other parameters such as Backup Mode, Replication, Encryption, snapshots, etc.


Multiple backup set configurations

ZRM for MySQL employs multiple levels of default inheritance to simplify the process of administering multiple backup sets:

Factory settings
These are the "built-in" assumptions that allow many administrators to use ZRM for MySQL right "out of the box" with few configuration changes.
Site Settings
These allow the admistrator to set global defaults used when creating backup sets. For example, if you have a single MySQL server and are creating multiple backup sets for different the databases it contains, you can set up a site-wide default MySQL server (and related parameters).
Backup set
The backup set itself allows you to override either Factory or Site settings.


Backup Set Starter Page

This is the first page of Zmanda Management Console (see below figure). The left panel can be used to create a new backup set. The right panel is the backup set dash board that shows the list of backup sets, status of the backup set backups and which MySQL server is being backed up.


Create New Backup Set

Backup Set Owner
Use the dropdown menu to choose the ZRM for MySQL user who will own the backup set. The only available user will be Admin until you configure more users.
Backup Set Name
Specify an unique and descriptive name for the backup set. The name can include any alphanumeric characters, along with periods and hyphens. Spaces are not allowed. Backup Set Name cannot be changed after creation.
Enter an optional comment that describes the purpose of the backup set. The comment can contain any alphanumeric characters. Special characters such as # and newline are not allowed.
Create Backup Set
Click the Create Backup Set button when you are done. The Backup Summary page is then displayed, allowing you to set further options for the backup set.


Backup Set Dashboard

Backup Set Name

The list of backup sets configured on the ZRM server. They can be sorted. You can select a backup set by clicking on the name.

Last Backup Level

The level of backup performed last for the backup set. 0 means full backup. 1 means log incremental or differential or chained differential backup.

Last Backup Date stamp

Date and time of last backup performed for the backup set.  The green icon indicates the last backup was successful. The Red icon indicates last backup was a failure and the backup set needs attention.


Each backup set is associated with a MySQL server. The host name or IP address of the MySQL server.