none
Exchange backup takes too much time longer than 30hrs with HP Data Protector RRS feed

  • Question

  • When we back up Exchange 2010 edb with the HP data projector, it is through a network, not a SAN. Caused by what? In addition, full backups, which used to take only eight hours when first configured, take more than 30 hours to complete.

    To achieve maximum performance, a separate SAN switch is also provided and connected.

    • Moved by Manu Meng Thursday, November 15, 2018 6:34 AM Because it is
    Wednesday, November 14, 2018 7:01 AM

All replies

  • 1. I would ensure the backup is actually finishing successfully truncating your logs.  Just check your oldest log for the DB in question and also look at log count

    2. Define "When it was first configured" i.e. are we talking about days, a month, years

    3. How big was the EDB when it took 8 hours and how big is it now

    4. Has anything else changed in your network since it only took 8 hours? 


    Search, Recover, Export Mailboxes, Contacts, Calendars, Tasks from ALL versions of Exchange Offline EDB's, On-Premises Exchange Databases & Office 365. Export, Migrate/Recover into On-Premises Exchange Server, Office 365 with Lucid8's DigiScope

    Wednesday, November 14, 2018 2:16 PM
  • When we back up Exchange 2010 edb with the HP data projector, it is through a network, not a SAN. Caused by what? In addition, full backups, which used to take only eight hours when first configured, take more than 30 hours to complete.

    To achieve maximum performance, a separate SAN switch is also provided and connected.

    I would ask HP
    • Proposed as answer by Ed CrowleyMVP Wednesday, November 14, 2018 7:31 PM
    Wednesday, November 14, 2018 2:26 PM
  • I'm not familiar with HP data projector ( protector? ) but some basic backup questions

    1) Do other backups run normally, or do they all take a significantly longer time?

    2) Check what Troy was saying - did the logs get successfully truncated or is it timing out eventually?

    3) Do you have other SQL servers in your environment and are those logs getting successfully truncated during the backups?
    4) Have you checked the backup logs for exceptions?  I've seen behavior similar to this when the credentials being used for the backups have been modified.

    Wednesday, November 14, 2018 4:47 PM