March 22, 2019 at 4:30 am
Hi Team,
We have some SQL Servers which are configured with Always on on Single node clusters.
As part of the testing we made the AlwaysOn Group offline. Now we are not able to bring it online.
So we have dropped AlwaysOn and recreated it.
Will there be any issue if AG on single node goes offline to bring online.
Could you please let me know is there any alternative to bring the Always on back online instead of dropping and recreating it.
Thank You.
Regards,
Raghavender Chavva
March 22, 2019 at 7:21 am
Hi,
how do you realize a AOAG on a single node?
Do you use named instances?
How did you take your AOAG offline?
"Suspend Data Movement?
Are there some errors ?
Kind regards,
Andreas
March 22, 2019 at 7:29 am
andreas.kreuzberg - Friday, March 22, 2019 7:21 AMHi,
how do you realize a AOAG on a single node?
Do you use named instances?
How did you take your AOAG offline?
"Suspend Data Movement?Are there some errors ?
Kind regards,
Andreas
Our Design is like Always On on 1 Node, 1+1, 3 Node clusters.
on all the instances we have Default instances only.
Used "
" query to offline the AG.
Thank You.
Regards,
Raghavender Chavva
March 22, 2019 at 8:05 am
Hm,
are there some entries in the ERRORLOG, or a Screenshot from the error, if you try to bring the AOAG online again?
Did you try the t-sql on both nodes?
Kind regards,
Andreas
March 25, 2019 at 1:07 am
Raghavender Chavva - Friday, March 22, 2019 4:30 AMHi Team,We have some SQL Servers which are configured with Always on on Single node clusters.
As part of the testing we made the AlwaysOn Group offline. Now we are not able to bring it online.
So we have dropped AlwaysOn and recreated it.Will there be any issue if AG on single node goes offline to bring online.
Could you please let me know is there any alternative to bring the Always on back online instead of dropping and recreating it.
Why did you take the AG offline? Taking an AG offline is a task used as part of cross-cluster migration, its not a suitable analog for failure testing of the cluster or the AG.
From Docs:
After an availability group goes offline, its databases become unavailable to clients, and you cannot bring the availability group back online. Therefore, use the OFFLINE option only during a cross-cluster migration of Always On availability groups, when migrating availability group resources to a new WSFC cluster.
A single-node Availability Group is difficult to test a failure against because there is no expected reaction to validate. It cannot failover or take any kind of remedial action, so in reality its no different to testing by turning the SQL Server off.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply