Cisco Cisco Process Orchestrator 3.0 User Guide

If your environment fails but you have snapshots of the Process Orchestrator server VMs saved at an 
alternate site, use the procedure described in 

instead.

Follow these steps when your environment fails and you do not have snapshots of the Process 
Orchestrator server VMs saved at an alternate site:

Contact your Cisco Process Orchestrator Support team (see 

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

contact the support team as early as possible and involve them throughout the process. Do not wait to 
call them until the disaster recovery process goes astray.

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.

To import the Windows security credentials encryption key from the Keys.xml file created in 

 to the new (first) Process 

Orchestrator server in the environment, enter the following command (do not cut and paste):

aspnet_regiis -pi “Tidal Intelligent Automation Server” Keys.xml -exp

Aspnet_regiis.exe is a Microsoft.NET framework utility that resides in the .Net Framework folder. For 
example, this folder is typically located at this location:

C:\Windows\Microsoft.Net\Framework64\{Version}\aspnet_regiis.exe

You might need to specify the full path to this utility if you have not defined the path in your Path 
environment variable.

It is not enough to just bring the Process Orchestrator environment up; you also need the security 
credentials encryption key to apply to the server at the new site to make this database copy 
usable. If you do not have a backup of this key, you cannot recover the database. In that case, 
you must reinstall the entire environment.

Reinstall the core Process Orchestrator software from the installation media. Be sure to reinstall the same 
version and all of the updates/hotfixes.

Replace the server configuration file on the new machine with the file copied in 

.

If the file contents contain any path (such as the log file path), make sure that the path is still 
valid in the new server machine.

Use the Database User utility (Tidal.Automation.Server.DatabaseUserConfigurationUtility.exe) to point 
the server to the restored database and/or credentials.

Start the Process Orchestrator service on this server.