Forum Discussion

Spiros_K_'s avatar
Spiros_K_
Level 4
9 years ago

BE2014 - W2012R2 -> Exchange 2010 - E00027

Enviroment :   Both, Exchange and BE Server are VM on the same VMWare Host. Backup Strategy - direct using RAWS  BE Server BE2014 W2012R2 16 GB Ram TEMP - 2 TB f...
  • Spiros_K_'s avatar
    9 years ago

    Last Sunday the DB of the Exchange goes offline and was not anymore able to get mounted. 

    After 8 hours of looking and searching we achieve to mount the DB after we moved the DB to a new vHD. ( Exchange is a VM) 

    After that we was able again to run Inc and Diff Backups with successful Catalog jobs. 

     

    But the whole process created a new problem, in the meantime of looking I try a whole restore of the DB.
    The Backup job of the DB ( ~700 GB ) is done after 2 hours and 20 Min. 
    Job rate is arround ~5GB pro min.

     

    The Restore job was running with 20-30 MB PRO Minute and that mean about 3-4 days to restore the whole DB. 
    I wasnt able to take a closer look why it was so slow but any comment could lead me faster to the solution.

     

    Exchange errors was : 3154 , 215 , 231, 1016,14035, 5000
    and the error from the Exchange Consoel during the mount process was "I/O error bad disk" that triggert the idea to
    move the DB to a new virtual hard disk and the problem was solved.

     

    Now I have to find out why a restore wasnt possible..

     

    I appreciate your hard work,

    Regards
    Spiros