Tag Info

Hot answers tagged

4

ELBs are engineered to not be a single point of failure - a "single" ELB will have multiple IP addresses, which correspond to multiple ELB instances behind the scenes (the technology they're running is not public information, but there have been very occasional ELB outages due to EBS issues which probably indicates they're EC2 instances under the hood, maybe ...


1

This answer is specific to those who are experiencing this same type of error after copying this example configuration from ISC's website. There is a subtle error caused by the encoding of the dashes on that page. In vim, if you place your cursor over the first dash of max-response-default and press ga while in command mode, you will see a unicode value of ...


1

You're going to have to setup a common storage that both can access at the same time, even when one goes down. I think you can point users' home directory to a network path, in which case you can setup a third system just for broadcasting the storage or a NAS. Otherwise, if they needs to see the storage as local, then you can look into setting up a SAN or ...


1

It basically works - but it seems to be impossible to use the loadbalancer target within a proxy block - hence, http://localhost has to be used. <Proxy balancer://Group1> ProxySet failonstatus=503 BalancerMember ajp://destination1 route=core1 ping=10 BalancerMember ajp://destination4 route=core1 ping=10 status=+H </Proxy> <Proxy ...


1

You need to check the binding order of the networks if you want to be specific about which interface(s) is the preferred for Cluster communication, since it will use whichever it can. To view the networks, their metric values, and if they were automatically or manually configured, run the clustering PowerShell cmdlet: PS > Get-ClusterNetwork ...


1

One of my clients depends heavily on OpenVPN over a multi-site setup, and we take two approaches: The main OpenVPN service is provided by two machines, in an HA-failover pair using heartbeat/CRM. If one goes down, the other takes over the shared IP addresses, and service continues. Existing sessions will be dropped, but the clients usually reauthenticate ...


1

Windows Failover Clustering (which is what Hyper-V uses for clustering) requires shared storage of some sort. Further to Massimo's answer, and if I'm reading this page right, I don't think you can use exclusively SMB shares for a failover cluster. You'd still need some shared disks (SAS, iSCSI, FC) for the cluster portion, but you can store the Hyper-V VM ...



Only top voted, non community-wiki answers of a minimum length are eligible