Hello,
I recently discovered a concerning issue with the Backup Windows plugin, it's not telling me when I have a backup that "Completed with warnings." Instead it just shows the backup was completed. Is this expected behavior of the plug-in or should it be displaying a different icon on the Backup Windows plug-in Manger tab? Currently it's just showing a green checkmark for success or a red "x" if a PC is not current or a backup has failed.
Completed with warnings - not reported by plug-in
Re: Completed with warnings - not reported by plug-in
Cane you post the error being reported?
Re: Completed with warnings - not reported by plug-in
Please see below for log details from Windows Server Backup:
Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {559CB328-A285-466D-A716-69D7B115C738}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 8
Failure Result: 800423F4
Application Result: 80004005
Application Message: (null)
Component: 0EFC96BD-C339-4971-A8A1-113B0EEF5145
Logical Path: (null)
Component Result: 800423F4
Component Message: (null)
File Spec: D:\VM\DATA\Virtual Machines\\0EFC96BD-C339-4971-A8A1-113B0EEF5145.vmcx Recursive: 0
File Spec: D:\VM\DATA\Virtual Machines\\0EFC96BD-C339-4971-A8A1-113B0EEF5145.VMRS Recursive: 0
File Spec: D:\VM\DATA\Virtual Machines\\0EFC96BD-C339-4971-A8A1-113B0EEF5145.vmgs Recursive: 0
File Spec: D:\VM\DATA\Virtual Hard Disks\\DATA.vhdx Recursive: 0
File Spec: D:\VM\DATA\Snapshots\0DBED8DF-F48D-45D9-916E-81C453E2E9E2.VMCX Recursive: 0
File Spec: D:\VM\DATA\Snapshots\0DBED8DF-F48D-45D9-916E-81C453E2E9E2.VMRS Recursive: 0
File Spec: D:\VM\DATA\Snapshots\0DBED8DF-F48D-45D9-916E-81C453E2E9E2.vmgs Recursive: 0
File Spec: D:\VM\DATA\Virtual Hard Disks\DATA-AutoRecovery.avhdx Recursive: 0
Component: 442261DE-846E-4407-BF81-938CC041D7B6
Logical Path: (null)
Component Result: 800423F4
Component Message: (null)
File Spec: D:\VM\SQL\Virtual Machines\\442261DE-846E-4407-BF81-938CC041D7B6.vmcx Recursive: 0
File Spec: D:\VM\SQL\Virtual Machines\\442261DE-846E-4407-BF81-938CC041D7B6.VMRS Recursive: 0
File Spec: D:\VM\SQL\Virtual Machines\\442261DE-846E-4407-BF81-938CC041D7B6.vmgs Recursive: 0
File Spec: D:\VM\SQL\Virtual Hard Disks\\SQL.VHDX Recursive: 0
File Spec: D:\VM\SQL\Snapshots\3BF37C71-FFD4-4E22-9608-8C14003112C6.VMCX Recursive: 0
File Spec: D:\VM\SQL\Snapshots\3BF37C71-FFD4-4E22-9608-8C14003112C6.VMRS Recursive: 0
File Spec: D:\VM\SQL\Snapshots\3BF37C71-FFD4-4E22-9608-8C14003112C6.vmgs Recursive: 0
File Spec: D:\VM\SQL\Virtual Hard Disks\SQL-AutoRecovery.avhdx Recursive: 0
*-----------------------------*
Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {559CB328-A285-466D-A716-69D7B115C738}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 8
Failure Result: 800423F4
Application Result: 80004005
Application Message: (null)
Component: 0EFC96BD-C339-4971-A8A1-113B0EEF5145
Logical Path: (null)
Component Result: 800423F4
Component Message: (null)
File Spec: D:\VM\DATA\Virtual Machines\\0EFC96BD-C339-4971-A8A1-113B0EEF5145.vmcx Recursive: 0
File Spec: D:\VM\DATA\Virtual Machines\\0EFC96BD-C339-4971-A8A1-113B0EEF5145.VMRS Recursive: 0
File Spec: D:\VM\DATA\Virtual Machines\\0EFC96BD-C339-4971-A8A1-113B0EEF5145.vmgs Recursive: 0
File Spec: D:\VM\DATA\Virtual Hard Disks\\DATA.vhdx Recursive: 0
File Spec: D:\VM\DATA\Snapshots\0DBED8DF-F48D-45D9-916E-81C453E2E9E2.VMCX Recursive: 0
File Spec: D:\VM\DATA\Snapshots\0DBED8DF-F48D-45D9-916E-81C453E2E9E2.VMRS Recursive: 0
File Spec: D:\VM\DATA\Snapshots\0DBED8DF-F48D-45D9-916E-81C453E2E9E2.vmgs Recursive: 0
File Spec: D:\VM\DATA\Virtual Hard Disks\DATA-AutoRecovery.avhdx Recursive: 0
Component: 442261DE-846E-4407-BF81-938CC041D7B6
Logical Path: (null)
Component Result: 800423F4
Component Message: (null)
File Spec: D:\VM\SQL\Virtual Machines\\442261DE-846E-4407-BF81-938CC041D7B6.vmcx Recursive: 0
File Spec: D:\VM\SQL\Virtual Machines\\442261DE-846E-4407-BF81-938CC041D7B6.VMRS Recursive: 0
File Spec: D:\VM\SQL\Virtual Machines\\442261DE-846E-4407-BF81-938CC041D7B6.vmgs Recursive: 0
File Spec: D:\VM\SQL\Virtual Hard Disks\\SQL.VHDX Recursive: 0
File Spec: D:\VM\SQL\Snapshots\3BF37C71-FFD4-4E22-9608-8C14003112C6.VMCX Recursive: 0
File Spec: D:\VM\SQL\Snapshots\3BF37C71-FFD4-4E22-9608-8C14003112C6.VMRS Recursive: 0
File Spec: D:\VM\SQL\Snapshots\3BF37C71-FFD4-4E22-9608-8C14003112C6.vmgs Recursive: 0
File Spec: D:\VM\SQL\Virtual Hard Disks\SQL-AutoRecovery.avhdx Recursive: 0
*-----------------------------*
Re: Completed with warnings - not reported by plug-in
Thanks, Let me have a look to see we interact with errors. I'll post back here shortly.
Re: Completed with warnings - not reported by plug-in
Hello,
I was interested to know if you had a chance to look at this. I am still seeing the same behavior where Windows server backup completes with errors, but the dashboard shows the backup was successful.
I was interested to know if you had a chance to look at this. I am still seeing the same behavior where Windows server backup completes with errors, but the dashboard shows the backup was successful.
Re: Completed with warnings - not reported by plug-in
Yea, I totaly forgot about this. Got pulled away doing other things and just forgot.
I will make a note and get you an answer on this. The logical answer is yes ot should give you what ever errors or logs the agent provides the plugin. We must be interperting the job as a success for some reason. Let me have a peek and see what triggers are geting fired when backup completes.
I will make a note and get you an answer on this. The logical answer is yes ot should give you what ever errors or logs the agent provides the plugin. We must be interperting the job as a success for some reason. Let me have a peek and see what triggers are geting fired when backup completes.