Cisco Finesse uses the
backup and restore tools provided by the common Cisco Unified Communications
To access the Disaster
Recovery System (DRS) application, direct your browser to the following URL:
IP is the IP address of your Finesse server.
For more information
about backup and restore, see the detailed online help provided with the DRS
Restore First Node
in HA Setup with Rebuild
In a high
availability (HA) setup, if a hard-drive failure or other critical hardware or
software failure occurs, you may need to rebuild the primary Finesse node
(publisher node). Perform the following steps to restore the publisher node to
its last backed up state.
fresh installation of Finesse. Make sure to install the same version of
Finesse, using the same administrator credentials, network configuration, and
security password that you used for the initial installation.
||Access the DRS
application (https://Finesse server IP:8443/drf).
Restore menu, select
backup device. Choose the location where your backup is stored.
backup file to use.
to choose the nodes to restore, choose the first node.
You can also
select node2 from the drop-down list in the Select the server from which
database data needs to be restored area to restore the recent data from the
secondary Finesse (subscriber) node.
restore process is complete, restart the node.
following command on the primary Finesse server:
utils dbreplication stop
following CLI command on the primary Finesse server to set up replication:
utils dbreplication reset
dbreplication reset command can take some time to complete.
Run the CLI
utils dbreplication runtimestate on the primary
Finesse node. If the RTMT counter value for replication status is 2 on all
nodes, replication is functioning properly.
In an HA setup,
if a hard-drive failure or critical software failure occurs that requires a
rebuild of the secondary Finesse node (subscriber node), you can reinstall the
secondary node using the same version of Finesse, administrator credentials,
network configuration, and security password that you used for the initial
installation. After the installation is complete, check that the dbreplication
is functioning and allow the data to propagate from the primary to the
secondary node. However, if you need to restore third-party gadgets to the
secondary node, you must either upload them again or run the restore process on
the secondary node.
Always check the
dbreplication status after any restore, using the CLI command