Testing the Geo Diverse failover script without replication software

Perform these steps to test the geo-diverse failover script without installing any replication software.

1. Configure two separate Application servers.

   Use the same passwords and passphrase while installing the second Application server.

2. Configure one Device server to the first Application server.

3. Add the second Application server using the vcgeoadmin.pl script on the first Application server.

4. Stop the services on the first Application server.

5. Create a tar file containing the data and database directories:

   tar cf first_app_server.tar db data.
   

6. Copy the tar file to the [Product directory] on the second Application server.

7. Stop the services on the second Application server.

8. Rename the original data and database directories on the second Application server:

   mv db db_save;
   mv data data_save
   

9. Extract the files from the tar file on the second Application server:

   tar xvf first_app_server.tar
   

10. Unlock the lockbox on the second Application server using the commands:

    1. source /etc/voyence.conf 
       		  

    2. [Product
       			 directory]/bin/cstdriver -lockbox [Product directory]/data/lockb.clb
       			 -passphrase <passphrase entered during the installation> 
       		  

11. Update the second Application server IP address in the postgres.conf file in the first Application server at [Product directory]/db/controldb/data/postgresql.conf.

    Search for listen_address and update the IP address.

12. Go to the vcgeo directory on the second Application server and run the command:

    ./vcgeoadmin.pl start -f
    

13. Copy the bundle.p12 file at [Product directory]/conf/bundle.p12 from second Application server to the Device server.

14. Login to the Device server and perform the following tasks:

    1. source /etc/voyence.conf 
       		  

    2. Backup the files [Product
       			 directory]/bin/demoCA/cacert.pem, [Product directory]/bin/demoCA/index.txt, and
       			 [Product directory]/conf/CA/voyenceca.crt.

    3. perl [Product
       			 directory]/bin/importcertsintods.pl <certificate password during the
       			 installation> <location of the copied bundle.p12 in step 14] 
       		  

       Do not keep the backup in the same location.

    4. Remove all the data in the [Product directory]/bin/demoCA/index.txt file.

       Note:

       Be sure to remove blank lines, if any, from index.txt. The file must be completely empty.

    5. Delete all the files with .0 extension from [Product directory]/conf/CA/ directory.
    6. bash makekeys.sh

15. Change the IP address and FQDN in the following files and point to the second Application server.

    1. source /etc/voyence.conf

    2. [Product
       			 directory]/data/.rhttps 
       		  

    3. [Product
       			 directory]/data/devserver/master.addr

    4. [Product
       			 directory]/bin/cstdriver -lockbox [Product directory]/data/lockb.clb
       			 -passphrase <passphrase entered during the installation> 
       		  

    5. Restart the services on the Device server.

16. Change the IP address and FQDN in the following files and point to the second Application server.

    1. source /etc/voyence.conf 
       		  

    2. [Product
       			 directory]/web/conf/web.properties /etc/voyence.conf 
       		  

    3. [Product
       			 directory]/cstbin/cstdriver -lockbox [Product directory]/data/lockb.clb
       			 -passphrase <passphrase entered during the installation> 
       		  

17. Restart vcmaster service on the second Application server.

    Verify if the services have started on the second Application server and login to the Network Configuration Manager application on the second Application server.

18. Start an auto-discovery job.