Discussions specific to the VMware vSphere hypervisor
Post Reply
Frosty
Expert
Posts: 158
Liked: 28 times
Joined: Dec 22, 2009 9:00 pm
Full Name: Stephen Frost
Contact:

SureBackuEvent Log warnings (Event IDs 4 and 134) on v9.5 U1

Post by Frosty » Mar 22, 2017 2:46 am

Just upgraded today to VBR v9.5 U1.
Have run some Backup and SureBackup jobs post-upgrade.
All of them ran and completed successfully.
I checked the System event log on my VBR server.
Found multiple Event ID 4 and a single Event ID 134 Warning at the beginning of the SureBackup jobs.
The Event ID 4 warnings are about File System Filter 'Quota' and 'Datascrn' failing to attach to a disk volume.
The Event ID 134 warning says "transaction resource manager on volume System encountered an error during recovery".
But then the job goes on and completes okay.
Just wondering if anyone else gets these Warnings with their SureBackup jobs?
Also wondering, given it is just a Warning, whether I should log a support ticket and follow this up?

PTide
Veeam Software
Posts: 4540
Liked: 371 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: SureBackuEvent Log warnings (Event IDs 4 and 134) on v9.

Post by PTide » Mar 22, 2017 10:17 am

Hi,

Event ID 134 might indicate that something is wrong with Windows file system transaction log.

Event ID 4 must be related to file screening minifilter driver.

I'd contact both Veeam and MS support teams.

Thank you

Frosty
Expert
Posts: 158
Liked: 28 times
Joined: Dec 22, 2009 9:00 pm
Full Name: Stephen Frost
Contact:

Re: SureBackuEvent Log warnings (Event IDs 4 and 134) on v9.

Post by Frosty » Mar 23, 2017 10:13 pm

Thanks,
These Event Log warnings ONLY appear when SureBackup jobs run.
So at face value it doesn't appear to be an issue with Windows Server itself.
I've started by opening a Veeam support ticket (#02109113).
Will see where that leads me.
Frosty

Frosty
Expert
Posts: 158
Liked: 28 times
Joined: Dec 22, 2009 9:00 pm
Full Name: Stephen Frost
Contact:

Re: SureBackuEvent Log warnings (Event IDs 4 and 134) on v9.

Post by Frosty » Mar 23, 2017 10:25 pm

I ran the "fltmc instances" command on my VBR server whilst a SureBackup job was being run. Everything seems to be in order. Drive D: is the CDROM drive which shows Detached, presumably because the drive is not Connected in vSphere.

----------------------------------

Filter Volume Name Altitude Instance Name Frame VlStatus
-------------------- ------------------------------------- ------------ --------------------- ----- --------
TmPreFilter \Device\Mup 328500 TmPreFlt Instance 0
TmPreFilter C: 328500 TmPreFlt Instance 0
TmPreFilter E: 328500 TmPreFlt Instance 0
TmPreFilter 328500 TmPreFlt Instance 0
TmPreFilter F: 328500 TmPreFlt Instance 0
TmPreFilter B: 328500 TmPreFlt Instance 0
TmPreFilter D: 328500 TmPreFlt Instance 0 Detached
luafv C: 135000 luafv 0
Quota B: 125000 quota 0

Frosty
Expert
Posts: 158
Liked: 28 times
Joined: Dec 22, 2009 9:00 pm
Full Name: Stephen Frost
Contact:

Re: SureBackuEvent Log warnings (Event IDs 4 and 134) on v9.

Post by Frosty » Mar 29, 2017 8:53 pm

Support suggest taking the question to Microsoft.
If I have time I will do that, however given it is just a Warning (not an Error), I doubt it is worth the effort.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 15 guests