Announcement

Collapse
No announcement yet.

Log corruption

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

  • Log corruption

    Hello,

    I am studying Exchange and I read what to do in the case the .edb file gets corrupted, and it is easy to understand, but I was wonderning:

    What if the log files become corrupted and then the backups go on every night, so you are keeping invalid backups! . Could this happen?

    Thanks in advance!
    -
    Madrid (Spain).

  • #2
    Re: Log corruption

    Technically, yes, which is why a good SysAdmin will test backups regularly.
    In Exchange, a lagged DAG copy would provide a possible solution

    Ultimately you can prepare for any possible disaster but the cost goes up and up, so there will be a balance between what level of reliability you plan for and how much you can afford to pay for it
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Log corruption

      If you are doing an Exchange aware backup, then the log corruption wouldn't last very long. The log would be flushed by the backup job, removing the corruption.

      No need to have a lagged database copy, as the DAG doesn't replicate the database, so cannot replicate a corruption in the database file. Real time is fine. I have never deployed a lagged copy in any deployment I have done.

      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

      Working...
      X