I would like to know what is the best practice in order to solve this upcoming problem. I will have configured my Always On environment from the source system with latest full backup. Once my secondary is synchronized from a point in time what is the best technique to sync up the remaining few transaction logs from a live Production system that does not have a period of inactivity? We cannot leave everything until to last minute since our cutover will be time sensitive (and we will have a some configuration after Always on has been set up). So to wait until the last minute will not work. In addition these are VLDBs (which makes it even more difficult). So do we do the one of the following: a) Break the AG and apply the last full logs and then setup again? b) Or is there a better technique to apply last few remaining logs(i.e. Log Shipping)? This entire effort is to upgrade the original environment to the new version of OS and SQL (Going from Always On Windows 2008R2 SQL 2012 to Windows 2016 SQL 2017). Our source system (current Always On Production environment) never stops (no period of inactivity). Your prompt assistance is greatly appreciated! Thank you.
Stephen Wexler