In order to be protected in future in the case of a breakdown you have got two possibilities how to recreate the high availability again. Both cases are based on the configuration described under disaster.

 

 

Method 1: The original backup server becomes a productive server

 

After the original server is ready for use again, an Enterprise server is installed and activated first. Afterwards you create a slave database on that machine. The master database on the other server persists. The original productive server becomes the backup server now and the other way around. That means the configuration conforms to the original configuration, however with exchanged servers.

 

 

Method 2: Recreation of the original configuration

 

In order to recreate the actual original state the following work steps are necessary:

 

- On the original productive server an Enterprise server is installed and activated

- At the original productive server a slave database is created

- The network logon profile file is changed in a way that it now refers to the newly created slave database at the original productive server

- The clients are restarted and now work on the original productive server where they are connected with the slave database at first

- Make sure that no more clients are connected with the server

- Carry out a manual synchronization

- The original backup server is stopped

- The slave database is converted to the master database. This can happen while the clients are connected with it

- At the original backup server the database account is deleted

- A new slave database is created on the original backup server

 

 

Method 3: Recreation of the original configuration by copying the database

 

- Both servers are stopped

- The database file of the backup server is copied to the productive server

- The database is linked at the productive server

- If desired, now the firewall at the productive server is configured

- The network logon profile file (optional) is changed in a way that it now points out to the newly linked master database at the original productive server

-The clients are started again and now work on the original productive server again

- The database account is deleted at the original backup server

- A new slave database is created at the original backup server

 

This method is not possible if the database has been created with hardware bonding!

 

 

Method 4: Recreation of the original configuration with a backup

 

It has been worked on the backup server and accrodant backups have been created after the case of disaster occured you can recreate high availability again with this method:

 

- The original backup server is stopped

- On the original productive server an Enterprise server is installed and activated

- Create a new master database and enter the backup file which you want to restore in the database assistant

- After the database has been created the data is automatically recreated in that database

- The database server has to be started again in order that the new database is available

- The network logon profile file (optional) is changed in a way that it now points out to the newly linked master database at the original productive server

-The clients are started again and now work on the original productive server again

- The database account is deleted at the original backup server

- A new slave database is created at the original backup server