Cross-datacenter Recording Server failover procedures in a Lync environment

This section contains configuration changes regarding cross-datacenter recorder server failover procedures required to manually switch between 2 datacenter sites. These procedures can only be applied in the following use case:

• Verba is deployed across 2 data centers.
• We assume Media Repository and Lync services are available in both datacenters
• Recording Servers are connected to local, data center specific Lync environments
• There is no cross-reference between the 2 sites on the Recording Server level.
• If all Recording Servers go down on one site, Verba needs to be manually reconfigured to record in the working datacenter the remote Lync system located in the other data center.

The Recording Server failover procedure contains 2 major steps: 

• Reconfigure the Verba Passive Recorder service to change announcement target URLs to preferred ones
• Reconfigure the Verba Passive Recorder service to connect to recorder proxies running on the other site

Reconfigure the Verba Passive Recorder service to change announcement target URLs to preferred ones

Currently, we support recording announcement for only one Lync pool even so we can record conferences from multiple pools on the same recorder server. If you prefer to use the site's with failed recorders announcement service(s) instead of local one(s), you should change recorder service's recording announcement servers list. 

To change the configuration, follow the next steps:

Step 1. Navigate to Administration/Verba Servers or Administration/Configuration Profiles (in case you want to update the configuration profile used by the recording servers)

Step 2. Select the server which runs the Recording Announcement service or the configuration profile

Step 3. Select the 'Change Configuration Settings' Tab and open the 'Passive Recorder node.

Step 4. Change the Recording Announcement for Lync Conference to the intended announcement service urls.

Step 5. After saving the changes, follow the instructions in the upper yellow banner to apply the changes on the affected server(s).

Step 6. Repeat the steps above on all servers or configuration profiles.

Reconfigure the Verba Passive Recorder service to connect to recorder proxies running on the other site

In a failover scenario, the settings of the passive recording service have to be changed in order to connect the recorder service to the other site's Verba Recorder Proxy/Remote Capture services as well. This modification will allow the recording system on the site with working recorder servers to record the calls belonging to the other site and to the local site. Failover feature of remote site's recorder proxies will reassign the to be recorded calls to the local recorder servers.