Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2004

    Unanswered: Strategy for nightly backups using ftp

    I am using SQL Server 2000 and trying to create a disaster recovery strategy that would run nightly and backup the database or at least the changes and would ftp these to a secure ftp site. For smaller database it is easy, I just take a full backup, zip up the file and ftp it to the secure backup site. This strategy does not work so well when the zipped up database is still close to 3GB. I have a pretty big window for doing everything but 3GB is just too much to ftp overnight. The recovery model is simple so the only other option seemed to be do a full backup once a month and take differentials nightly. The problem is I am offsight and the client may need to take a full backup during the day and my nightly differential would get screwed up.

    There is a fairly low volume of transactions so the idea of just doing nightly backups on the data that has changed is the obvious choice but differentials don't seem to fit. Any ideas?


  2. #2
    Join Date
    May 2003
    Rochester, NY


    ...just finished an evaluation of SQL LiteSpeed...while the setup of the product can and is cumbersome, the size reduction is real. My evaluation was based on 15 databases of varying size which averaged a 75% decrease in backup file size. Having this great of a reduction would help probably help you achieve the transfer size/times you'd like...

  3. #3
    Join Date
    Jul 2003
    San Antonio, TX
    You can look into striping backup. This way you get several files of much smaller size.
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts