| Event Id | 18270 |
| Source | MSSQLServer |
| Description | Database differential changes backed up: Database: %1, creation date(time): %2(%3), pages dumped: %4!d!, first LSN: %5, last LSN: %6, full backup LSN: %7, number of dump devices: %10!d!, device information: (%11). |
| Event Information | According to Microsoft Cause: This message indicates that a differential database backup has completed successfully. This message is written to the application event log and the SQL Server errorlog every time a backup completes. 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. For more information about how to increase the number of SQL Server error logs retained, see the Microsoft Knowledge Base article 196909. 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 to 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. For detailed instructions on how to enable a trace flag with the -T startup option, see "Using Startup Options" in Books Online. |
| Reference Links | Event Id:18270 of Source Id:MSSQLServer |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.