Exchange 2010 Database cannot be mounted.

Hello Experts,

Need your help here.
Exchange 2010 SP2 Running in VM, 3 Node DAG,

One of the database "DBName" is not getting mounted.ErrorCopies status
Eseutil /MH = Dirty Shutdown.
Eseutil /ML = OK
Eseutil /r = Operation terminated with error -566 (JET_errDbTimeTooOld, dbtime on page smaller than dbtimeBefore in record)

Same results on both copies.
Need some urgent advice and help.
LVL 12
Vaseem MohammedAsked:
Who is Participating?
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.

Vaseem MohammedAuthor Commented:
Don't want to go on Repair option right away as this is critical DB and Size of DB is approx. 150GB.
TIME is really short, need to get this up before working hours start.
0
Casey WeaverNetwork EngineerCommented:
What happened before this? Are there missing logs? File system corruption?
0
Vaseem MohammedAuthor Commented:
A "volume copy" was done to move underlying storage volume to new storage.
This was done at storage level. after copy was done, the new is set to primary and old is still in sync as secondary.
Other databases is mounted except this one.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Casey WeaverNetwork EngineerCommented:
/mh how many log(s) are missing?
0
Vaseem MohammedAuthor Commented:
Logs are available.
 
 
 DB Signature: Create time:04/17/2013 10:29:42 Rand:506830687 Computer:
         cbDbPage: 32768
           dbtime: 898832538 (0x3593189a)
            State: Dirty Shutdown
     Log Required: 1441910-1441916 (0x160076-0x16007c)
    Log Committed: 0-1441916 (0x0-0x16007c)
   Log Recovering: 1441916 (0x16007c)
  GenMax Creation: 10/18/2015 02:52:58
         Shadowed: Yes
       Last Objid: 31993
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
 Old Repair Count: 0
  Last Consistent: (0x15CD21,8,1F)  10/12/2015 18:36:34
      Last Attach: (0x15CD22,9,86)  10/12/2015 18:36:34
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:04/17/2013 10:29:42 Rand:506818397 Computer:
       OS Version: (6.1.7601 SP 1 NLS ffffffff.ffffffff)
     Reseed Count: 2
      Reseed Date: 10/12/2015 13:53:34
 Old Reseed Count: 0
      Patch Count: 1
       Patch Date: 10/12/2015 13:53:34
  Old Patch Count: 0

Open in new window

0
Casey WeaverNetwork EngineerCommented:
Ok I see this situation is a bit complex. Have you seen this article? https://exchangelab.wordpress.com/2013/05/13/how-to-solve-ese-566-errors-jet_errdbtimetooold/
0
Vaseem MohammedAuthor Commented:
I already tried doing soft recovery.
soft recovery
0
Vaseem MohammedAuthor Commented:
Had to restore from Backup.
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
AmitIT ArchitectCommented:
Better you focus on storage part. Also going forward, always move your sever into maintenance mode, before you perform any server level activity.
0
Vaseem MohammedAuthor Commented:
Thank you Casey for trying to help and the link you shared.
Due to lack of time and need to get DB online ASAP, couldn't dig into  the problem, but search for possible reason and fix will keep going.
In this short period, multiple things might have caused the problem.
May be for some reason the database did not commit logs during the VM shutdown process.
As the underlying volume was copied it might have caused.

Important thing "Keep Backup Clean", Before performing any maintenance task schedule a FULL backup. Know the backup window and Time required for FULL backup.
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
Windows Server 2012

From novice to tech pro — start learning today.