Backing Up the ARS Configuration Database (35799)

This article provides information about backing up the ActiveRoles Server configuration data.

Note: Backing up the ARS configuration data is not equivalent to backing up Active Directory data. The Active Directory data should be backed up separately.

BACKING UP A STANDALONE ARS DATABASE / ARS SHARED DATABASE.

Given that there is a relatively small amount of configuration data, the ARS database is usually around 50MB in size, and changes made to the database are small scale and infrequent. Therefore, it is sufficient to adopt a Simple Recovery Model for the ARS database and carry out a full backup approximately once per hour.

An alternative is to perform a differential backup at a higher frequency, perhaps once every 15 minutes, and a full backup once per day. Such a backup regime allows for manageable administration and provides adequate security for the ARS configuration data. Other methods of backup are also acceptable, depending on the customer's particular requirements.

BACKING UP AN ARS DATABASE IN A REPLICATION ENVIRONMENT

If ARS replication has been configured, the recovery model and backup regime for the ARS database itself remains unchanged. A full backup of the ARS database can be carried out once per hour. Alternatively, a differential backup could be carried out at a higher frequency, perhaps once every 15 minutes, and a full backup once per day.
However, in addition to the ARS database, the system databases must also be included in the backup plan:

• master
• msdb
• distribution

For ARS, the distribution database is by default named ARServer6x (depends on ARS build version 6.5, 6.7, etc.)

In a replication environment, it is necessary to consider two possible scenarios:

Scenario 1: the Publisher goes down

A backup of the Publisher alone may be used to restore the replication group. In the event of Publisher failure, the system databases should be restored first, followed by the ARS database. Then, the ARS Service should be installed, selecting the option to use an existing database and specifying the restored ARS database.

Scenario 2: The Subscriber goes down

In this case no backup is required. The Subscriber can be restored by simply installing the ARS Service on a clean machine, and then adding the new ARS Service to the replication group. However, if preferred, the Publisher and all Subscribers can be backed up, and in the case of restore, individual Subscribers can be restored separately.

REFERENCES

The following links provide additional information on database recovery.

GENERAL DATABASE RECOVERY
 

• Simple recovery: http://msdn.microsoft.com/en-us/library/ms186216.aspx
• Selecting a Recovery Model: http://msdn.microsoft.com/en-us/library/ms189275.aspx
  
  REPLICATION
• Strategies for Backing Up and Restoring Merge Replication: http://msdn.microsoft.com/en-us/library/ms152497.aspx
• Backing Up and Restoring the model, msdb, and distribution Databases: http://msdn.microsoft.com/en-us/library/ms190190.aspx
• Backing Up and Restoring Replication Databases: http://msdn.microsoft.com/en-us/library/ms151152.aspx