THIS STEP IS TO BE PERFORMED ON THE DR SERVERS!

Back4 configuration has to be updated so it looks into the correct shared volumes on the DR servers instead of the "Live" L-servers.

The configuration is stored in the SQL database and like the previous step, since the database at this point is a copy of the Live database, the configuration is still pointing to shared folders on the Live servers.

You may prepare beforehand an SQL script on C:\Tera\DR of the DR SQL server called PrimeDBForLive.sql., so it's enough to paste it into SQL Management Studio and execute it. Note: what follows is only an example that may be unsuitable for your situation!

The sample script code

-- PrimeDBForLive.sql 

-- ------------------ 

-- 

-- This script updates all the Back4 file sources to use the directories on the Buffalo Grove's Back4 server 

-- instead of the live Back4 server's directories 

-- 

-- Use this script to 'prime' the database in case the Buffalo Grove servers are needed as disaster recovery 

-- servers 

-- 

-- Back4 File Sources: 

Update s_DatasrcfilesTable Set s_outputDir = REPLACE(s_outputDir, '\\l-gn4back4\', '\\bg-gn4back4\') Update s_DatasrcfilesTable Set s_inputDir = REPLACE(s_inputDir, '\\lb-gn4back4\', '\\bg-gn4back4\') Update s_DatasrcfilesTable Set s_errorDir = REPLACE(s_errorDir, '\\l-gn4back4\', '\\dr-gn4back4\') 

-- Volumes: 

Update gn_VolumeTable Set gn_Url = REPLACE(gn_Url, '//l-gn4back4/', '//dr-gn4back4/')

What you should do?

Run this script by opening it in SQL Server Management Studio and using the Execute button. Make sure you have GN4 database selected as the default database:

The script should only take couple of seconds to run and you should see something like this as the result: