| View previous topic :: View next topic |
| Author |
Message |
mwaters
Joined: 23 May 2013
Posts: 29
|
 Posted: Thu Oct 02, 2014 12:41 pm Post subject: Redundant Servers |
 |
|
| Is there any way to run two servers in a high availability context so that we would always have one server available should one be down? Aside from just building another server and moving serial cables when we wanted to work on one of the servers.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Thu Oct 02, 2014 12:44 pm Post subject: |
|
|
| What are your output methods? From the context of your message, it sounds like you're using a direct serial connection to a TAP terminal? |
|
| Back to top |
|
mwaters
Joined: 23 May 2013
Posts: 29
|
| Posted: Thu Oct 02, 2014 12:47 pm Post subject: |
|
|
| We use both TAP as well as TCP/IP connections. Recipients are either Cell phones, regular pagers or special circuit boards in remote locations over VPN connections.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Thu Oct 02, 2014 12:48 pm Post subject: |
|
|
| The reason I ask is that you can configure a backup server and configure PageGate's Synchronization feature, which will have the primary server periodically update the secondary server on a timescale you decide. However, there isn't an automatic way to have one server fail over to the other server, you would still need to switch the secondary for the primary if the primary ever goes down. Also, if you're using a serial connection to a TAP terminal, you would still need to move the cable to the alternate server to keep using that output method. |
|
| Back to top |
|
mwaters
Joined: 23 May 2013
Posts: 29
|
| Posted: Thu Oct 02, 2014 12:54 pm Post subject: |
|
|
Hmm, that /may/ work. I am trying to shorten the amount of time that the server would be unavailable, such as when a reboot is necessary because of security updates.
Although, our dispatchers also have the local GUI client installed on their workstations as an alternate way to send pages. Normally they send via our CAD dispatch software which connects to PageGate through a serial connection. Would I need a second client installed for them to use while the first server was out of commission?
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Thu Oct 02, 2014 1:36 pm Post subject: |
|
|
| Not necessarily. The PageGate Client references the PageGate Server's database either by mapped network drive or UNC path. If the primary server ever goes down, you can assign the machine name and/or IP address to the secondary server and, assuming the PageGate Database directory has been shared out with the same share name as the primary, the client would just connect to the secondary server since it would be mimicking the primary. |
|
| Back to top |
|
OzCom
Joined: 22 Oct 2003
Posts: 1122
Location: US
|
|
| Back to top |
|
killlereye
Joined: 10 Feb 2015
Posts: 1
Location: Pakistan
|
| Posted: Tue Feb 10, 2015 7:21 am Post subject: |
|
|
| Normally they send via our CAD dispatch software which connects to PageGate through a serial connection. Would I need a second client installed for them to use while the first server was out of commission?
_________________
GuL
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Tue Feb 10, 2015 9:12 am Post subject: |
|
|
| It depends on how you configure things. If the secondary server is going to be assigned the primary server's IP and/or machine name if it's ever 'made' the primary, there isn't anything you'll need to configure in the Client. If it's going to retain its own unique IP/machine name, the only thing you'll need to do is give the Client the UNC path to the secondary server's database because when the primary server goes down, the path that the client references will be invalid. |
|
| Back to top |
|
|
