Backing up and restoring Monitoring Server databases
In this article:
The process of backing up the Monitoring Server database is dependent on the data that is stored in the Monitoring Server database. The Monitoring Server database stores the application data, such as data sources, reports, and dashboards. The server files and components do not need to be backed up because they are not modified when the application is used.
The server files and components can be restored by running Monitoring Server Configuration Manager. The dashboards that have been exported to Windows SharePoint Services can be backed up in the same manner to any other SharePoint site or can simply be republished from Dashboard Designer once the application database has been restored.
Either Office SharePoint Server 2007 or Windows SharePoint Services must be installed in order to successfully install and use Monitoring Server. The terms Windows SharePoint Services and SharePoint Services are used collectively in PerformancePoint Server documentation to refer to Office SharePoint Server 2007 and Windows SharePoint Services 3.0.
Backing up a Monitoring Server installation
Back up a Monitoring Server installation
After connecting to the appropriate instance of the Microsoft SQL Server 2005 Database Engine, click the server name to expand the server tree.
Expand Databases, and then select the database specified when running the Monitoring Server Configuration Manager.
Right-click the database, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.
In the Database list box, verify that you have selected the correct database name.
In the Backup type list box, select Full.
In the Description text box, enter a description of the backup set.
Click Add to specify the folder where the backup file will be saved.
Click OK. After the backup file has been created and saved, it is recommended that a copy be made and stored in a separate location.
Restoring a Monitoring Server installation
When restoring a Monitoring Server installation, you will be first deleting the existing database and replacing it with a backup of a previous installation. This is done if the existing database is corrupted or damaged in some way.
The previous database is restored either by restoring an image of the computer or by completing a reinstallation of the current application on a newly formatted computer and running the Monitoring Server Configuration Manager. Once the Monitoring Server is available and a database has been deployed, the backup created in the previous steps needs to be restored.
Restore a Monitoring Server installation
After connecting to the appropriate instance of the Microsoft SQL Server Database Engine, click the server name to expand the server tree.
Expand Databases, select the database specified when running the Monitoring Server Configuration Manager, and then click Delete. Make sure to write down the name of the deleted database because it will be needed later.
Right-click on the database node, and then click Restore Database. The Restore Database dialog box appears.
In the To database box, type the name of the database you deleted.
The database name specified must match the name of the database that has been deleted.
Select From device, and then click Browse…. The Specify Backup dialog box will open.
Click Add to select the backup file. Click OK.
Click OK again to re-create the database.
Using Notepad, edit the Web.config file. Set the UseASCustomData and ConnectionPerUser to values specific to your deployment.
Complete the restoration of Monitoring Server either by completing the Windows SharePoint Services backup or by exporting the content from Dashboard Designer that had been published to a SharePoint site.
TasksMigrating Monitoring Server data from a test environment
ConceptsBack up and restore Dashboard Designer content
Retrieve lost or overwritten content in Dashboard Designer
Best practices for managing dashboard metadata and data sources
PerformancePoint Monitoring Server maintenance
Maintaining Monitoring Server databases
Monitoring Server validation and error logging