Hi guys,
Im in the process of setting up and configuring a secondary server on our public network that will ensure uptime is maintained in the cause of an outage with our primary server. The server itself is an IBM 336 X series running Windows Server 2003 SP1.
Within our environment we currently have a primary server, also running Windows Server 2003 SP1, which supports all of the clients running the PWB browser within our public area. What Im wanting to know is....
Is it possible to configure the INI files in the case of server downtime, so that the clients can pull the desired configuration data from either server that is still online?
So far I have begun testing this with success. Problem is, the INI file points to only one IP address or server. That being, in our case, the primary domain controller.
CheckURLFile=\\192.168.65.254\pwb_profiles\pac\URL.txt
When this server goes offline I get the following message on screen at the client end, which of course is to be expected.
"Warning! File not found : \\192.168.65.254\pwb_profiles\pac\URL.txt"
Obviously I could set it to the following...
;CheckURLFile=\\192.168.65.254\pwb_profiles\pac\URL.txt
CheckURLFile=\\192.168.65.252\pwb_profiles\pac\URL.txt
...so that it then points to the secondary, but this may mean having to make numerous changes whilst both the primary server is down, as well as all of the public workstations. Id like to have this seamless to the clients so that if the server were to go offline, the clients would continue to function without any problems.
Is it possible to allow the INI file to choose from a number of servers or IP addresses? This would be ideal as this would then allow for server outages whilst not disrupting normal operations.
Thanks,
John
PWB redundancy
Moderators: Tyler, Scott, PWB v2 Moderator
-
- Observer
- Posts: 9
- Joined: Tue Feb 15, 2005 9:53 pm
- Location: Ipswich
PWB redundancy
What could possibly go wrong?
-
- Observer
- Posts: 9
- Joined: Tue Feb 15, 2005 9:53 pm
- Location: Ipswich
My apologies...
Of course the solution here is to copy the URL.txt file across to the client from BOTH servers via a batch file group policy, (obviously the one that's down will be ignored) and store the URL.txt file LOCALLY rather than on the servers.
Seems odd I tried this earlier and it didnt work. Oh well, appears to be working now.
John
Why is it that it comes to you just *AFTER* you press submit on this damned forum!!!
Of course the solution here is to copy the URL.txt file across to the client from BOTH servers via a batch file group policy, (obviously the one that's down will be ignored) and store the URL.txt file LOCALLY rather than on the servers.
Seems odd I tried this earlier and it didnt work. Oh well, appears to be working now.
John
Why is it that it comes to you just *AFTER* you press submit on this damned forum!!!
What could possibly go wrong?