Log shipping to DR env

The scenario is a production W2k3 domain running a SQL 2005 cluster and
remotely located DR domain that is a clone of the production domain but is
isolated from a network standpoint. Is there a way to do log shipping - or
some other form of so that the DR dbs can be kept in fairly close (every 24
hours) synch with the production dbs? This is being done in the same sceario
but with SQL 2000 by opening of necessary firewall ports and natting between
the machines and I want to know if its doable in 2005, my DBA claims log
shipping machines must be part of the same domain in Sql 2005.
My goal is to to keep the production domains and DR domains as stand-alone
clones but keep sql in synch. The dba is proposing that the DR machines be
part of the production domain in order to keep the dbs in synch.
Thanks
Thanks for the reply and information.
"Greg Linwood" wrote:

> Just realised I should've pointed out that "out of the box" Log Shipping
> does require domain permissions, but you need to use the standard version
> really as it doesn't offer much extra functionality than a few scripts can
> achieve as it essentially just builds SQLAgent jobs in the background which
> you can easily script yourself..
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> Benchmark your query performance
> http://www.SQLBenchmarkPro.com
> "Greg Linwood" <g_linwood@.hotmail.com> wrote in message
> news:uhLQ8D01HHA.3760@.TK2MSFTNGP03.phx.gbl...
>
>

Log shipping to DR env

The scenario is a production W2k3 domain running a SQL 2005 cluster and
remotely located DR domain that is a clone of the production domain but is
isolated from a network standpoint. Is there a way to do log shipping - or
some other form of so that the DR dbs can be kept in fairly close (every 24
hours) synch with the production dbs? This is being done in the same sceario
but with SQL 2000 by opening of necessary firewall ports and natting between
the machines and I want to know if its doable in 2005, my DBA claims log
shipping machines must be part of the same domain in Sql 2005.
My goal is to to keep the production domains and DR domains as stand-alone
clones but keep sql in synch. The dba is proposing that the DR machines be
part of the production domain in order to keep the dbs in synch.
ThanksYour DBA is wrong - Log Shipping has nothing to do with domains. As long as
you can automate the scripting involved to backup the TLog on the production
server, copy / ftp it to the DR server & restore it (with no recovery) on
the DR server, you will have the foundations of Log Shipping in place.
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
Benchmark your query performance
http://www.SQLBenchmarkPro.com
"pdx" <pdx@.discussions.microsoft.com> wrote in message
news:3EDE4AB5-9793-43A5-B056-1C11D3436A9D@.microsoft.com...
> The scenario is a production W2k3 domain running a SQL 2005 cluster and
> remotely located DR domain that is a clone of the production domain but is
> isolated from a network standpoint. Is there a way to do log shipping - or
> some other form of so that the DR dbs can be kept in fairly close (every
> 24
> hours) synch with the production dbs? This is being done in the same
> sceario
> but with SQL 2000 by opening of necessary firewall ports and natting
> between
> the machines and I want to know if its doable in 2005, my DBA claims log
> shipping machines must be part of the same domain in Sql 2005.
> My goal is to to keep the production domains and DR domains as stand-alone
> clones but keep sql in synch. The dba is proposing that the DR machines be
> part of the production domain in order to keep the dbs in synch.
> Thanks|||Just realised I should've pointed out that "out of the box" Log Shipping
does require domain permissions, but you need to use the standard version
really as it doesn't offer much extra functionality than a few scripts can
achieve as it essentially just builds SQLAgent jobs in the background which
you can easily script yourself..
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
Benchmark your query performance
http://www.SQLBenchmarkPro.com
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:uhLQ8D01HHA.3760@.TK2MSFTNGP03.phx.gbl...
> Your DBA is wrong - Log Shipping has nothing to do with domains. As long
> as you can automate the scripting involved to backup the TLog on the
> production server, copy / ftp it to the DR server & restore it (with no
> recovery) on the DR server, you will have the foundations of Log Shipping
> in place.
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> Benchmark your query performance
> http://www.SQLBenchmarkPro.com
> "pdx" <pdx@.discussions.microsoft.com> wrote in message
> news:3EDE4AB5-9793-43A5-B056-1C11D3436A9D@.microsoft.com...
>|||Thanks for the reply and information.
"Greg Linwood" wrote:

> Just realised I should've pointed out that "out of the box" Log Shipping
> does require domain permissions, but you need to use the standard version
> really as it doesn't offer much extra functionality than a few scripts can
> achieve as it essentially just builds SQLAgent jobs in the background whic
h
> you can easily script yourself..
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> Benchmark your query performance
> http://www.SQLBenchmarkPro.com
> "Greg Linwood" <g_linwood@.hotmail.com> wrote in message
> news:uhLQ8D01HHA.3760@.TK2MSFTNGP03.phx.gbl...
>
>

Log shipping to DR env

The scenario is a production W2k3 domain running a SQL 2005 cluster and
remotely located DR domain that is a clone of the production domain but is
isolated from a network standpoint. Is there a way to do log shipping - or
some other form of so that the DR dbs can be kept in fairly close (every 24
hours) synch with the production dbs? This is being done in the same sceario
but with SQL 2000 by opening of necessary firewall ports and natting between
the machines and I want to know if its doable in 2005, my DBA claims log
shipping machines must be part of the same domain in Sql 2005.
My goal is to to keep the production domains and DR domains as stand-alone
clones but keep sql in synch. The dba is proposing that the DR machines be
part of the production domain in order to keep the dbs in synch.
ThanksYour DBA is wrong - Log Shipping has nothing to do with domains. As long as
you can automate the scripting involved to backup the TLog on the production
server, copy / ftp it to the DR server & restore it (with no recovery) on
the DR server, you will have the foundations of Log Shipping in place.
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
Benchmark your query performance
http://www.SQLBenchmarkPro.com
"pdx" <pdx@.discussions.microsoft.com> wrote in message
news:3EDE4AB5-9793-43A5-B056-1C11D3436A9D@.microsoft.com...
> The scenario is a production W2k3 domain running a SQL 2005 cluster and
> remotely located DR domain that is a clone of the production domain but is
> isolated from a network standpoint. Is there a way to do log shipping - or
> some other form of so that the DR dbs can be kept in fairly close (every
> 24
> hours) synch with the production dbs? This is being done in the same
> sceario
> but with SQL 2000 by opening of necessary firewall ports and natting
> between
> the machines and I want to know if its doable in 2005, my DBA claims log
> shipping machines must be part of the same domain in Sql 2005.
> My goal is to to keep the production domains and DR domains as stand-alone
> clones but keep sql in synch. The dba is proposing that the DR machines be
> part of the production domain in order to keep the dbs in synch.
> Thanks|||Just realised I should've pointed out that "out of the box" Log Shipping
does require domain permissions, but you need to use the standard version
really as it doesn't offer much extra functionality than a few scripts can
achieve as it essentially just builds SQLAgent jobs in the background which
you can easily script yourself..
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
Benchmark your query performance
http://www.SQLBenchmarkPro.com
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:uhLQ8D01HHA.3760@.TK2MSFTNGP03.phx.gbl...
> Your DBA is wrong - Log Shipping has nothing to do with domains. As long
> as you can automate the scripting involved to backup the TLog on the
> production server, copy / ftp it to the DR server & restore it (with no
> recovery) on the DR server, you will have the foundations of Log Shipping
> in place.
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> Benchmark your query performance
> http://www.SQLBenchmarkPro.com
> "pdx" <pdx@.discussions.microsoft.com> wrote in message
> news:3EDE4AB5-9793-43A5-B056-1C11D3436A9D@.microsoft.com...
>> The scenario is a production W2k3 domain running a SQL 2005 cluster and
>> remotely located DR domain that is a clone of the production domain but
>> is
>> isolated from a network standpoint. Is there a way to do log shipping -
>> or
>> some other form of so that the DR dbs can be kept in fairly close (every
>> 24
>> hours) synch with the production dbs? This is being done in the same
>> sceario
>> but with SQL 2000 by opening of necessary firewall ports and natting
>> between
>> the machines and I want to know if its doable in 2005, my DBA claims log
>> shipping machines must be part of the same domain in Sql 2005.
>> My goal is to to keep the production domains and DR domains as
>> stand-alone
>> clones but keep sql in synch. The dba is proposing that the DR machines
>> be
>> part of the production domain in order to keep the dbs in synch.
>> Thanks
>|||Thanks for the reply and information.
"Greg Linwood" wrote:
> Just realised I should've pointed out that "out of the box" Log Shipping
> does require domain permissions, but you need to use the standard version
> really as it doesn't offer much extra functionality than a few scripts can
> achieve as it essentially just builds SQLAgent jobs in the background which
> you can easily script yourself..
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> Benchmark your query performance
> http://www.SQLBenchmarkPro.com
> "Greg Linwood" <g_linwood@.hotmail.com> wrote in message
> news:uhLQ8D01HHA.3760@.TK2MSFTNGP03.phx.gbl...
> > Your DBA is wrong - Log Shipping has nothing to do with domains. As long
> > as you can automate the scripting involved to backup the TLog on the
> > production server, copy / ftp it to the DR server & restore it (with no
> > recovery) on the DR server, you will have the foundations of Log Shipping
> > in place.
> >
> > Regards,
> > Greg Linwood
> > SQL Server MVP
> > http://blogs.sqlserver.org.au/blogs/greg_linwood
> > Benchmark your query performance
> > http://www.SQLBenchmarkPro.com
> >
> > "pdx" <pdx@.discussions.microsoft.com> wrote in message
> > news:3EDE4AB5-9793-43A5-B056-1C11D3436A9D@.microsoft.com...
> >> The scenario is a production W2k3 domain running a SQL 2005 cluster and
> >> remotely located DR domain that is a clone of the production domain but
> >> is
> >> isolated from a network standpoint. Is there a way to do log shipping -
> >> or
> >> some other form of so that the DR dbs can be kept in fairly close (every
> >> 24
> >> hours) synch with the production dbs? This is being done in the same
> >> sceario
> >> but with SQL 2000 by opening of necessary firewall ports and natting
> >> between
> >> the machines and I want to know if its doable in 2005, my DBA claims log
> >> shipping machines must be part of the same domain in Sql 2005.
> >> My goal is to to keep the production domains and DR domains as
> >> stand-alone
> >> clones but keep sql in synch. The dba is proposing that the DR machines
> >> be
> >> part of the production domain in order to keep the dbs in synch.
> >>
> >> Thanks
> >
> >
>
>

Log Shipping or something else?

Here's my scenario.
I have two sql servers, one located in another state, but connected via a
continuous vpn so it really looks like it's always on my network.
I only make changes to the sql server on the remote server, but I want the
local server to be as close as possible to having exactly the same data on
it, for primarily queries, etc.
The local server could be read only I guess, but only if no changes would
need to be made to the queries (MS query mostly).
Would log shipping work' Would something else work better'
Also the remote database is call xxx but my local db will be called yyy, but
it will essentially have the same tables in it.
This is because I have hundreds of queries that reference yyy even though
database xxx is our new database that we're using.
Thanks
Alan SawyerHi,
Do you need the local server for reporting or something ?
With Log shipping your local server is not available for reporting or as a
matter of fact for nothing as it requires an exclusive lock on the database
to restore the log and it will forcibly remove the users or the log shipping
job would fail.
I would say a transactional replication would be a better option. You might
wanna explore more on this.
Also refer to this
[url]http://www.sqlservercentral.com/columnists/pibison/logshippingvsreplication.asp[/u
rl]
Hopefully the above gives you a better idea of what you might do. Do let us
know if you face any problem in setting up the same. I am sure some one will
be able to help you.
Abhishek
"asawyer@.chambersREMOVEbelt.com" wrote:

> Here's my scenario.
> I have two sql servers, one located in another state, but connected via a
> continuous vpn so it really looks like it's always on my network.
> I only make changes to the sql server on the remote server, but I want the
> local server to be as close as possible to having exactly the same data on
> it, for primarily queries, etc.
> The local server could be read only I guess, but only if no changes would
> need to be made to the queries (MS query mostly).
> Would log shipping work' Would something else work better'
>
> Also the remote database is call xxx but my local db will be called yyy, b
ut
> it will essentially have the same tables in it.
> This is because I have hundreds of queries that reference yyy even though
> database xxx is our new database that we're using.
> Thanks
> Alan Sawyer
>|||I definetly need access to the local server, as I want to qurey from it.
I'll take a look at what you suggest.
Alan

Log Shipping and C;ustering

Can you Implement Log Shipping between geographically dispersed clusters.
The main aim is to provide DR for 2 clusters to a single cluster located in
a seperate Datacenter.
Any input will be appreciated.
Yes. The two technologies are not mutually exclusive. Geographic
separation is not an issue with log shipping. You may find it easier to
implement a third party or home grown log shipping solution. The
implementation provided by Microsoft is good, but it may not offer all the
options you need.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Adrian56" <Adrian56@.discussions.microsoft.com> wrote in message
news:936B33BA-7C0B-4BF5-9C7F-C3DE24424809@.microsoft.com...
> Can you Implement Log Shipping between geographically dispersed clusters.
> The main aim is to provide DR for 2 clusters to a single cluster located
in
> a seperate Datacenter.
> Any input will be appreciated.