Recover Planning Server with SQL Server

Take the backups from all the Planning databases (service database, system database, all application databases) and Microsoft Windows SharePoint Services databases (if you use Windows SharePoint Services) from your previous backups and restore these database backups and their latest valid transactional logs into the new computer that is running SQL Server.

Prepare the new Planning Server computer that will run SQL Server. For more information about preparing the new computer, see the PerformancePoint Server 2007 Deployment Guide. For additional information about setting up the new computer, see Mirroring the Planning Server.

For a multi-computer deployment scenario, you might need to configure the security settings among the computers that are running the following software:

• SQL Server

• Microsoft SQL Server 2005 Analysis Services

• Windows SharePoint Services

For more information about configuring security settings in multi-computer deployment scenarios, see the PerformancePoint Server 2007 Deployment Guide.

Stop Planning Process Service on the server running Planning Process Service.

If there are applications on the failed SQL Server computer, connect to Planning Administration Console and take those applications to an offline state.

Fix some internal tables for the name changes for the computer that is running Planning Server and SQL Server.

First, manually update the BizSystem table in SystemDB by using the following command.

UPDATE BizSystem
SET ReferenceDBServerName = @NewAppDBServer,
StagingDBServerName = @NewStagingDBServer,
WHERE BizApplicationLabel = @BizApplicationLabel

Then, manually update the DeployInfo table in the application database.

Next, get BizAppNodeID from the BizAppNodes table by using the following command.

SELECT BizAppNodeID FROM BizAppNodes
WHERE BizAppNodeLabel = @BizAppNodeLabel

Then, update the DeployInfo table by using the following command.

UPDATE DeployInfo
SET AppNodeSQLStoreDBServer = @NewAppNodeSQLStoreDBServer
WHERE BizAppNodeID = @BizAppNodeID

Update the OLAP database connection strings in the computer that is running Analysis Services.

1. Expand the OLAP database hierarchy in SQL Server Management Studio.

2. Expand each database name, and then expand the Data Sources folder.

3. Right-click each subnode, select Properties, click Connection String, and then click the ellipsis for the Connection String box.

4. Enter the new SQL Server name in the Server Name field.

5. Repeat for all OLAP databases.

On the Planning Web Service and Planning Process Service servers, make the following changes in the PerformancePoint.Config file, which is located in the C:\PerformancePointTemp\3.0\Config folder.

1. Change the database server entry to the name of the new computer that is running SQL Server.

2. Change the OLAP server entry to the new OLAP server computer name.

   Note

   You only need to do this in a single server setup, because the entry was set by Setup in this scenario. For a multi-server deployment, this field is empty; you do not need to modify it.

On the computer that is running SQL Server, manually enable SQL Server Service Broker on all Planning Server application databases by performing the following SQL Server query:

ALTER DATABASE [PPSApplicationDatabaseName] SET ENABLE_BROKER

On both Planning Web Service server and Planning Process Service server, at the Windows command prompt, run IISRESET.

On Planning Web Service server and Planning Process Service server, restart Planning Process Service. This ensures that all changes to the configuration files are picked up by the servers.

If Windows SharePoint Services is used, you need to reconnect the Windows SharePoint Services server to it. Point Windows SharePoint Services back to its configuration and content databases on the new computer that is running SQL Server.

Take the following steps:

1. On the computer running Planning Server and Windows SharePoint Services, open Internet Information Services.

2. Expand the list and open the Web Sites folder.

3. Right-click SharePoint Central Administration and select Browse.

4. Click Set configuration database server.

5. Change the server name to the new SQL Server name.

6. Select Connect to existing configuration database.

7. Click OK.

8. Select Set default content database server and verify that the new name is correct. If not, update the name to reflect the new database server name, and then click OK.