Event Id | 18265 |
Source | MSSQLServer |
Description | Log backed up: Database: %1, creation date(time): %2(%3), first LSN: %4, last LSN: %5, number of dump devices: %7!d!, device information: (%8). |
Event Information | CAUSE: This informational message indicates that a transaction log backup has completed successfully. This message is written to the application event log and the SQL Server error log when a backup finishes. RESOLUTION: 1. If the message is filling up your application Event Viewer logs, you can change properties of the log by setting the "Maximum log size" or choosing a different option under "When maximum log size is reached". 2. If the message is causing your SQL Server error log to grow too large, you can execute the sp_cycle_errorlog stored procedure to create a new log. 3. You can enable the trace flag 3226. This trace flag will prevent all informational BACKUP and RESTORE messages from being written to the SQL Server error log and the NT application event log. Informational BACKUP and RESTORE messages include 18264, 18265, 18266, 18267, 18268, 18269, 18270, 18271, 18276, and 18277. Be aware that alerts for BACKUP and RESTORE informational messages will no longer fire, since they rely on an entry in the NT application event log. |
Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 18265 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.