On 2012-10-25 10:48, noob1321 wrote:
> Hey Guys,
> I have my Director, DB, and Storage on a server running CentOS 6. I
> am backing up a client over the network that is physically about 15
> miles away and is running a Windows 2008 R2 Small Business Server .
> I'm backing up 170 gigabytes. Right now the job has been running for
> 37 minutes and has backed up 394,920,354 bytes or 0.367798 gigabytes.
> It is processing at 181,739 bytes per second. Now that is only .17
> MB/s at this pace it is only backing up .6 Gigs per hour which means
> to back up 170Gigs will require nearly two weeks to complete. I
> understand this is a slow process but I mean there has to be
> something
> wrong if its at .17 MB/s!!!
>
> I do not have spooling enabled. I am backing up to file(my server), I
> am not using any compression in the FileSet Resource and I am using
> the MD5 signature.
>
> Please help me out here!!!
>
> Thanks,
> noob
>
You left out one key piece of information that I suspect could be the
bottle neck, which is the Link speed between the locations. If the link
speed is the issue, compression might actually improve the backup
performance as it will be done by the file daemon before transmitting
the data across the link, however this all depends on the nature of the
data and how well it compresses.
--
Thanks,
Dean E. Weimer
http://www.dweimer.net/
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
