DR strategies

We have a large database for production and need to come up with a solution
for Disaster Recovery.
Performing tasks such as a full backup and transaction backups, then
shipping over across country is okay during initial setup. But long term it
will not be possible to ship a full backup across. Transactional backups
shipping and restoring to a read-only instance would be okay; but, occasional
full backups of the production system would be needed for development teams.
So this would cause a problem for the DR system.
What are the different options either via a Microsoft solution or a 3rd party?Tom,
For MS solutions you might want to have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;822400.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:9D54441D-E203-4544-8F37-6EDAFE7DCC79@.microsoft.com...
> We have a large database for production and need to come up with a
solution
> for Disaster Recovery.
> Performing tasks such as a full backup and transaction backups, then
> shipping over across country is okay during initial setup. But long term
it
> will not be possible to ship a full backup across. Transactional backups
> shipping and restoring to a read-only instance would be okay; but,
occasional
> full backups of the production system would be needed for development
teams.
> So this would cause a problem for the DR system.
> What are the different options either via a Microsoft solution or a 3rd
party?