• patrickmcginnis59 10839 (10/20/2016)


    Brandie Tarvin (10/20/2016)


    Jeff Moden (10/19/2016)


    Steve Jones - SSC Editor (10/19/2016)


    Jeff Moden (10/18/2016)


    Using compress backups and having a really good team that put together some remarkable hardware, I'm backing up 2.3 TeraBytes to Network Attached Storage (NAS) in 1 hour and 4 minutes. YMMV.

    Wow, that's impressive.

    I agree. I'm totally amazed myself. I don't know the particulars of how they did it but it has to do with some "Nimble" (brand name) hardware they bought. They're using it both for DR and backups. My hat's off to the folks in NetOps where I work. All I did was tweak the buffers settings on my backups and they did the rest. This used to take close to 6 hours... more if the system was under load.

    I'm betting they have de-dup technology they're using for your backups. That stuff changed the way we do our backups and also made them much faster.

    From what I've read, compressed backups don't play well with deduping technology.

    https://www.brentozar.com/archive/2009/11/why-dedupe-is-a-bad-idea-for-sql-server-backups/

    Thanks, Patrick. I'm thinking I have some alternative testing to do.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)