Jim Wilcoxson wrote:
> Hi Les - thanks for trying it out!
>
> It sounds like you are seeing about 300GB in 1200 minutes, or 4
> minutes per GB. That's about what I see on average when backing up a
> real system initially. Yesterday I backed up 33GB on a G5 Mac (the
> Mac version isn't released yet), and it took 110 minutes.
>
> However, incrementals are much faster: The incremental for the same
> Mac took 7 minutes. One of my Linux development systems (about 1.5GB)
> takes 4 minutes to backup initially, but only 20 seconds to do an
> incremental when just a few things change. I backup my /home/jim user
> directory, about 1.5GB, every 15 minutes and it usually takes 5-10
> seconds.
>
> You can restart the same backup and it will pick backup up where it
> left off after a short delay.
>
> Thanks again for checking it out! Much appreciated.
Unfortunately I was testing on the same disk where I do a weekly image
copy so I'll have to start over later - but I do have another place to
try it. What does it use to map the hardlinks internally? Is this
likely to remain correct if backuppc rebuilds collision chains in the
pool during a copy - or even before the next incremental?
Even if that is handled safely or the copy is made with backuppc
stopped, I expect a restore to take an impractical amount of time to
reconstruct all of the links - but I hope I'm wrong.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
