Isolation procedures for Verba
Overview
In some cases it may be necessary to temporarily disable, remove, or disconnect Verba from the network to isolate a problem or to stabilize the network. This topic provides a description of the process and a detailed procedure that will allow a technical support engineer to completely disable and isolate your Verba solution.
In case of mirror port (SPAN) based recording, the Verba Recording Server component is listening on a monitor port of a switch, so it does not generate traffic on the network. The Verba Media Repository component (SQL Server, Apache/Tomcat) behaves like a web server using a database. When users play back recorded calls, the system transfers the media file through the network to the user's computer.
Stopping Verba in a Lync environment
Step 1 Connect to the Verba Recording server(s) / Verba Media Repository remotely using Remote Desktop/Terminal Services Client/PcAnywhere or equivalent. If remote connection is not available then perform the following steps locally on the server.
Step 2 Open the Service Control window (services.msc).
Step 3 Select the following services from the list and stop them by clicking on them with the right mouse button and select Stop :
- Verba System Monitor Service (it is important to stop this service first, why? As otherwise, this service will restart other stopped Verba services.)
- Verba Recorder Proxy Service
- Verba Passive Recorder Service
- Verba Storage Management Service
- Verba Node Manager Agent Service
- Verba Web Application Service
- MSSQLSERVER
Stopping all services ensures that Verba is disabled.
Step 4 Connect to the Lync Front End server remotely using Remote Desktop/Terminal Services Client/PcAnywhere or equivalent. If remote connection is not available then perform the following steps locally on the server.
Step 5 Open the Service Control window (services.msc).
Step 6 Select the following services from the list and stop them by clicking on them with the right mouse button and select Stop:
- Verba Node Manager Agent Service
- Verba Lync Filter
Stopping all the services ensures that Verba is disabled.
Step 7 Repeat Steps 1-7 on all Verba servers and Lync Front End servers.
Step 8 If one of the services does not stop normally then follow the steps outlined in the "Shutting down Verba server" section.
Stopping Verba in a Cisco environment
If you are experiencing service degradation in your Cisco UCM system, always start by stopping the Verba Cisco Central Recorder Database Service on your recorders.
Step 1 Connect to the Verba Recording server(s) / Verba Media Repository remotely using Remote Desktop/Terminal Services Client/PcAnywhere or equivalent. If remote connection is not available then perform the following steps locally on the server.
Step 2 Open the Service Control window (services.msc).
Step 3 Select the following services from the list and stop them by clicking on them with the right mouse button and select Stop:
- Verba System Monitor Service (it is important to stop this service first, why? As otherwise, this service will restart other stopped Verba services)
- Verba Passive Recorder Service
- Verba Cisco Central Recorder Service
- Verba Cisco Central Recorder Database Service,
- Verba Storage Management Service
- Verba Node Manager Agent Service
- Verba Web Application Service
- MSSQLSERVER.
Stopping all the services ensures that Verba is disabled.
Step 4 Repeat Steps 1-7 on all Verba servers.
Step 5 If one of the services does not stop normally then follow the steps outlined in the "Shutting down Verba server" section.
Shutting down Verba server
Step 1 Connect to the server remotely using Remote Desktop/Terminal Services Client/PcAnywhere or equivalent. If remote connection is not available log in locally to the server.
Step 2 Initiate a shut down from the Start menu (Start menu/Shut down/Shut down). If the server shuts down normally, Verba is disabled.
Step 3 If the server hangs after initiating the shut down, switch off the server manually.