Passwordstate Documentation

High Availability Considerations ​

If you are licensed for the High Availability module, this will most likely mean you have two production Passwordstate websites replicating data in real time using some form of SQL Replication.

The more advanced and modern replication technologies such as Always On or Basic Availability Groups can handle database schema changes whilst still having replication enabled. But if you are using Microsoft SQL Transactional Replication this does not process schema changes automatically.

In this scenario you will need to delete your transactional Publisher and Subscriber before you upgrade your primary Passwordstate server, and re-establish replication before you attempt to upgrade your second Passwordstate web server.

  • Occasionally an upgrade will perform a re-encryption of data in your database. This process is completely automated, but best practice is to pause or disable SQL replication whilst upgrading your primary server. You can resume replication once the primary server is completed. Check Change Log notes before each build to determine if re-encryption will occur. You will see a note in the Change Log saying “the database upgrade screen may take some time to complete”
  • Not all Passwordstate releases have database schema changes, which means you may not have to delete your Transactional Replication as part of your upgrade process. See section Upgrade Dependency Matrix for information on which builds will make changes to the schema.
  • If you are using Transactional Replication, and you see a notification on your database upgrade screen that replication still appears to exist when performing your upgrade, run the following SQL commands to clean up left over replication tables and data:
SQL
USE Master
EXEC sp_removedbreplication passwordstate

If using Transactional Replication, and you need to re-establish replication after the primary database has been upgraded, please re-follow these instructions - Transactional Replication

If you are upgrading from a build prior to 9968, please also refer to the following KB Article regarding a possible MultiSubnetFailover setting in your web.config file - Upgrade Considerations Pre Build 9968