Planning, Implementing and Managing SafeBoot Enterprise Systems

Transcription

1 Off s a f e b o o t h o t b a c k u p d e s i g n

2 Overview Having a single physical server for your SafeBoot enterprise is obviously risky, and even if regular backups are taken delays can occur in user recovery or updates during a server failure. Therefore we would advise in all cases that steps be taken to expedite recovery from a failed or dead server. The following is an example how this could be achieved. This backup method uses a Main server hosting the SafeBoot Object Directory (ODB) and a second server which can take over in the case of failure of the Main server. Edisonbaan MN Nieuwegein The Netherlands T. +31 (0) F. +31 (0) E. [email protected] I.

3 Hot Backup Databases By replicating the SafeBoot Object Directory to a 2 nd physical server you can alleviate down time in the event of a server failure to a minimum. Control Break International offers an optional tool to efficiently replicate the directory. This tool SFDBBack (SafeBoot DataBase Backup Tool) can be obtained from your SafeBoot representative. SFDBBack is optimized to follow the change log of a SafeBoot 4 Object Directory. SFDBBack can used to make regular backups of the ODB, giving further recovery options in the event of a disaster. By following the change log Backups can be made over very short intervals keeping the spare directory synchronised with its master. SFDBBack allows you to create a very resilient system using two physical computers both hosting SafeBoot Servers, one hosting the master ODB and the 2 nd having a Hot Backup which is kept offline until needed. In the event of the master server failing, the SafeBoot Server service on the 2 nd backup box can be started to serve clients. You can then rebuild or replace the problem machine and create a new master. To keep integrity of the SafeBoot Enterprise, only ONE database can be in use at any one time. If two directories become live at once you run the risk of loosing data when the failover process begins. The following procedure documents how to set up a reliable failover process. Creating a Master / Hot Backup system Create a SafeBoot Directory, with 2 SafeBoot servers to service client requests. In this example only one server service is running at any one time (normally Server A). On Server A (the master), install the main SafeBoot Directory. Install SafeBoot Administration software on machine A Create and configure your Master Directory. Create 2 SafeBoot Servers, one for this machine s IP or DNS name and one for the 2 nd backup server (using that machine s different IP or DNS name). Logout On Server B (the backup), create a directory (to be used as the Hot Backup). On machine B also install the SafeBoot Administration software choosing the same options Create an object directory (this is temporary) Logout and browse inside the SBAdmin directory within the installation directory with explorer. Remove the SBDATA directory from B, and all its contents, and replace with a copy of SBDATA folder from Server A. On Server A (the master), setup the SFDBBack tool Setup SFDBBack; add a new event to sync/copy all changed files from Server A to the Server B SBDATA directory. Now you can start the SafeBoot Server service on Server A as normal. Make an install Set and choose Servers A and B as the servers for your clients talk to. Install on a test machine.

4 choose Hot Backup and log in. On Server B (the backup) create the server entry for Hot Backup server mode Go to Start Menu, SafeBoot Administration, SafeBoot Server, the SafeBoot Logon box appears. Go to Advanced, and highlight the entry that has the sbfiledb.dll address. Click Properties, change the description to HOT BACKUP Server or similar. You will only start this SafeBoot Server service if the main server A is down. Now your system is ready to use. Normal operation (Figure 1) During normal operation the SafeBoot Server service on A (the master) will authenticate incoming client connections before sending them to the database also on Server A. Hot-Backup Operation (Figure 2) Transferring control to the backup server involves ensuring the master server is offline, and then starting the backup server to take over communications. Your clients will try to authenticate with Server A as normal and fail to connect of course, next they try Server B and will sync as normal from their point of view. However they will be syncing with the Hot Backup copy of the database. Transferring back to Normal Operation To transfer back to normal mode operation, you need to stop ALL servers, copy the Object Directory from the Backup server to the Master, and then restart the Master server. To do this: log off any admin first from B stop all SafeBoot Server services copy the SBDATA folder and contents from Server B back to A, replacing any SBDATA folder there. You could set up an event in SFDBBack to be run manually which copies data from B to A to do this. bring up the SafeBoot Server service on A Clients who find B is no longer available will now authenticate with A again when they sync. If Server A fails: ensure that Server A service will not start itself (by disconnecting the server from the network, or powering it off) on machine B (the backup) start the SafeBoot Server

5 Figure 1

6 Figure 2