Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Last time I did it, I had my own ASN and spoke BGP to both ISPs announcing my own /24 (which you can get from either ISP, or maybe ARIN). You could go down this route, but its a fair bit of setup. And a random Cable/DSL ISP probably won't set this up with you. This does eliminate all the points of failure and makes the switchover completely transparent.</p> <p>You can also lower the TTLs on the DNS records to 5 minutes or so. This won't be instant switch over, but 5 minutes may be fast enough.</p> <p>Otherwise, you certainly can use the remote server in a colo, but then of course that becomes the single point of failure. You have a couple of choices of how to redirect the traffic:</p> <ul> <li>GRE/etc. tunnel: You run two tunnels from the colo box, one to each connection at your office. Tunnel all relevant traffic both ways and you wind up with a few IPs from the colo at your office. You can then run a routing protocol (even something simple, like RIP) to make this automatically fail over, or even use both ISPs simultaneously for additional bandwidth. This can be implemented fairly easily on Linux boxes or Cisco routers. I assume Juniper can to, but I've never used them. Failover is transparent (e.g., will not break VPN connections). Beware of MTU issues. If your office connections do not do reverse path filtering (or can make an exception for you), you do not have to tunnel outgoing traffic back to the colo.</li> <li>NAT. May or may not work with whatever protocols you're running, but you can set up 1:1 static NAT at the colo to redirect the traffic. Easily done for common TCP protocols, and maybe your VPN too. Doable on pretty much anything. Failover is not transparent; existing connections will time out. Can also use both connections for additional bandwidth on a per-connection basis. Traffic must be tunneled back to colo.</li> <li>Obvious third answer: Move the services to the colo. Has the advantage of protecting from power outages, too.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POEnsuring Network Redundancy: How to switch from default ISP to backup ISP without downtime
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USderobert
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEnsuring Network Redundancy: How to switch from default ISP to backup ISP without downtime
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload