Migration with upgrade
There may be situations where the upgrade involves a migration of data from old servers to new servers at the same time as the upgrade. A migration with upgrade is recommended where:
If you have a lot of customizations
If you are upgrading your hardware at the same time
If you are upgrading from a non-supported version of the product
Your upgrade is going to be complicated
A migration with upgrade ensures the current production version of Bravura Security Fabric remains available as long as possible during the change of versions.
When performing a migration with upgrade, you must install a second instance that will become the new version. Then you can manually copy or migrate configuration files and data from the databases to this new version instance.
It is possible to perform a migration with upgrade on a single server. The only limitations are that the second instance – the new version – must have a unique instance name and all the port numbers of the services for the second instance must be changed from their default values. Thus, you will need to modify any configuration parameters that contain the instance name or port numbers. This includes both the Bravura Security Fabric server, targets with local agents, or transparent password synchronization triggers, and clients with Bravura Security Fabric components. It is recommended that you use two servers to perform all manual migrations to avoid these complications.
Migrations with upgrade, including those that are migrating to a new instance at the same time, involve many complex components that require an in-depth knowledge of Bravura Security Fabric . It is highly recommended you contact support@bravurasecurity.com for assistance.