Announcement

Collapse
No announcement yet.

Corrupted Exchange databases and storage

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Corrupted Exchange databases and storage

    I'm managing an Exchange 2007 organization, on a CCR cluster. Last week we had a failover and could't update CCR on other node as three databases were corrupted (at least this information was received after we run backup with verification). we decided to create new database, move mailboxes to that new database, deleted the corrupted ones, recreate again, move mailboxes back. All went ok until backup with verification was started again and same three databases appeared corrupted.
    Seems to me clear that there is a problem on storage (something wrong with the LUNs) as there is too much coincidence, but when asking the storage admins they say that no errors appear from their side.

    What aproach can I chose ?
    Have you experienced something similar ?

    If aditional info is required, please ask.

    Thanks in advance.

  • #2
    Re: Corrupted Exchange databases and storage

    What kind of back-up do you take? Who is the vendor?
    [Powershell]
    Start-DayDream
    Set-Location Malibu Beach
    Get-Drink
    Lay-Back
    Start-Sleep
    ....
    Wake-Up!
    Resume-Service
    Write-Warning
    [/Powershell]

    BLOG: Therealshrimp.blogspot.com

    Comment


    • #3
      Re: Corrupted Exchange databases and storage

      Backup is performed with Netapp SnapManager for Exchange.

      Backup without verification is ok, while when running backup with verification following errors appears:

      "Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 2167.540 seconds.

      ERROR: page 7727973 checksum failed ( 0x77537753b67abcd8 / 0x1956e6a9afdc8f5f )"

      Could this be maybe related to SnapManager for Exchange application maybe, and not to storage...

      Comment


      • #4
        Re: Corrupted Exchange databases and storage

        Backup Applications will often report the database is corrupt when it is not.
        It usually means it cannot backup something that it wants to, and when it fails reports it as "corrupt".
        Ensure that you are using the latest version of your backup application.
        If you need to, use another tool or the native Windows Backup to backup Exchange and confirm that backup works correctly.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: Corrupted Exchange databases and storage

          Problem looks solved...solution was moving db with error, deleting the LUNs and old databases, recreating LUNs and databases, moving mailboxes back.

          So far so good...

          /closed

          Comment

          Working...
          X