> Hi! Hi Tobias, Thanx for your reply!
> Wijngaarden van, J (Jeroen) schrieb: > > I know I already posted a question today, but I think it’s better to > > post a message per subject. So, here is an other one.. ;-) > > Good idea - one question, one mail. > > > I have setup one (Windows 2003) server with the OTC server and > manager > > installed. This works well, but if the server goes down non of the > thin > > clients can be used.. It’s a single point of failure. > > Yes. > > > What is the best way to backup the server? Can I just backup the > > complete installation-folder? And can I just restore that directory > in > > case of an emergency? > > You usually don't need the entire installation folder. All > configuration > information is located in the apacheds-store under server\default\data. > > It is usually enough if you save this. Ok, good to know! > > I was thinking the following, please let me know if this is going to > work: > > > > > > > > - Setup 2 identical Windows 2003 servers (hostname, ip- > adsress, > > etc is offcourse different) > > Ok. > > > - Install on both servers the OTC server and manager > > > > - Server 1 will be the production server, and server 2 the > > backup server (failover server) > > > > - Make a simple script that copies the complete installation > > folder from server 1 to server 2 > > > > - In case server 1 goes down, I only have to change the > option > > in the DHCP-scope so the clients search for server 2 and not server 1 > > No need to do something like that at all if clients and servers are > in the same network segment. OTC comes with a DHCP proxy that listens > to client requests and supplies the boot information. Your regular > DHCP server just needs to supply IP, GW, DNS... Well, we use a Windows DHCP server and I had to add options 066 (Boot Server Host Name) and 076 (Bootfile Name) to get OTC to work! - 066: ip-addres of the server where the OTC server is installed - 076: pxelinux.0 <- found this on the internet.. I first tried it without these options, but the pc's didn't boot from the network. Then I tried it with only option 066, but that didn't work too. Ow, and if we are talking about DHCP and stuff.. When I first boot a PC/thin client I can't see him in "PXE clients" in the manager.. I have to add the thin client manually in "ThinClients" in the manager. I have to enter a name and MAC-address, then I have to reboot the client before it works. > > Is this going to work? Or is there a better way to get a failover > server?? > > Well, what I would do: > - install both servers, > - activate the OTC service on the primary, deactivate on the secondary, > - regularly sync apacheds-store from primary to secondary, ( > ... normal operation... > > Now, in case of disaster: > - activate OTC service on backup server, > - run OTC updates (if needed) > - boot clients... > > If the primary does come up again, either sync back (if config changes > make that seem a good idea) or just let it run and shut down the backup > service when the clients are down. That sounds like a good idea! Thanx Jeroen > -- > Bye, > Tobias Abt > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org [email protected] https://lists.sourceforge.net/lists/listinfo/openthinclient-user
