Hi Juan, welcome to the forums.
First, I need to inform you that you're using
unsupported methods for our Powershell module here, so the research will be light as we simply cannot get deep into the behaviors of unsupported methods (they may change or not be intended for use, etc)
Code: Select all
$Job = Get-VBRJob -name db
$SQLJob = $Job.FindChildSqlLogBackupJob()
$Session = [Veeam.Backup.Core.CBackupSession]::GetByJob($SQLJob.Id) | select -Last 1 ## The Working session
$taskSession = (Get-VBRTaskSession -Session $session)[1] ## Using the first one as I have 3 hosts here
2nd and 3rd line here are using unsupported methods, and you can workaround this to get the SQL log backup SessionID with Get-VBRSession:
Code: Select all
$tlogSess = Get-VBRSession -Type Sqllogbackup
The ID can then be passed to
and you will get a normal SQL Backup Log Transaction session in a supported way.
As for the Logger.GetLog() call, this pulls the messages from the UI window, and I suppose there's probably just some limit internally on that session view, but I'm not sure it's worth getting into.
Is there a reason our VeeamOne report isn't suitable for monitoring the SQL Transaction Log backups?
https://helpcenter.veeam.com/docs/one/r ... story.html
If you really need to go the powershell route and to get information on each object that was processed by the SQL Log Backup job, use the report, or from the Session returned by Get-VBRBackupSession, there is
an unsupported method GetTaskSessions() which I believe is more informative for your reporting, as it should cover all objects in the SQL Log backup session.