srch

28.04.2015 · To investigate why SQL log truncation has failed, the Veeam logs will need to be reviewed to determine which part of the truncation procedure failed. For Veeam Backup & Replication, the log file containing information about the truncation procedure will be found on the SQL server, is named: C:\ProgramData\Veeam\Backup\VeeamGuestHelper_ddmmyyyy.log

Hi, Do you see any errors in the Windows Event log for that SQL Server when you run the backup job using the "truncate" option only?

04.03.2015 · The job is set to Truncate SQL transaction logs but it isn't happening. I noticed laste week I had a 280GB transaction log file on my primary DB. I manually shrank it and it is back up to 33GB after only 4 days. so despite the fact that Veeam is saying it successfully backed up the machine and truncated the transaction log it isn't happening.

23.02.2018 · Challenge. After installing Veeam 9.5 Update 3, SQL logs are not truncated during backup, but the truncation task is still marked as a success in the job statistics. SQL Log Backup sessions complete with 0 KB transferred. You can confirm if any SQL VMs are affected by this change by checking the Guest Helper log located on the Guest VM.

This specific error means that the account in the error isn't listed in the "Logins" section of the SQL Instance, and therefore has no right to ...

After installing Veeam 9.5 Update 3, SQL logs are not truncated during backup, but the truncation task is still marked as a success in the ...

03.09.2019 · The SQL Server being protected by Veeam is using a SQL OLE DB provider which does not support TLS 1.2 Solution Behavior Change …

10.09.2021 · If you truncate transaction logs with Veeam Agent for Microsoft Windows, the chain of transaction logs will be broken, and the Microsoft SQL Server log backup job will not be able to produce a consistent log backup. With this option selected, Veeam Agent for Microsoft Windows produces a backup file and does not trigger transaction log truncation.

If the backup or replication job fails, Veeam Backup & Replication does not truncate transaction logs on the VM. In this scenario, you can ...

Sep 29, 2021 · When the backup job completes, Veeam Backup & Replication will not truncate transaction logs on the Microsoft SQL Server VM. It is recommended that you enable this option for databases that use the Simple recovery model.

Sep 10, 2021 · If you truncate transaction logs with Veeam Agent for Microsoft Windows, the chain of transaction logs will be broken, and the Microsoft SQL Server log backup job will not be able to produce a consistent log backup. With this option selected, Veeam Agent for Microsoft Windows produces a backup file and does not trigger transaction log truncation.

17.10.2018 · Veeam Community discussions and solutions for: SQL Server does not truncate Log´s of Veeam Agent for Windows

Jun 26, 2014 · SQL 2012 logs are not being truncated by Veeam June 26, 2014 / René Bos As the title states, I had some problems with truncating logs of my SQL databases when using Veeam. This post will explain why this happened and how you can fix it. Some days ago, I noticed a disk, which was used for SQL logging, that was filling up quiet rapidly.

Hi Elpretension, You may want to go to your SQL Server and locate the Guest Helper Log File on C:\ProgramData\Veeam\Backup\YOURJOBNAME\ - ...

Note: This screenshot shows the VeeamBackup database only as an example. One should perform the shrink task against the database whose log file ...

Select Do not truncate logs to preserve transaction logs. When the backup job completes, Veeam Agent for Microsoft Windows will not truncate ...

Apr 28, 2015 · For Veeam Agent for Microsoft Windows, the log file containing truncation details will be found on the SQL server in: C:\ProgramData\Veeam\Endpoint\<jobname>\Job.Backup.log. Within the Job.Backup.log log file, beneath the line "Checking if can truncate SQL logs."

If the backup application (Veeam) has sent the request to truncate, then you need to look SQL side and see what's not working. Top. Gostev: SVP, ...

18.08.2021 · Do not Truncate Logs. You can choose not to truncate transaction logs on the VM. This option is recommended if together with Veeam Backup & Replication you use another backup tool. For example, you can use Veeam Backup & Replication to create a VM image backup and instruct the native Microsoft SQL Server log backup job to back up transaction logs

26.06.2014 · SQL 2012 logs are not being truncated by Veeam. June 26, 2014 / René Bos. As the title states, I had some problems with truncating logs of my SQL databases when using Veeam. This post will explain why this happened and how you can fix it. Some days ago, I noticed a disk, which was used for SQL logging, that was filling up quiet rapidly.

Select Do not truncate logs to preserve transaction logs. When the backup job completes, Veeam Backup & Replication will not truncate ...

03.07.2013 · The logs not being truncated are a symptom. They are not being truncated because the VSS Writer is failing. Veeam only truncates logs if all writers return success since that's the only way to be sure that the backup was truly successful and consistent. You have to fix the writer to get the logs to truncate. Top.

Mar 04, 2015 · If you ask SQL, does it think the logs are being backed up? (Right click the DB, go to properties) So last night Veeam again shows it successfully truncated the logs, however SQL does not show a log backup. It does show a Database backup at the time my Veeam job ran. The last log backup is still my manual job from the day before 

Oct 18, 2018 · SQL Server does not truncate Log´s Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE) 3 posts • Page 1 of 1

29.09.2021 · Select Do not truncate logs to preserve transaction logs. When the backup job completes, Veeam Backup & Replication will not truncate transaction logs on the Microsoft SQL Server VM. It is recommended that you enable this option for databases that use the Simple recovery model. If you enable this option for databases that use the Full or Bulk-logged …