Post reply

SQL Backup path change from Local to Network

  • April 6, 2016 at 1:35 pm

    #309765

    What are the best practices to follow to backup dbs to UNC path.

    We are planning to remove local backup drives and backup to network across the environment.

    We have DBS from 5 GBs to 2 TBs. Clustered and Standalone environments. When we did a test backing up over the network, it is taking 20 times longer than local backup.

    Please share your thoughts on this.

  • April 6, 2016 at 2:31 pm

    #1870312

    best practice is still to use a local drive.

    that's the only drives you can consitently depend on exisitng, right?

    After creating the backup, you would want to compress the file if it is not created with compression, then move it to a network share;

    i use either built in compresison when it's an enterprise server, or 7zip and robocopy to zip and copy backups.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • April 6, 2016 at 2:44 pm

    #1870320

    Trust me, you do not want to back up to a UNC path. Not only is it far slower (as you have seen) but it is far less reliable. Often the OS network buffers are overwhelmed by the I/O that the backup generates, causing the backup to fail. The only way I have seen network-based backups succeed is if there is a third party backup agent that does the actual work; running over native Windows network structures is simply a bad idea for SQL backups.

  • April 6, 2016 at 4:19 pm

    #1870329

    Thanks Jeff.

  • April 6, 2016 at 4:20 pm

    #1870330

    Thanks Lowell.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply