August 7, 2025 at 1:32 pm
Hello,
I have a large database about 8 GB. It is in an AG.
I have three replicas (Replica1, Replica2 and Replica3)
Replica1 is Primary and healthy
Replica2 is Secondary and heathy
Replica3 is Secondary and not healthy.
I need get Replica3 healthy again. My thought was to wait until after the normal backup run which goes about three hours.
1. stop log backup job.
2. Take one last log backup
3. Copy database backup to Replica3 and the last log backup
4. Restore with norecovery
5. Then on the Primary remove the database from the Ag
6. Check the Secondaries that the database is removed from the Ag.
7. Then move it back in the AG and let the reseeding will start on the two replicas.
However, I am seeing some articles that say log shipping is the wait to prep for a large database to bring it into an AG.
I can start a log shipping between Replica1 and Replica3 then pickup at step 5 instead of bringing the database backup and log file and then allow automatic seeding.
Question. Can the primary database be in an AG and also start log shipping to Replica3? I don't want to impact production at all, if possible until I need to remove the database from the Ag and put it back.
Any thoughts or experiences would be helpful.
Thanks.
Things will work out. Get back up, change some parameters and recode.
August 8, 2025 at 2:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
August 11, 2025 at 10:58 am
August 13, 2025 at 2:09 pm
Well, I don't think SQL server will allow that, else the whole idea of having a cluster like combination of Log shipping and mirroring internals , will be defeated. Best is to try though.
August 14, 2025 at 2:33 pm
Thanks! It was a thought. We decided to remove the DR for now. I will rearchitect it correctly and move it back into the node after doing the due diligence planning.
Things will work out. Get back up, change some parameters and recode.
August 19, 2025 at 10:19 am
Hello,
I have a large database about 8 GB. It is in an AG.
I have three replicas (Replica1, Replica2 and Replica3)
Replica1 is Primary and healthy
Replica2 is Secondary and heathy
Replica3 is Secondary and not healthy.
I need get Replica3 healthy again. My thought was to wait until after the normal backup run which goes about three hours.
1. stop log backup job.
2. Take one last log backup
3. Copy database backup to Replica3 and the last log backup
4. Restore with norecovery
5. Then on the Primary remove the database from the Ag
6. Check the Secondaries that the database is removed from the Ag.
7. Then move it back in the AG and let the reseeding will start on the two replicas.
However, I am seeing some articles that say log shipping is the wait to prep for a large database to bring it into an AG.
I can start a log shipping between Replica1 and Replica3 then pickup at step 5 instead of bringing the database backup and log file and then allow automatic seeding.
Question. Can the primary database be in an AG and also start log shipping to Replica3? I don't want to impact production at all, if possible until I need to remove the database from the Ag and put it back.
Any thoughts or experiences would be helpful.
Thanks.
You can take the database out of your normal backup plan and then configure log shipping. This plan should work fine as it is just like you are doing a normal backup and restore in initiating the replica.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply