Page History

...

Recovery and Migration Best Practices 

Verify the Configuration of the Target SQL Server

When identifying the new SQL Server instance that you want to host the Repository and Services, make sure this instance meets or exceeds the product requirements as well as these specific requirements.

• • You can dedicate the target instance to hosting the SQL Diagnostic Manager only
  • The target instance runs the same version of SQL Server software that is currently running on the existing SQL Diagnostic Manager computer

Back up the Repository Database

Use a tool such as IDERA SQLsafe to perform a full backup of the Repository database. If you changed the default recovery model to full, make sure your backup includes all transaction logs.

Identify how often to backup the Repository database

The frequency at which you backup the Repository database depends on the following factors:

...

The backup frequency should reflect your maintenance needs and allow you to meet future monitoring requirements.

Schedule routine backups of the Repository database

After you identify the appropriate backup frequency for your monitoring needs, use a tool such as IDERA SQLsafe to schedule routine backups of the Repository database. If you changed the default recovery model to full, make sure your backup includes all transaction logs.

Review disaster recovery guidelines

Make sure your recovery strategy includes plans to reinstate the original computer once it is repaired. Consider the following guidelines:

• To minimize data loss, plan to back up the Repository database on the temporary Repository computer immediately before reinstating the original computer.
• Use the procedures in this Technical Solution to reinstate the Repository on the original computer and configure the Management Service.
• To verify all components were reinstated correctly, test your implementation.
• Uninstall the components you previously implemented on the temporary computer.

...