Loghipping to multiple servers SQL 2008

I have existing log shipping setup up and running with one secondary server.What if I need to add one more secondary to the setup without any downtime on the existing logshipping setup.?
My company is to perform this without downtime on the existing logshipping. How can this be achieved?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The key to this is that you already have the primary fully configured.  Prep your additional secondary in the same way as the first one, go in to the log shipping settings on the primary, and add the secondary from there
venk_rAuthor Commented:
Thanks for the reply.
My question is how will Log sequence be in synch between these 2 secondaries.How will the logs catch up with the new secondary that has been added?
Ilya RubinshteynCommented:
@venk_r, during the initial synchronization, a snapshot will be pushed down from the publisher to the additional subscriber. Once that completes, the rest of the changes will be replicated to subscriber. Afterwards, it will depend on the schedule that you set up.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

venk_rAuthor Commented:
Are you talking about replication?The question I asked was about Log shipping.
The snapshot @irnmamont talks about is actually a full database backup then sets an initial point from which the server will restore the transaction logs for the Log shipping

If you have a look at http://www.mssqltips.com/sqlservertip/2301/step-by-step-sql-server-log-shipping/ - the section "Initialize Secondary Database tab" will give you the steps you need
venk_rAuthor Commented:
If there is already a primary - secondary configured up and running logshipping for say about 1 year and then we add  a additional secondary today then how will the new secondary sync up on fly from primary?
At any point we need both the secondaries in synch with production.
In order to be up to date the new secondary doesn't actually need to apply all the shipped logs for the entire year, just from the last full backup that is applied to it.

When you go through the steps to add a secondary it'll handle this for you.

Once it is up and running the lag between the new or old secondary with the primary is entirely down to the schedules you have set up.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
venk_rAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.