Event ID 509, Ese followed by Eventid 218: "Mailbox Database experienced a performance problem"

Since yesterday we're getting warnings in the event viewer of exchange 2013.
And also the Windows Backup is showing completed with warnings.
The server has enough harddisk memory and our ram is 28 GB  

The exchange server 2013 Enterprise SP2 is running on a Windows server 2012 R2 (virtual machine)hyper-v

Can you provide me a solution for this problem ?
As an attachment i've attached the event 509, event 218, windows bak error and performance specs
Thanks.
EVENT218.jpg
EVENT509.jpg
Windowsbak.png
Performance.png
Program1981Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
The first error is to be expected if you aren't in a DAG.
The second and third errors would point to a hardware problem. Hard disk or RAID controller most likely.
That could have caused some corruption within the Exchange database.

If this is a branded server (HP, Dell etc) then you will need to use their tools to see if there is an issue.

"exchange server 2013 Enterprise SP2"

That doesn't exist.
It is either SP1, or one of the cumulative updates. If it is on CU, then it needs to be CU7 or CU8 (at the time of writing) to be supported.

Simon.
0
Program1981Author Commented:
This problem occured after we've deleted a snapshot of the virtuele machine where the exchange server 2013 SP1 is running on. Can it be that during the merging of the VM the databases became corrupted.
Hyperv 2012 R3
0
Simon Butler (Sembee)ConsultantCommented:
You shouldn't snapshot an Exchange server. It isn't a supported backup/restore method with Exchange and usually ends up causing problems.

Are users able to get email correctly? If so I would create a new database in Exchange 2013 then move all users across to the new database and drop the original.

And stop taking snapshots of the server.

Simon.
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Program1981Author Commented:
Thank you for your answer Simon as of the error of 509 disappeared when rebooting the server and starting the Windows backup manually. The weird part is that we're receiving different error's now after each other but then the backup works.
The windows backup is schedules to run a full backup.

Event 2112, Msexchangerepl:
The Microsoft Exchange Replication service VSS Writer instance 21d1051d-fdae-4503-8d3c-e3399adc802d failed with error code 80070020 when preparing for a backup of database 'DB1'.

Event 2024, Msexchangerepl:
The Microsoft Exchange Replication service VSS Writer (Instance 21d1051d-fdae-4503-8d3c-e3399adc802d) failed with error 80070020 when preparing for a backup.

Event 16389, SPP:
Writer Microsoft Exchange Writer experienced retryable error during shadow copy creation. Retrying...  More info: .

Event 8229, VSS:
A VSS writer has rejected an event with error 0x00000000,
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.


Our exchange 2013 server build is 15.00.0847.032
0
Simon Butler (Sembee)ConsultantCommented:
That is SP1 (aka CU4), so you are well out of date.
We are now on CU8. To remain supported you need to be on the current or previous CU.

I would suggest an update, and see if that resolves the VSS writer issues.

Simon.
0
Program1981Author Commented:
Simon the problem was a faulty disk and the disk has been replaced.

Everything is fine now
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Program1981Author Commented:
yes
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.