Just as step 10 and 14 add an IP and dependency for the listener client access point, from the network in the remote region, you need to add a secondary IP for the Cluster Name from the network in the remote region. If this is not done and the primary region fails, the Cluster Name will not come online in the secondary region, potentially creating problems with managing the Cluster when you attempt to bring it online.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@richardspitz Thanks for the comment. We are actively looking into it and will update you soon.
@richardspitz Do you want those statements to be added to the document?
@MikeRayMSFT please add your comments
@jakaruna-MSFT Sure!
cc: @MicahMcKittrick-MSFT
@MikeRayMSFT Please consider the users request and update the doc as needed.
@MashaMSFT
@richardspitz , thank you so much for reaching out and helping improve our documentation! You are correct, the IP should be added to the cluster resource as well. I have created an internal work item to track this work (1657328). I'm going to close out this Git Issue for the time being but please comment should you need anything further from us in the meantime.
Thanks!
Masha from the SQL Docs team
Hi @richardspitz , thanks again for helping improve our documentation! I am reaching out to let you know that a change has been processed to add steps for adding the IP address to the cluster as well. This change should be live later today :)
Please feel free to comment should you need anything further.
Thanks again for reaching out and hope you have a wonderful rest of your day!
Masha from the SQL Docs team