Guest Bill H Posted November 11, 2007 Posted November 11, 2007 I have a couple of ntbackup scripts written to automate the backup process. The main script (a .bat file) pauses a dbms, runs ntbackup, compresses the 4.5Gb backup file to 500MB, SFTPs the file to another server within our network, and emails me the results. This all works fine. It takes about 11 minutes to create a 4.5Gb backup file, which is ok, but it also takes about 40 minutes to compress this file, with WinRAR, down to 600Mb. In Linux I'd be able to pipe the backup through compression software so the compression happens at the same time as the backup and is just as fast as the "tar". I've been looking for some kind of reasonably priced backup software but can't find anything others generall recommend. Is there a way, or a product I can use, that can pipe ntbackup through compression in order to eliminate the additional 40 minutes spent compression the ntbackup file? Any assistance would be appreciated. Bill -- Bill
Guest Pegasus \(MVP\) Posted November 11, 2007 Posted November 11, 2007 Re: ntbackup compression "Bill H" <BillH@discussions.microsoft.com> wrote in message news:1553E517-226F-4ED5-A76A-6379BF2BCBED@microsoft.com... >I have a couple of ntbackup scripts written to automate the backup process. > The main script (a .bat file) pauses a dbms, runs ntbackup, compresses the > 4.5Gb backup file to 500MB, SFTPs the file to another server within our > network, and emails me the results. This all works fine. > > It takes about 11 minutes to create a 4.5Gb backup file, which is ok, but > it > also takes about 40 minutes to compress this file, with WinRAR, down to > 600Mb. In Linux I'd be able to pipe the backup through compression > software > so the compression happens at the same time as the backup and is just as > fast > as the "tar". > > I've been looking for some kind of reasonably priced backup software but > can't find anything others generall recommend. Is there a way, or a > product > I can use, that can pipe ntbackup through compression in order to > eliminate > the additional 40 minutes spent compression the ntbackup file? > > Any assistance would be appreciated. > > Bill > -- > Bill Since the compression phase takes 40 minutes, you will at best reduce your compression + backup time from 51 to 40 minutes when running the two processes concurrently. Seems hardly worth the trouble. You would save much more time if you could reduce your compression time from 40 to perhaps 10 minutes. In other words, its the compression process that costs you lots of time, not the lack of concurrency.
Guest Bill H Posted November 11, 2007 Posted November 11, 2007 Re: ntbackup compression In Linux (I hate to use this word), the backup and the "backup | compress" take about the same amount of time (11 minutes vs 12 minutes). WinRAR works much faster with smaller "source" files. So, what seems to be taking the time is that WinRAR, and other compression programs, start compressing an already created large file rather than simply building the compressed file "on the fly", so to speak. That's why I thought a "pipe" concept would work, or another product that does this. -- Bill "Pegasus (MVP)" wrote: > > "Bill H" <BillH@discussions.microsoft.com> wrote in message > news:1553E517-226F-4ED5-A76A-6379BF2BCBED@microsoft.com... > >I have a couple of ntbackup scripts written to automate the backup process. > > The main script (a .bat file) pauses a dbms, runs ntbackup, compresses the > > 4.5Gb backup file to 500MB, SFTPs the file to another server within our > > network, and emails me the results. This all works fine. > > > > It takes about 11 minutes to create a 4.5Gb backup file, which is ok, but > > it > > also takes about 40 minutes to compress this file, with WinRAR, down to > > 600Mb. In Linux I'd be able to pipe the backup through compression > > software > > so the compression happens at the same time as the backup and is just as > > fast > > as the "tar". > > > > I've been looking for some kind of reasonably priced backup software but > > can't find anything others generall recommend. Is there a way, or a > > product > > I can use, that can pipe ntbackup through compression in order to > > eliminate > > the additional 40 minutes spent compression the ntbackup file? > > > > Any assistance would be appreciated. > > > > Bill > > -- > > Bill > > Since the compression phase takes 40 minutes, you will at best > reduce your compression + backup time from 51 to 40 minutes > when running the two processes concurrently. Seems hardly > worth the trouble. You would save much more time if you could > reduce your compression time from 40 to perhaps 10 minutes. > In other words, its the compression process that costs you lots > of time, not the lack of concurrency. > > >
Guest Pegasus \(MVP\) Posted November 11, 2007 Posted November 11, 2007 Re: ntbackup compression Nothing wrong with other OSs . . . AFAIK, it is a characteristic of Linux that piped output from one command can be processed by the next command immediately. I don't think that Windows can do this. Maybe there are some file compressors that work faster with your files than WinRAR. You should also turn on hardware compression if your tape drive supports it. "Bill H" <BillH@discussions.microsoft.com> wrote in message news:808063BC-4B56-4CD2-9145-A855D0121A03@microsoft.com... > In Linux (I hate to use this word), the backup and the "backup | compress" > take about the same amount of time (11 minutes vs 12 minutes). WinRAR > works > much faster with smaller "source" files. So, what seems to be taking the > time is that WinRAR, and other compression programs, start compressing an > already created large file rather than simply building the compressed file > "on the fly", so to speak. > > That's why I thought a "pipe" concept would work, or another product that > does this. > -- > Bill > > > "Pegasus (MVP)" wrote: > >> >> "Bill H" <BillH@discussions.microsoft.com> wrote in message >> news:1553E517-226F-4ED5-A76A-6379BF2BCBED@microsoft.com... >> >I have a couple of ntbackup scripts written to automate the backup >> >process. >> > The main script (a .bat file) pauses a dbms, runs ntbackup, compresses >> > the >> > 4.5Gb backup file to 500MB, SFTPs the file to another server within our >> > network, and emails me the results. This all works fine. >> > >> > It takes about 11 minutes to create a 4.5Gb backup file, which is ok, >> > but >> > it >> > also takes about 40 minutes to compress this file, with WinRAR, down to >> > 600Mb. In Linux I'd be able to pipe the backup through compression >> > software >> > so the compression happens at the same time as the backup and is just >> > as >> > fast >> > as the "tar". >> > >> > I've been looking for some kind of reasonably priced backup software >> > but >> > can't find anything others generall recommend. Is there a way, or a >> > product >> > I can use, that can pipe ntbackup through compression in order to >> > eliminate >> > the additional 40 minutes spent compression the ntbackup file? >> > >> > Any assistance would be appreciated. >> > >> > Bill >> > -- >> > Bill >> >> Since the compression phase takes 40 minutes, you will at best >> reduce your compression + backup time from 51 to 40 minutes >> when running the two processes concurrently. Seems hardly >> worth the trouble. You would save much more time if you could >> reduce your compression time from 40 to perhaps 10 minutes. >> In other words, its the compression process that costs you lots >> of time, not the lack of concurrency. >> >> >>
Recommended Posts