Skip to main content
Removed thanks
Source Link
Erik
  • 4.8k
  • 4
  • 28
  • 57

I have set up a 3-node, multi-subnet Always On Availability group in AWS, which seems to be working well. However, each node only has a single network adaptor with 3 IP addresses assigned to it (1 primary, 1 WSFC IP resource, 1 listener). Is this sufficient for high-availability, or do I need additional networks? I believe with a traditional cluster you would need multiple networks & adaptors to ensure there is no single point of failure. I'm not sure if this is the case in AWS, as I assume they have redundancy built-in at their end?

Thanks

I have set up a 3-node, multi-subnet Always On Availability group in AWS, which seems to be working well. However, each node only has a single network adaptor with 3 IP addresses assigned to it (1 primary, 1 WSFC IP resource, 1 listener). Is this sufficient for high-availability, or do I need additional networks? I believe with a traditional cluster you would need multiple networks & adaptors to ensure there is no single point of failure. I'm not sure if this is the case in AWS, as I assume they have redundancy built-in at their end?

Thanks

I have set up a 3-node, multi-subnet Always On Availability group in AWS, which seems to be working well. However, each node only has a single network adaptor with 3 IP addresses assigned to it (1 primary, 1 WSFC IP resource, 1 listener). Is this sufficient for high-availability, or do I need additional networks? I believe with a traditional cluster you would need multiple networks & adaptors to ensure there is no single point of failure. I'm not sure if this is the case in AWS, as I assume they have redundancy built-in at their end?

Correcting Always On spelling to make Allan Hirt a happy camper
Source Link
Brent Ozar
  • 43.2k
  • 47
  • 226
  • 382

AlwaysOn Always On Availability Groups Network Configuration in AWS

I have set up a 3-node, multi-subnet AlwaysOnAlways On Availability group in AWS, which seems to be working well. However, each node only has a single network adaptor with 3 IP addresses assigned to it (1 primary, 1 WSFC IP resource, 1 listener). Is this sufficient for high-availability, or do I need additional networks? I believe with a traditional cluster you would need multiple networks & adaptors to ensure there is no single point of failure. I'm not sure if this is the case in AWS, as I assume they have redundancy built-in at their end?

Thanks

AlwaysOn Availability Groups Network Configuration in AWS

I have set up a 3-node, multi-subnet AlwaysOn Availability group in AWS, which seems to be working well. However, each node only has a single network adaptor with 3 IP addresses assigned to it (1 primary, 1 WSFC IP resource, 1 listener). Is this sufficient for high-availability, or do I need additional networks? I believe with a traditional cluster you would need multiple networks & adaptors to ensure there is no single point of failure. I'm not sure if this is the case in AWS, as I assume they have redundancy built-in at their end?

Thanks

Always On Availability Groups Network Configuration in AWS

I have set up a 3-node, multi-subnet Always On Availability group in AWS, which seems to be working well. However, each node only has a single network adaptor with 3 IP addresses assigned to it (1 primary, 1 WSFC IP resource, 1 listener). Is this sufficient for high-availability, or do I need additional networks? I believe with a traditional cluster you would need multiple networks & adaptors to ensure there is no single point of failure. I'm not sure if this is the case in AWS, as I assume they have redundancy built-in at their end?

Thanks

Source Link
Matt
  • 53
  • 4

AlwaysOn Availability Groups Network Configuration in AWS

I have set up a 3-node, multi-subnet AlwaysOn Availability group in AWS, which seems to be working well. However, each node only has a single network adaptor with 3 IP addresses assigned to it (1 primary, 1 WSFC IP resource, 1 listener). Is this sufficient for high-availability, or do I need additional networks? I believe with a traditional cluster you would need multiple networks & adaptors to ensure there is no single point of failure. I'm not sure if this is the case in AWS, as I assume they have redundancy built-in at their end?

Thanks