I have a 2 node AG in a non-prod environment and we are looking to shut down the secondary node for cost savings, leaving this with just the primary node. I have some questions based on this process, and my research hasn't answered all of them. Could somehow fill in the blanks here on what is possible / best to do?
is it possible to keep just a single node AG? if so, is there a reason to actually do it? As I understand it, there is no benefit to keeping the AG at all if you remove all the secondary nodes, as it then becomes just a stand alone instance. If i kept the AG, then the transaction logs of the DB's will not truncate, as its trying to find a place to send the logs to, correct?
The AG Listener - Moot point if we remove the AG altogether, but if i kept the AG as a single node, the listener would not function correct? My app team will need to make code changes to use something else since listener name is coded to be used, and they would like to avoid that if possible. i don't think this is possible, but wanted to check.
Secondary node down the road - we may spin up the secondary node on demand down the road, so is there an issue with leaving the cluster resources in place after we remove the AG, or does the removal delete the cluster objects? I think they stay, but I have not found an answer on this.
- SSRS question - we are in a scale-out deployment, do I need to remove the secondary from the scale out? I would prefer to leave it since we may need to recreate the secondary down the road. I would need to update connection strings, etc to use the primary node and not the listener.
My assumed workflow is like this based on what I found
- Connect to primary replica
- Delete the entire AG (this removes AG settings from all DB's, primary and secondary), and throws secondary DB's into restoring state, while leaving primary DB's accessible and completely separate.
- log backups will continue on primary like normal and log truncation will happen as expected.