AlwaysOn + Log shipping related blogs
Below blog post are all related to AlwaysOn and log shipping configured together,
-> Configuring Log Shipping with AlwaysOn
-> Error: The specified agent_id 1D58DD23-142C-498F-83AB-5077791B5781 or agent_type 1 do not form a valid pair for log shipping monitoring processing
-> JBSAG1, JBSAG2 and JBSAG3 are part of a failover cluster without shared storage. Alwayson Availability group is configured between JBSAG1, JBSAG2 and JBSAG3. JBSAG1 is the current primary, JBSAG2 is the synchronous secondary and JBSAG3 is Asynchronous secondary. The database(s) that is part of Always on Availability group has log shipping configured and its secondary is on JBSAG4.
-> The requirement is to remove log shipping from this setup.
-> On Asynchronous secondary JBSAG3. Right click on the log shipped database JBDB and click properties. Click on “Transaction Log Shipping” Tab.
-> Uncheck “Enable this as a primary database in a log shipping configuration” and click OK.
-> On Synchronous secondary JBSAG2. Follow the same steps as above and disable Log shipping,
-> On primary JBSAG1. Follow the same steps as above and disable Log shipping,
-> Once above actions are completed. Check SQL Server agent on JBSAG1, JBSAG2, JBSAG3, JBSAG4 and ensure log shipping related jobs are absent to make sure we have removed log shipping completely.
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.