none
Storage groups always 'inconsistent' RRS feed

  • Question

  • I ran DPM 2010 for about 1.5 weeks, never was able to do get a good set off of Exchange 2003.  I turned off the " use eseutil on the DPM Server" box, and that seemed to fix it.  What exactly does this mean in terms of reliability of the backups ?
    Thursday, June 3, 2010 9:09 PM

Answers

  • ESEUtil, is an exchange utility is run on Exchange backups to verify that the backups are indeed in restorable state to avoid any corruptions in backups. Removing this is not a good idea, please follow the technet documentation on how to enable ESEUtil on DPM machines.
    Thanks, Praveen D [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, June 4, 2010 6:09 AM

All replies

  • ESEUtil, is an exchange utility is run on Exchange backups to verify that the backups are indeed in restorable state to avoid any corruptions in backups. Removing this is not a good idea, please follow the technet documentation on how to enable ESEUtil on DPM machines.
    Thanks, Praveen D [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, June 4, 2010 6:09 AM
  • Hi Rick,

     

    The following KB article will guide you on copying the correct Exchange 2003 versions of the eseutil.exe and ese.dll files to the DPM 2010 server.

     

    970640 Error 0x800700D8 occurs when you use Data Protection Manager 2007 to protect Exchange storage groups
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;970640


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, June 4, 2010 5:53 PM
    Moderator
  • I have double checked.  My Exchange 2003 is a 32 bit box (Eseutil.exe is 6.5.7638.1 ; ese.dll 6.5.7638.2) and DPM 2010 is running on Server 2008 R2 (64 bit) and is (Eseutil.exe is 6.5.7638.1 ; ese.dll 6.5.7638.2) as well.

    Any other suggestions ?

    Wednesday, June 9, 2010 2:48 PM
  • In Data Protection Manager 2007, when configuring a protection group for protection of Exchange data for the versions that DPM supports (Exchange Server 2003 w/SP2 or higher and 2007), you are given an option to enable execution of ESEUTIL.EXE against those Exchange data sources you wish to protect. When enabled, DPM performs ESEUTIL consistency checks on the data written to disk or tape to ensure that the backup is not corrupt and that it will be readable when or if it’s required. Enabling this also minimizes backup-related performance impact by offloading the typical ESEUTIL operations that most backup applications force on the production server and instead the DPM server handles this on the redundant data, lightening the load on the production Exchange Server so that it can serve more users with the goal to have less of an impact on production.

    http://blogs.technet.com/b/askcore/archive/2008/06/12/data-protection-manager-2007-important-information-for-using-eseutil-when-configuring-exchange-server-protection.aspx

     

     


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, June 9, 2010 4:22 PM
  • Thanks for the reply, but please tell me how your latest post helps me fix my problem?? Quoting from the propaganda booklet does not negate the fact that I am running the proper versions of those two files, where they need to be... Do you have any more 'help' for me? Or is this another case where microsoft leaves it up to the end user to fix / document what they did to fix an issue, or to get help with a product they released way to early in the devlopement cycle, or force me to pay $375.00 per issue to help, possibley, get resolved... On another note, the various scripts that are supposed to be living in the /bin folder are not there ( to do with the promotion / demotion of the various DPM servers ); and, while on the same topic, the start-productionserver xxxx cmdlet has the most pathetic attempt at documentation ever. For instance, the -protectiontype switch, does not have ANY correspondig documentation about what the possible values are. there are some references in the corresponding script file (.ps1), but am I supposed to guess at values???? C'mon Microsoft, we certainly expect better of you than this.
    Monday, June 14, 2010 9:58 PM
  • Rick

    I think this is a documentation error on our part and we will fix it.

    For your combination of 64 bit DPM server and 32 bit exchange server, the KB, http://support.microsoft.com/default.aspx?scid=kb%3bEN-US%3b970640 mentions that you need to copy over the eseutil.exe and ese.dll to the DPM server, which is not the right solution and the reason why you are seeing the issue persist.

    The real issue is that exchange 2003 is not supported on 64 bit platforms, and there is no wow64 support as well, so the 32 executables will not work and error out on the 64 bit DPM server. To work around this problem, you should copy the 64 bit version of eseutil.exe and ese.dll from a higher version of exchange, either exchange 2007 or exchange 2010. These are backward compatible with exchange 2003.

     

    Take a look at this similar post

    http://www.eggheadcafe.com/software/aspnet/32149147/dpm-2007--exchange-2003.aspx

    See here for supported proc architecture for exchange server 2003

    http://www.msexchange.org/ExchangeNews/July-2005-Exchange-64-Bit-Support.html

     

    Hope this helps

    -Roopesh [MSFT]

     

    Tuesday, June 15, 2010 7:00 AM
    Moderator