Log truncation with Full Recovery or Bulk Logged model databases (4033875)

SQL databases with the Full Recovery model or Bulk-Logged model cannot have their logs truncated without taking a backup of the transaction log first. This is by design within SQL Server in order to maintain the log chain. When the transaction log is backed up, the log is truncated.

By design, vRanger cannot perform a log backup. The freeze.bat script install can be tweaked to do a backup to NUL, but it is not recommended. (Anything that is written to 'NUL' is discarded by the OS). 

Currently, It is not possible for vRanger to truncate the logs for these types of databases.

To identify Full Recovery and Bulk-Logged databases, this query can be run within SQL management studio:

• SELECT name FROM master.dbo.sysdatabases WHERE name NOT IN ('master','model','msdb','tempdb') AND DATABASEPROPERTYEX(name, 'Recovery') <> 'SIMPLE'

However, it is possible to create a log transaction backup within the SQL agent jobs using T-SQL or using SQLCMD as a scheduled task to a local drive or a shared location:

If the database is configured with the Simple recovery model, it can be truncated successfully when using the vRanger VSS tools.