Password Safe Enterprise Server

Case of disaster

Case of disaster

Previous topic Next topic  

Case of disaster

Previous topic Next topic  

If the productive server should drop out for longer you can make the slave database available in a very short time.

 

Conversion of the slave database to a master database

In the first step you convert a slave database to a master database here. To do so it is enough to do a click with your right mouse button on the slave database at the server in the database overview and afterwards a click on convert to master. The conversion only takes a few seconds.

 

slave_to_master_1

 

The conversion has to be confirmed again in a second step:

 

slave_to_master_2

 

Making available the new master database

After the slave database has been converted to a master database, open the network logon profile file for editing. This can be done at the server as well as at on of the  clients. To do so click on extras -> configure network logon. Via the folder symbol you can now open the profile file:

 

open_nlc

 

Via a double click the file is opened for editing:

 

open_nlc_2

 

Now change the access data of the database here:

 

slave_assistent

 

Now follow the assistant and save your profile file. It is suggested not to change the name of the profile file. In order to conclude the users only have to restart their client and then they have direct access to their data.