Our backup exec 2014 software is giving us this error when doing a GRT resotre. Backup of the DB runs fine with no errors, however a GRT generates this message which, according to MS, there is a checksum error in the database.

this is a brand new server (win 2012 standard r2) with a new install of exchange 2013.  exchange 2007 server is working fine.

thanks in advance for any ideas

Jo

So a -1018 is a very serious issue and you can read up more on it here https://support.microsoft.com/en-us/kb/314917

This is usually caused by a hardware based issue and the most common causes are because of something in the disk subsystem.  With that said you referenced that this is a new server correct?  I ask because many times for a server that's been running without issue for some time things like firmware memory updates or disk subsystem updates can be the culprit.   All of that said this needs to be dealt with ASAP because a 1018 is basically killing your DB and left unchecked you will have a major failure.  So....

1. Check your Application event logs for the -1018 and see how long this has been going on

2. Check your system event logs to see if there are any critical errors around the disk system

3. See if there are any firmware, driver updates for anything within the disk storage system and if so apply them to see if it resolves the issue.  Another cause could be configuration of certain raid controllers and you would definitely see issues in the event log and you would need to speak to the MFG regarding any possible changes to resolve.

NOTE: three very important things to keep in mind

A: Running backups, checkdisk and eseutil repairs etc on the should be avoided as it puts more stress on the Disk and will inject more errors into the EDB

B: If you cannot find the root cause I would create a new server and move everyone to it immediately

C: You may want to consider taking the DB's offline and then making copies to an portable system so that you have copies with the least amoutn of damage in case thing go boom.  However again I would look at your event logs first and try to resolve before making copies since even that will stress the system

also, try updating the firmware associated with the drive

Correct check firmware on all objects associated in the disk subsystem chain AND if it the latest already applied I have seen a few cases where you have to role back a rev but that's fairly rare adn chould only be done IF everything was working fine before a firmware update OR the MFG tells you to roll back.

Correct check firmware on all objects associated in the disk subsystem chain AND if it has the latest already applied I have seen a few cases where you have to role back a rev but that's fairly rare and should only be done IF everything was working fine before a firmware update OR the MFG tells you to roll

Hi, Jo Bime.

Any updates? How are things going?

I suggest to move mailboxes in this database to another as soon as possible.

Please come back and let us know the results.

Best Regards.

Turns out this was a Backup Exec problem that was causing this error, not a Microsoft error.

• Marked as answer by Jo Bime 18 hours 40 minutes ago

Well a few things

1. Backup Exec (the product) has nothing to do with an ESE -1018 being generated so I would look very close at your application event logs to ensure that their are not -1018's being generated via ESE

2. The only thing BE would be doing to cause a -1018 would be the backup itself because the backup process puts stress on the disk subsystem which will then bring out additional 1018's however again that is not a BE exclusive issue i.e. any heavy stress on the disk system from backups via any product, heavy copies etc can exacerbate the issue with the disk system

With all of that said perhaps you can share a bit regarding the BE issue you discovered?