Add Secondary Node to existing WSFC Cluster
I need to add new server in my existing WSFC cluster server setup. I need few details on following :
1. I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
2. Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
sql-server-2012 availability-groups sql-server-2016 clustering
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I need to add new server in my existing WSFC cluster server setup. I need few details on following :
1. I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
2. Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
sql-server-2012 availability-groups sql-server-2016 clustering
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I need to add new server in my existing WSFC cluster server setup. I need few details on following :
1. I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
2. Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
sql-server-2012 availability-groups sql-server-2016 clustering
I need to add new server in my existing WSFC cluster server setup. I need few details on following :
1. I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
2. Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
sql-server-2012 availability-groups sql-server-2016 clustering
sql-server-2012 availability-groups sql-server-2016 clustering
asked Apr 18 '17 at 8:36
MySQL DBAMySQL DBA
367312
367312
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
- I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
Yes, you can... however, it will not be readable as a secondary and if you ever fail over to it, the SQL Server 2012 instance will no longer synchronize and your databases will be upgraded. Unless you're planning on doing an upgrade, I wouldn't mix and match versions - it gets you nothing.
- Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
Yes, but do see above for restrictions and limitations. I would only do this if you're starting a rolling upgrade scenario and plan to finish it fairly quickly. Do not leave multiple versions in the same topology for any appreciable amount of time.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f171267%2fadd-secondary-node-to-existing-wsfc-cluster%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
- I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
Yes, you can... however, it will not be readable as a secondary and if you ever fail over to it, the SQL Server 2012 instance will no longer synchronize and your databases will be upgraded. Unless you're planning on doing an upgrade, I wouldn't mix and match versions - it gets you nothing.
- Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
Yes, but do see above for restrictions and limitations. I would only do this if you're starting a rolling upgrade scenario and plan to finish it fairly quickly. Do not leave multiple versions in the same topology for any appreciable amount of time.
add a comment |
- I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
Yes, you can... however, it will not be readable as a secondary and if you ever fail over to it, the SQL Server 2012 instance will no longer synchronize and your databases will be upgraded. Unless you're planning on doing an upgrade, I wouldn't mix and match versions - it gets you nothing.
- Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
Yes, but do see above for restrictions and limitations. I would only do this if you're starting a rolling upgrade scenario and plan to finish it fairly quickly. Do not leave multiple versions in the same topology for any appreciable amount of time.
add a comment |
- I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
Yes, you can... however, it will not be readable as a secondary and if you ever fail over to it, the SQL Server 2012 instance will no longer synchronize and your databases will be upgraded. Unless you're planning on doing an upgrade, I wouldn't mix and match versions - it gets you nothing.
- Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
Yes, but do see above for restrictions and limitations. I would only do this if you're starting a rolling upgrade scenario and plan to finish it fairly quickly. Do not leave multiple versions in the same topology for any appreciable amount of time.
- I have Windows Server Failover Cluster setup on 2012 R2 with SQL Server 2012, Can I have my new server with Windows Server 2012 R2 with SQL Server 2016?
Yes, you can... however, it will not be readable as a secondary and if you ever fail over to it, the SQL Server 2012 instance will no longer synchronize and your databases will be upgraded. Unless you're planning on doing an upgrade, I wouldn't mix and match versions - it gets you nothing.
- Can I add it on my existing AlwaysOn Availability Group, which is configured with SQL Server 2012?
Yes, but do see above for restrictions and limitations. I would only do this if you're starting a rolling upgrade scenario and plan to finish it fairly quickly. Do not leave multiple versions in the same topology for any appreciable amount of time.
answered Apr 18 '17 at 11:56
Sean GallardySean Gallardy
15.5k22447
15.5k22447
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f171267%2fadd-secondary-node-to-existing-wsfc-cluster%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown