Moving the database of the Verba system consist of various steps. Before starting the process, make sure you have the followings available:
- Administrator access to the existing SQL Server which is hosting the Verba database
- Administrator access to the new SQL Server which will be hosting the Verba database
- Microsoft SQL Server Management Studio, the application can be downloaded from: https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms
- A clear and definite plan for the database move including a rollback plan
- The process includes taking the database offline, which means that certain features will not be available during the procedure, make sure it does not interfere with your business and regulations
- When you have a complex deployment, make sure you have the right engineering resources available knowledgeable of the deployment
The following list briefly outlines the database moving process:
- Reconfiguring the system to use the new SQL Server
- Taking the database offline on the old SQL Server
- Detaching the database on the old SQL Server
- Moving the database files to the new SQL Server
- Attaching the database on the new SQL Server
The following features will be not available while the database is offline:
- Any feature available through the web based user interface including search, playback, configuration changes, etc.
- Storage policies will not run and wait until the database is online again
- Recorders will not insert data into the database, recording will continue to work, database records will be inserted once the connection is restored
Changing the SQL Server connection parameters
Step 1 - Change the database connection parameters to the new server. It has to be done before moving the database because after moving the database, the system configuration cannot be changed until the new database is connected. Login to the web interface and navigate to the Servers or Configuration Profiles under System.
Step 2 - Navigate to Change Configuration Settings tab and drill down to Database Connection. Change the connection parameters for the new SQL Server. Make sure you enter the right information because once you save the new settings, the system configuration cannot be changed (only manually in the local registry). For more information see Configuring database connection.
Step 3 - Save the changes by clicking on the icon.
Step 4 - Repeat the steps above on all servers and configuration profiles. It has to be changed on all servers.
Step 5 - A notification banner will appear on the top. Click on the click here link, so you will be redirected to the Configuration Tasks tab. Click on the Execute button in order to execute the changes.
From this point, the system will try to connect to the new SQL Server. Since the Verba database does not exist on the new SQL Server (yet), the system will raise database connection down alerts. See above for restrictions while the database is offline.
Taking the database offline and detaching it
Step 6 - Connect to the SQL Server hosting the Verba database using SQL Server Management Studio.
Step 7 - Expand Databases, and select the name of the Verba database you want to move.
Step 8 - Right-click on the database name, select Tasks, select Take Offline. The database cannot be taken offline if there are active connections blocking the task. In order to close all blocking connections, right-click on the SQL Server instance name and select Activity Monitor from the menu. Once Activity Monitor has loaded, expand the Processes section. Scroll down to the SPID of the process you would like to kill. Right-click on that line and select Kill Process. A popup window will open for you to confirm that you want to kill the process. Once this is done, the process will be terminated and all uncompleted transactions will begin the rollback process.
Step 9 - Lookup the location of the database files on the server and make a note of the information. Right-click on the database name, select Properties then select Files. You can find the information in the Path and File Name columns.
Step 10 - Under Tasks, click Detach to detach the database.
Moving and attaching the database
Step 11 - Copy the database files (both .mdf and .log files) to the new SQL Server.
Step 12 - In SQL Server Management Studio Object Explorer, connect to the new SQL Server and then expand that instance
Step 13 - Right-click Databases and click Attach.
Step 14 - In the Attach Databases dialog box, to specify the database to be attached, click Add; and in the Locate Database Files dialog box, select the disk drive where the new copy of the database resides and expand the directory tree to find and select the .mdf file of the database. For example C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\Verba.mdf
Step 15 - The system should be able to reconnect to the database and send database connection up alerts. Verify that all components are able to connect to the database.