Hi MVPs,
I have a situation where I have a DB server that is in a VLAN that is only
accessable from a server in the DMZ, and I have a site operated by a service
provider that will be offering a DR facility. I want to switch on log
shipping, but how can I get the data to the service provider data centre via
the DMZ.
What options do I have?
I'd be very grateful for your help.
Mac
Dude, I'm not an MVP, but I play one at work... anyway, your options here are
extremely limited. If you can't get direct access to the server to ship the
files, then your only choice is to roll your own. You can either write a
process to ship the logs to an ftp and then another process to pull them down
and restore them, or you can create a common share and drop the logs there
and pick them up on the other side. Either way, you're gonna have to do some
coding. And it's a pain. It's best to get them to punch a hole if you can.
"Mac" wrote:
> Hi MVPs,
> I have a situation where I have a DB server that is in a VLAN that is only
> accessable from a server in the DMZ, and I have a site operated by a service
> provider that will be offering a DR facility. I want to switch on log
> shipping, but how can I get the data to the service provider data centre via
> the DMZ.
> What options do I have?
> I'd be very grateful for your help.
> Mac
Showing posts with label via. Show all posts
Showing posts with label via. Show all posts
Friday, March 30, 2012
Log Shipping v Database Mirroring (again!)
Hi
I'm looking at replicating our primary SQL server to a secondary offsite server (linked via 100Mb so effectively LAN speed). What are people's preference when deciding on a solution?
On the surface mirroring looks much better but having dug a little I've found it is recommended only 10 databases are mirrored per instance. That said, I've found a post from someone who is upto 58 databases mirrored. Are there similar limitations with log shipping?
Does anyone have any experience of mirroring and is using it in prefence to log shipping?
Our current recovery strategy is the classic restore the SQL dump from tape onto a rebuilt server so either method will be a vast improvement. None of our databases are mission critical that they need upto the second replication. 15 minute replication would be fine leading me to think that log shipping may be better given the possible limitations of mirroring
For recovery, I was considering amending the DNS records of the Database servers. Does anyone see any issues with this approach? I understand there is a automatic failure function if using mirror but this may require the application to be coded correctly?
Thanks in advance for any feedback
Robert
I also was greatly disappointed to learn that MS recommends only 10 mirrors per server instance. Considering that I have around 1300 databases in a federated model spread out over 12 servers, it threw a major monkey-wrench into our plans. So, now we are considering ranking clients on a scale and putting top level clients on DB Mirrors and 2nd level clients on log shipping. Demo db's for the various inernal departments get nothing (no soup for you!!).
Currently, I am still trying to figure out how many mirrors I can actually do on a server. I have 19 mirrors running on a 64 bit server with a 64 bit mirror with no noted performance degradation. Thread consumption did double (approximately) when I added the mirrors, but I'm still way below what's available (average of 100 threads consumed out of an available 512). However, I have to keep in mind that this is the slow part of the year for our clients and we have to leave enough threads avaialble to handle the increased load that will come at the end of the year.
I've suggested offering DB miroring as an upgrade that clients can purchase due to the increased hardware requirements. Log shipping = free, mirroring = $$$.
Yes, handling of the automatic failover does require some specific coding. The SQL Native Client and ADO.Net 2.0 have the ability to specify a failover partner in the connection string, and it automatically tries the failover partner if the principal server is not available. Earlier versions of ADO or other db access interfaces that do not support failover partners must be coded to manually try a second connection string if the first fails (which generally invovles a long timeout period). Another option is to build a middle tier that handles the transport of client db access so that the client isn't even aware of which server it is using.
If indeed you do not need the data to be up to the minute, then perhaps log shipping is the answer for you.
|||Yes, I'm rapidly coming to the conclusion that 15 minute log shipping will be sufficient for our needs.
The majority of our database requirements are from 3rd party software. There are often very slow to update - many don't support SQL 2005 yet anyway!
|||Robert,
I would be interested in any real world information you would like to share about mirroring. It would be good fodder for future articles at SSWUG.ORG as well as support to my company for implementing mirroring. They are concerned about the newness of this feature.
Cheers,
Ben
btaylor@.sswug.org
|||As was stated above, we currently recommend no more than ten databases be configured for mirroring on a single instance. This is not a fixed limit, but due to resource consumption is a good general guideline. Some customers are perfectly happy with larger number of mirrored databases, however your mileage may vary depending on hardware, application, etc. Mirroring was not designed for large numbers of database on the same instance. If you are facing this scenario, MSCS is a more natural choice (with optional addition of storage level replication for disaster recovery).
Regards,
Matt Hollingsworth
Microsoft SQL Server
Log Shipping v Database Mirroring (again!)
Hi
I'm looking at replicating our primary SQL server to a secondary offsite server (linked via 100Mb so effectively LAN speed). What are people's preference when deciding on a solution?
On the surface mirroring looks much better but having dug a little I've found it is recommended only 10 databases are mirrored per instance. That said, I've found a post from someone who is upto 58 databases mirrored. Are there similar limitations with log shipping?
Does anyone have any experience of mirroring and is using it in prefence to log shipping?
Our current recovery strategy is the classic restore the SQL dump from tape onto a rebuilt server so either method will be a vast improvement. None of our databases are mission critical that they need upto the second replication. 15 minute replication would be fine leading me to think that log shipping may be better given the possible limitations of mirroring
For recovery, I was considering amending the DNS records of the Database servers. Does anyone see any issues with this approach? I understand there is a automatic failure function if using mirror but this may require the application to be coded correctly?
Thanks in advance for any feedback
Robert
I also was greatly disappointed to learn that MS recommends only 10 mirrors per server instance. Considering that I have around 1300 databases in a federated model spread out over 12 servers, it threw a major monkey-wrench into our plans. So, now we are considering ranking clients on a scale and putting top level clients on DB Mirrors and 2nd level clients on log shipping. Demo db's for the various inernal departments get nothing (no soup for you!!).
Currently, I am still trying to figure out how many mirrors I can actually do on a server. I have 19 mirrors running on a 64 bit server with a 64 bit mirror with no noted performance degradation. Thread consumption did double (approximately) when I added the mirrors, but I'm still way below what's available (average of 100 threads consumed out of an available 512). However, I have to keep in mind that this is the slow part of the year for our clients and we have to leave enough threads avaialble to handle the increased load that will come at the end of the year.
I've suggested offering DB miroring as an upgrade that clients can purchase due to the increased hardware requirements. Log shipping = free, mirroring = $$$.
Yes, handling of the automatic failover does require some specific coding. The SQL Native Client and ADO.Net 2.0 have the ability to specify a failover partner in the connection string, and it automatically tries the failover partner if the principal server is not available. Earlier versions of ADO or other db access interfaces that do not support failover partners must be coded to manually try a second connection string if the first fails (which generally invovles a long timeout period). Another option is to build a middle tier that handles the transport of client db access so that the client isn't even aware of which server it is using.
If indeed you do not need the data to be up to the minute, then perhaps log shipping is the answer for you.
|||Yes, I'm rapidly coming to the conclusion that 15 minute log shipping will be sufficient for our needs.
The majority of our database requirements are from 3rd party software. There are often very slow to update - many don't support SQL 2005 yet anyway!
|||Robert,
I would be interested in any real world information you would like to share about mirroring. It would be good fodder for future articles at SSWUG.ORG as well as support to my company for implementing mirroring. They are concerned about the newness of this feature.
Cheers,
Ben
btaylor@.sswug.org
|||As was stated above, we currently recommend no more than ten databases be configured for mirroring on a single instance. This is not a fixed limit, but due to resource consumption is a good general guideline. Some customers are perfectly happy with larger number of mirrored databases, however your mileage may vary depending on hardware, application, etc. Mirroring was not designed for large numbers of database on the same instance. If you are facing this scenario, MSCS is a more natural choice (with optional addition of storage level replication for disaster recovery).
Regards,
Matt Hollingsworth
Microsoft SQL Server
Wednesday, March 28, 2012
log shipping set up via scripts instead of GUI
Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!
Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!
|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!
|||yes.
this is exactly what we are doing here.
Here is an example script to apply logs to the standby.
Cheers,
Greg Jackson
PDX, Oregon
begin 666 RETORE LOG SCRIPT FOR ALL TRAN BAKS IN A DIR.SQL
M__XO`"H`*@.`J`"H`*@.`J`" `3P!B`&H`90!C`'0`.@.`@.`" `4P!T`&\`<@.!E
M`&0`( !0`'(`;P!C`&4`9 !U`'(`90`@.`'4`<P!P`%\`4@.!A`'0`:0!N`&<`
M<P!?`%0`<@.!A`&X`<P!A`&,`= !I`&\`;@.!,`&\`9P!?`%(`90!S`'0`;P!R
M`&4`( `@.`" `( !3`&,`<@.!I`' `= `@.`$0`80!T`&4`.@.`@.`# `-0`O`#$`
M,@.`O`#(`, `P`# `( `X`#H`-0`W`#H`,@.`U`" `4 !-`" `*@.`J`"H`*@.`J
M`"H`+P`-``H`+P`J`"H`*@.`J`"H`*@.`@.`$\`8@.!J`&4`8P!T`#H`( `@.`%,`
M= !O`'(`90!D`" `4 !R`&\`8P!E`&0`=0!R`&4`( !U`',`< !?`%(`80!T
M`&D`;@.!G`',`7P!4`'(`80!N`',`80!C`'0`:0!O`&X`3 !O`&<`7P!2`&4`
M<P!T`&\`<@.!E`" `( `J`"H`*@.`J`"H`*@.`O``T`"@.`O`"H`"0!7`'(`:0!T
M`'0`90!N`" `0@.!Y`#H`( !!`&P`90!X`" `5P!E`'(`9P!E`&P`90!S``T`
M"@.`J`" `"0!#`'(`90!A`'0`90!D`#H`( `@.`# `-0`O`# `,0`O`#(`, `P
M`#$`#0`*`"H`"0!.`&\`= !E`',`.@.`-``H`*@.`-``H`*@.`@.`" `( `@.`" `
M( `@.`" `( !!`&P`= !E`'(`90!D`" `0@.!Y`#H`( `@.`$$`; !E`'@.`( !7
M`&4`<@.!G`&4`; !E`',`#0`*`"H`( `@.`" `( `@.`" `( `@.`" `1 !A`'0`
M90`Z`" `( `P`#8`+P`P`#$`+P`R`# `, `Q``T`"@.`J`" `( `@.`" `( `@.
M`" `( `@.`$X`;P!T`&4`<P`Z`" `( !#`&\`;0!M`&4`;@.!T`&4`9 `-``H`
M*@.`-``H`*@.`@.`" `( `@.`" `( `@.`" `( !!`&P`= !E`'(`90!D`" `0@.!Y
M`#H`( `-``H`*@.`@.`" `( `@.`" `( `@.`" `( !$`&$`= !E`#H`#0`*`"H`
M( `@.`" `( `@.`" `( `@.`" `3@.!O`'0`90!S`#H`( `@.`$D`1@.`@.`%D`3P!5
M`" `00!,`%0`10!2`" `5 !(`$D`4P`@.`% `4@.!/`$,`10!$`%4`4@.!%`"P`
M( !#`$\`4 !9`" `00!.`$0`( !0`$$`4P!4`$4`( !4`$@.`10`@.`"<`00!,
M`%0`10!2`$4`1 `@.`$(`60`G``T`"@.`J`" `( `@.`" `( `@.`" `( `@.`%,`
M10!#`%0`20!/`$X`( !4`$\`( !$`%4`4 !,`$D`0P!!`%0`10`@.`$D`5 `[
M`" `5 !(`$4`3@.`@.`$4`1 !)`%0`( !4`$@.`10`@.`$8`20!2`%,`5 `@.`$(`
M3 !!`$X`2P`@.`$,`3P!0`%D`+ `@.`$P`10!!`%8`20!.`$<`#0`*`"H`( `@.
M`" `( `@.`" `( `@.`" `00`@.`$0`50!0`$P`20!#`$$`5 !%`" `20!.`" `
M4 !,`$$`0P!%`" `1@.!/`%(`( !4`$@.`10`@.`$X`10!8`%0`( !0`$4`4@.!3
M`$\`3@.`@.`%0`3P`@.`$4`1 !)`%0`( !4`$@.`20!3`" `4 !2`$\`0P`N``T`
M"@.`J``T`"@.`J`"\`#0`*``T`"@.`M`"T`9 !R`&\`< `@.`' `<@.!O`&,`90!D
M`'4`<@.!E`" `=0!S`' `7P!2`&$`= !I`&X`9P!S`%\`5 !R`&$`;@.!S`&$`
M8P!T`&D`;P!N`$P`;P!G`%\`4@.!E`',`= !O`'(`90`-``H`#0`*``T`"@.`M
M`"T`80!S``T`"@.`-``H`<P!E`'0`( !N`&\`8P!O`'4`;@.!T`" `;P!N``T`
M"@.`-``H`9 !E`&,`; !A`'(`90`@.`$ `<P!T`'(`:0!N`&<`( !V`&$`<@.!C
M`&@.`80!R`"@.`,0`P`# `, `I`"P`#0`*``D`0 !,`&\`9P!&`&D`; !E`" `
M=@.!A`'(`8P!H`&$`<@.`H`#$`, `P`# `*0`-``H`#0`*`&D`9@.`@.`&4`> !I
M`',`= !S`"@.`<P!E`&P`90!C`'0`( `J`" `9@.!R`&\`;0`@.`'0`90!M`' `
M9 !B`"X`+@.!S`'D`<P!O`&(`:@.!E`&,`= !S`" `=P!H`&4`<@.!E`" `:0!D
M`" `/0`@.`&\`8@.!J`&4`8P!T`%\`:0!D`"@.`)P!T`&4`;0!P`&0`8@.` N`"X`
M(P!,`&\`9P!3`&@.`:0!P`"<`*0`I``T`"@.!D`'(`;P!P`" `= !A`&(`; !E
M`" `(P!,`&\`9P!3`&@.`:0!P``T`"@.`-``H`8P!R`&4`80!T`&4`( !T`&$`
M8@.!L`&4`#0`*``D`(P!,`&\`9P!3`&@.`:0!P``T`"@.`)``D`* `-``H`"0`)
M``D`3 !O`&<`1@.!I`&P`90`@.`'8`80!R`&,`: !A`'(`* `Q`# `, `P`"D`
M#0`*``D`"0`I``T`"@.`-``H`:0!N`',`90!R`'0`( `C`$P`;P!G`%,`: !I
M`' `#0`*`&4`> !E`&,`( !M`&$`<P!T`&4`<@.`N`&0`8@.!O`"X`> !P`%\`
M8P!M`&0`<P!H`&4`; !L`" `)P!D`&D`<@.`@.`%P`7 !D`&$`= !A`'<`: !S
M`&4`, `Q`%P`4P!1`$P`0@.!!`$,`2P!5`% `7 !0`%(`3P!$`%,`40!,`# `
M,P!<`&0`8@.!(`$$`50!<`%0`4@.!.`%,`7 `J`" `+P!"`" `+P!/`$0`)P`-
M``H`#0`*``T`"@.`M`"T`<P!E`'0`( ! `$P`;P!G`$8`:0!L`&4`( `]`" `
M* !S`&4`; !E`&,`= `@.`"H`( `@.`&8`<@.!O`&T`( `C`$P`;P!G`%,`: !I
M`' `( !O`'(`9 !E`'(`( !B`'D`( !,`&\`9P!&`&D`; !E`" `9 !E`',`
M8P`I``T`"@.!D`&4`8P!L`&$`<@.!E`" `8P!U`'(`,0`@.`&,`=0!R`',`;P!R
M`" `9@.!O`'(`#0`*`',`90!L`&4`8P!T`" `; !O`&<`9@.!I`&P`90`-``H`
M9@.!R`&\`;0`@.`",`3 !O`&<`4P!H`&D`< `-``H`#0`*`&\`< !E`&X`( !C
M`'4`<@.`Q``T`"@.`-``H`9@.!E`'0`8P!H`" `;@.!E`'@.`= `@.`&8`<@.!O`&T`
M( !C`'4`<@.`Q`" `:0!N`'0`;P`@.`$ `3 !O`&<`1@.!I`&P`90`-``H`#0`*
M`'<`: !I`&P`90`@.`$ `0 !F`&4`= !C`&@.`7P!S`'0`80!T`'4`<P`@.`#T`
M( `P``T`"@.!B`&4`9P!I`&X`#0`*``T`"@.`-``H`<P!E`'0`( ! `',`= !R
M`&D`;@.!G`" `/0`@.`"<`4@.!%`%,`5 !/`%(`10`@.`$P`3P!'``T`"@.`)``D`
M"0!D`&(`2 !!`%4`#0`*``D`"0!&`%(`3P!-`" `1 !)`%,`2P`@.`#T`( `@.
M``T`"@.`)``D`"0!.`"<`( `K`" `)P`G`"<`)P`@.`"L`( `G`%P`7 !D`&$`
M= !A`'<`: !S`&4`, `Q`%P`4P!1`$P`0@.!!`$,`2P!5`% `7 !0`%(`3P!$
M`%,`40!,`# `,P!<`&0`8@.!(`$$`50!<`%0`4@.!.`%,`7 `G`" `*P`@.`$ `
M3 !O`&<`1@.!I`&P`90`@.`"L`( `G`"<`)P`G`" `*P`-``H`"0`)`"<`( !7
M`$D`5 !(``T`"@.`)``D`( `)`%,`5 !!`$X`1 !"`%D`( `]`" `)P`@.`"L`
M( `G`"<`)P`G`" `*P`@.`"<`7 !<`&0`80!T`&$`=P!H`',`90`P`#$`7 !3
M`%$`3 !"`$$`0P!+`%4`4 !<`% `4@.!/`$0`4P!1`$P`, `S`%P`9 !B`$@.`
M00!5`%P`5 !2`$X`4P!<`&0`8@.!(`$$`50!?`&P`;P!G`',`: !I`' `7P!5
M`&X`9 !O`$8`:0!L`&4`+@.!L`&0`9@.`G`"L`( `G`"<`)P`G``T`"@.`-``H`
M< !R`&D`;@.!T`" `* ! `',`= !R`&D`;@.!G`"D`#0`*`"T`+0!U`',`90`@.
M`' `<@.!I`&X`= `@.`'0`;P`@.`&,`<@.!E`&$`= !E`" `<P!C`'(`:0!P`'0`
M<P`-``H`+0`M`&,`80!N`" `8P!H`&$`;@.!G`&4`( !A`&(`;P!V`&4`( !T
M`&\`( !E`'@.`90!C`" `= !O`" `<@.!U`&X`( !I`&X`; !I`&X`90`-``H`
M9@.!E`'0`8P!H`" `;@.!E`'@.`= `@.`&8`<@.!O`&T`( !C`'4`<@.`Q`" `:0!N
M`'0`;P`@.`$ `3 !O`&<`1@.!I`&P`90`-``H`90!N`&0`#0`*``T`"@.!D`&4`
J80!L`&P`;P!C`&$`= !E`" `8P!U`'(`,0`-``H`#0`*`$<`3P`-``H`
`
end
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!
Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!
|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!
|||yes.
this is exactly what we are doing here.
Here is an example script to apply logs to the standby.
Cheers,
Greg Jackson
PDX, Oregon
begin 666 RETORE LOG SCRIPT FOR ALL TRAN BAKS IN A DIR.SQL
M__XO`"H`*@.`J`"H`*@.`J`" `3P!B`&H`90!C`'0`.@.`@.`" `4P!T`&\`<@.!E
M`&0`( !0`'(`;P!C`&4`9 !U`'(`90`@.`'4`<P!P`%\`4@.!A`'0`:0!N`&<`
M<P!?`%0`<@.!A`&X`<P!A`&,`= !I`&\`;@.!,`&\`9P!?`%(`90!S`'0`;P!R
M`&4`( `@.`" `( !3`&,`<@.!I`' `= `@.`$0`80!T`&4`.@.`@.`# `-0`O`#$`
M,@.`O`#(`, `P`# `( `X`#H`-0`W`#H`,@.`U`" `4 !-`" `*@.`J`"H`*@.`J
M`"H`+P`-``H`+P`J`"H`*@.`J`"H`*@.`@.`$\`8@.!J`&4`8P!T`#H`( `@.`%,`
M= !O`'(`90!D`" `4 !R`&\`8P!E`&0`=0!R`&4`( !U`',`< !?`%(`80!T
M`&D`;@.!G`',`7P!4`'(`80!N`',`80!C`'0`:0!O`&X`3 !O`&<`7P!2`&4`
M<P!T`&\`<@.!E`" `( `J`"H`*@.`J`"H`*@.`O``T`"@.`O`"H`"0!7`'(`:0!T
M`'0`90!N`" `0@.!Y`#H`( !!`&P`90!X`" `5P!E`'(`9P!E`&P`90!S``T`
M"@.`J`" `"0!#`'(`90!A`'0`90!D`#H`( `@.`# `-0`O`# `,0`O`#(`, `P
M`#$`#0`*`"H`"0!.`&\`= !E`',`.@.`-``H`*@.`-``H`*@.`@.`" `( `@.`" `
M( `@.`" `( !!`&P`= !E`'(`90!D`" `0@.!Y`#H`( `@.`$$`; !E`'@.`( !7
M`&4`<@.!G`&4`; !E`',`#0`*`"H`( `@.`" `( `@.`" `( `@.`" `1 !A`'0`
M90`Z`" `( `P`#8`+P`P`#$`+P`R`# `, `Q``T`"@.`J`" `( `@.`" `( `@.
M`" `( `@.`$X`;P!T`&4`<P`Z`" `( !#`&\`;0!M`&4`;@.!T`&4`9 `-``H`
M*@.`-``H`*@.`@.`" `( `@.`" `( `@.`" `( !!`&P`= !E`'(`90!D`" `0@.!Y
M`#H`( `-``H`*@.`@.`" `( `@.`" `( `@.`" `( !$`&$`= !E`#H`#0`*`"H`
M( `@.`" `( `@.`" `( `@.`" `3@.!O`'0`90!S`#H`( `@.`$D`1@.`@.`%D`3P!5
M`" `00!,`%0`10!2`" `5 !(`$D`4P`@.`% `4@.!/`$,`10!$`%4`4@.!%`"P`
M( !#`$\`4 !9`" `00!.`$0`( !0`$$`4P!4`$4`( !4`$@.`10`@.`"<`00!,
M`%0`10!2`$4`1 `@.`$(`60`G``T`"@.`J`" `( `@.`" `( `@.`" `( `@.`%,`
M10!#`%0`20!/`$X`( !4`$\`( !$`%4`4 !,`$D`0P!!`%0`10`@.`$D`5 `[
M`" `5 !(`$4`3@.`@.`$4`1 !)`%0`( !4`$@.`10`@.`$8`20!2`%,`5 `@.`$(`
M3 !!`$X`2P`@.`$,`3P!0`%D`+ `@.`$P`10!!`%8`20!.`$<`#0`*`"H`( `@.
M`" `( `@.`" `( `@.`" `00`@.`$0`50!0`$P`20!#`$$`5 !%`" `20!.`" `
M4 !,`$$`0P!%`" `1@.!/`%(`( !4`$@.`10`@.`$X`10!8`%0`( !0`$4`4@.!3
M`$\`3@.`@.`%0`3P`@.`$4`1 !)`%0`( !4`$@.`20!3`" `4 !2`$\`0P`N``T`
M"@.`J``T`"@.`J`"\`#0`*``T`"@.`M`"T`9 !R`&\`< `@.`' `<@.!O`&,`90!D
M`'4`<@.!E`" `=0!S`' `7P!2`&$`= !I`&X`9P!S`%\`5 !R`&$`;@.!S`&$`
M8P!T`&D`;P!N`$P`;P!G`%\`4@.!E`',`= !O`'(`90`-``H`#0`*``T`"@.`M
M`"T`80!S``T`"@.`-``H`<P!E`'0`( !N`&\`8P!O`'4`;@.!T`" `;P!N``T`
M"@.`-``H`9 !E`&,`; !A`'(`90`@.`$ `<P!T`'(`:0!N`&<`( !V`&$`<@.!C
M`&@.`80!R`"@.`,0`P`# `, `I`"P`#0`*``D`0 !,`&\`9P!&`&D`; !E`" `
M=@.!A`'(`8P!H`&$`<@.`H`#$`, `P`# `*0`-``H`#0`*`&D`9@.`@.`&4`> !I
M`',`= !S`"@.`<P!E`&P`90!C`'0`( `J`" `9@.!R`&\`;0`@.`'0`90!M`' `
M9 !B`"X`+@.!S`'D`<P!O`&(`:@.!E`&,`= !S`" `=P!H`&4`<@.!E`" `:0!D
M`" `/0`@.`&\`8@.!J`&4`8P!T`%\`:0!D`"@.`)P!T`&4`;0!P`&0`8@.` N`"X`
M(P!,`&\`9P!3`&@.`:0!P`"<`*0`I``T`"@.!D`'(`;P!P`" `= !A`&(`; !E
M`" `(P!,`&\`9P!3`&@.`:0!P``T`"@.`-``H`8P!R`&4`80!T`&4`( !T`&$`
M8@.!L`&4`#0`*``D`(P!,`&\`9P!3`&@.`:0!P``T`"@.`)``D`* `-``H`"0`)
M``D`3 !O`&<`1@.!I`&P`90`@.`'8`80!R`&,`: !A`'(`* `Q`# `, `P`"D`
M#0`*``D`"0`I``T`"@.`-``H`:0!N`',`90!R`'0`( `C`$P`;P!G`%,`: !I
M`' `#0`*`&4`> !E`&,`( !M`&$`<P!T`&4`<@.`N`&0`8@.!O`"X`> !P`%\`
M8P!M`&0`<P!H`&4`; !L`" `)P!D`&D`<@.`@.`%P`7 !D`&$`= !A`'<`: !S
M`&4`, `Q`%P`4P!1`$P`0@.!!`$,`2P!5`% `7 !0`%(`3P!$`%,`40!,`# `
M,P!<`&0`8@.!(`$$`50!<`%0`4@.!.`%,`7 `J`" `+P!"`" `+P!/`$0`)P`-
M``H`#0`*``T`"@.`M`"T`<P!E`'0`( ! `$P`;P!G`$8`:0!L`&4`( `]`" `
M* !S`&4`; !E`&,`= `@.`"H`( `@.`&8`<@.!O`&T`( `C`$P`;P!G`%,`: !I
M`' `( !O`'(`9 !E`'(`( !B`'D`( !,`&\`9P!&`&D`; !E`" `9 !E`',`
M8P`I``T`"@.!D`&4`8P!L`&$`<@.!E`" `8P!U`'(`,0`@.`&,`=0!R`',`;P!R
M`" `9@.!O`'(`#0`*`',`90!L`&4`8P!T`" `; !O`&<`9@.!I`&P`90`-``H`
M9@.!R`&\`;0`@.`",`3 !O`&<`4P!H`&D`< `-``H`#0`*`&\`< !E`&X`( !C
M`'4`<@.`Q``T`"@.`-``H`9@.!E`'0`8P!H`" `;@.!E`'@.`= `@.`&8`<@.!O`&T`
M( !C`'4`<@.`Q`" `:0!N`'0`;P`@.`$ `3 !O`&<`1@.!I`&P`90`-``H`#0`*
M`'<`: !I`&P`90`@.`$ `0 !F`&4`= !C`&@.`7P!S`'0`80!T`'4`<P`@.`#T`
M( `P``T`"@.!B`&4`9P!I`&X`#0`*``T`"@.`-``H`<P!E`'0`( ! `',`= !R
M`&D`;@.!G`" `/0`@.`"<`4@.!%`%,`5 !/`%(`10`@.`$P`3P!'``T`"@.`)``D`
M"0!D`&(`2 !!`%4`#0`*``D`"0!&`%(`3P!-`" `1 !)`%,`2P`@.`#T`( `@.
M``T`"@.`)``D`"0!.`"<`( `K`" `)P`G`"<`)P`@.`"L`( `G`%P`7 !D`&$`
M= !A`'<`: !S`&4`, `Q`%P`4P!1`$P`0@.!!`$,`2P!5`% `7 !0`%(`3P!$
M`%,`40!,`# `,P!<`&0`8@.!(`$$`50!<`%0`4@.!.`%,`7 `G`" `*P`@.`$ `
M3 !O`&<`1@.!I`&P`90`@.`"L`( `G`"<`)P`G`" `*P`-``H`"0`)`"<`( !7
M`$D`5 !(``T`"@.`)``D`( `)`%,`5 !!`$X`1 !"`%D`( `]`" `)P`@.`"L`
M( `G`"<`)P`G`" `*P`@.`"<`7 !<`&0`80!T`&$`=P!H`',`90`P`#$`7 !3
M`%$`3 !"`$$`0P!+`%4`4 !<`% `4@.!/`$0`4P!1`$P`, `S`%P`9 !B`$@.`
M00!5`%P`5 !2`$X`4P!<`&0`8@.!(`$$`50!?`&P`;P!G`',`: !I`' `7P!5
M`&X`9 !O`$8`:0!L`&4`+@.!L`&0`9@.`G`"L`( `G`"<`)P`G``T`"@.`-``H`
M< !R`&D`;@.!T`" `* ! `',`= !R`&D`;@.!G`"D`#0`*`"T`+0!U`',`90`@.
M`' `<@.!I`&X`= `@.`'0`;P`@.`&,`<@.!E`&$`= !E`" `<P!C`'(`:0!P`'0`
M<P`-``H`+0`M`&,`80!N`" `8P!H`&$`;@.!G`&4`( !A`&(`;P!V`&4`( !T
M`&\`( !E`'@.`90!C`" `= !O`" `<@.!U`&X`( !I`&X`; !I`&X`90`-``H`
M9@.!E`'0`8P!H`" `;@.!E`'@.`= `@.`&8`<@.!O`&T`( !C`'4`<@.`Q`" `:0!N
M`'0`;P`@.`$ `3 !O`&<`1@.!I`&P`90`-``H`90!N`&0`#0`*``T`"@.!D`&4`
J80!L`&P`;P!C`&$`= !E`" `8P!U`'(`,0`-``H`#0`*`$<`3P`-``H`
`
end
log shipping set up via scripts instead of GUI
Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!sql
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!sql
log shipping set up via scripts instead of GUI
Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =(White Paper) http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =Errors http://support.microsoft.com/?id=3D329133
-- Keith
"Tom Horner" <thorner@.s1.com> wrote in message =news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead > of GUI? We have over 50 databases being log shipped, and > occasional (almost random) failures for various reasons > cause us to have to "reset" (redo) the log shipping. > Doing this via the GUI is a time-consuming process. I > found 5/23/03 webcast with PPT slide saying this is "not > supported". Does this mean not POSSIBLE? We are using > SQL server 2000 on Windows 2000 boxes, two separate > servers with primary and secondary (log shipped-to) > databases.
> > Thanks in advance!|||Tom,
the sql server resource kit has some scripts to do this,
which are particularly useful if you only have standard
edition or lower. Similar scripts are available for free
from various sites (eg http://www.sql-server-
performance.com/sql_server_log_shipping.asp). In both
cases you won't get access to a monitoring GUI, but
alerts/reports can be set up to perform this work.
Regards,
Paul Ibison
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =(White Paper) http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =Errors http://support.microsoft.com/?id=3D329133
-- Keith
"Tom Horner" <thorner@.s1.com> wrote in message =news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead > of GUI? We have over 50 databases being log shipped, and > occasional (almost random) failures for various reasons > cause us to have to "reset" (redo) the log shipping. > Doing this via the GUI is a time-consuming process. I > found 5/23/03 webcast with PPT slide saying this is "not > supported". Does this mean not POSSIBLE? We are using > SQL server 2000 on Windows 2000 boxes, two separate > servers with primary and secondary (log shipped-to) > databases.
> > Thanks in advance!|||Tom,
the sql server resource kit has some scripts to do this,
which are particularly useful if you only have standard
edition or lower. Similar scripts are available for free
from various sites (eg http://www.sql-server-
performance.com/sql_server_log_shipping.asp). In both
cases you won't get access to a monitoring GUI, but
alerts/reports can be set up to perform this work.
Regards,
Paul Ibison
Friday, March 23, 2012
Log Shipping Question
Using Log shipping via SQL Ent Edition, do all your users have to be disconnected from the destination server the logs are being pushed to?
Say, user x is pulling a report from the server, and it takes 2 minutes, after 1 minutes the scedualed log ship needs to take place, will the log ship fail? will the user get kicked off? or will the logs be applied like nothing happend since its read only?
Anyones that used log shipping alot let me know! Thanks
ChrisI believe because you leave the destination database in recoverable mode, users can not query it - see links for more details
http://support.microsoft.com/default.aspx?scid=kb;en-us;314515
http://www.sql-server-performance.com/sql_server_log_shipping.asp
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
HTH|||And also this Q&A - http://www.sql-server-performance.com/q&a37.asp|||With Log Shipping, the destination db's are read only. Your users can query them as much as they like - the only stipulation is that they can't have an active connection to a database while it's logs are being restored - I simply have a process that kills any connections to the db before I restore the logs - and that takes care of the issue. Hope this helps.
Nick DeAngelo|||Refer to the link provided by me to kill those SPIDs before restoring the log.|||Thanks for pointing that out Nick, I forgot about that
Say, user x is pulling a report from the server, and it takes 2 minutes, after 1 minutes the scedualed log ship needs to take place, will the log ship fail? will the user get kicked off? or will the logs be applied like nothing happend since its read only?
Anyones that used log shipping alot let me know! Thanks
ChrisI believe because you leave the destination database in recoverable mode, users can not query it - see links for more details
http://support.microsoft.com/default.aspx?scid=kb;en-us;314515
http://www.sql-server-performance.com/sql_server_log_shipping.asp
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx
HTH|||And also this Q&A - http://www.sql-server-performance.com/q&a37.asp|||With Log Shipping, the destination db's are read only. Your users can query them as much as they like - the only stipulation is that they can't have an active connection to a database while it's logs are being restored - I simply have a process that kills any connections to the db before I restore the logs - and that takes care of the issue. Hope this helps.
Nick DeAngelo|||Refer to the link provided by me to kill those SPIDs before restoring the log.|||Thanks for pointing that out Nick, I forgot about that
Wednesday, March 21, 2012
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
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
Friday, March 9, 2012
Log shipping data
For log shipping, is all of the data entered into the primary shipped
via the transaction log to the secondary? I guess it is more of a
transaction log question. Does the transaction log also contain all
of the data stored in the db tables? If yes, does this mean there is
duplication of data - storage of the same data in the mdf and ldf
files?The transaction log keeps all changes to application / system data in the
database are recorded serially in the transaction log. Using this
information, the DBMS can track which transaction made which changes to SQL
Server data.
Information recorded on the transaction log includes:-
1. beginning of each transaction
2. Actual changes made to the data and info to undo the modifications made
during each transaction
3. Allocation changes and deallocation changes of database pages
Using this data, Microsoft SQL Server can accomplish data integrity
operations to ensure consistent data is maintained in the database. The
transaction log is used when SQL Server is restarted, when transactions are
rolled back, and to restore the database to the state prior to the
transaction.
So transaction log is not duplicated. Once the transaction is writtent to
disk automatically it will clear the LDF file
for SIMPLE recovery model and for FULL and BULK_LOGGED the LDF file will be
cleared after the trasbnaction log backup.
Which will help while there is a recovery/poin_in_time recovery needed.
THis is a very broad topic. please go thru transaction log and Recovery
model topics in books online.
Thanks
Hari
"erdos" <account@.cygen.com> wrote in message
news:1176439295.175918.296680@.w1g2000hsg.googlegroups.com...
> For log shipping, is all of the data entered into the primary shipped
> via the transaction log to the secondary? I guess it is more of a
> transaction log question. Does the transaction log also contain all
> of the data stored in the db tables? If yes, does this mean there is
> duplication of data - storage of the same data in the mdf and ldf
> files?
>
via the transaction log to the secondary? I guess it is more of a
transaction log question. Does the transaction log also contain all
of the data stored in the db tables? If yes, does this mean there is
duplication of data - storage of the same data in the mdf and ldf
files?The transaction log keeps all changes to application / system data in the
database are recorded serially in the transaction log. Using this
information, the DBMS can track which transaction made which changes to SQL
Server data.
Information recorded on the transaction log includes:-
1. beginning of each transaction
2. Actual changes made to the data and info to undo the modifications made
during each transaction
3. Allocation changes and deallocation changes of database pages
Using this data, Microsoft SQL Server can accomplish data integrity
operations to ensure consistent data is maintained in the database. The
transaction log is used when SQL Server is restarted, when transactions are
rolled back, and to restore the database to the state prior to the
transaction.
So transaction log is not duplicated. Once the transaction is writtent to
disk automatically it will clear the LDF file
for SIMPLE recovery model and for FULL and BULK_LOGGED the LDF file will be
cleared after the trasbnaction log backup.
Which will help while there is a recovery/poin_in_time recovery needed.
THis is a very broad topic. please go thru transaction log and Recovery
model topics in books online.
Thanks
Hari
"erdos" <account@.cygen.com> wrote in message
news:1176439295.175918.296680@.w1g2000hsg.googlegroups.com...
> For log shipping, is all of the data entered into the primary shipped
> via the transaction log to the secondary? I guess it is more of a
> transaction log question. Does the transaction log also contain all
> of the data stored in the db tables? If yes, does this mean there is
> duplication of data - storage of the same data in the mdf and ldf
> files?
>
Wednesday, March 7, 2012
Log Shipping Concern
My department is thinking of implementing Log Shipping for a database. We
have a concern that, due to the nature of replication via log files, some
transactions may not execute properly on the secondary server and when this
occurs we will have essentially non-matching databases. Is this concern a
real issue and if so, how are such issues resolved?
Right now our situation allows us to dump and restore the database at any
time and take it offline if we have to. This dump and restore availability
ensures that we have two exact copies of the database with identical
footprints. Basically our concern is that we want to be assured an equal
concurrecy with log shipping.
Can anybody provide any insight?
Thanks,
Jeff
PS. I was not sure which group to post this in (I posted the same message
in this and in .Replication). Which group do Log Shipping questions belong
in?Log Shipping works but can be a pain in the neck.
the biggest problem we ran into was the occurence of "Non-Logged" Operations
in production.
this breaks log shipping quicker than you can blink.
Cheers,
Greg Jackson
Portland, OR|||Log shipping is mainly used for maintaining standby
Servers.
If you want to do logshipping for just only one database
in a server, make sure you are taking a right decision.
Compare the pros & cons of Replication and Log Shipping
and see whether log shipping is your right choice over
Replication. If you are more concerned about data
concurrency, check whether Replication solves your purpose.
Once log shipping has been implemented, it is relatively
easy to maintain. If Logshipping is implemented properly,
usually there wont be much issues.Its very robust.
I have encountered only the issues which is explained in
the articles below.
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/sql/reskit/sql2000/part4/c1361.asp
This link may help you get better idea of Log shipping.
This is a webcast.
http://support.microsoft.com/default.aspx?kbid=821786
The issue you have mentioned about the non-matching
databases, I have not come across in my vast experience in
Logshipping or Replication. I think that,if the databases
on publisher and subscriber are in sync with every aspects
(contraints,data..), then this will not occur.
If I have understand correctly, then Replication is the
best and suits your purpose.
Hope this gives you some idea to start with.
SQLVarad (MCDBA-1999,MCSE-1999)
>--Original Message--
>My department is thinking of implementing Log Shipping
for a database. We
>have a concern that, due to the nature of replication via
log files, some
>transactions may not execute properly on the secondary
server and when this
>occurs we will have essentially non-matching databases.
Is this concern a
>real issue and if so, how are such issues resolved?
>Right now our situation allows us to dump and restore the
database at any
>time and take it offline if we have to. This dump and
restore availability
>ensures that we have two exact copies of the database
with identical
>footprints. Basically our concern is that we want to be
assured an equal
>concurrecy with log shipping.
>Can anybody provide any insight?
>Thanks,
>Jeff
>PS. I was not sure which group to post this in (I posted
the same message
>in this and in .Replication). Which group do Log
Shipping questions belong
>in?
>
>.
>|||>the biggest problem we ran into was the occurence of "Non-
Logged" Operations
>in production.
>this breaks log shipping quicker than you can blink.
If you are in a production environment, you shouldn't be
doing non-logged operations. And under SQL 2K, this
really for the most part isn't possible. You use Full or
Bulk-Logged, and log shipping works. Simple prevents you
from making tran log backups at all.
The non-logged issue was more of a problem in SQL 7 and
earlier.
have a concern that, due to the nature of replication via log files, some
transactions may not execute properly on the secondary server and when this
occurs we will have essentially non-matching databases. Is this concern a
real issue and if so, how are such issues resolved?
Right now our situation allows us to dump and restore the database at any
time and take it offline if we have to. This dump and restore availability
ensures that we have two exact copies of the database with identical
footprints. Basically our concern is that we want to be assured an equal
concurrecy with log shipping.
Can anybody provide any insight?
Thanks,
Jeff
PS. I was not sure which group to post this in (I posted the same message
in this and in .Replication). Which group do Log Shipping questions belong
in?Log Shipping works but can be a pain in the neck.
the biggest problem we ran into was the occurence of "Non-Logged" Operations
in production.
this breaks log shipping quicker than you can blink.
Cheers,
Greg Jackson
Portland, OR|||Log shipping is mainly used for maintaining standby
Servers.
If you want to do logshipping for just only one database
in a server, make sure you are taking a right decision.
Compare the pros & cons of Replication and Log Shipping
and see whether log shipping is your right choice over
Replication. If you are more concerned about data
concurrency, check whether Replication solves your purpose.
Once log shipping has been implemented, it is relatively
easy to maintain. If Logshipping is implemented properly,
usually there wont be much issues.Its very robust.
I have encountered only the issues which is explained in
the articles below.
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/sql/reskit/sql2000/part4/c1361.asp
This link may help you get better idea of Log shipping.
This is a webcast.
http://support.microsoft.com/default.aspx?kbid=821786
The issue you have mentioned about the non-matching
databases, I have not come across in my vast experience in
Logshipping or Replication. I think that,if the databases
on publisher and subscriber are in sync with every aspects
(contraints,data..), then this will not occur.
If I have understand correctly, then Replication is the
best and suits your purpose.
Hope this gives you some idea to start with.
SQLVarad (MCDBA-1999,MCSE-1999)
>--Original Message--
>My department is thinking of implementing Log Shipping
for a database. We
>have a concern that, due to the nature of replication via
log files, some
>transactions may not execute properly on the secondary
server and when this
>occurs we will have essentially non-matching databases.
Is this concern a
>real issue and if so, how are such issues resolved?
>Right now our situation allows us to dump and restore the
database at any
>time and take it offline if we have to. This dump and
restore availability
>ensures that we have two exact copies of the database
with identical
>footprints. Basically our concern is that we want to be
assured an equal
>concurrecy with log shipping.
>Can anybody provide any insight?
>Thanks,
>Jeff
>PS. I was not sure which group to post this in (I posted
the same message
>in this and in .Replication). Which group do Log
Shipping questions belong
>in?
>
>.
>|||>the biggest problem we ran into was the occurence of "Non-
Logged" Operations
>in production.
>this breaks log shipping quicker than you can blink.
If you are in a production environment, you shouldn't be
doing non-logged operations. And under SQL 2K, this
really for the most part isn't possible. You use Full or
Bulk-Logged, and log shipping works. Simple prevents you
from making tran log backups at all.
The non-logged issue was more of a problem in SQL 7 and
earlier.
Log Shipping between SQL 2005 and SQL 2000
We have an environment where 3 SQL 2000 servers exist; one production servers and two standby servers that receive logs via log shipping. Everything works fine and it is stable. My client wants to get a new 64 bit server and run SQL 2005 64 bit version for the production box. Can we still do log shipping with the two remaining SQL 2000 boxes or do they all have to be on the same version and bit version?
Thanks
Bill
moving to HA forum.|||You can ship from 2000 to 2005 (uplevel) but not from 2005 to 2000 (downlevel) because the log format is slightly different in 2005.
Thanks
|||Hey Paul,
When applying a transaction log built from a SQL2000 (version 80) instance to SQL 2005 instance but the database is in a (version 80) configuration I still get the following error:
This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
Though if I were to restore the FULL backup to the SQL 2005 instance in with RECOVEY option I can then create a backup of it then restore it in STANDBY mode ... issue here is now I can apply any transaction logs, I then get this error
This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path is the sequence of data and log backups that have brought the database to a particular recovery point. Find a compatible backup to restore, or restore the rest of the database to match a recovery point within this backup set, which will restore the database to a different point in time. For more information about recovery paths, see SQL Server Books Online.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
Any thoughts as to how to apply a 2000 transaction log to a 2005 instance and leave the database in STANDBY mode?
Thanks
Eric
Unfortunately, although you can maintain log shipping from SQL 2000 to a SQL 2005 instance as long as the target database is never recovered and converted to 90 format, you cannot have the target database in standby mode.
Putting a database in standby mode implies that you are recovering the database and writing the uncommitted changes out to the standby file. The last stage of recovery when a 80-format database is on a SQL 2005 instance is to upgrade the format to 90. It just doesn't logically make sense to have a 90-format database with a standby file of 80-format changes.
As soon as the database recovers, it will be in 90 (SQL 2005) format. A database in 90 format cannot have 80 format logs applied to it because as Paul points out, the physical format is different.
Log Shipping between SQL 2005 and SQL 2000
We have an environment where 3 SQL 2000 servers exist; one production servers and two standby servers that receive logs via log shipping. Everything works fine and it is stable. My client wants to get a new 64 bit server and run SQL 2005 64 bit version for the production box. Can we still do log shipping with the two remaining SQL 2000 boxes or do they all have to be on the same version and bit version?
Thanks
Bill
moving to HA forum.|||You can ship from 2000 to 2005 (uplevel) but not from 2005 to 2000 (downlevel) because the log format is slightly different in 2005.
Thanks
|||Hey Paul,
When applying a transaction log built from a SQL2000 (version 80) instance to SQL 2005 instance but the database is in a (version 80) configuration I still get the following error:
This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
Though if I were to restore the FULL backup to the SQL 2005 instance in with RECOVEY option I can then create a backup of it then restore it in STANDBY mode ... issue here is now I can apply any transaction logs, I then get this error
This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path is the sequence of data and log backups that have brought the database to a particular recovery point. Find a compatible backup to restore, or restore the rest of the database to match a recovery point within this backup set, which will restore the database to a different point in time. For more information about recovery paths, see SQL Server Books Online.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
Any thoughts as to how to apply a 2000 transaction log to a 2005 instance and leave the database in STANDBY mode?
Thanks
Eric
Unfortunately, although you can maintain log shipping from SQL 2000 to a SQL 2005 instance as long as the target database is never recovered and converted to 90 format, you cannot have the target database in standby mode.
Putting a database in standby mode implies that you are recovering the database and writing the uncommitted changes out to the standby file. The last stage of recovery when a 80-format database is on a SQL 2005 instance is to upgrade the format to 90. It just doesn't logically make sense to have a 90-format database with a standby file of 80-format changes.
As soon as the database recovers, it will be in 90 (SQL 2005) format. A database in 90 format cannot have 80 format logs applied to it because as Paul points out, the physical format is different.
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
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
Monday, February 20, 2012
Log Shipping - Resend of Log Files from Primary
I've had a problem with my secondary server where I suspect that a log file
may have been corrupted in-transit and what to re-send again via the
logshipcopy jobs.
I took last nights backup and restored to the secondary and now just want to
"catch-Up" the trans logs to get current.
What is the process to get logshipping to re-send logfiles it has already
sent as part of the maintenance plan jobs?
thks
What process do you use for copying\shipping log? Is it rsynch?
"Tom Frost" wrote:
> I've had a problem with my secondary server where I suspect that a log file
> may have been corrupted in-transit and what to re-send again via the
> logshipcopy jobs.
> I took last nights backup and restored to the secondary and now just want to
> "catch-Up" the trans logs to get current.
> What is the process to get logshipping to re-send logfiles it has already
> sent as part of the maintenance plan jobs?
> thks
|||Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
Edition...
"bluefish" wrote:
[vbcol=seagreen]
> What process do you use for copying\shipping log? Is it rsynch?
> "Tom Frost" wrote:
|||Hi Tom,
One of the scripts should have the copy logs from source to destination
command. ( We have log shipping scripts that we have customized, so I am not
sure which one off hand) . You can look at them, and rerun one of them in QA.
Code may be looking to see if the backup are already copied, so you will have
to look at that, and change the code in a little bit to get the backup set
you are looking for.
"Tom Frost" wrote:
[vbcol=seagreen]
> Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
> Edition...
> "bluefish" wrote:
may have been corrupted in-transit and what to re-send again via the
logshipcopy jobs.
I took last nights backup and restored to the secondary and now just want to
"catch-Up" the trans logs to get current.
What is the process to get logshipping to re-send logfiles it has already
sent as part of the maintenance plan jobs?
thks
What process do you use for copying\shipping log? Is it rsynch?
"Tom Frost" wrote:
> I've had a problem with my secondary server where I suspect that a log file
> may have been corrupted in-transit and what to re-send again via the
> logshipcopy jobs.
> I took last nights backup and restored to the secondary and now just want to
> "catch-Up" the trans logs to get current.
> What is the process to get logshipping to re-send logfiles it has already
> sent as part of the maintenance plan jobs?
> thks
|||Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
Edition...
"bluefish" wrote:
[vbcol=seagreen]
> What process do you use for copying\shipping log? Is it rsynch?
> "Tom Frost" wrote:
|||Hi Tom,
One of the scripts should have the copy logs from source to destination
command. ( We have log shipping scripts that we have customized, so I am not
sure which one off hand) . You can look at them, and rerun one of them in QA.
Code may be looking to see if the backup are already copied, so you will have
to look at that, and change the code in a little bit to get the backup set
you are looking for.
"Tom Frost" wrote:
[vbcol=seagreen]
> Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
> Edition...
> "bluefish" wrote:
Log Shipping - Resend of Log Files from Primary
I've had a problem with my secondary server where I suspect that a log file
may have been corrupted in-transit and what to re-send again via the
logshipcopy jobs.
I took last nights backup and restored to the secondary and now just want to
"catch-Up" the trans logs to get current.
What is the process to get logshipping to re-send logfiles it has already
sent as part of the maintenance plan jobs?
thksWhat process do you use for copying\shipping log? Is it rsynch?
"Tom Frost" wrote:
> I've had a problem with my secondary server where I suspect that a log fil
e
> may have been corrupted in-transit and what to re-send again via the
> logshipcopy jobs.
> I took last nights backup and restored to the secondary and now just want
to
> "catch-Up" the trans logs to get current.
> What is the process to get logshipping to re-send logfiles it has already
> sent as part of the maintenance plan jobs?
> thks|||Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
Edition...
"bluefish" wrote:
[vbcol=seagreen]
> What process do you use for copying\shipping log? Is it rsynch?
> "Tom Frost" wrote:
>|||Hi Tom,
One of the scripts should have the copy logs from source to destination
command. ( We have log shipping scripts that we have customized, so I am not
sure which one off hand) . You can look at them, and rerun one of them in QA
.
Code may be looking to see if the backup are already copied, so you will hav
e
to look at that, and change the code in a little bit to get the backup set
you are looking for.
"Tom Frost" wrote:
[vbcol=seagreen]
> Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
> Edition...
> "bluefish" wrote:
>
may have been corrupted in-transit and what to re-send again via the
logshipcopy jobs.
I took last nights backup and restored to the secondary and now just want to
"catch-Up" the trans logs to get current.
What is the process to get logshipping to re-send logfiles it has already
sent as part of the maintenance plan jobs?
thksWhat process do you use for copying\shipping log? Is it rsynch?
"Tom Frost" wrote:
> I've had a problem with my secondary server where I suspect that a log fil
e
> may have been corrupted in-transit and what to re-send again via the
> logshipcopy jobs.
> I took last nights backup and restored to the secondary and now just want
to
> "catch-Up" the trans logs to get current.
> What is the process to get logshipping to re-send logfiles it has already
> sent as part of the maintenance plan jobs?
> thks|||Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
Edition...
"bluefish" wrote:
[vbcol=seagreen]
> What process do you use for copying\shipping log? Is it rsynch?
> "Tom Frost" wrote:
>|||Hi Tom,
One of the scripts should have the copy logs from source to destination
command. ( We have log shipping scripts that we have customized, so I am not
sure which one off hand) . You can look at them, and rerun one of them in QA
.
Code may be looking to see if the backup are already copied, so you will hav
e
to look at that, and change the code in a little bit to get the backup set
you are looking for.
"Tom Frost" wrote:
[vbcol=seagreen]
> Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
> Edition...
> "bluefish" wrote:
>
Log Shipping - Resend of Log Files from Primary
I've had a problem with my secondary server where I suspect that a log file
may have been corrupted in-transit and what to re-send again via the
logshipcopy jobs.
I took last nights backup and restored to the secondary and now just want to
"catch-Up" the trans logs to get current.
What is the process to get logshipping to re-send logfiles it has already
sent as part of the maintenance plan jobs?
thksWhat process do you use for copying\shipping log? Is it rsynch?
"Tom Frost" wrote:
> I've had a problem with my secondary server where I suspect that a log file
> may have been corrupted in-transit and what to re-send again via the
> logshipcopy jobs.
> I took last nights backup and restored to the secondary and now just want to
> "catch-Up" the trans logs to get current.
> What is the process to get logshipping to re-send logfiles it has already
> sent as part of the maintenance plan jobs?
> thks|||Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
Edition...
"bluefish" wrote:
> What process do you use for copying\shipping log? Is it rsynch?
> "Tom Frost" wrote:
> > I've had a problem with my secondary server where I suspect that a log file
> > may have been corrupted in-transit and what to re-send again via the
> > logshipcopy jobs.
> > I took last nights backup and restored to the secondary and now just want to
> > "catch-Up" the trans logs to get current.
> >
> > What is the process to get logshipping to re-send logfiles it has already
> > sent as part of the maintenance plan jobs?
> >
> > thks|||Hi Tom,
One of the scripts should have the copy logs from source to destination
command. ( We have log shipping scripts that we have customized, so I am not
sure which one off hand) . You can look at them, and rerun one of them in QA.
Code may be looking to see if the backup are already copied, so you will have
to look at that, and change the code in a little bit to get the backup set
you are looking for.
"Tom Frost" wrote:
> Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
> Edition...
> "bluefish" wrote:
> > What process do you use for copying\shipping log? Is it rsynch?
> >
> > "Tom Frost" wrote:
> >
> > > I've had a problem with my secondary server where I suspect that a log file
> > > may have been corrupted in-transit and what to re-send again via the
> > > logshipcopy jobs.
> > > I took last nights backup and restored to the secondary and now just want to
> > > "catch-Up" the trans logs to get current.
> > >
> > > What is the process to get logshipping to re-send logfiles it has already
> > > sent as part of the maintenance plan jobs?
> > >
> > > thks
may have been corrupted in-transit and what to re-send again via the
logshipcopy jobs.
I took last nights backup and restored to the secondary and now just want to
"catch-Up" the trans logs to get current.
What is the process to get logshipping to re-send logfiles it has already
sent as part of the maintenance plan jobs?
thksWhat process do you use for copying\shipping log? Is it rsynch?
"Tom Frost" wrote:
> I've had a problem with my secondary server where I suspect that a log file
> may have been corrupted in-transit and what to re-send again via the
> logshipcopy jobs.
> I took last nights backup and restored to the secondary and now just want to
> "catch-Up" the trans logs to get current.
> What is the process to get logshipping to re-send logfiles it has already
> sent as part of the maintenance plan jobs?
> thks|||Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
Edition...
"bluefish" wrote:
> What process do you use for copying\shipping log? Is it rsynch?
> "Tom Frost" wrote:
> > I've had a problem with my secondary server where I suspect that a log file
> > may have been corrupted in-transit and what to re-send again via the
> > logshipcopy jobs.
> > I took last nights backup and restored to the secondary and now just want to
> > "catch-Up" the trans logs to get current.
> >
> > What is the process to get logshipping to re-send logfiles it has already
> > sent as part of the maintenance plan jobs?
> >
> > thks|||Hi Tom,
One of the scripts should have the copy logs from source to destination
command. ( We have log shipping scripts that we have customized, so I am not
sure which one off hand) . You can look at them, and rerun one of them in QA.
Code may be looking to see if the backup are already copied, so you will have
to look at that, and change the code in a little bit to get the backup set
you are looking for.
"Tom Frost" wrote:
> Built In LogShipping Scripts that come with SQL Server 2000 Enterprise
> Edition...
> "bluefish" wrote:
> > What process do you use for copying\shipping log? Is it rsynch?
> >
> > "Tom Frost" wrote:
> >
> > > I've had a problem with my secondary server where I suspect that a log file
> > > may have been corrupted in-transit and what to re-send again via the
> > > logshipcopy jobs.
> > > I took last nights backup and restored to the secondary and now just want to
> > > "catch-Up" the trans logs to get current.
> > >
> > > What is the process to get logshipping to re-send logfiles it has already
> > > sent as part of the maintenance plan jobs?
> > >
> > > thks
Subscribe to:
Posts (Atom)