Previous Topic: General Backup TasksNext Topic: Backup Tasks for Oracle

Administration Guide › CMS Administration › Backing Up and Restoring the CMS › Backup Tasks for SQL Server

Backup Tasks for SQL Server

Note: Backup and recovery procedures have been tested using Microsoft SQL Server 2000. These procedures may work correctly with other versions of SQL Server, but they have not been tested.

If you use SQL Server as your database engine, the backup procedure has four steps:

  1. Back up the master encryption registry key.
  2. Set up a maintenance plan for your system databases. If your organization already uses SQL Server databases for other purposes unrelated to CA DataMinder, it is probable that you have already set up a maintenance plan for your system databases. If not, you must up set up a maintenance plan for your system databases that incorporates a backup plan.
    1. In the SQL Server Enterprise Manager, expand the Management branch of your CMS and launch the Database Maintenance Plan Wizard.
    2. The following steps highlight the areas where specific settings are required for a successful CA DataMinder backup.
    3. If a Wizard screen is not mentioned, you can safely assume that settings on that screen do not affect CA DataMinder backups. Create a maintenance plan for all system databases (master, model and msdb).
    4. Schedule a database integrity check.
    5. Create a database backup plan. You need to:
      • Verify the integrity of the backup when it completes.
      • Choose a backup location (tape or disk) for the backup file.
      • Schedule when the backup runs.
    6. When prompted by the Wizard, do not specify a transaction log backup plan for your system databases.

      Important! You will specify a transaction log backup plan for your CA DataMinder database (see next section, step 3.4). Because of a known SQL Server problem, do not also specify a transaction log backup plan for your system databases. For details, see the MS Knowledge Base article Q285288.

    7. In the remaining screens of the Database Maintenance Plan Wizard, there are no specific settings needed for CA DataMinder backups.
  3. Set up a maintenance plan for your CA DataMinder database. The procedure is the same as for your system databases, except this time the maintenance plan does include a transaction log backup plan.
    1. Select your CMS in the SQL Server Enterprise Manager and launch the Database Maintenance Plan Wizard. As before, the following steps highlight only those areas where specific settings are required for a successful CA DataMinder backup.
    2. Schedule a database integrity check.
    3. Create a database backup plan. You need to:
      • Verify the integrity of the backup when it completes.
      • Choose a backup location (tape or disk) for the backup file.
      • Schedule when the backup runs. We recommend that you back up your CMS every week. Make sure that the backups for your system databases and CA DataMinder database not overlap.
    4. When prompted by the Wizard, do specify a transaction log backup plan for your CA DataMinder databases.

      Note: When you schedule the transaction log backup plan, make sure that it does not overlap with the scheduled backup of your CA DataMinder database.

    5. In the remaining screens of the Database Maintenance Plan Wizard, there are no specific settings needed for CA DataMinder backups.
  4. Back up your CA DataMinder data folder.

More information:

General Backup Tasks