January 29, 2015 at 12:05 pm
Sorry for the confusion...
Just to summarize what was needed:
An instance which will fail over to another node as a cluster and as new databases will constantly be added in the instance and therefore be failed over automatically along with the instance to node 2.
should I need Level 5 details FCIs and a walk through of the setup as its been done in PART 3?
January 29, 2015 at 1:06 pm
I just had a change in what we would need to accomplish and not even sure if possible. Where can I find the other docs you list as there's been a change in plans and some additional requirements for my deployment.
Level 7 will detail combining FCIs as a replica in an AlwaysOn group.
January 29, 2015 at 1:36 pm
January 29, 2015 at 4:44 pm
Perry Whittle (1/29/2015)
level 7 is not published yet but you can find detail on combining an FCI into an AlwaysOn group starting at this link[/url]
OK thank you.
Basically what I need to do is replicate an instance between 2 primary nodes residing in different locations?
Would the this AG with FCI be the best solution ?
January 30, 2015 at 5:21 am
if you're replicating between 2 nodes they both cant be primary. One will be primary one will be secondary, it seems you are after either database mirroring or AlwaysOn Availability groups.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 30, 2015 at 7:43 am
Perry Whittle (1/30/2015)
if you're replicating between 2 nodes they both cant be primary. One will be primary one will be secondary, it seems you are after either database mirroring or AlwaysOn Availability groups.
I think this is what we want.
Site A in FCI ( node 1 active primary and node 2 passive failover )
Site B has node 1 ( replicating from site A node 1 ) and a FCI on another node
is this possible with a constantly growing databases ?
or should we just have 1 primary and 3 passive failovers in an FCI ?
February 10, 2015 at 8:25 am
Perry Whittle (1/21/2015)
johnnyrmtl (1/21/2015)
Thanks for the reply...and sorry for the confusion.I need to propose a 2 server clustering / failover solution with SQL 2012 and it seems that the log shipping feature will not suit us since we have instances where databases will be created at random through an application.
My question is if the ALWAYSON solution is indeed what I should look into given this scenario?
An AlwaysOn availability group will not automatically add new databases to the group as they're created if that's what you're asking
Hello Perry...
I have set up this 2 nodes in FCI and it works well. In getting back to one of my questions on how I can also replicate the primary databases onto another location outside of the site through mirroring , the only problem as you say is that new databases must be manually configured with a mirroring process, would there be a way to script this ?
much appreciated
February 10, 2015 at 10:02 am
johnnyrmtl (2/10/2015)
Perry Whittle (1/21/2015)
johnnyrmtl (1/21/2015)
Thanks for the reply...and sorry for the confusion.I need to propose a 2 server clustering / failover solution with SQL 2012 and it seems that the log shipping feature will not suit us since we have instances where databases will be created at random through an application.
My question is if the ALWAYSON solution is indeed what I should look into given this scenario?
An AlwaysOn availability group will not automatically add new databases to the group as they're created if that's what you're asking
Hello Perry...
I have set up this 2 nodes in FCI and it works well. In getting back to one of my questions on how I can also replicate the primary databases onto another location outside of the site through mirroring , the only problem as you say is that new databases must be manually configured with a mirroring process, would there be a way to script this ?
much appreciated
Just extend the Windows Server failover cluster and add a new replica to house another secondary database
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 10, 2015 at 10:33 am
I think one issue will be that there will be separate SAN's between the site 1 and site 2
So over and above the FCI on site 1 between 2 nodes , I will need to automatically replicate all databases and any new database automatically from site 1 instance ( primary )
over to a site 2 instance
i hope i'm clear 😉
February 10, 2015 at 10:39 am
the whole point with AlwaysOn availability groups is you don't need shared storage. Put a 3rd node in the cluster on the remote site and put a standalone instance of sql server on it then join it to the AlwaysOn availability group
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 10, 2015 at 10:44 am
Perry Whittle (2/10/2015)
the whole point with AlwaysOn availability groups is you don't need shared storage. Put a 3rd node in the cluster on the remote site and put a standalone instance of sql server on it then join it to the AlwaysOn availability group
Ok so just to recap...
The shared storage is only between the FCI on site 1 ( nodes A and B )
Now you are saying I can also replicate the node A instance databases with AO AG over to Site 2,
What happens when new DB's are added to node A , does AO availaibility groups also automatically ship them as I read it does not ?
February 10, 2015 at 10:45 am
johnnyrmtl (2/10/2015)
Perry Whittle (2/10/2015)
the whole point with AlwaysOn availability groups is you don't need shared storage. Put a 3rd node in the cluster on the remote site and put a standalone instance of sql server on it then join it to the AlwaysOn availability groupOk so just to recap...
The shared storage is only between the FCI on site 1 ( nodes A and B )
Now you are saying I can also replicate the node A instance databases with AO AG over to Site 2,
What happens when new DB's are added to node A , does AO availaibility groups also automatically ship them as I read it does not ?
You have to actually add a new database to an AlwaysOn availability group
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 10, 2015 at 10:53 am
Perry Whittle (2/10/2015)
johnnyrmtl (2/10/2015)
Perry Whittle (2/10/2015)
the whole point with AlwaysOn availability groups is you don't need shared storage. Put a 3rd node in the cluster on the remote site and put a standalone instance of sql server on it then join it to the AlwaysOn availability groupOk so just to recap...
The shared storage is only between the FCI on site 1 ( nodes A and B )
Now you are saying I can also replicate the node A instance databases with AO AG over to Site 2,
What happens when new DB's are added to node A , does AO availaibility groups also automatically ship them as I read it does not ?
You have to actually add a new database to an AlwaysOn availability group
That's my show stopper as new databases are constantly created by the application :unsure:
would there be another solution to replicating to another site over and above the cluster on site 1
February 10, 2015 at 11:16 am
I'm not sure if I understand you correctly but if your apps constantly creating new databases, you have option to put it in your existing AG or create new AG. Did I answer your question?
February 10, 2015 at 11:26 am
CooLDBA (2/10/2015)
I'm not sure if I understand you correctly but if your apps constantly creating new databases, you have option to put it in your existing AG or create new AG. Did I answer your question?
But this would be a manual task to put in an AG 🙁
Is there a way to automate ?
Viewing 15 posts - 31 through 45 (of 50 total)
You must be logged in to reply to this topic. Login to reply