Log Shipping transaction log backup files have wrong timestamp

I'm experiencing a weird problem with log shipping in SQL 2005.

I've setup Log Shipping for a production database between two sites. The standby database is being updated correctly and everything seems to be working as expected but for one detail: the name of the transaction log backups are generated with an UTC timestamp instead of my local timezone.

The the data below extracted from the backup history:

2007-06-23 17:30:00.000 D:\Backup\Databases\mydb\mydb_20070623073000.trn
2007-06-23 17:15:00.000 D:\Backup\Databases\mydb\mydb_20070623071500.trn
2007-06-23 17:00:00.000 D:\Backup\Databases\mydb\mydb_20070623070000.trn
2007-06-23 16:45:00.000 D:\Backup\Databases\mydb\mydb_20070623064500.trn

My timezone here is GMT+10.

Although it's not affecting Log Shipping, it's very confusing as the full backups have a timestamp in the local timezone!

Has anyone seen experienced something similar to this? Please see below my SQL details:

1 ProductName NULL Microsoft SQL Server
2 ProductVersion 589824 9.00.3042.00
3 Language 1033 English (United States)
4 Platform NULL NT AMD64
5 Comments NULL NT AMD64
6 CompanyName NULL Microsoft Corporation
7 FileDescription NULL SQL Server Windows NT - 64 Bit
8 FileVersion NULL 2005.090.3042.00
9 InternalName NULL SQLSERVR
10 LegalCopyright NULL ? Microsoft Corp. All rights reserved.
11 LegalTrademarks NULL Microsoft? is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation
12 OriginalFilename NULL SQLSERVR.EXE
13 PrivateBuild NULL NULL
14 SpecialBuild 199360512 NULL
15 WindowsVersion 248381957 5.2 (3790)
16 ProcessorCount 4 4
17 ProcessorActiveMask 4 f
18 ProcessorType 8664 NULL
19 PhysicalMemory 4095 4095 (4294037504)
20 Product ID NULL NULL

Thanks,
Andr

Hi Andre

The use of UTC timestamp for the log shipping files is by design and how log shipping is supposed to work. The main reason for this is so that there is no way timestamps can jump backward or forward when daylight savings time starts or finishes, for example. Log shipping uses the timestamps to work out if there is anything new to process and using UTC ensures this process works reliably.

Thanks, Mark

|||Thanks, Mark.

It would be good, though, that the maintenance plan's backup task had at least an option to use the same approach when naming backup files, for consistency purposes.

Is this feature documented in Books Online? I couldn't find any reference.

Thanks,

Andr