Best Practices for Disaster Recovery

  • Article

Applies To: System Center Data Protection Manager 2007

Backups of data, whether by DPM or third-party software, rely on the integrity of the data being protected. To minimize the risk of data corruption, we recommend the following guidelines:

  • Run tools that check application integrity regularly, such as DBCC in SQL Server.

  • Monitor event logs on the protected computers and DPM server for hardware and file system errors.

  • Perform regular test recoveries of protected data.

  • Perform frequent consistency checks on critical data.

  • Use a secondary DPM server to provide additional protection and redundancy.

DPM runs the pre-backup and post-backup scripts by using the local system account. As a best practice, you should ensure that the scripts have Read and Execute permissions for the administrator and local system accounts only. This level of permissions helps to prevent unauthorized users from modifying the scripts.

On each protected computer, you should back up the scripting file, ScriptingConfig.xml, at \Program Files\Microsoft DPM\DPM\Scripting, and all pre-backup and post-backup scripts.

See Also

Concepts

Backing Up DPM by Using a Secondary DPM Server
Using Pre-Backup and Post-Backup Scripts