>-----Original Message----- >From: Holger Parplies [mailto:[email protected]] >Sent: Friday, April 15, 2011 6:50 AM >To: [email protected]; General list for user discussion, questions >and support >Subject: Re: [BackupPC-users] How to restore an 8GB archive file? > >> >-----Original Message----- >> >From: Jeffrey J. Kosowsky [mailto:********@********.org] > >please don't do that. At least now I know why I'm getting spam to my >backuppc-list-only email address. > >> >To: General list for user discussion, questions and support > >Much better, though this address is probably less sensitive ... > >> >Cc: [email protected] > >Your problem :-).
I don't follow, don't do what?? >> OTOH, ext3 is said to have a max file size limit from about 16GB up to >> some 2TB, depending on block size. > >Several years ago, I worried about file sizes, too. It turned out to "just >work" even back then. I haven't encountered such limits in years. Then again, >on relevant file systems I don't tend to use ext3, because it *still* seems to >have occasional problems with online resizing (admittedly on a Debian etch >installation; might have gone away since). Huge files seem to go hand in hand >with online resizing requirements. I was limited to ext3 on the old backup server, as well as the hosts. The hosts were installed with CentOS 5.0 a few years back, at which time only ext3 was available as the most proven and stable file system. We will most probably go with ext4 when CentOS 6 is released, and we do a full fresh install of everything. >Sorin Srbu wrote on 2011-04-14 08:37:54 +0200 [Re: [BackupPC-users] How to >restore an 8GB archive file?]: >> [...] >> >From: Les Mikesell >> >Sent: Wednesday, April 13, 2011 5:10 PM >> >>> Why don't you just restore it back to his machine, using the typical >> >>> option 1? If BackupPC archived it in the first place, it can restore it >> >>> the same way. >> >> >> >> I've never had that option to work. This time I got a weird "unable to >> >read 4 bytes"-error when trying a direct restore. >> > >> >Usually that means the restore is configured to use ssh in some way, and >> >the ssh keys aren't set up correctly. Is there something different >> >about the way your restore command works? >> >> I do use passwordless login for the backups to work. The backup works fine >> using ssh this way; I don't get prompted for a password. >> >> Not sure though, how you mean different for restoring. Could you elaborate a >> bit? > >You've got it the wrong way around. *You* need to elaborate. What are your >RsyncClientCmd and RsyncClientRestoreCmd (it was rsync, wasn't it?)? If we >knew those, we could see what might be misconfigured or causing problems (or >what is even *involved* in backing up/restoring in your setup). Yes, rsync, I use the default settings. They seem to have worked fine, until now at least. RsyncClientCmd: $sshPath -q -x -l root $host $rsyncPath $argList+ RsyncClientRestoreCmd: $sshPath -q -x -l root $host $rsyncPath $argList+ >So let's get back to that topic, if you're still interested. I am. Would be nice to understand why things went kinda' pear-shaped at first. Sorry if I spaced out... I find linux, and BPC, somewhat frustrating sometime. 8-/ -- /Sorin ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
