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?

DR for Crystal Enterprise and Business Objects

Have to build DR solution and subj is a part of it.

Maybe some one has done it already… share the experience please.

Dr in my case will between 2 different data centers, replication is san 2 san so on other side I have a warm standby that does not see san disks and will become active if and only if the primary data center is down, windows domain is the same, ip addresses, names of the servers are different. How a cluster will behave is interesting as well (I mean CE is on cluster, not geo distributed cluster).

I have CE90. I’m talking to their tech support that seems to be outsourced, they didn’t really produce in 5 days anything more then a part of their own documentation in pdf format for CE version I do not use J…

So I’m wondering maybe somebody had to walk similar path already…

I see you were already involved on the previous thread that discussed some of the general considerations for such SAN replication (it was titled SAN Replication and is at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=465113&SiteID=1). Unfortunately I'm not aware of any specific considerations for CE.

double-take for high availability?

has anyone used double-take for high availability solution?
i am interested in product short comings and pitfalls when used in
conjunction with sql server.
thanks, gigelNo Microsoft support...big short-coming.
But I have seen the demos and heard good things about it from the SBS crowd.
:)
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Gigel" <gigel@.microsoft.com> wrote in message
news:eMB8816fIHA.4476@.TK2MSFTNGP06.phx.gbl...
> has anyone used double-take for high availability solution?
> i am interested in product short comings and pitfalls when used in
> conjunction with sql server.
> thanks, gigel
>|||Make sure you understand Service Principle Names (SPNs) and how to set them
manually.
In addition granting the right to set SPNs to the service account running
SQL server.
In some landscapes this AD level permission is not allowed to be set.
Finally if all you are going to do is log ship with it use log shipping.
Joe
"Gigel" wrote:
> has anyone used double-take for high availability solution?
> i am interested in product short comings and pitfalls when used in
> conjunction with sql server.
> thanks, gigel
>
>