Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Log shipping

0 views
Skip to first unread message

Abba

unread,
Nov 23, 2009, 4:02:53 AM11/23/09
to
Hello,

Iam planning to set up Log shipping between two servers running SQL2008 Std
edition 64-bit, SP1. The log backups will be taken every 15minutes,copied
across and then restored in the destination box. My question is regarding
timezones: my origin server is in PST and destination is in CST.

In this scenario, how will Log Shipping work? How will the destination
server identify a Log backup that was taken 15 minutes earlier? Any pointers
will be helpful!


tia,
AbbA


TheSQLGuru

unread,
Nov 23, 2009, 11:23:05 PM11/23/09
to
I believe log shipping uses internal metadata to know what database the
backup came from and what the last LSN of the previous last transaction was,
etc. Not sure server time is a factor here.

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"Abba" <sql_...@aaa.com> wrote in message
news:uQ1zlvBb...@TK2MSFTNGP06.phx.gbl...

Abba

unread,
Nov 23, 2009, 11:41:32 PM11/23/09
to
Thanks Kevin. Thats what my thinking was as well.

Reason why Iam asking is because the Log shipping is not working. Even
though the respective jobs in both servers are running fine, when I look in
the job steps of the Log Restore job in destination server, I see these:

"Skipped log backup file"
and
"Could not find a log backup file that could be applied to secondary
database '<dbname>'.
The restore operation was successful. Secondary Database: '<dbname>', Number
of log backup files restored: 0"

These are the respective timezones:

select GETDATE()
--Origin server (PST)
--2009-11-23 20:13:08.913

--Destination server (CST)
--2009-11-23 22:15:27.120

tia,
AbbA

"TheSQLGuru" <kgb...@earthlink.net> wrote in message
news:RKudnYqSQLVow5bW...@earthlink.com...

Abba

unread,
Nov 24, 2009, 6:03:43 AM11/24/09
to
I have fixed the problem. There was another log backup that was running
apart from Log Shipping, that messed up the log sequence. I stopped that Log
backup, reconfigured the LS and it worked fine.

"Abba" <sql_...@aaa.com> wrote in message

news:eNQxOCMb...@TK2MSFTNGP02.phx.gbl...

TheSQLGuru

unread,
Nov 24, 2009, 9:46:12 AM11/24/09
to
a VERY common problem!! Glad you fixed it! :-)

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"Abba" <sql_...@aaa.com> wrote in message

news:eSBbyXPb...@TK2MSFTNGP04.phx.gbl...

0 new messages