Return
-
Title
Fastcompression backup run not on schedule. -
Description
We have set the option to force a full backup after 6 days but full backup is forced to run after 5th day of second week. On third week, full backup is forced after 6th day and on fourth week, again it is forced to run after 5th day and so on.
-
Cause
Litespeed does not take into account local time zone and depending on local time (GMT-8 or GMT+5) could be -8 or +5 hours off in calculation.
-
Resolution
Workaround:Add +1 day to the "Force a full backup every day" value.
Status:
Waiting for fix in a future release of Litespeed for SQL Server.
-
Defect ID
LS126