Wednesday, March 7, 2012

Log Shipping and Reporting Servers

My scenario:
One SQL Server (DB4) in Oklahoma, and it's warm standby (DB3) in Oklahoma
(via Log shipping).
One SQL Server in St. Louis (DB1) , which is a distant warm standby (via Log
shipping) over our WAN.
I want a reporting server in St. Louis. I don't necessary want to set up
another log shipping operation across the WAN with the high amount of
activity that the log shipping is dealing with now.. I would like to grab
the databases off of the warm standby in St. Louis and restore/etc to
another server in St. Louis. I don't want to increase traffic over our WAN
when the data is already on here on this server. The log shipping sent to
the St. Louis server happens every 5 minutes.
Is their a best way to accomplish this? I realized I cannot backup up the
current database because they're in Warm Standby mode. Is is possible to
take them out of this mode, back them up, and put them back in that mode for
the Log Shipping to resume?
TIA,
EricEric
You can not do anything with your warm standby in St
Louis, what you can do is use the transaction log backups
that the log shipping is already copying to the server in
St Louis.
You would need to copy the full database from Oklahoma and
restore it to set up the second warm standby, you could
then use the transaction logs that were already being
coppied.
You would need to then set up your own version of log
shipping using the logs you already have.
Hope this helps.
Regards
John

No comments:

Post a Comment