Code: Select all
SELECT top 1000 *
FROM [VeeamBackup].[dbo].[Audit.Records]
JOIN [VeeamBackup].[dbo].[Audit.RecordParams] ON [VeeamBackup].[dbo].[Audit.RecordParams].record_id = [VeeamBackup].[dbo].[Audit.Records].id
Cheers.
Code: Select all
SELECT top 1000 *
FROM [VeeamBackup].[dbo].[Audit.Records]
JOIN [VeeamBackup].[dbo].[Audit.RecordParams] ON [VeeamBackup].[dbo].[Audit.RecordParams].record_id = [VeeamBackup].[dbo].[Audit.Records].id
That's odd. Can you please share a little more details on operations performed? Are those operations shown under VBR GUI > History node?none of the operations I've executed via Powershell are showing
Code: Select all
Add-VBRViBackupCopyJob -Name $CopyJobName -Repository $TargetRepository -Description $paramBackupDescription -BackupJob $BackupJobName -DirectOperation | Out-Null
Hi Rob,ratkinsonuk wrote: ↑Nov 11, 2021 1:04 pm I guess VeeamOne captures the changes in a more verbose way?
I've tested the Windows event logs, and the info seems to be in there, although somewhat hidden away in the data payload, but not impossible to access.Egor Yakovlev wrote: ↑Nov 11, 2021 2:08 pm Yes, that's right - Veeam Audit Reports are mostly used to track restore operations.
For your case it will be best to look for Windows Event log event IDs that we push, those have much wider coverage and are easier to track and manipulate with.
Basically, all Administrator events. Such as, backup creation, modification and deletion. The same for repositories, and any other major function. Ideally down to the field level.
Users browsing this forum: Bing [Bot], Semrush [Bot] and 49 guests