Promoting High Availability Instance
Click Studios
Passwordstate
Instructions to Promote
High Availability Instance of Passwordstate
to Primary Instance
This document and the information controlled therein is the property of Click Studios. It must not be reproduced in whole/part, or
otherwise disclosed, without prior consent in writing from Click Studios.
Click Studios
Table of Contents
1
OVERVIEW ................................................................................................................................... 3
2
INSTRUCTIONS WHEN USING SQL SERVER TRANSACTIONAL REPLICATION............................. 4
3
INSTRUCTIONS WHEN USING SQL SERVER HIGH AVAILABILITY GROUPS OR CLUSTERING ..... 5
Click Studios
1 Overview
In the event of a disaster, you may need to promote your High Availability Instance of Passwordstate to
your Primary Instance. This should only be done if you’re sure the Primary instance won’t be available for
some time, and need to be able to update data in Passwordstate.
There are two sets of instructions below, and they differ depending on how you have your SQL Server
configured in terms of data availability.
Note: This is only required if you are using Transactional SQL Replication
Click Studios
2 Instructions When Using SQL Server Transactional Replication
When using SQL Server transactional Replication to move data between database servers, you must follow
these instructions to promote the HA instance to be the primary:
1. Using SQL Server Management Studio connect to the database server hosting the High Availability
Instance of Passwordstate, with an account which has elevated privileges, and perform the
following:
a. Delete the SQL Server replication Subscription
b. For the SQL Account ‘passwordstate_user’ modify the permissions so it has ‘db_owner’
access to the Passwordstate database. If your database was created using version 7 of
Passwordstate, this will not be required
c. Open a new query window, and execute the following statement to reset the “Seeded
Indentity” value for each of the tables:
USE Passwordstate
EXEC sp_MSForEachTable '
IF OBJECTPROPERTY(object_id(''?''), ''TableHasIdentity'') = 1
DBCC CHECKIDENT (''?'', RESEED)'
2. Edit the file ‘c:\inetpub\passwordstate\web.config’ and change the value of key=’PassiveNode’ to
False
3. Restart the Passwordstate Windows Service
You can now open your browser and point it to the promoted Passwordstate web site.
Click Studios
3 Instructions When Using SQL Server High Availability Groups or
Clustering
When using SQL Server High Availability Groups, or clustering, where both installs of Passwordstate is able
to write to the database, then please follow these instructions to promote the HA instance to be the
primary:
1. Using SQL Server Management Studio, make sure the SQL Account ‘passwordstate_user’ has
‘db_owner’ access to the Passwordstate database. If your database was created using version 7 of
Passwordstate, this will not be required
2. Edit the file ‘c:\inetpub\passwordstate\web.config’ and change the value of key=’PassiveNode’ to
False
3. Restart the Passwordstate Windows Service
You can now open your browser and point it to the promoted Passwordstate web site.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement