-
- Service Provider
- Posts: 195
- Liked: 40 times
- Joined: Mar 01, 2016 10:16 am
- Full Name: Gert
- Location: Denmark
- Contact:
Warning handling for Powered Off VMs
Hi Veeam
Is there any logic behind marking VM's as a warning when they are powered off when Periodically SQL Transaction
log backups are enabled with the "Backup logs periodically (backed up logs will be truncated)" function?
One of our customers have a dynamic environment where VM's get powered on/off quite a lot, and we are getting a lot of "false positives"
Veeam will mark the VM as warning even though that it know that the VM is powered off.
Skipping guest processing (VM is powered off)
Failed to retrieve SQL server databases information required to perform transaction logs backup <--- This line is marked as a warning
This behaviour doesn't happen if the "Truncate logs (prevents logs from growing forever)" function is used.
Is there any plans on changing this behaviour? In our case we'd prefer to have the "Backup logs periodically (backed up logs will be truncated)"
enabled on the backup jobs incase a VM is powered on again to ensure we are pulling the SQL logs, but it sucks to have all these warnings on our jobs.
Is there any logic behind marking VM's as a warning when they are powered off when Periodically SQL Transaction
log backups are enabled with the "Backup logs periodically (backed up logs will be truncated)" function?
One of our customers have a dynamic environment where VM's get powered on/off quite a lot, and we are getting a lot of "false positives"
Veeam will mark the VM as warning even though that it know that the VM is powered off.
Skipping guest processing (VM is powered off)
Failed to retrieve SQL server databases information required to perform transaction logs backup <--- This line is marked as a warning
This behaviour doesn't happen if the "Truncate logs (prevents logs from growing forever)" function is used.
Is there any plans on changing this behaviour? In our case we'd prefer to have the "Backup logs periodically (backed up logs will be truncated)"
enabled on the backup jobs incase a VM is powered on again to ensure we are pulling the SQL logs, but it sucks to have all these warnings on our jobs.
-
- Veeam Software
- Posts: 3801
- Liked: 640 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Warning handling for Powered Off VMs
Hi Gert,
We don't have plans to change this behavior but your request fully makes sense. Would a registry key that controls the severity level (Warning/Info) of this message work in your case?
Thanks!
We don't have plans to change this behavior but your request fully makes sense. Would a registry key that controls the severity level (Warning/Info) of this message work in your case?
Thanks!
-
- Service Provider
- Posts: 195
- Liked: 40 times
- Joined: Mar 01, 2016 10:16 am
- Full Name: Gert
- Location: Denmark
- Contact:
Re: Warning handling for Powered Off VMs
Hi PetrM
Yes a registry key would be much appreciated
Yes a registry key would be much appreciated

-
- Veeam Software
- Posts: 3801
- Liked: 640 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Warning handling for Powered Off VMs
Hi Gert,
Got it. One more question: do you see this warning in the parent backup job action log or in the log backup itself? I guess the first one but want to double check.
Thanks!
Got it. One more question: do you see this warning in the parent backup job action log or in the log backup itself? I guess the first one but want to double check.
Thanks!
-
- Service Provider
- Posts: 195
- Liked: 40 times
- Joined: Mar 01, 2016 10:16 am
- Full Name: Gert
- Location: Denmark
- Contact:
Re: Warning handling for Powered Off VMs
Hi Petr
We see this in the parent log for the Backup job itself.
We see this in the parent log for the Backup job itself.
Who is online
Users browsing this forum: Paul.Loewenkamp and 57 guests