Home Forums SQL Server 2005 Backups Backup speed depending on whether file already exists RE: Backup speed depending on whether file already exists

  • tim.nyland-jones (3/15/2013)


    Well, interesting findings over the past few days... it's not whether the file exists, it's all down to HyperBac compression...

    HyperBac off: Backups 400GB, 1.25 hours, read speed 100MBps, write speed 100MBps. (roughly)

    Hyperbac on: Backups 80GB, 2.5 hours, read speed 50MBps, write speed 8MBps (again, roughly).

    This is not the performance I've come to expect from HyperBac, anyone seen anything similar?

    (As it's now a product-specific question, I'll also post on the RedGate forums, but very interested to hear any similar experiences here)

    Used Hyperbac at a previous employer, the compressed backups ran in half the time of the uncompressed backups.

    Your times above, are they computed or did you get them from specific counters, just curious. At another previous employer they experienced a different problem with compressed backups. Sometimes they would report as failed even though the backup had actually completed. It turned out that part of the problem was that the estimated size of the backup file was much greater than the actual file size of the backup and the system was timing out while the OS reset the EOF for the file. The backups were being written to an EMC NAS.