Migrating files and registry
Generally, migrating files and registries between instances is simple. In the case of files, you copy them from one system to another. In the registry case, you export from one server and import from the other. There are a few things to keep in mind:
If the hardware, operating system, file system, or installed software (which includes the Bravura Security software and web server) is configured differently between the instances, then be certain the content of the files or registry export is valid for the server you are copying it to. This can mean checking hard-coded drive letters, file paths, and file names in your files and registry imports.
The regularly scheduled file replication task only pushes new or changed files from the primary server to the replicas and proxies. As such, when copying files, they must be copied to the primary server. Files can optionally be copied to the replica servers if you don’t want to wait for or force the scheduled task.
As with handling files, the registry replication only pushes changes from the primary to the other servers. As such, all registry changes must at least be made to the primary server and optionally to the replicas and proxies.
If the file or registry entry being changed or added is related to a running service, that service must be restarted to recognize the change.
For more details on the capability and limits of the file and registry replication service (such as maintaining white lists and black lists that apply limits on what should and should not be replicated), see: