Cisco Cisco Process Orchestrator 3.0 User Guide

To create a new database on a new database server:

Open a console connecting to any Process Orchestrator server in the environment.

Choose Administration > Database Settings, right-click Report Database and choose Remove Cisco 
Process Orchestrator Reporting Database Connection.

Create a new Reporting database on the new database server (see 

).

The changes will propagate throughout the entire high availability environment.

If your entire database has failed:

Contact your Cisco Process Orchestrator Support team (see 

). To ensure that the latest procedures are followed and to minimize downtime, 

the support team should be contacted as early as possible and involved throughout the process. Do not 
wait to call them until the disaster recovery process goes astray.

Stop the Process Orchestrator service on all of the server machines.

Restore the database from the latest backup to a new database server (or new database schema). The 
restore will depend on the database version; follow the manufacturer’s instructions for your database 
server.

If you do not have a backup, you cannot recover the database. In that case, you must reinstall the 
entire environment.

Log in to the first Process Orchestrator server, then use the Database User utility 
(Tidal.Automation.Server.DatabaseUserConfigurationUtility.exe) to point the server to the new database 
and/or new credentials.

Start the Process Orchestrator service on this server. 

Launch the Process Orchestrator console, then verify and correct Reporting database configuration if 
needed. This step is required if the Reporting database connection or the reporting credentials have 
changed.

Log in, reconfigure, and restart (

 and 

) all other Process Orchestrator servers in the 

environment.