Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

About Database Feature

The Database Feature ensures that tables be locked and flushed before a backup operation can take place. Database feature coordinates with the point-in-time file system snapshot.

The Database feature requires you to specify a database account with administrative privileges that is used by the Backup Agent to flush tables with read lock before the file system snapshot is taken. And the lock must be held until the snapshot completes.

If you use CDP to backup MySQL and do not use the R1Soft Database Feature, then the table lock and flush operation will not take place and your MySQL backup may likely be corrupt.

Databases Replication and Restore Overview

Do the following to backup your database:

  1. Add an Agent to the system and enable the Databases Add-on for the Agent. See [Enabling Databases Add-On for Agent].
  2. Upload Java connector (only for MySQL). See [Installing the MySQL Connector JDBC into CDP3 Server].
  3. Create a Policy for the Agent. On the "MySQL," "SQL" and "Exchange" tabs, add your database instance(s) and specify other settings. See [Adding a MySQL Instance to a Policy], [Configuring MS SQL Server Replication], [Configuring an Exchange Instance].
  4. Run the created Policy.
In Server Backup Manager, end-user level databases backup is not supported. Only super-users can fulfill databases backup. Sub-users are limited by agent user permission.

The following steps should be taken to restore your database:

  • [Restoring a MySQL Database]
  • [Restoring MS SQL Server]
  • [Restoring a Microsoft Exchange 2010 Database to an Alternate Location]
  • [Restoring a Microsoft Exchange 2007 Storage Group to an Alternate Location]

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.