Database Guide › Database Backups › Backup Tasks for SQL Server

Backup Tasks for SQL Server

If you use SQL Server as your database engine, the backup procedure has four steps. First, you must back up essential registry keys on your CMS. Second, you must set up a maintenance plan for your system databases. Third, you set up a similar plan for your CA DataMinder database. Finally, you must add the CA DataMinder data folder into your existing backup regime.

1. Back up the data management registry key

   See the general backup tasks.

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, you have probably 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.

      Note: The following steps describe where specific settings are required for a successful CA DataMinder backup. If a wzard screen is not mentioned, you can safely assume that settings on that screen do not affect CA DataMinder backups.

   2. Create a maintenance plan for all system databases (master, model and msdb).
   3. Schedule a database integrity check.

      Important! The Integrity Check wizard screen includes an option to ‘Attempt to repair any minor problems’. Because of a known SQL Server issue, do not select this option because it may cause related backup jobs to fail. For details, see the MS Knowledge Base article Q290622.

   4. Create a database backup plan. You need to:
      • Verify the integrity of the completed backup.
      • Choose a backup location (tape or disk) for the backup file.
      • Schedule when the backup runs.
   5. 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 issue, do not specify a transaction log backup plan for your system databases. For details, see the MS Knowledge Base article Q285288.

   6. 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. See the following steps for details.

   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 completed backup.
      • 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 and 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 system 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