Re: Log Shipping

[Abba]

Jay,

Not sure exactly what you meant; however, 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

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"

tia,
AbbA

"Jay" <sp...@nospam.org> wrote in message
news:ejsHSDLb...@TK2MSFTNGP04.phx.gbl...
>I admit this is a guess, however, if both servers are set using GMT/UTC and
>the timezone is set correctly on each server, then the systems will know
>the true times and you will have no issue.
>
> "Abba" <sql_...@aaa.com> wrote in message
> news:e$VDA%23KbKH...@TK2MSFTNGP04.phx.gbl...
>> 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
>>
>
>

[Jay]

I really doubt that your problem has to do with timezones. Log shipping has
more to do with log numbers than time.

Are you sure you have the right backup restored on the destination, so that
the log is, in fact, the correct one in the series?

Jay

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

news:%23hH4E%23LbKH...@TK2MSFTNGP02.phx.gbl...

[Abba]

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:%23hH4E%23LbKH...@TK2MSFTNGP02.phx.gbl...