> On 10/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi when backing-up my local host using .tar it would sometimes take 3 days > > or more. > > I only know this because of disk usage.the hd led is constantly on. It > > this normal?
I once experimented a lot with archiving the entire BackupPC data pool to tape (just tar'ing the whole thing up as one monolithic mass). Not exactly what you're doing, but it does provide a notable data point. - When I was using LVM snapshots, so that I didn't have to quiesce BackupPC, it would take 2 days to back up 200+GB. - When I stopped BackupPC before running the snapshot, let the tar command run, then re-started BackupPC afterwards, it took only perhaps 8 hours. The upshot of this is to check: - Are you using LVM snapshots of anything? (probably not, but just asking). - How many backup processes do you have going simultaneously? (the default of '4' is too high). - Is the box doing anything else disk or processor-intensive? - Are you hitting swap? - Is swap on a disk other than your BackupPC data pool? - Is your BackupPC data pool on its own disk? - Is your data pool filesystem mounted noatime? - If using Reiserfs for your data pool filesystem, is it mounted notail? - If using a journaled filesystem which supports this, is the journal on a device other than the data pool device? -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
