On various servers (Windows 2000 Std SP4 + SQL Server 2000 Std SP3a + hotfixes) I am seeing very weird behaviour with SQLLiteSpeed 2005 (v.220.127.116.11). When the first transaction log backup of the morning runs, at about 3am, LiteSpeed is backing up the entire database to the log file backup. This is using the xp_backup_log command with parameters (backup file name is constructed with the date & time in it). This backup follows normal overnight maintenance (full db backup, dbcc checkdb, selective reindexing). I reckon I'm going to have to seek support from Quest, but I wondered if any of you have seen this behaviour? There is no way anything other than an xp_backup_log is being executed, but it is definitely resulting in a full database backup as opposed to a t-log backup. And this is happening on a range of different servers.