Hi,
I understand your concern about the potential issues that might arise during the migration of your SQL standalone to a SQL Always On Availability Group for your SCCM site.
Here’s some information that might help:
- During the Migration: If an error occurs during the migration process, it could potentially disrupt the connection between your primary site and the standalone SQL server. This is because the migration process involves changing the SQL configuration settings to use the listener name of the AOAG.
- Post Migration Failure: If the migration fails and the connection is broken, the primary site might not function as expected due to the lack of a database connection.
- Recovery Options: In case of such a failure, one of the recovery options is indeed to perform a site recovery.
- Precautions: Before starting the migration, make sure to take a full backup of your site database. This backup can be crucial for recovery in case of any issues.
I hope this information helps! If you have any more questions, feel free to ask. 😊