nssbackup-team team mailing list archive

Thread
Date

Re: [Question #116342]: tar takes a long time, 100% CPU, with no output

To: nssbackup-team@xxxxxxxxxxxxxxxxxxx
From: Jean-Peer Lorenz <question116342@xxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 03 Jul 2010 17:57:09 -0000
Reply-to: question116342@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

Question #116342 on NSsbackup changed:
https://answers.launchpad.net/nssbackup/+question/116342

    Status: Open => Answered

Jean-Peer Lorenz proposed the following answer:
Hello,
do backups work for you again? You've written 'the first incremental backup this morning'; how long take the backups now?

I guess you are seeing a problematic behavior of tar here: in tests I
did on my machine I've seen similar things. Tar is creating the
incremental snapshot file (snar file) when using 100% cpu and the
files.tar.* file does not increase in size meanwhile. On my machine I
experienced 2 hours of preparation followed by 1 hour of data transfer.
I don't know exactly what's causing this exactly but I think it is quite
undesirable. IMO tar's incremental backup feature has some serious
drawbacks.

HTH.
Jean-Peer

-- 
You received this question notification because you are a member of
NSsbackup team, which is an answer contact for NSsbackup.