June 3, 2015 at 5:52 am
Hello all,
Ive read a few docs and i have some doubts about the implementation i ll make.
I will setup a FCI between ServerA and ServerB. So my databases will be running on server A or on ServerB. they will be replicated using AllwaysON to ServerC.
Because ill use a diferent vlan for AllwaysON replication iam having some doubts on how can i set the endpoints...
For example.
I ll have the following ips configured for AllwaysON replication on Server A, Server B and Server C 10.10.240.1/10.10.240.2/10.10.240.3
Database teste will be running on serverA. the endpoint configured will be 10.10.240.1 but when database fails over to Server B (using FCI) the ip configured there will be 10.10.240.2... so AO replication will stop working.
I tough on associating a virtual ip to the AllwaysON cluster resource but Microsoft doesn't recommend to alter AllwaysON cluster resource.
Can anyone give an input on this? How can i implement this configuration? Any document where this is explained...?
Regards,
June 3, 2015 at 5:57 am
Arestas (6/3/2015)
I tough on associating a virtual ip to the AllwaysON cluster resource
That's exactly how you'll need to do this, a shared IP address will be needed. FCIs have a huge impact on the complexity and management of AO groups, this is just one more to add to the list
Arestas (6/3/2015)
but Microsoft doesn't recommend to alter AllwaysON cluster resource.,
No, they don't recommend you modify the possible owners list on the AlwaysOn group cluster resource, this is managed dynamically by the cluster service during an AO group failover
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 3, 2015 at 6:14 am
Know any documentation about this?
Regards,
Arestas
June 3, 2015 at 7:11 am
Arestas (6/3/2015)
Know any documentation about this?Regards,
Arestas
In response to the modification of resources this link states
MSDN
Do not use the Failover Cluster Manager to manipulate availability groups:For example:
?Do not change any availability group properties, such as the possible owners.
?Do not use the Failover Cluster Manager to fail over availability groups. You must use Transact-SQL or SQL Server Management Studio.
Here are recommendations for when using database mirroring or AlwaysOn groups
MSDN
Recommendations for Computers That Host Availability Replicas (Windows System)--------------------------------------------------------------------------------
•Comparable systems: For a given availability group, all the availability replicas should run on comparable systems that can handle identical workloads.
•Dedicated network adapters: For best performance, use a dedicated network adapter (network interface card) for AlwaysOn Availability Groups.
•Sufficient disk space: Every computer on which a server instance hosts an availability replica must possess sufficient disk space for all the databases in the availability group. Keep in mind that as primary databases grow, their corresponding secondary databases grow the same amount.
This link details specifying server network addresses when using mirroring or AO groups
When creating your endpoint for the replica which is an FCI you would use
CREATE ENDPOINT hadr_endPoint
STATE = STARTED
AS TCP (LISTENER_PORT = 5022, LISTENER_IP = TheSharedIPAddress)
FOR DATABASE_MIRRORING
(AUTHENTICATION = WINDOWS NEGOTIATE,
ENCRYPTION = REQUIRED ALGORITHM AES,
ROLE = ALL);
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 3, 2015 at 8:21 am
Tanks again for your precious Help.
Will give a feedback as soon as i implement it.
Regards,
Arestas
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply