http://sqlservermct.wordpress.com/2011/10/07/backup-database-to-disk-n%E2%80%98nul%E2%80%99-%E2%80%93-and-misconceptions/
Veeam can truncate log base on some option.
http://www.veeam.com/vmware-backup/help-center/v6_1/hyperv/index.html?vmware_replica_guest_processing.htm
It make backup chain broken.
When they perform truncate log, you can see 2 of the log like this.
SQL VSS is normal behavior to create SnapShot on disk.
But, Veeam Backup and replication with truncate log isn’t good option to manage database.
I recommend that do not enable truncate log on Veeam replication manager.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
| select top 10 *
from msdb.dbo.backupset
where is_snapshot=1
--It's due to SQL VSS.
--Program_Name : "Microsoft SQL Server VSS Writer"
--ex)
--BACKUP DATABASE [DBNAME] TO VIRTUAL_DEVICE='{4C5C20F9-FE32-4FCA-BE43-FFFFFFFFFFFF}1' WITH SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
select top 10 *
from msdb.dbo.backupmediafamily
where physical_device_name='NUL'
--It's due to Veeam.
--Program_Name : "Veeam Backup and Replication"
--ex)
--BACKUP LOG [DBNAME] TO DISK = 'NUL'
|