0

I have a log shipping process running. Today I realized that the log files must have been overwritten during the clock change period yesterday, where the clock was set back from 3 AM to 2 AM. So I am concerned that something may be wrong. I looked at the files that have been backed up and found out they are stored with a filename in UTC time. The period of 01 AM - 02 AM UTC is missing here.

The same output is in log_shipping_monitor_history_detail's output: Here 01AM-02AM are missing as well while the log_time colum is ongoing wihtout any duplicates.

I do backup, copy and restore in 15 minute periods.

The genreal status (master.dbo.sp_help_log_shipping_monitor) of the log shipping process shows 0 (OK).

Does logshipping consider the clock change or do I have to take any actions?

Improve this question
2
  • 1
    Log shipping will not be affected by day light saving
    – Shanky
    Oct 31, 2016 at 10:52
  • the time change may have caused the first 1am-2am tlog backup file to be over written but as long as that file was already restored to your secondary you should be ok.
    – Bob Klimes
    Oct 31, 2016 at 14:30

1 Answer 1

Reset to default
1

Log shipping restores (like all restores) are based on LSN. Created .trn files should not be affected. Also, is this for Daylight savings in US, as that is next weekend, not yesterday. If files have gone missing, there is a different reason for it. Missing from Primary or Secondary?

Improve this answer
1
  • It is in Europe.
    – Magier
    Oct 31, 2016 at 16:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.