Configuring a Warm Redundant IS2000 Server
Install the same version of IS2000 on both the Primary and Secondary servers. Both servers should be configured to run IS2000 independently of each other and should have their own database. We recommend using SQL Authentication or Mixed Mode Authentication for the SQL Server installation.
Backup the Primary Server:
Run the Backup Utility on the Primary Server and set the Backup location to be on a drive that the Secondary Server will have access to. The Backup Utility will backup the entire IS2000 folder and the IS2000 SQL Server database to the specified drive in the IS2000_Backup folder. To automate scheduled backups click on the “Schedule Backups/Restore” command to create batch files that can be added to the Task Scheduler.
Share the entire drive where the IS2000_Backup folder is located on the Primary Server, so that the Secondary Server has access to this.
Restore Backup from Primary Server to Secondary Server:
Once a backup has been created on the Primary Server, map a drive letter on the Secondary Server to point to the drive on the Primary Server with the IS2000_Backup folder. Run the Backup Utility from the Secondary Server, and configure the Restore From drive to be the newly mapped drive letter pointing to the drive that has the Primary Server’s IS2000_Backup folder.
Before testing the Restore command, make sure IS2000 is not running on the Secondary Server. A restore function will not work when IS2000 is running on the Secondary Server. IS2000 can however continue to run on the Primary Server. Test the Restore command, and if successful, execute the “Schedule Backups/Restore” command and follow the instructions to automate the Restore task.
Making the Secondary Server the Primary
If the Primary Server fails, then remove the Restore task from the Task Scheduler (Control Panel > Scheduled Tasks) on the Secondary server, so that it doesn’t continue to restore files from the inactive Primary server.
Launch IS2000 from the Secondary Server. From Hardware Manager change the ComputerName property of the driver from the Primary Server’s computer name to the Secondary Server’s computer name and start the necessary drivers.
Configuring Clients to look to the Secondary Server
To configure the clients to look at the Secondary Server, you must first create a ShareName for the Data folder on the IS2000 Secondary Server and give the Users who will access it Full Control. Run the Configuration Utility from each of the clients and set their RemotePath property to the new Data folder located on the IS2000 Secondary Server. For SQL Server sites set the Hide SQL Logon property to false, so the client will be prompted to enter the new SQL logon information when they start IS2000.
Additional Notes –
Redundant Warm Server:
This utilizes the Data Replicator Application and monitors the Primary Server in the event if it goes offline. If the Primary Server goes offline, cannot be pinged and/or the database cannot be read, the Backup Server becomes the Primary Server and begins polling the hardware. Clients then need to be manually re-directed to the new Primary Server.
Maintains a duplicate copy of the server’s database tables. Multiple destinations can be configured to allow remote viewing of copied versions of the master database tables. Replication can be setup to occur periodically during scheduled intervals.
The redundant server app runs on the back-up server since it’s monitoring the primary. This is a warm redundancy solution since a simple manual process is required on the back-up server to act as the primary.