Hi, when backing up exchangeinformation store using backupexec, there are always heaps of ESE events logged as ESETUIL [a number] database engine stopped or started. The backup completed successfully though. Any explanation or fix? thanks in advance!
what are the event IDs? aren't they just informational? -- Susan Conkey [MVP] "tree leafs" wrote in message news:eSWtJWgtIHA.1936@TK2MSFTNGP04.phx.gbl... > Hi, > when backing up exchangeinformation store using backupexec, there are > always heaps of ESE events logged as ESETUIL [a number] database engine > stopped or started. The backup completed successfully though. > Any explanation or fix? > thanks in advance! > >
The event IDs are 100 and 101. Yes, they are informational. Any explanation and how to stop them? "Susan" wrote in message news:eL5KkagtIHA.4912@TK2MSFTNGP03.phx.gbl... > what are the event IDs? aren't they just informational? > > -- > Susan Conkey [MVP] > > > > "tree leafs" wrote in message > news:eSWtJWgtIHA.1936@TK2MSFTNGP04.phx.gbl... >> Hi, >> when backing up exchangeinformation store using backupexec, there are >> always heaps of ESE events logged as ESETUIL [a number] database engine >> stopped or started. The backup completed successfully though. >> Any explanation or fix? >> thanks in advance! >> >> > >
I don't believe you can, unless you stop doing backups and online maintenance...why would you want to stop them? -- Susan Conkey [MVP] "tree leafs" wrote in message news:O520qzmtIHA.2292@TK2MSFTNGP03.phx.gbl... > The event IDs are 100 and 101. Yes, they are informational. Any > explanation and how to stop them? > > "Susan" wrote in message > news:eL5KkagtIHA.4912@TK2MSFTNGP03.phx.gbl... >> what are the event IDs? aren't they just informational? >> >> -- >> Susan Conkey [MVP] >> >> >> >> "tree leafs" wrote in message >> news:eSWtJWgtIHA.1936@TK2MSFTNGP04.phx.gbl... >>> Hi, >>> when backing up exchangeinformation store using backupexec, there are >>> always heaps of ESE events logged as ESETUIL [a number] database engine >>> stopped or started. The backup completed successfully though. >>> Any explanation or fix? >>> thanks in advance! >>> >>> >> >> > >
