Here is a link to the default for the SQL system databases: (v=sql.105). One of my colleague ask if we changed all the databases to simple, and we did not only change the "master" system database. The log files look like this after the change.ġ7-09-2016 11:43:44 2792 Using account DOMAIN\Veeam_Serviceġ7-09-2016 11:43:44 2792 Database master: skipped transaction log truncation.ġ7-09-2016 11:43:44 2792 Database tempdb: skipped transaction log truncation.ġ7-09-2016 11:43:44 2792 Database model: skipped transaction log truncation.ġ7-09-2016 11:43:44 2792 Database msdb: skipped transaction log truncation.ġ7-09-2016 11:43:44 2792 Database BI-PRODUCTION: transation logs have been truncated. So it look like Veeam does not support changing that. Then i looked at the "master" system database on the instance and found the the customers SQL DBA had change the "Recovery model" for that system database to "Full".Īfter changing the Recovery model to Simple, with also is the Microsoft default, the warning disappeared. If any of the VSS writers encounter an error, the entire backup job will fail. When the snapshot is created, any Volume Shadow Copy Service (VSS) writer associated with the volume is called.
Use BACKUP DATABASE instead.ġ6-09-2016 22:19:08 3528 Database tempdb: skipped transaction log truncation.ġ6-09-2016 22:19:08 3528 Database model: skipped transaction log truncation.ġ6-09-2016 22:19:08 3528 Database msdb: skipped transaction log truncation.ġ6-09-2016 22:19:08 3528 Database BI-PRODUCTION: transation logs have been truncated. Veeam Explorer for Microsoft SQL is used to restore a backed-up database to the original SQL server, or a separate one, if needed. When Windows Server backup attempts to back up a disk volume, a Volume Shadow Copy Snapshot is created for the volume.
Features & component requirements will affect your decision how you install the backup server e.g. So i looked at the log files on the machine that has the SQL database instance, C:\ProgramData\Veeam\Backup\VeeamGuestHelper_XXXXXXXXX.txt and found this:ġ6-09-2016 22:19:08 3528 Using account DOMAIN\Veeam_Serviceġ6-09-2016 22:19:08 3528 Database master: failed to truncate transaction logs. Veeam Backup & Replication is a modular solution that lets you build a scalable availability infrastructure for environments of different sizes and configurations. This normally means that the account used for Application Aware backup is not a member of the role "sysadmin" on the instance, but I check and it was "sysadmin". Find Microsoft SQL Server 2012 Express LocalDB (or whatever version).I had a customer that contacted me to day because he got a warning that Veeam Backup was "Unable to truncate Microsoft SQL Server transaction logs.Details: Failed to process 'TruncateSQLLog' command.įailed to truncate SQL server transaction logs for instances: BI See guest helper log.".
The server experiencing issues in our case has the Microsoft Azure AD Connect sync installed and an update messed up the SQL settings. Click on Install to install Veeam Backup and Replication onto your Server. This option only allows to be managed by the Backup Server. A new wizard is starting and for our scenario we’ll go for the third option Failover cluster. On the Data Locations window, click on Next to proceed. From the Protection Group we have created let’s do a right click and Add to backup job > windows > new job. On the Port configuration Window, click on Next. Writer Class Id: Ĭommand Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe" I am okay with the Veeam Backup and Replication database name. Check the event log for related events from the application hosting the VSS writer. Changes that the writer made to the writer components while handling the event will not be available to the requester. A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.