Announcement

Collapse
No announcement yet.

Help! DB Inconsistencies & Never Backed Up - 228.450 Log Files!

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

  • Help! DB Inconsistencies & Never Backed Up - 228.450 Log Files!

    I came in to help a growing non-profit whose single Exchange 2010 server crashed last summer.
    They installed a new Exchange 2010 server last August. I found the following problems:

    1. It has NEVER been backed up since the August installation.
    2. The server now has 228,450 log files that need to be dealt with (lots of space).
    - - - - OUCH ! - - - -
    3. When I tested a backup, it failed with DB or Log inconsistency errors.
    4. I plan to enable extended logging "Set-EventLogLevel... -Level-Expert"
    5. I want to avoid dismounting their only database without having a good backup.
    6. The organization relies on this single Exchange instance and cannot sustain downtime.
    7. Iím thinking the lowest risk is to install a second database and migrate all mailboxes.

    Is moving existing mailboxes over to the new 2010 database a workable approach?

    1. Exchange 2010 can throttle mailbox moves to accommodate user access to the mailstore during use (150 staff).
    2. Exchange 2010 will perform the data validation in real-time and there should be no user downtime.
    3. I can deal with failed mailbox moves later and it should be a much smaller problem then.
    4. Once the NEW DATABASE comes online we can start backups on it
    5. I'm not sure backing up about during move-requests. I probably need to "suspend" moves during backup.

    Iím looking for your comments and suggestions to help us resolve this bad situation.

    Any help is much appreciated!

  • #2
    It's likely to be easier to move the mailboxes to a new store,like you already said.
    Just setup circular logging on the new store, until the moves are complete. then disable circular logging and setup appropriate backups.
    Do you have the disk space to achieve what is basically a full replica of the current mdb?
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Yes plenty of space available for new mdb. So, why do you suggest setting up CL on the new store during the mailbox moves (69GB)?

      Comment


      • #4
        Prevent excessive log generation
        Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

        Comment


        • #5
          Thank you... what should happen with the existing logs on the old mdb? Will they move to the new mdb and then be checkpointed normally following successful backups?

          Comment


          • #6
            https://www.petri.com/forums/core/im.../icon_beer.gif

            Comment


            • #7
              Sorry for delay ; the existing logs, once you've deleted the existing mdb, will just get deleted. They don't matter any more because all the data is in the new MDB
              Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

              Comment

              Working...
              X