From boxbackup at fluffy.co.uk Fri Jan 23 09:46:35 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Fri, 23 Jan 2004 09:46:35 +0000 Subject: [Box Backup] First test message Message-ID: <0834A75A-4D89-11D8-8BB3-003065F8EC8E@moomoo.org> Test From boxbackup at fluffy.co.uk Fri Jan 23 09:49:07 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Fri, 23 Jan 2004 09:49:07 +0000 Subject: [Box Backup] First test message In-Reply-To: <0834A75A-4D89-11D8-8BB3-003065F8EC8E@moomoo.org> References: <0834A75A-4D89-11D8-8BB3-003065F8EC8E@moomoo.org> Message-ID: <62E36351-4D89-11D8-8BB3-003065F8EC8E@fluffy.co.uk> Test reply On 23 Jan 2004, at 09:46, Ben Summers wrote: > > Test > > _______________________________________________ > boxbackup mailing list > boxbackup at fluffy.co.uk > http://lists.warhead.org.uk/mailman/listinfo/boxbackup > From boxbackup at fluffy.co.uk Fri Jan 23 09:52:52 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Fri, 23 Jan 2004 09:52:52 +0000 Subject: [Box Backup] Test three Message-ID: Test three From boxbackup at fluffy.co.uk Sat Jan 24 00:06:13 2004 From: boxbackup at fluffy.co.uk (Greg Fitzgerald) Date: Fri, 23 Jan 2004 19:06:13 -0500 Subject: [Box Backup] compile fail Message-ID: <20040124000613.GC10017@evilbint> Hi, Very interested in the backup tool. Great ideas from what i see. I just tried to compile the software on Gentoo Linux and ran into some errors. mkdir install/boxbackup-0.02-backup-client-Linux (cd bin/bbackupd; make RELEASE=1) make[1]: Entering directory `/mnt/home/gregf/boxbackup-0.02/bin/bbackupd' (cd ../../lib/common; make RELEASE=1 NODEPS=1) make[2]: Entering directory `/mnt/home/gregf/boxbackup-0.02/lib/common' g++ -DNDEBUG -O2 -Wall -DPLATFORM_LINUX -DPLATFORM_GCC3 -DBOX_VERSION="\"0.02\"" -c UnixUser.cpp -o ../../release/lib/common/UnixUser.o In file included from UnixUser.cpp:50: Box.h:167:27: warning: extra tokens at end of #undef directive UnixUser.cpp:119: error: default argument given for parameter 1 of `void UnixUser::ChangeProcessUser(bool)' UnixUser.h:64: error: after previous specification in `void UnixUser::ChangeProcessUser(bool)' make[2]: *** [../../release/lib/common/UnixUser.o] Error 1 make[2]: Leaving directory `/mnt/home/gregf/boxbackup-0.02/lib/common' make[1]: *** [dep_modules] Error 2 make[1]: Leaving directory `/mnt/home/gregf/boxbackup-0.02/bin/bbackupd' make: *** [install/boxbackup-0.02-backup-client-Linux.tgz] Error 2 --Greg From boxbackup at fluffy.co.uk Sat Jan 24 16:36:19 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Sat, 24 Jan 2004 16:36:19 +0000 Subject: [Box Backup] compile fail In-Reply-To: <20040124000613.GC10017@evilbint> References: <20040124000613.GC10017@evilbint> Message-ID: <703C3710-4E8B-11D8-99ED-003065F8EC8E@fluffy.co.uk> On 24 Jan 2004, at 00:06, Greg Fitzgerald wrote: > Hi, > > Very interested in the backup tool. Great ideas from what i see. > I just tried to compile the software on Gentoo Linux and ran > into some errors. Your particular version of GCC is less tolerant than mine! In lib/common/UnixUser.cpp, edit the line which reads void UnixUser::ChangeProcessUser(bool Temporary = false) to void UnixUser::ChangeProcessUser(bool Temporary) This is of course, an error on my part. I have changed it for the next version, but this sorts things out for this version. I've found getting things to work on Linux a bit of an experience. I've been writing for OpenBSD only for much of the project, and then when I decided to open source it, I then had to get it to work on other platforms. The infinite varieties of Linux have been entertaining. Thanks for trying it out -- I look forward to hearing about your experiences. Ben > > mkdir install/boxbackup-0.02-backup-client-Linux > (cd bin/bbackupd; make RELEASE=1) > make[1]: Entering directory > `/mnt/home/gregf/boxbackup-0.02/bin/bbackupd' > (cd ../../lib/common; make RELEASE=1 NODEPS=1) > make[2]: Entering directory `/mnt/home/gregf/boxbackup-0.02/lib/common' > g++ -DNDEBUG -O2 -Wall -DPLATFORM_LINUX -DPLATFORM_GCC3 > -DBOX_VERSION="\"0.02\"" -c UnixUser.cpp -o > ../../release/lib/common/UnixUser.o > In file included from UnixUser.cpp:50: > Box.h:167:27: warning: extra tokens at end of #undef directive > UnixUser.cpp:119: error: default argument given for parameter 1 of > `void > UnixUser::ChangeProcessUser(bool)' > UnixUser.h:64: error: after previous specification in `void > UnixUser::ChangeProcessUser(bool)' > make[2]: *** [../../release/lib/common/UnixUser.o] Error 1 > make[2]: Leaving directory `/mnt/home/gregf/boxbackup-0.02/lib/common' > make[1]: *** [dep_modules] Error 2 > make[1]: Leaving directory > `/mnt/home/gregf/boxbackup-0.02/bin/bbackupd' > make: *** [install/boxbackup-0.02-backup-client-Linux.tgz] Error 2 > > --Greg > _______________________________________________ > boxbackup mailing list > boxbackup at fluffy.co.uk > http://lists.warhead.org.uk/mailman/listinfo/boxbackup > From boxbackup at fluffy.co.uk Tue Jan 27 12:38:30 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Tue, 27 Jan 2004 09:38:30 -0300 (BRT) Subject: [Box Backup] Production use Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Ben. I'm currently installing a new CVS/Backup server in our corporation.=20 I'm thinking about using boxbackup to replace our poor rsync+scp=20 system. Our boxes are only BSD/Linux based, so no Windows adaptation=20 will be necessary (thank God!). We have about 30 servers, 90%=20 OpenBSD-based. Our system is snapshot-based, where every machine connects to the main=20 backup repository at each time, syncing the files using incremental=20 checks, checksums, preserving symlinks and permissions and backing up=20 on a weeekly-directory basis (rsync's 'backup-dir' option) + regex=20 exclusion of sockets and non-backupeable data. Will boxbackup suit my needs? Any Pros or Cons? For the community: What are your impressions about boxbackup? How=20 stable is it until now? =20 Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAFlvJpKK2uJoGDlMRAvpiAKCNG9Ibt67WOGDdCeMTHBAoi2937QCgsPlb WpPoDSmz0UbYmvuCPGR2QKE=3D =3D6qTK -----END PGP SIGNATURE----- From boxbackup at fluffy.co.uk Tue Jan 27 13:10:01 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Tue, 27 Jan 2004 13:10:01 +0000 Subject: [Box Backup] Production use In-Reply-To: References: Message-ID: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> On 27 Jan 2004, at 12:38, Eduardo Alvarenga wrote: > > I'm currently installing a new CVS/Backup server in our corporation. > I'm thinking about using boxbackup to replace our poor rsync+scp > system. Our boxes are only BSD/Linux based, so no Windows adaptation > will be necessary (thank God!). We have about 30 servers, 90% > OpenBSD-based. > > Our system is snapshot-based, where every machine connects to the main > backup repository at each time, syncing the files using incremental > checks, checksums, preserving symlinks and permissions and backing up > on a weeekly-directory basis (rsync's 'backup-dir' option) + regex > exclusion of sockets and non-backupeable data. > > Will boxbackup suit my needs? Any Pros or Cons? It will be a bit of a change in how your backups work. Instead of saying "take a snapshot now" the backup daemon uploads files as it notice changes, as long as those changes were made a configurable time ago. Future versions will allow a snapshot based approach in addition to this behaviour, but for now, you have to be aware that what you restore is not going to be what was on the disc at a particular moment in time (if you see what I mean). But you will have all your data backed up in a timely manner. Regex exclusion isn't done yet, but is not a big job. If you wanted to use this seriously, then I'll put it in as a priority item. Hard links are not handled (multiple copies of the same data would be made). Symlinks and UNIX attributes are. Checksums are intrinsic to the system. You get RAID on your backup server very cheaply and easily if you put in multiples of three discs. You probably need a less powerful machine to run the backup server. > > For the community: What are your impressions about boxbackup? How > stable is it until now? > I am taking the very conservative and cautious view that it is not ready for production machines, as it simply hasn't had enough testing. However, I would be very glad if people would test it, but I do not feel I can currently recommend using it as your only means of backup. However, I am working hard to get to a stage where I can recommend it's use. It would help me enormously if you would consider running it in parallel with your existing backup systems, and let me know how it works out. Thanks! Ben From boxbackup at fluffy.co.uk Tue Jan 27 13:18:56 2004 From: boxbackup at fluffy.co.uk (Jesus Climent) Date: Tue, 27 Jan 2004 14:18:56 +0100 Subject: [Box Backup] Production use In-Reply-To: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> Message-ID: <20040127131856.GY22435@reypastor.hispalinux.es> On Tue, Jan 27, 2004 at 01:10:01PM +0000, Ben Summers wrote: > > However, I am working hard to get to a stage where I can recommend it's > use. It would help me enormously if you would consider running it in > parallel with your existing backup systems, and let me know how it > works out. I am thinking about making a Debian package, and uploading it to the Debian repository. J -- Jesus Climent info:www.pumuki.org Unix SysAdm|Linux User #66350|Debian Developer|2.4.23|Helsinki Finland GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 There's nothing that can't be done. --McManus (The usual suspects) From boxbackup at fluffy.co.uk Tue Jan 27 13:18:58 2004 From: boxbackup at fluffy.co.uk (Jesus Climent) Date: Tue, 27 Jan 2004 14:18:58 +0100 Subject: [Box Backup] Production use In-Reply-To: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> Message-ID: <20040127131856.GY22435@reypastor.hispalinux.es> On Tue, Jan 27, 2004 at 01:10:01PM +0000, Ben Summers wrote: > > However, I am working hard to get to a stage where I can recommend it's > use. It would help me enormously if you would consider running it in > parallel with your existing backup systems, and let me know how it > works out. I am thinking about making a Debian package, and uploading it to the Debian repository. J -- Jesus Climent info:www.pumuki.org Unix SysAdm|Linux User #66350|Debian Developer|2.4.23|Helsinki Finland GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 There's nothing that can't be done. --McManus (The usual suspects) From boxbackup at fluffy.co.uk Tue Jan 27 13:47:05 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Tue, 27 Jan 2004 13:47:05 +0000 Subject: [Box Backup] New version released -- 0.03 Message-ID: <4B3D74DC-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> Hi, I've just uploaded a new release: * Improvements to the build system, especially configuring for random Linux systems. * Worked round an issue with the gcc 2.95.x libraries which meant that the backup daemon slowly used more and more memory. * Efficiency improvements. Given that the previous version had issues with memory allocation on non-gcc3 platforms, I recommend that you download and use this version as soon as you can. Hopefully this sorts out all the little things which you've so kindly reported to me over the last few days. Thanks for all your testing! Ben From boxbackup at fluffy.co.uk Tue Jan 27 13:49:13 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Tue, 27 Jan 2004 13:49:13 +0000 Subject: [Box Backup] Production use In-Reply-To: <20040127131856.GY22435@reypastor.hispalinux.es> References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> <20040127131856.GY22435@reypastor.hispalinux.es> Message-ID: <979F34EA-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> On 27 Jan 2004, at 13:18, Jesus Climent wrote: > On Tue, Jan 27, 2004 at 01:10:01PM +0000, Ben Summers wrote: >> >> However, I am working hard to get to a stage where I can recommend >> it's >> use. It would help me enormously if you would consider running it in >> parallel with your existing backup systems, and let me know how it >> works out. > > I am thinking about making a Debian package, and uploading it to the > Debian > repository. That would be very kind of you! Is it possible to mark packages as not recommended for production use? I wouldn't want people to mistakenly use a beta packages on a live system. Ben From boxbackup at fluffy.co.uk Tue Jan 27 14:05:50 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Tue, 27 Jan 2004 11:05:50 -0300 (BRT) Subject: [Box Backup] Production use In-Reply-To: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 27 Jan 2004, Ben Summers wrote: > > Our system is snapshot-based, where every machine connects to the > > main backup repository at each time, syncing the files using=20 > > incremental checks, checksums, preserving symlinks and permissions=20 > > and backing up on a weeekly-directory basis (rsync's 'backup-dir'=20 > > option) + regex exclusion of sockets and non-backupeable data. > > > > Will boxbackup suit my needs? Any Pros or Cons? >=20 > It will be a bit of a change in how your backups work. Instead of > saying "take a snapshot now" the backup daemon uploads files as it > notice changes, as long as those changes were made a configurable time > ago. Future versions will allow a snapshot based approach in addition > to this behaviour, but for now, you have to be aware that what you > restore is not going to be what was on the disc at a particular moment > in time (if you see what I mean). But you will have all your data > backed up in a timely manner. Is there any workaround to make weekly-{directory,files} backup? I=20 mean, a directory for each day-of-{week,month} where the files=20 (encrypted or not) are stored? This is confortable (at least for me) to retrieve any file revision=20 from the last week very easily. > Regex exclusion isn't done yet, but is not a big job. If you wanted to=20 > use this seriously, then I'll put it in as a priority item. Yes, this is serious. Many large temporary files may not be backuped.=20 So exclusions based on regex are very welcome. If you mind... please=20 keed it priority #1. > Hard links are not handled (multiple copies of the same data would be=20 > made). Symlinks and UNIX attributes are. Checksums are intrinsic to the= =20 > system. I hardly use hard links, so it'll not be a problem for me at all. > You get RAID on your backup server very cheaply and easily if you put=20 > in multiples of three discs. >=20 > You probably need a less powerful machine to run the backup server. Well, the machine is a development one, running mysql, apache, php, cvs and another tools. Any statistics about CPU/Memory usage of boxbackup? > > For the community: What are your impressions about boxbackup? How > > stable is it until now? > > > I am taking the very conservative and cautious view that it is not=20 > ready for production machines, as it simply hasn't had enough testing.=20 > However, I would be very glad if people would test it, but I do not=20 > feel I can currently recommend using it as your only means of backup. >=20 > However, I am working hard to get to a stage where I can recommend it's= =20 > use. It would help me enormously if you would consider running it in=20 > parallel with your existing backup systems, and let me know how it=20 > works out. Our backup system as noticed in the last message is poor. The current=20 backup machine is getting it's resources exausted and I'm going to=20 exchange it by this new one (more disk, more speed, more reliable). So=20 I'm looking for a better tool then ours. I'm seriously thinking about=20 boxbackup, for real. All I need to make it blow here: Regex exclusion and {daily,weekly}=20 based backup structure; as explained above. Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAFnBApKK2uJoGDlMRAupLAJ9j/LzG5u6uYzWxu0zJKFrbNljD4ACgvqo0 BNxYEAsqQayfb3/a7/Btqn4=3D =3D+h2+ -----END PGP SIGNATURE----- From boxbackup at fluffy.co.uk Tue Jan 27 14:08:14 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Tue, 27 Jan 2004 11:08:14 -0300 (BRT) Subject: [Box Backup] New version released -- 0.03 In-Reply-To: <4B3D74DC-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> References: <4B3D74DC-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 27 Jan 2004, Ben Summers wrote: > I've just uploaded a new release: [big-snip] Any AnonCVS server avaliable? CVS_RSH=3D/usr/bin/ssh is welcome ;-) Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAFnDQpKK2uJoGDlMRAgnWAJ0Qq7BsPHlXu6eu54Gxhxh8U9Ax4QCgwWDS fMFk7uh2q7WEn5qsp+53FGM=3D =3DiY1R -----END PGP SIGNATURE----- From boxbackup at fluffy.co.uk Tue Jan 27 13:51:59 2004 From: boxbackup at fluffy.co.uk (Jesus Climent) Date: Tue, 27 Jan 2004 14:51:59 +0100 Subject: [Box Backup] Production use In-Reply-To: <979F34EA-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> <20040127131856.GY22435@reypastor.hispalinux.es> <979F34EA-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> Message-ID: <20040127135159.GA22435@reypastor.hispalinux.es> On Tue, Jan 27, 2004 at 01:49:13PM +0000, Ben Summers wrote: > > >I am thinking about making a Debian package, and uploading it to the > >Debian repository. > > That would be very kind of you! > > Is it possible to mark packages as not recommended for production use? > I wouldn't want people to mistakenly use a beta packages on a live > system. It can be uploaded to experimental, the very-unstable branch of development. J -- Jesus Climent info:www.pumuki.org Unix SysAdm|Linux User #66350|Debian Developer|2.4.23|Helsinki Finland GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 I've decided what to do with my life. I wanna be a cleaner. --Mathilda (Leon, the Cleaner) From boxbackup at fluffy.co.uk Tue Jan 27 14:22:04 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Tue, 27 Jan 2004 14:22:04 +0000 Subject: [Box Backup] Production use In-Reply-To: <20040127135159.GA22435@reypastor.hispalinux.es> References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> <20040127131856.GY22435@reypastor.hispalinux.es> <979F34EA-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> <20040127135159.GA22435@reypastor.hispalinux.es> Message-ID: <2E223194-50D4-11D8-A33B-003065F8EC8E@fluffy.co.uk> On 27 Jan 2004, at 13:51, Jesus Climent wrote: > On Tue, Jan 27, 2004 at 01:49:13PM +0000, Ben Summers wrote: >> >>> I am thinking about making a Debian package, and uploading it to the >>> Debian repository. >> >> That would be very kind of you! >> >> Is it possible to mark packages as not recommended for production use? >> I wouldn't want people to mistakenly use a beta packages on a live >> system. > > It can be uploaded to experimental, the very-unstable branch of > development. Sounds perfect! Ben From boxbackup at fluffy.co.uk Tue Jan 27 14:50:09 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Tue, 27 Jan 2004 14:50:09 +0000 Subject: [Box Backup] New version released -- 0.03 In-Reply-To: References: <4B3D74DC-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> Message-ID: <1A9E34C9-50D8-11D8-A603-003065F8EC8E@fluffy.co.uk> On 27 Jan 2004, at 14:08, Eduardo Alvarenga wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 27 Jan 2004, Ben Summers wrote: > >> I've just uploaded a new release: > [big-snip] > > Any AnonCVS server avaliable? > > CVS_RSH=/usr/bin/ssh is welcome ;-) I'm afraid not. I don't think it's worth running one because * 408k downloads don't cause much of problem. * I don't have an anoncvs server installed already, and don't want to run "unnecessary" services with all their attendant potential security holes. * It doesn't fit in well with my development process, where I develop using a private CVS server and then use a script to generate the release archive. Although I'm willing to be persuaded otherwise. Ben From boxbackup at fluffy.co.uk Tue Jan 27 15:04:30 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Tue, 27 Jan 2004 12:04:30 -0300 (BRT) Subject: [Box Backup] New version released -- 0.03 In-Reply-To: <1A9E34C9-50D8-11D8-A603-003065F8EC8E@fluffy.co.uk> References: <4B3D74DC-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> <1A9E34C9-50D8-11D8-A603-003065F8EC8E@fluffy.co.uk> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 27 Jan 2004, Ben Summers wrote: > > CVS_RSH=3D/usr/bin/ssh is welcome ;-) >=20 > I'm afraid not. I don't think it's worth running one because >=20 > * 408k downloads don't cause much of problem. >=20 > * I don't have an anoncvs server installed already, and don't want to=20 > run "unnecessary" services with all their attendant potential security=20 > holes. >=20 > * It doesn't fit in well with my development process, where I develop=20 > using a private CVS server and then use a script to generate the=20 > release archive. >=20 > Although I'm willing to be persuaded otherwise. Hmm... #1: Make a daily "boxbackup-current.tar.gz" file. #2: Every log message in your commits *may* be sent to a mailling list. #3: CVSweb? Rsync ? Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAFn4ApKK2uJoGDlMRAvlRAJ9ZydLhdhHZBCvQaw4UROgwgTGq9gCffQil s7W+Fm6MdEPyRUx5lSxpnm4=3D =3DoEA0 -----END PGP SIGNATURE----- From boxbackup at fluffy.co.uk Tue Jan 27 15:14:30 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Tue, 27 Jan 2004 15:14:30 +0000 Subject: [Box Backup] New version released -- 0.03 In-Reply-To: References: <4B3D74DC-50CF-11D8-A33B-003065F8EC8E@fluffy.co.uk> <1A9E34C9-50D8-11D8-A603-003065F8EC8E@fluffy.co.uk> Message-ID: <8124438B-50DB-11D8-A603-003065F8EC8E@fluffy.co.uk> On 27 Jan 2004, at 15:04, Eduardo Alvarenga wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 27 Jan 2004, Ben Summers wrote: > >>> CVS_RSH=/usr/bin/ssh is welcome ;-) >> >> I'm afraid not. I don't think it's worth running one because >> >> * 408k downloads don't cause much of problem. >> >> * I don't have an anoncvs server installed already, and don't want to >> run "unnecessary" services with all their attendant potential security >> holes. >> >> * It doesn't fit in well with my development process, where I develop >> using a private CVS server and then use a script to generate the >> release archive. >> >> Although I'm willing to be persuaded otherwise. > > Hmm... > > #1: Make a daily "boxbackup-current.tar.gz" file. > #2: Every log message in your commits *may* be sent to a mailling > list. > #3: CVSweb? Rsync ? Given that this is a backup system, and that I wouldn't be happy with anyone running a snapshot which has not received much testing, what benefits would this bring to users? I don't have any other developers working on this. Ben From boxbackup at fluffy.co.uk Tue Jan 27 15:29:11 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Tue, 27 Jan 2004 15:29:11 +0000 Subject: [Box Backup] Production use In-Reply-To: References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> Message-ID: <8EADFF2B-50DD-11D8-A603-003065F8EC8E@fluffy.co.uk> On 27 Jan 2004, at 14:05, Eduardo Alvarenga wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 27 Jan 2004, Ben Summers wrote: > >>> Our system is snapshot-based, where every machine connects to the >>> main backup repository at each time, syncing the files using >>> incremental checks, checksums, preserving symlinks and permissions >>> and backing up on a weeekly-directory basis (rsync's 'backup-dir' >>> option) + regex exclusion of sockets and non-backupeable data. >>> >>> Will boxbackup suit my needs? Any Pros or Cons? >> >> It will be a bit of a change in how your backups work. Instead of >> saying "take a snapshot now" the backup daemon uploads files as it >> notice changes, as long as those changes were made a configurable time >> ago. Future versions will allow a snapshot based approach in addition >> to this behaviour, but for now, you have to be aware that what you >> restore is not going to be what was on the disc at a particular moment >> in time (if you see what I mean). But you will have all your data >> backed up in a timely manner. > > Is there any workaround to make weekly-{directory,files} backup? I > mean, a directory for each day-of-{week,month} where the files > (encrypted or not) are stored? Not really, without loosing all the efficiency gains. As it's so completely against the basic design, it's not really worth thinking about. > > This is confortable (at least for me) to retrieve any file revision > from the last week very easily. This is what you can do now to view and retrieve an old version: ======================================================================== == /usr/local/bin/bbackupquery query > cd home/profiles/USERNAME query > list -ot 00000078 f--o- 2004-01-21T20:17:48 NTUSER.DAT 00000079 f--o- 2004-01-21T20:17:48 ntuser.dat.LOG 0000007a f--o- 2004-01-21T17:55:12 ntuser.ini 0000007b f---- 2004-01-12T15:32:00 ntuser.pol 0000007c -d--- 1970-01-01T00:00:00 Templates 00000089 -d--- 1970-01-01T00:00:00 Start Menu 000000a0 -d--- 1970-01-01T00:00:00 SendTo 000000a6 -d--- 1970-01-01T00:00:00 Recent 00000151 -d--- 1970-01-01T00:00:00 PrintHood 00000152 -d--- 1970-01-01T00:00:00 NetHood 00000156 -d--- 1970-01-01T00:00:00 My Documents 0000018d -d--- 1970-01-01T00:00:00 Favorites 00000215 -d--- 1970-01-01T00:00:00 Desktop 00000219 -d--- 1970-01-01T00:00:00 Cookies 0000048b -d--- 1970-01-01T00:00:00 Application Data 000005da -d--- 1970-01-01T00:00:00 UserData 0000437e f--o- 2004-01-24T02:45:43 NTUSER.DAT 0000437f f--o- 2004-01-24T02:45:43 ntuser.dat.LOG 00004380 f--o- 2004-01-23T17:01:29 ntuser.ini 00004446 f--o- 2004-01-24T02:45:43 NTUSER.DAT 00004447 f--o- 2004-01-24T02:45:43 ntuser.dat.LOG 000045f4 f---- 2004-01-26T15:54:16 NTUSER.DAT 000045f5 f---- 2004-01-26T15:54:16 ntuser.dat.LOG 000045f6 f---- 2004-01-26T16:54:31 ntuser.ini query > get -i 0000437e NTUSER.DAT Object ID 0000437e fetched sucessfully. ======================================================================== == Basically, list the directory with o and t options, which displays the time and doesn't filter out old version, find the ID number of the file you want, and fetch that. (using the name only fetches the latest version) Fetching an entire directory isn't easy at the moment, as restore to snapshots is required for that. What I'm planning to do is to be able to do a "show snapshots" command, which lists all the snapshots on the server, then a "select snapshot", and then all the queries and restores you do relate to that. The design is there, and it's all built to do this, just a matter of implementing that last bit of code which actually does the magic! > >> Regex exclusion isn't done yet, but is not a big job. If you wanted to >> use this seriously, then I'll put it in as a priority item. > > Yes, this is serious. Many large temporary files may not be backuped. > So exclusions based on regex are very welcome. If you mind... please > keed it priority #1. Not a problem. It's now next on the list! > >> Hard links are not handled (multiple copies of the same data would be >> made). Symlinks and UNIX attributes are. Checksums are intrinsic to >> the >> system. > > I hardly use hard links, so it'll not be a problem for me at all. > >> You get RAID on your backup server very cheaply and easily if you put >> in multiples of three discs. >> >> You probably need a less powerful machine to run the backup server. > > Well, the machine is a development one, running mysql, apache, php, > cvs > and another tools. Any statistics about CPU/Memory usage of boxbackup? Nothing terribly meaningful. Here's one I made earlier: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 11081 0.0 0.9 2172 3052 ?? I 11:29AM 0:05.05 bbackupd: idle (bbackupd) Memory usage is in the order of a few Mb, rather than hundred of Mb. Depends on how many directories (not files) you have. And it will get less as I go forward, as there are a load of optimisations I know I can make. CPU usage is fairly minimal, it's basically all I/O bound (usually network). There's no reason you couldn't nice it a bit if it were a problem. > >>> For the community: What are your impressions about boxbackup? How >>> stable is it until now? >>> >> I am taking the very conservative and cautious view that it is not >> ready for production machines, as it simply hasn't had enough testing. >> However, I would be very glad if people would test it, but I do not >> feel I can currently recommend using it as your only means of backup. >> >> However, I am working hard to get to a stage where I can recommend >> it's >> use. It would help me enormously if you would consider running it in >> parallel with your existing backup systems, and let me know how it >> works out. > > Our backup system as noticed in the last message is poor. The current > backup machine is getting it's resources exausted and I'm going to > exchange it by this new one (more disk, more speed, more reliable). So > I'm looking for a better tool then ours. I'm seriously thinking about > boxbackup, for real. > > All I need to make it blow here: Regex exclusion and {daily,weekly} > based backup structure; as explained above. Splendid. How long have I got? :-) Ben From boxbackup at fluffy.co.uk Tue Jan 27 15:51:59 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Tue, 27 Jan 2004 12:51:59 -0300 (BRT) Subject: [Box Backup] Production use In-Reply-To: <8EADFF2B-50DD-11D8-A603-003065F8EC8E@fluffy.co.uk> References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> <8EADFF2B-50DD-11D8-A603-003065F8EC8E@fluffy.co.uk> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 27 Jan 2004, Ben Summers wrote: > >> notice changes, as long as those changes were made a configurable > >> time ago. Future versions will allow a snapshot based approach in > >> addition to this behaviour, but for now, you have to be aware that > >> what you restore is not going to be what was on the disc at a > >> particular moment in time (if you see what I mean). But you will > >> have all your data backed up in a timely manner. > > > > Is there any workaround to make weekly-{directory,files} backup? I > > mean, a directory for each day-of-{week,month} where the files > > (encrypted or not) are stored? >=20 > Not really, without loosing all the efficiency gains. As it's so > completely against the basic design, it's not really worth thinking > about. > > > > This is confortable (at least for me) to retrieve any file revision > > from the last week very easily. >=20 > This is what you can do now to view and retrieve an old version: [snip] That's awesome ;-). It really DO suit my needs.=20 =20 > What I'm planning to do is to be able to do a "show snapshots" > command, which lists all the snapshots on the server, then a "select > snapshot", and then all the queries and restores you do relate to > that. >=20 > The design is there, and it's all built to do this, just a matter of =20 > implementing that last bit of code which actually does the magic! Well, a snapshot-based option will be very pleased on full system=20 emergency recoveries. Normally i'll be using it when the data is lost=20 or the client hard disk fails. > >> Regex exclusion isn't done yet, but is not a big job. If you wanted to > >> use this seriously, then I'll put it in as a priority item. > > > > Yes, this is serious. Many large temporary files may not be backuped. > > So exclusions based on regex are very welcome. If you mind... please > > keed it priority #1. >=20 > Not a problem. It's now next on the list! Okay, when regex is ok i'll start installing boxbackup... [snip] > >> However, I am working hard to get to a stage where I can recommend > >> it's use. It would help me enormously if you would consider running > >> it in parallel with your existing backup systems, and let me know > >> how it works out. > > > > Our backup system as noticed in the last message is poor. The current > > backup machine is getting it's resources exausted and I'm going to > > exchange it by this new one (more disk, more speed, more reliable). So > > I'm looking for a better tool then ours. I'm seriously thinking about > > boxbackup, for real. > > > > All I need to make it blow here: Regex exclusion and {daily,weekly} > > based backup structure; as explained above. >=20 > Splendid. How long have I got? :-) Hm... not so much time. Actually I'm just waiting for our developers to=20 commit their changes our CVS/Backup server to migrate information to=20 the new system. It should not take more than 2-3 days. Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAFokhpKK2uJoGDlMRAjhiAJwJKT77ITPFgj/uffaZfRsbLeyUmwCeJqeh WwONdziS8OYikH9iYsfBY3k=3D =3DhTHp -----END PGP SIGNATURE----- From boxbackup at fluffy.co.uk Tue Jan 27 16:52:42 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Tue, 27 Jan 2004 16:52:42 +0000 Subject: [Box Backup] Production use In-Reply-To: References: <1D714728-50CA-11D8-A33B-003065F8EC8E@fluffy.co.uk> <8EADFF2B-50DD-11D8-A603-003065F8EC8E@fluffy.co.uk> Message-ID: <393FA262-50E9-11D8-A603-003065F8EC8E@fluffy.co.uk> On 27 Jan 2004, at 15:51, Eduardo Alvarenga wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 27 Jan 2004, Ben Summers wrote: > >>>> notice changes, as long as those changes were made a configurable >>>> time ago. Future versions will allow a snapshot based approach in >>>> addition to this behaviour, but for now, you have to be aware that >>>> what you restore is not going to be what was on the disc at a >>>> particular moment in time (if you see what I mean). But you will >>>> have all your data backed up in a timely manner. >>> >>> Is there any workaround to make weekly-{directory,files} backup? I >>> mean, a directory for each day-of-{week,month} where the files >>> (encrypted or not) are stored? >> >> Not really, without loosing all the efficiency gains. As it's so >> completely against the basic design, it's not really worth thinking >> about. >>> >>> This is confortable (at least for me) to retrieve any file revision >>> from the last week very easily. >> >> This is what you can do now to view and retrieve an old version: > [snip] > > That's awesome ;-). It really DO suit my needs. Great. I will pop that little example on the web site. > >> What I'm planning to do is to be able to do a "show snapshots" >> command, which lists all the snapshots on the server, then a "select >> snapshot", and then all the queries and restores you do relate to >> that. >> >> The design is there, and it's all built to do this, just a matter of >> implementing that last bit of code which actually does the magic! > > Well, a snapshot-based option will be very pleased on full system > emergency recoveries. Normally i'll be using it when the data is lost > or the client hard disk fails. I didn't think it was *that* vital, which is why I haven't quite got around to implementing it. > >>>> Regex exclusion isn't done yet, but is not a big job. If you wanted >>>> to >>>> use this seriously, then I'll put it in as a priority item. >>> >>> Yes, this is serious. Many large temporary files may not be >>> backuped. >>> So exclusions based on regex are very welcome. If you mind... please >>> keed it priority #1. >> >> Not a problem. It's now next on the list! > > Okay, when regex is ok i'll start installing boxbackup... > > [snip] >>>> However, I am working hard to get to a stage where I can recommend >>>> it's use. It would help me enormously if you would consider running >>>> it in parallel with your existing backup systems, and let me know >>>> how it works out. >>> >>> Our backup system as noticed in the last message is poor. The >>> current >>> backup machine is getting it's resources exausted and I'm going to >>> exchange it by this new one (more disk, more speed, more reliable). >>> So >>> I'm looking for a better tool then ours. I'm seriously thinking >>> about >>> boxbackup, for real. >>> >>> All I need to make it blow here: Regex exclusion and {daily,weekly} >>> based backup structure; as explained above. >> >> Splendid. How long have I got? :-) > > Hm... not so much time. Actually I'm just waiting for our developers > to > commit their changes our CVS/Backup server to migrate information to > the new system. It should not take more than 2-3 days. I should have a private snapshot for you within that time limit. :-) Ben From boxbackup at fluffy.co.uk Wed Jan 28 05:30:55 2004 From: boxbackup at fluffy.co.uk (Pascal Lalonde) Date: Wed, 28 Jan 2004 00:30:55 -0500 Subject: [Box Backup] Error messages at execution Message-ID: <20040128053055.GA22473@plasma.doom.und> First of all, I didn't succeed in running bbstored on an OpenBSD 3.3 box. I keep getting an 'Exception: RaidFile (2/8)' when trying to create an account. So I decided to try on a 3.4 box, although I'm not root on this one. So I modified all the paths in the .h files from /etc/box to /home/plalonde/etc/box. I compiled everything, and the installation went all fine. But when I execute bbstored, I get: 'bbstored: exception Common (1/2)'. My setups are all with RAID disabled, since I don't have many hard discs to do my tests. The thing is, the exception messages are not quite "revealing" ;-) I tried to gdb bbstored, but I couldn't get it to match the executable with the source files. So I'm quite stuck. And I generated my certificates by hand, like this: openssl req -newkey rsa:2048 -nodes -keyout domain.com-key.pem -keyform PEM -out domain.com-csr.pem -outform PEM and I signed it with my already-existing test CA key: openssl ca -in domain.com-csr.pem and copied the resulting certificate as clientCA.pem How do you usually debug boxbackup? And, do you know what these exceptions mean? Here is my raidfile.conf: ---- disc0 { SetNumber = 0 BlockSize = 2048 Dir0 = /home/plalonde/bbackup Dir1 = /home/plalonde/bbackup Dir2 = /home/plalonde/bbackup } ---- And my bbstored.conf: ---- RaidFileConf = /home/plalonde/etc/box/raidfile.conf AccountDatabase = /home/plalonde/etc/box/bbstored/accounts.txt TimeBetweenHousekeeping = 900 Server { PidFile = /var/run/bbstored.pid User = plalonde ListenAddresses = inet:domain.com CertificateFile = /home/plalonde/etc/box/bbstored/domain.com-cert.pem PrivateKeyFile = /home/plalonde/etc/box/bbstored/domain.com-key.pem TrustedCAsFile = /home/plalonde/etc/box/bbstored/clientCA.pem } ---- Output of 'bbstoreaccounts info 1': ---- Account ID: 00000001 Last object ID: 1 Blocks used: 2 Blocks used by old files: 0 Blocks used by deleted files: 0 Blocks used by directories: 2 Block soft limit: 841061 Block hard limit: 1041061 Client store marker: 0 ---- I know I don't have what could be called "standard setups"... :) Thanks, Pascal Lalonde From boxbackup at fluffy.co.uk Wed Jan 28 08:29:39 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Wed, 28 Jan 2004 08:29:39 +0000 Subject: [Box Backup] Error messages at execution In-Reply-To: <20040128053055.GA22473@plasma.doom.und> References: <20040128053055.GA22473@plasma.doom.und> Message-ID: <1D4A646A-516C-11D8-8F43-003065F8EC8E@fluffy.co.uk> On 28 Jan 2004, at 05:30, Pascal Lalonde wrote: > > First of all, I didn't succeed in running bbstored on an OpenBSD 3.3 > box. I keep getting an 'Exception: RaidFile (2/8)' when trying to > create > an account. Does the directory you specified to raidfile-config have write permissions for the user you're running bbstored under? > > So I decided to try on a 3.4 box, although I'm not root on this one. So > I modified all the paths in the .h files from /etc/box to > /home/plalonde/etc/box. I compiled everything, and the installation > went > all fine. But when I execute bbstored, I get: 'bbstored: exception > Common > (1/2)'. This probably means that it can't find the configuration file. > > My setups are all with RAID disabled, since I don't have many hard > discs > to do my tests. > > The thing is, the exception messages are not quite "revealing" ;-) > I tried to gdb bbstored, but I couldn't get it to match the executable > with the source files. So I'm quite stuck. You need to look for RaidFileException.h (for RaidFile exceptions, and so on) which will tell you what the codes mean. The release versions don't include the necessary symbols for gdb to work properly. > > And I generated my certificates by hand, like this: > openssl req -newkey rsa:2048 -nodes -keyout domain.com-key.pem -keyform > PEM -out domain.com-csr.pem -outform PEM Did bbstored-config not work? > > and I signed it with my already-existing test CA key: > > openssl ca -in domain.com-csr.pem > > and copied the resulting certificate as clientCA.pem Shouldn't that be domain.com-cert.pem ? clientCA.pem is the certificate used to validate incoming client connections. > > > > How do you usually debug boxbackup? I use the unit tests in debug mode, generally. Although in this case, just running in debug mode would be helpful -- you can use gdb, and exceptions give much more information. > And, do you know what these > exceptions mean? 1/2 -- can't open file 2/8 -- raid file system encountered an os error > > Here is my raidfile.conf: > [snip] > > I know I don't have what could be called "standard setups"... Firstly... let's try using the standard code but pointing it at different directories. Start again from the distribution archive (without your modifications) and build a new version. Use the installation scripts as described in the documentation, but whereever they say "/etc/box", put "/home/plalonde/etc/box" Use the bbstored-certs script to generate a certification authority. Sign the CSR generated with bbstored-config. (Make sure you follow instructions for both of them). Edit the bbstored.conf file to remove the "User = plalonde" line, and change the "PidFile = /var/run/bbstored.pid" to be a file somewhere you have permission to write. (I suspect this is the problem which is stopping this working.) "domain.com" needs to be the actual hostname of the machine, or "localhost" for testing locally. Start it up with bbstored /home/plalonde/etc/box/bbstored.conf When you use bbstoredaccounts, do something like bbstoredaccount -c /home/plalonde/etc/box/bbstored.conf info 1 Both of these variations specify an alternative configuration file -- I need this facility to be able to run them in the tests. If this doesn't help, then build and use the debug versions. To build a debug bbstored, do cd bin/bbstored make (make defaults to debug version in the module directories) Then use the bbstored exe from debug/bin/bbstored to test things. You should get more helpful error messages. Ben From boxbackup at fluffy.co.uk Wed Jan 28 15:36:30 2004 From: boxbackup at fluffy.co.uk (Ben Lovett) Date: Wed, 28 Jan 2004 07:36:30 -0800 Subject: [Box Backup] Debugging boxbackup Message-ID: Hi, I'm trying to get boxbackup 0.03 building / running properly on OpenBSD/sparc64. The machine in question is running -current (gcc3 from base..) It builds fine, but as I go through the setup steps, create certificates, add certificates, I run into problems. prozac% sudo /usr/local/bin/bbstoreaccounts # yes, it aborts even with the args zsh: 10724 abort sudo /usr/local/bin/bbstoreaccounts I tried this patch -- --- makebuildenv.pl.orig 2004-01-27 20:52:59.000000000 -0800 +++ makebuildenv.pl 2004-01-27 20:53:05.000000000 -0800 @@ -443,7 +443,7 @@ __E # CXX = g++ .ifdef RELEASE -CXXFLAGS = -DNDEBUG -O2 -Wall $include_paths -D$platform_define$extra_platform_ defines -DBOX_VERSION="\\"$product_version\\"" +CXXFLAGS = -g -O2 -Wall $include_paths -D$platform_define$extra_platform_defines -D BOX_VERSION="\\"$product_version\\"" OUTBASE = ../../release OUTDIR = ../../release/$mod DEPENDMAKEFLAGS = -D RELEASE and that ended up making the build fail due to missing symbols (lib/debug) stuff.. Ben, what are you doing to enable debugging? Maybe I'm just missing it... thanks, --ben From boxbackup at fluffy.co.uk Wed Jan 28 17:39:33 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Wed, 28 Jan 2004 17:39:33 +0000 Subject: [Box Backup] Debugging boxbackup In-Reply-To: References: Message-ID: On 28 Jan 2004, at 15:36, Ben Lovett wrote: > Hi, > > I'm trying to get boxbackup 0.03 building / running properly on > OpenBSD/sparc64. The machine in question is running -current (gcc3 > from base..) > > It builds fine, but as I go through the setup steps, create > certificates, add certificates, I run into problems. > > prozac% sudo /usr/local/bin/bbstoreaccounts # yes, it aborts even with > the args > zsh: 10724 abort sudo /usr/local/bin/bbstoreaccounts > > I tried this patch -- > --- makebuildenv.pl.orig 2004-01-27 20:52:59.000000000 -0800 > +++ makebuildenv.pl 2004-01-27 20:53:05.000000000 -0800 > @@ -443,7 +443,7 @@ __E > # > CXX = g++ > .ifdef RELEASE > -CXXFLAGS = -DNDEBUG -O2 -Wall $include_paths > -D$platform_define$extra_platform_ > defines -DBOX_VERSION="\\"$product_version\\"" > +CXXFLAGS = -g -O2 -Wall $include_paths > -D$platform_define$extra_platform_defines -D > BOX_VERSION="\\"$product_version\\"" > OUTBASE = ../../release > OUTDIR = ../../release/$mod > DEPENDMAKEFLAGS = -D RELEASE > > and that ended up making the build fail due to missing symbols > (lib/debug) stuff.. > > Ben, what are you doing to enable debugging? Maybe I'm just missing > it... To build, say, bbstoreaccounts in debug mode, simply do cd bin/bbstoreaccounts make Then you'll find the debug exe in debug/bin/bbstoreaccounts. (I default to debug mode as that's the one I use most.) Of course, typing make at top level does release mode -- this effectively does cd bin/bbstoreaccounts make -D RELEASE (the release exe goes in release/bin/bbstoreaccounts) There are some programmer's notes in the "notes" directory. I'm very curious about where the abort happens. Thanks for trying it on an unusual platform! Ben From boxbackup at fluffy.co.uk Wed Jan 28 20:46:08 2004 From: boxbackup at fluffy.co.uk (Ben Lovett) Date: Wed, 28 Jan 2004 12:46:08 -0800 Subject: [Box Backup] Debugging boxbackup In-Reply-To: References: Message-ID: <20040128204608.GA31679@tilderoot.com> On Wed, Jan 28, 2004 at 05:39:33PM +0000, Ben Summers wrote: > I'm very curious about where the abort happens. Thanks for trying it on > an unusual platform! Starting program: /usr/obj/ports/boxbackup-0.03/boxbackup-0.03/debug/bin/bbstoreaccounts/bbstoreaccounts create 1 0 2097152 2306867 Program received signal SIGSEGV, Segmentation fault. 0x000000000016bc48 in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::lower_bound(void* const&) (this=0x30ffffffffffffdf, __k=@0xe0ffffffffffffa7) at /usr/include/g++/bits/stl_tree.h:1320 1320 _Link_type __x = _M_root(); /* Current node. */ (gdb) where #0 0x000000000016bc48 in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::lower_bound(void* const&) (this=0x30ffffffffffffdf, __k=@0xe0ffffffffffffa7) at /usr/include/g++/bits/stl_tree.h:1320 #1 0x000000000016bba4 in std::map, std::allocator > >::lower_bound(void* const&) (this=0x30ffffffffffffdf, __x=@0xe0ffffffffffffa7) at /usr/include/g++/bits/stl_map.h:508 #2 0x000000000016ba28 in std::map, std::allocator > >::operator[](void* const&) (this=0xffffffffffffa8, __k=@0x30ffffffffffffdf) at /usr/include/g++/bits/stl_map.h:316 My C++ is very rusty, so I'm afraid I won't be much use here ... --ben From boxbackup at fluffy.co.uk Wed Jan 28 21:08:53 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Wed, 28 Jan 2004 21:08:53 +0000 Subject: [Box Backup] Debugging boxbackup In-Reply-To: <20040128204608.GA31679@tilderoot.com> References: <20040128204608.GA31679@tilderoot.com> Message-ID: <2D8E4060-51D6-11D8-A154-003065F8EC8E@fluffy.co.uk> On 28 Jan 2004, at 20:46, Ben Lovett wrote: > On Wed, Jan 28, 2004 at 05:39:33PM +0000, Ben Summers wrote: >> I'm very curious about where the abort happens. Thanks for trying it >> on >> an unusual platform! > > Starting program: > /usr/obj/ports/boxbackup-0.03/boxbackup-0.03/debug/bin/ > bbstoreaccounts/bbstoreaccounts create 1 0 2097152 2306867 > > Program received signal SIGSEGV, Segmentation fault. > 0x000000000016bc48 in std::_Rb_tree MallocBlockInfo>, std::_Select1st MallocBlockInfo> >, std::less, std::allocator const, MallocBlockInfo> > >::lower_bound(void* const&) > (this=0x30ffffffffffffdf, __k=@0xe0ffffffffffffa7) > at /usr/include/g++/bits/stl_tree.h:1320 > 1320 _Link_type __x = _M_root(); /* Current node. */ > (gdb) where > #0 0x000000000016bc48 in std::_Rb_tree MallocBlockInfo>, std::_Select1st MallocBlockInfo> >, std::less, std::allocator const, MallocBlockInfo> > >::lower_bound(void* const&) > (this=0x30ffffffffffffdf, __k=@0xe0ffffffffffffa7) > at /usr/include/g++/bits/stl_tree.h:1320 > #1 0x000000000016bba4 in std::map std::less, std::allocator MallocBlockInfo> > >::lower_bound(void* const&) > (this=0x30ffffffffffffdf, __x=@0xe0ffffffffffffa7) > at /usr/include/g++/bits/stl_map.h:508 > #2 0x000000000016ba28 in std::map std::less, std::allocator MallocBlockInfo> > >::operator[](void* const&) (this=0xffffffffffffa8, > __k=@0x30ffffffffffffdf) > at /usr/include/g++/bits/stl_map.h:316 > > My C++ is very rusty, so I'm afraid I won't be much use here ... Well it looks to me like the compiler is generating bad code -- the error is deep in the STL, which is nothing at all to do with me. I wonder if you're using the 2.95.x STL with the 3.x compiler? Is there a test suite for g++ you can try out to see if your install is OK? Ben From boxbackup at fluffy.co.uk Wed Jan 28 22:36:06 2004 From: boxbackup at fluffy.co.uk (Ben Lovett) Date: Wed, 28 Jan 2004 14:36:06 -0800 Subject: [Box Backup] Debugging boxbackup In-Reply-To: <2D8E4060-51D6-11D8-A154-003065F8EC8E@fluffy.co.uk> References: <20040128204608.GA31679@tilderoot.com> <2D8E4060-51D6-11D8-A154-003065F8EC8E@fluffy.co.uk> Message-ID: <20040128223606.GA12828@tilderoot.com> On Wed, Jan 28, 2004 at 09:08:53PM +0000, Ben Summers wrote: > Well it looks to me like the compiler is generating bad code -- the > error is deep in the STL, which is nothing at all to do with me. > > I wonder if you're using the 2.95.x STL with the 3.x compiler? > > Is there a test suite for g++ you can try out to see if your install is > OK? > > Ben Is this of any use? Core generated using the "installed" version of bbstoreaccounts, dump used with the debugging version.. Core was generated by `bbstoreaccounts'. Program terminated with signal 6, Aborted. #0 0x0000000048ab6800 in ?? () (gdb) bt #0 0x0000000048ab6800 in ?? () #1 0x00000000001360e4 in Configuration::LoadAndVerify(char const*, ConfigurationVerify const*, std::string&) (Filename=0x0, pVerify=0x0, rErrorMsg=@0x0) at Configuration.cpp:144 #2 0x0000000000136474 in Configuration::LoadAndVerify(char const*, ConfigurationVerify const*, std::string&) (Filename=0x0, pVerify=0x0, rErrorMsg=@0x0) at Configuration.cpp:179 --ben From boxbackup at fluffy.co.uk Wed Jan 28 22:47:14 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Wed, 28 Jan 2004 22:47:14 +0000 Subject: [Box Backup] Debugging boxbackup In-Reply-To: <20040128223606.GA12828@tilderoot.com> References: <20040128204608.GA31679@tilderoot.com> <2D8E4060-51D6-11D8-A154-003065F8EC8E@fluffy.co.uk> <20040128223606.GA12828@tilderoot.com> Message-ID: On 28 Jan 2004, at 22:36, Ben Lovett wrote: > On Wed, Jan 28, 2004 at 09:08:53PM +0000, Ben Summers wrote: >> Well it looks to me like the compiler is generating bad code -- the >> error is deep in the STL, which is nothing at all to do with me. >> >> I wonder if you're using the 2.95.x STL with the 3.x compiler? >> >> Is there a test suite for g++ you can try out to see if your install >> is >> OK? >> >> Ben > > Is this of any use? Core generated using the "installed" version of > bbstoreaccounts, dump used with the debugging version.. > > Core was generated by `bbstoreaccounts'. > Program terminated with signal 6, Aborted. > #0 0x0000000048ab6800 in ?? () > (gdb) bt > #0 0x0000000048ab6800 in ?? () > #1 0x00000000001360e4 in Configuration::LoadAndVerify(char const*, > ConfigurationVerify const*, std::string&) (Filename=0x0, pVerify=0x0, > rErrorMsg=@0x0) > at Configuration.cpp:144 > #2 0x0000000000136474 in Configuration::LoadAndVerify(char const*, > ConfigurationVerify const*, std::string&) (Filename=0x0, pVerify=0x0, > rErrorMsg=@0x0) > at Configuration.cpp:179 That's a bit odd, it shouldn't have all zeros as parameters -- possibly it's not correct as it sounds as if you're using something from one build with another. You certainly wouldn't see it getting far enough to recurse if it were the case. If you build the and run the debug version of bbstoreaccounts under gdb with cd bin/bbstoreaccounts make cd ../../debug/bin/bbstoreaccounts gdb bbstoreaccounts then in gdb, type run -c create 21 for example (with replaced with the config file you're using). It should then crash, then type bt to see the backtrace, and it should be more accurate. Ben From boxbackup at fluffy.co.uk Wed Jan 28 23:15:24 2004 From: boxbackup at fluffy.co.uk (Tim Fletcher) Date: Wed, 28 Jan 2004 23:15:24 +0000 Subject: [Box Backup] 0.03 linux feedback Message-ID: <1075331724.1320.17.camel@oxygen.period.org.uk> Just to let you know that 0.03 configured and built first time on fedora core 1. -- Tim Fletcher .~. /V\ L I N U X email: tim at night-shade.org.uk // \\ >Don't fear the penguin< irc: Night-Shade on Quakenet /( )\ ^^-^^ Never apply a StarTrek solution to a Babylon 5 problem From boxbackup at fluffy.co.uk Wed Jan 28 23:30:03 2004 From: boxbackup at fluffy.co.uk (Pascal Lalonde) Date: Wed, 28 Jan 2004 18:30:03 -0500 Subject: [Box Backup] Error messages at execution In-Reply-To: <1D4A646A-516C-11D8-8F43-003065F8EC8E@fluffy.co.uk> References: <20040128053055.GA22473@plasma.doom.und> <1D4A646A-516C-11D8-8F43-003065F8EC8E@fluffy.co.uk> Message-ID: <20040128233003.GA6482@plasma.doom.und> On Wed, Jan 28, 2004 at 08:29:39AM +0000, Ben Summers wrote: > > On 28 Jan 2004, at 05:30, Pascal Lalonde wrote: > > > > >First of all, I didn't succeed in running bbstored on an OpenBSD 3.3 > >box. I keep getting an 'Exception: RaidFile (2/8)' when trying to > >create > >an account. > > Does the directory you specified to raidfile-config have write > permissions for the user you're running bbstored under? > Ok, you got me... shame. So afterall it works on 3.3. But it wasn't just that. > > > >And I generated my certificates by hand, like this: > >openssl req -newkey rsa:2048 -nodes -keyout domain.com-key.pem -keyform > >PEM -out domain.com-csr.pem -outform PEM > > Did bbstored-config not work? A while ago I was experimenting with OpenSSL, and creating a test CA. Naturally, I had my OPENSSL_CONF variable set. So it would use a different openssl.cnf than the default one. Unsetting this variable made things work. I didn't try to install it as non-root on the other box. Maybe I'll try it when I have more spare time. Could be useful, as users could setup stores for themselves. And I also have a question. Why not back up /etc ? I always do, since it would be a pain to configure everything over again. Or do you mean by that to back it up on static media (CD?) ? It's not my intention to blindly restore /etc, but I use it as a reference, or to restore individual files. Thanks, Pascal Lalonde From boxbackup at fluffy.co.uk Wed Jan 28 23:38:53 2004 From: boxbackup at fluffy.co.uk (Ben Lovett) Date: Wed, 28 Jan 2004 15:38:53 -0800 Subject: [Box Backup] Debugging boxbackup In-Reply-To: References: <20040128204608.GA31679@tilderoot.com> <2D8E4060-51D6-11D8-A154-003065F8EC8E@fluffy.co.uk> <20040128223606.GA12828@tilderoot.com> Message-ID: <20040128233853.GA673@tilderoot.com> On Wed, Jan 28, 2004 at 10:47:14PM +0000, Ben Summers wrote: > > On 28 Jan 2004, at 22:36, Ben Lovett wrote: > >Core was generated by `bbstoreaccounts'. > >Program terminated with signal 6, Aborted. > >#0 0x0000000048ab6800 in ?? () > >(gdb) bt > >#0 0x0000000048ab6800 in ?? () > >#1 0x00000000001360e4 in Configuration::LoadAndVerify(char const*, > >ConfigurationVerify const*, std::string&) (Filename=0x0, pVerify=0x0, > >rErrorMsg=@0x0) > > at Configuration.cpp:144 > >#2 0x0000000000136474 in Configuration::LoadAndVerify(char const*, > >ConfigurationVerify const*, std::string&) (Filename=0x0, pVerify=0x0, > >rErrorMsg=@0x0) > > at Configuration.cpp:179 > > That's a bit odd, it shouldn't have all zeros as parameters -- possibly > it's not correct as it sounds as if you're using something from one > build with another. You certainly wouldn't see it getting far enough to > recurse if it were the case. > > If you build the and run the debug version of bbstoreaccounts under gdb > with > > cd bin/bbstoreaccounts > make > cd ../../debug/bin/bbstoreaccounts > gdb bbstoreaccounts > > then in gdb, type > > run -c create 21 > > for example (with replaced with the config file you're > using). It should then crash, then type > > bt > > to see the backtrace, and it should be more accurate. ok .. with gdb 4.16.1 i get -- (gdb) run -c /etc/ports/box/bbstored.conf create 21 Starting program: /usr/home/ben/boxbackup-0.03/debug/bin/bbstoreaccounts/bbstoreaccounts -c /etc/ports/box/bbstored.conf create 21 Program received signal SIGSEGV, Segmentation fault. 0x16bc48 in _ZNSt8_Rb_treeIPvSt4pairIKS0_15MallocBlockInfoESt10_Select1stIS4_ESt4lessIS0_ESaIS4_EE11lower_boundERS2_ (this=0x90ffffffffffffdf, __k=@0xe0ffffffffffff39) at MemLeakFinder.cpp:108 108 } (gdb) bt #0 0x16bc48 in _ZNSt8_Rb_treeIPvSt4pairIKS0_15MallocBlockInfoESt10_Select1stIS4_ESt4lessIS0_ESaIS4_EE11lower_boundERS2_ (this=0x90ffffffffffffdf, __k=@0xe0ffffffffffff39) at MemLeakFinder.cpp:108 #1 0x16bba4 in _ZNSt3mapIPv15MallocBlockInfoSt4lessIS0_ESaISt4pairIKS0_S1_EEE11lower_boundERS5_ (this=, __x=@0x1cffffffffffff43) at MemLeakFinder.cpp:108 #2 0x16ba28 in _ZNSt3mapIPv15MallocBlockInfoSt4lessIS0_ESaISt4pairIKS0_S1_EEEixERS5_ (this=, __k=@0x0) at MemLeakFinder.cpp:108 #3 0x14b9cc in memleakfinder_malloc (size=0, file=0x0, line=0) at MemLeakFinder.cpp:98 #4 0x15b1bc in _ZN16MemoryBlockGuardIPhEC1Ei (this=, BlockSize=0) at BackupStoreFilenameClear.cpp:75 #5 0x119d98 in _Z41__static_initialization_and_destruction_0ii ( __initialize_p=0, __priority=0) at BackupStoreFilenameClear.cpp:75 #6 0x119ebc in _GLOBAL__I__ZN45_GLOBAL__N_BackupStoreFilenameClear.cpp1PX2Zs13sEncodeMethodE () at BackupStoreFilenameClear.cpp:75 #7 0x104188 in ___start () #8 0x1041d8 in ___start () #9 0x103f0c in __init () #10 0x10403c in ___start () that looks _really_ weird.. i'm not 100% sure that everything is fine with this systems install of gcc3, but i'm reasonably sure since i have not had any other problems.. maybe i'll try doing a reinstall if the current snapshots have gcc3 in them. the backtrace where you thought that it was maybe gcc 2.95.x STL, with gcc3 was captured using gdb 6, which has much better sparc64 support, so i was trusting it more in the beginning. thanks, --ben From boxbackup at fluffy.co.uk Thu Jan 29 11:13:09 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Thu, 29 Jan 2004 11:13:09 +0000 Subject: [Box Backup] Version with excludes Message-ID: <1EB36CB5-524C-11D8-92C0-003065F8EC8E@fluffy.co.uk> I've just implemented the exclude functionality -- stop files and directories being backed up either by name or by regular expression. If anyone would like a copy, please ask. But I need to test it a bit more on other platforms before doing a proper release with it in. Ben From boxbackup at fluffy.co.uk Thu Jan 29 14:28:28 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Thu, 29 Jan 2004 14:28:28 +0000 Subject: [Box Backup] Error messages at execution In-Reply-To: <20040128233003.GA6482@plasma.doom.und> References: <20040128053055.GA22473@plasma.doom.und> <1D4A646A-516C-11D8-8F43-003065F8EC8E@fluffy.co.uk> <20040128233003.GA6482@plasma.doom.und> Message-ID: <67F10E48-5267-11D8-92C0-003065F8EC8E@fluffy.co.uk> On 28 Jan 2004, at 23:30, Pascal Lalonde wrote: > On Wed, Jan 28, 2004 at 08:29:39AM +0000, Ben Summers wrote: >> >> On 28 Jan 2004, at 05:30, Pascal Lalonde wrote: >> >>> >>> First of all, I didn't succeed in running bbstored on an OpenBSD 3.3 >>> box. I keep getting an 'Exception: RaidFile (2/8)' when trying to >>> create >>> an account. >> >> Does the directory you specified to raidfile-config have write >> permissions for the user you're running bbstored under? >> > Ok, you got me... shame. I'll put in a check for that in the config scripts. > So afterall it works on 3.3. > But it wasn't just that. :-) > >>> >>> And I generated my certificates by hand, like this: >>> openssl req -newkey rsa:2048 -nodes -keyout domain.com-key.pem >>> -keyform >>> PEM -out domain.com-csr.pem -outform PEM >> >> Did bbstored-config not work? > A while ago I was experimenting with OpenSSL, and creating a test CA. > Naturally, I had my OPENSSL_CONF variable set. So it would use a > different openssl.cnf than the default one. Unsetting this variable > made > things work. I will also make the scripts check to see that this variable isn't set. > > I didn't try to install it as non-root on the other box. Maybe I'll try > it when I have more spare time. Could be useful, as users could setup > stores for themselves. Only one use could, though, as it needs to use a well-known port. It does work -- the tests run bbstored as a normal user. > > And I also have a question. Why not back up /etc ? I always do, since > it > would be a pain to configure everything over again. Or do you mean by > that to back it up on static media (CD?) ? It's not my intention to > blindly restore /etc, but I use it as a reference, or to restore > individual files. My main concern is that the backup keys are not backed up. It shouldn't be a problem, but it's always best to play safe with cryptography. Now that I have the exclude files functionality, I'm going to modify the scripts to exclude the key file explicitly, and then allow /etc to be backed up. But until I get snapshot functionality, I'll still have reservations due to the "lazy" way things get backed up. Ben From boxbackup at fluffy.co.uk Thu Jan 29 14:30:11 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Thu, 29 Jan 2004 14:30:11 +0000 Subject: [Box Backup] Debugging boxbackup In-Reply-To: <20040128233853.GA673@tilderoot.com> References: <20040128204608.GA31679@tilderoot.com> <2D8E4060-51D6-11D8-A154-003065F8EC8E@fluffy.co.uk> <20040128223606.GA12828@tilderoot.com> <20040128233853.GA673@tilderoot.com> Message-ID: On 28 Jan 2004, at 23:38, Ben Lovett wrote: [snip] > that looks _really_ weird.. > > i'm not 100% sure that everything is fine with this systems install of > gcc3, > but i'm reasonably sure since i have not had any other problems.. > maybe i'll > try doing a reinstall if the current snapshots have gcc3 in them. It does appear there's something odd going on within the gcc libraries. I will be taking a closer look! I've only run this on x86 platforms (and Mac OS X) so when it comes to something a bit more unusual, I suppose we can expect problems. Ben From boxbackup at fluffy.co.uk Thu Jan 29 17:43:25 2004 From: boxbackup at fluffy.co.uk (Pascal Lalonde) Date: Thu, 29 Jan 2004 12:43:25 -0500 Subject: [Box Backup] Error messages at execution In-Reply-To: <67F10E48-5267-11D8-92C0-003065F8EC8E@fluffy.co.uk> References: <20040128053055.GA22473@plasma.doom.und> <1D4A646A-516C-11D8-8F43-003065F8EC8E@fluffy.co.uk> <20040128233003.GA6482@plasma.doom.und> <67F10E48-5267-11D8-92C0-003065F8EC8E@fluffy.co.uk> Message-ID: <20040129174325.GA19174@plasma.doom.und> > > > >>> > >>>And I generated my certificates by hand, like this: > >>>openssl req -newkey rsa:2048 -nodes -keyout domain.com-key.pem > >>>-keyform > >>>PEM -out domain.com-csr.pem -outform PEM > >> > >>Did bbstored-config not work? > >A while ago I was experimenting with OpenSSL, and creating a test CA. > >Naturally, I had my OPENSSL_CONF variable set. So it would use a > >different openssl.cnf than the default one. Unsetting this variable > >made > >things work. > > I will also make the scripts check to see that this variable isn't set. I think it could even be better to include an openssl.cnf with the package, and override then OPENSSL_CONF var, just in case the default /etc/ssl/openssl.cnf has been modified or erased for whatever reason. > > > >I didn't try to install it as non-root on the other box. Maybe I'll try > >it when I have more spare time. Could be useful, as users could setup > >stores for themselves. > > Only one use could, though, as it needs to use a well-known port. It > does work -- the tests run bbstored as a normal user. Unless you add an option to specify an alternate listening port in a later version :-) But I'm not in need of that, at least not now. I'm only suggesting. Pascal Lalonde From boxbackup at fluffy.co.uk Thu Jan 29 19:55:50 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Thu, 29 Jan 2004 16:55:50 -0300 (BRT) Subject: [Box Backup] Boxbackup suggestions Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ben, I have a few suggestions: - Make bbackupquery accept ftp commands like ls/dele/get/etc and some switch to show the files in ftp format like: -rwxr-xr-x 1 eduardo users 2470 Dec 29 21:23 start-backup drwx------ 12 eduardo users 1024 Aug 30 21:13 tct-1.14 -rw-r--r-- 1 eduardo users 316852 Jan 21 19:34 tct-1.14.tar.gz -rw-r--r-- 1 eduardo users 12590686 Jan 23 09:26 tct.tar.gz -rw-r--r-- 1 eduardo users 3798856 Dec 27 21:49 terminator.wmv I think it'll be MUCH more easy for begginers to understand it. - Install manpages for each command and develop further documentation. The website's documentation is very fuzzy... I almost got lost on it. The "Exception: RaidFile (2/8)" error is an example.. I simply found nothing about it anywhere. I know "RaidFileException.h" exists an has some information, but it REALLY does not solve my problems. If you mind, I could help you with the documentation process (html/man). - Install useful error messages. The "Exception" errors just get me angry ;-). - Why have you chosen hex format by default? I think bbstoreaccounts and other tools could be much more easy to use/administer/remember if the account_id could be freely specified. I have 30 servers here, each one of them have it's own name. If I need to connect to them, I simply type ssh USER + it's NAME (easy to remember) and not it's HEX-code (hard do remember, and almost impossible to remember unless you have a internal brain-calculator). Unless you have a VERY real reason for it, I think this is not necessary. - An option to specify the allocation size in Mb or Gb and not only in blocks. (I need a calculator everytime I want to insert/alter any size. This is not cool). - Wrap you source code/documentation in 72/80 columns. It's much more easy to deal with it. I can forward this email to the list if you want. Best Regards, -- Eduardo A. Alvarenga Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAGWVIpKK2uJoGDlMRAsWYAJkB6AGtQFaHdyt+meaYu+8wNdMzQACgz2l0 ExW9t6Olw6WRHxgVXa/SvWw=3D =3DexlJ -----END PGP SIGNATURE----- From boxbackup at fluffy.co.uk Thu Jan 29 20:59:40 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Thu, 29 Jan 2004 20:59:40 +0000 Subject: [Box Backup] Boxbackup suggestions In-Reply-To: References: Message-ID: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> Before I answer some of these suggestions, I should probably explain why the project is like it is. I started this as a proprietary product, not intending to release it to the wider world. It only occurred to me a few months ago that open sourcing it would be a good plan. So, I haven't really been terribly worried about documenting all the little funny bits that people have encountered, because the packaging would take care of all these little things. And besides, *I* know what they mean! Now of course I realise that this isn't ideal for an open source project, but I thought getting it out the door would be better than nothing -- I am very busy so it would have been a long delay to get everything absolutely perfect since I really need to get the basic functionality in for my own use. It just wouldn't have got done, and be pushed backwards again and again. And this way I get to know what I really need to address. So far everyone has been very helpful. So, on to the suggestions: On 29 Jan 2004, at 19:55, Eduardo Alvarenga wrote: > > - Make bbackupquery accept ftp commands like ls That one gets me all the time too. I'll pop in an alias. > /dele Meaningless -- you can't actually delete anything from the server. > /get Implemented. > /etc The commands which modify the store are not useful. Either they would be undone by bbackupd the next time it scanned the files, or it'd be much easier just to let it get on with things. The basic read and navigation commands are all there -- see bin/bbackupquery/documentation.txt > and > some switch to show the files in ftp format like: > > -rwxr-xr-x 1 eduardo users 2470 Dec 29 21:23 start-backup > drwx------ 12 eduardo users 1024 Aug 30 21:13 tct-1.14 > -rw-r--r-- 1 eduardo users 316852 Jan 21 19:34 tct-1.14.tar.gz > -rw-r--r-- 1 eduardo users 12590686 Jan 23 09:26 tct.tar.gz > -rw-r--r-- 1 eduardo users 3798856 Dec 27 21:49 terminator.wmv > > I think it'll be MUCH more easy for begginers to understand it. Now this is more tricky. The way it works means that attributes would have to be dug out of the stored files on the server, and finding the size is another huge amount of code. I'm not entirely sure how much extra information it gives anyway... this is a tool for assessing the state of the store, and the information is shows does give very useful information when you want to know what's going on. The actual contents and attributes of the files aren't terribly useful. However, I can see the use of an ftp-like listing, so it's on the list. > > - Install manpages for each command and develop further documentation. > The website's documentation is very fuzzy... I almost got lost on it. > The "Exception: RaidFile (2/8)" error is an example.. I simply found > nothing about it anywhere. I know "RaidFileException.h" exists an has > some information, but it REALLY does not solve my problems. These were really intended for me. But what I think I will do is have something which has a list of exception codes and most common causes, and print a suggested cause out when they occur. Better than nothing. > If you > mind, I could help you with the documentation process (html/man). Help is always appreciated! > > - Install useful error messages. The "Exception" errors just get me > angry ;-). Sorry. > > - Why have you chosen hex format by default? Constant width, compact representation, and clear display of byte boundaries, all very helpful when debugging. Also, fits in very nicely with my intended use of the system. > I think bbstoreaccounts > and other tools could be much more easy to use/administer/remember if > the account_id could be freely specified. I have 30 servers here, each > one of them have it's own name. If I need to connect to them, I simply > type ssh USER + it's NAME (easy to remember) and not it's HEX-code > (hard do remember, and almost impossible to remember unless you have > a internal brain-calculator). Unless you have a VERY real reason for > it, I think this is not necessary. The symbolic name to account number will be done by a management system. And in practical terms, if you're using bbackupquery, it will get all the info from the config file. > > - An option to specify the allocation size in Mb or Gb and not only in > blocks. (I need a calculator everytime I want to insert/alter any > size. > This is not cool). Yes, this should be done. Sort of annoying for me too. > > - Wrap you source code/documentation in 72/80 columns. It's much more > easy to deal with it. My screen is 1920 pixels wide :-) , and I have an editor which soft-wraps my documentation. This I think is explained by the history of the project -- things are done to make my life easy. Of course, this does not mean to say that I'm not going to make things easier for others eventually. This is a learning experience for me. > > I can forward this email to the list if you want. I'd be interested in hearing any other experiences. It sounds like it's quite an aggravating thing to install and use? Ben From boxbackup at fluffy.co.uk Thu Jan 29 21:10:50 2004 From: boxbackup at fluffy.co.uk (Alaric B Snell) Date: Thu, 29 Jan 2004 21:10:50 +0000 Subject: [Box Backup] Boxbackup suggestions In-Reply-To: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> References: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> Message-ID: <401976DA.9000509@alaric-snell.com> Ben Summers wrote: >> If you >> mind, I could help you with the documentation process (html/man). > Help is always appreciated! And I've not forgotten that I've promised to go over it too when I get time :-) > > Ben > ABS From boxbackup at fluffy.co.uk Thu Jan 29 21:54:17 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Thu, 29 Jan 2004 18:54:17 -0300 (BRT) Subject: [Box Backup] Boxbackup suggestions In-Reply-To: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> References: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 29 Jan 2004, Ben Summers wrote: > I started this as a proprietary product, not intending to release it to= =20 > the wider world. It only occurred to me a few months ago that open=20 > sourcing it would be a good plan. Nice approach. > So, I haven't really been terribly worried about documenting all the > little funny bits that people have encountered, because the packaging > would take care of all these little things. And besides, *I* know what > they mean! When the code is small, everything makes sense. Without documentation, you might get lost one day and be forced to remember everything you=20 took a long time to develop. > The commands which modify the store are not useful. Either they would=20 > be undone by bbackupd the next time it scanned the files, or it'd be=20 > much easier just to let it get on with things. >=20 > The basic read and navigation commands are all there -- see=20 > bin/bbackupquery/documentation.txt Another thing I miss: String-based listing.=20 Something like this: -- ls rc.* ls *.gif ls foo?.*.c -- How about ftp's mget feature? Any possibility to include this? Or to make things better, implement recursive fetches from=20 files/directories directly via 'get': -- get -r remotedir/ localdir/ get rc.* localdir/ get -r foo/bar/* localdir/foo/bar/ -- > > some switch to show the files in ftp format like: > Now this is more tricky. The way it works means that attributes would > have to be dug out of the stored files on the server, and finding the > size is another huge amount of code. I'm not entirely sure how much > extra information it gives anyway... this is a tool for assessing the > state of the store, and the information is shows does give very useful > information when you want to know what's going on. The actual contents > and attributes of the files aren't terribly useful. Hm... maybe yes, maybe no. Let's suppose /var/log gets full. So we=20 delete old log files to save more space. Then, 15 minutes after this,=20 our boss asks for the last logs from the past 30 days. Oh!! it was=20 deleted, so what? Cry? My idea is to make boxbackup a REAL recovery system and not just a=20 storage where the user might browse thru all their files, like he does=20 every day on his machine, and fetch any file or directory (even=20 recursively) like he was connected to a mirrored ftp server. The log files is an example, but let's complicate a little more. What=20 if your boss asks for the last pictures from last year's catalog=20 you've just deleted by his order? How to *list* and *get* the correct=20 files based on size, date, time, and type? > However, I can see the use of an ftp-like listing, so it's on the list. Thanks. And please, put a pager on it like less/more, activated =20 automatically or not. > > - Why have you chosen hex format by default? >=20 > Constant width, compact representation, and clear display of byte=20 > boundaries, all very helpful when debugging. >=20 > Also, fits in very nicely with my intended use of the system. > The symbolic name to account number will be done by a management > system. And in practical terms, if you're using bbackupquery, it will > get all the info from the config file. Hm.. management system. Any snapshot? > > - An option to specify the allocation size in Mb or Gb and not only > > in blocks. (I need a calculator everytime I want to insert/alter=20 > > any size. This is not cool). >=20 > Yes, this should be done. Sort of annoying for me too. I was almost certain you would agree with me ;-). > > - Wrap you source code/documentation in 72/80 columns. It's much > > more easy to deal with it. >=20 > My screen is 1920 pixels wide :-) , and I have an editor which > soft-wraps my documentation. This I think is explained by the history > of the project -- things are done to make my life easy. Of course, > this does not mean to say that I'm not going to make things easier for > others eventually. This is a learning experience for me. =20 Okey dokey ;-). I run at 2048x768. I know what you mean. Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAGYELpKK2uJoGDlMRArPxAJ9sI8HlqKMqkUqmbcvG8+WRawXa2ACeLV0l rUxs7Ih0kPiSH3+8AuCEX4Q=3D =3DHFro -----END PGP SIGNATURE----- From boxbackup at fluffy.co.uk Thu Jan 29 22:06:14 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Thu, 29 Jan 2004 22:06:14 +0000 Subject: [Box Backup] Boxbackup suggestions In-Reply-To: References: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> Message-ID: <5AADECF8-52A7-11D8-92C0-003065F8EC8E@fluffy.co.uk> On 29 Jan 2004, at 21:54, Eduardo Alvarenga wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 29 Jan 2004, Ben Summers wrote: > > > >> I started this as a proprietary product, not intending to release it >> to >> the wider world. It only occurred to me a few months ago that open >> sourcing it would be a good plan. > > Nice approach. I'm not sure if you mean that? > >> So, I haven't really been terribly worried about documenting all the >> little funny bits that people have encountered, because the packaging >> would take care of all these little things. And besides, *I* know what >> they mean! > > When the code is small, everything makes sense. Without documentation, > you might get lost one day and be forced to remember everything you > took a long time to develop. Hence the contents of the notes directory, and the vast quantities of comments in the source files. With the debug version, it is really easy to see what has happened when you get an error. The code is not small already. I would very much welcome comments on the code quality, and the sustainability of documentation and code. > > > >> The commands which modify the store are not useful. Either they would >> be undone by bbackupd the next time it scanned the files, or it'd be >> much easier just to let it get on with things. >> >> The basic read and navigation commands are all there -- see >> bin/bbackupquery/documentation.txt > > Another thing I miss: String-based listing. > Something like this: > > -- > ls rc.* > ls *.gif > ls foo?.*.c > -- Yes, might be handy. > > How about ftp's mget feature? Any possibility to include this? > Or to make things better, implement recursive fetches from > files/directories directly via 'get': > > -- > get -r remotedir/ localdir/ > get rc.* localdir/ > get -r foo/bar/* localdir/foo/bar/ > -- Implemented using the 'restore' command, and it's even restartable should your transfer get interrupted. > >>> some switch to show the files in ftp format like: > > > >> Now this is more tricky. The way it works means that attributes would >> have to be dug out of the stored files on the server, and finding the >> size is another huge amount of code. I'm not entirely sure how much >> extra information it gives anyway... this is a tool for assessing the >> state of the store, and the information is shows does give very useful >> information when you want to know what's going on. The actual contents >> and attributes of the files aren't terribly useful. > > Hm... maybe yes, maybe no. Let's suppose /var/log gets full. So we > delete old log files to save more space. Then, 15 minutes after this, > our boss asks for the last logs from the past 30 days. Oh!! it was > deleted, so what? Cry? It is possible to fetch the old versions at the moment. > > My idea is to make boxbackup a REAL recovery system and not just a > storage where the user might browse thru all their files, like he does > every day on his machine, and fetch any file or directory (even > recursively) like he was connected to a mirrored ftp server. I'm not sure I quite follow. > > The log files is an example, but let's complicate a little more. What > if your boss asks for the last pictures from last year's catalog > you've just deleted by his order? How to *list* and *get* the correct > files based on size, date, time, and type? At the moment it's not easy, I admit. bbackupquery is a primitive tool which is the bare minimum required. This is not a finished project! > >> However, I can see the use of an ftp-like listing, so it's on the >> list. > > Thanks. And please, put a pager on it like less/more, activated > automatically or not. I'll see what I can do... > > > >>> - Why have you chosen hex format by default? >> >> Constant width, compact representation, and clear display of byte >> boundaries, all very helpful when debugging. >> >> Also, fits in very nicely with my intended use of the system. > > > >> The symbolic name to account number will be done by a management >> system. And in practical terms, if you're using bbackupquery, it will >> get all the info from the config file. > > Hm.. management system. Any snapshot? Not yet. > >>> - An option to specify the allocation size in Mb or Gb and not only >>> in blocks. (I need a calculator everytime I want to insert/alter >>> any size. This is not cool). >> >> Yes, this should be done. Sort of annoying for me too. > > I was almost certain you would agree with me ;-). I use it too! Ben From boxbackup at fluffy.co.uk Thu Jan 29 22:22:40 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Thu, 29 Jan 2004 19:22:40 -0300 (BRT) Subject: [Box Backup] Boxbackup suggestions In-Reply-To: <5AADECF8-52A7-11D8-92C0-003065F8EC8E@fluffy.co.uk> References: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> <5AADECF8-52A7-11D8-92C0-003065F8EC8E@fluffy.co.uk> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 29 Jan 2004, Ben Summers wrote: > I'm not sure if you mean that? As you can see, my english sucks. My native language is brazilian portuguese, so please forgive me. s/approach/choice/ Better? > > When the code is small, everything makes sense. Without > > documentation, you might get lost one day and be forced to remember=20 > > everything you took a long time to develop. >=20 > Hence the contents of the notes directory, and the vast quantities of > comments in the source files. With the debug version, it is really > easy to see what has happened when you get an error. The code is not > small already. >=20 > I would very much welcome comments on the code quality, and the > sustainability of documentation and code. I was not judging the code itself. But the software documentation, the=20 userland stuff. > > How about ftp's mget feature? Any possibility to include this? > > Or to make things better, implement recursive fetches from > > files/directories directly via 'get': > > > > -- > > get -r remotedir/ localdir/ > > get rc.* localdir/ > > get -r foo/bar/* localdir/foo/bar/ > > -- >=20 > Implemented using the 'restore' command, and it's even restartable=20 > should your transfer get interrupted. I'm now getting used to read your 'documentation.txt' files. Sorry. But something like "restore rc.* localdir/" already works? > > My idea is to make boxbackup a REAL recovery system and not just a > > storage where the user might browse thru all their files, like he does > > every day on his machine, and fetch any file or directory (even > > recursively) like he was connected to a mirrored ftp server. >=20 > I'm not sure I quite follow. Then, show us your proposal.=20 Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAGYeypKK2uJoGDlMRAltiAJ9ERju82kwkHYS0RBhWvI2Bffv1sgCaAn6j I3qiwcEKVmmpuH8wTPkxRCs=3D =3D6UEg -----END PGP SIGNATURE----- From boxbackup at fluffy.co.uk Fri Jan 30 05:34:40 2004 From: boxbackup at fluffy.co.uk (Pascal Lalonde) Date: Fri, 30 Jan 2004 00:34:40 -0500 Subject: [Box Backup] Boxbackup suggestions In-Reply-To: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> References: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> Message-ID: <20040130053440.GA13425@plasma.doom.und> > > I'd be interested in hearing any other experiences. It sounds like it's > quite an aggravating thing to install and use? > It's not that bad when you get to know what those exceptions mean... Maybe a few "configure variables", or a config.h, to modify things like the install path, the default config file path, the default listening port, pid file... And to be able to specify some of these parameters on the command-line. There is something I don't quite understand: why do we have to specify the user in the config file if we do an "su" anyways? I don't know if I'm missing something or if you had the intention of dropping privileges at startup, and the "su" is a temporary workaround? Of course, what I speak of here are mostly minor details. I think the most important things right now are error messages, and maybe implementing a minimal "help" command in bbackupquery, to know the available commands quickly. Pascal Lalonde From boxbackup at fluffy.co.uk Fri Jan 30 18:38:23 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Fri, 30 Jan 2004 18:38:23 +0000 Subject: [Box Backup] Error messages at execution In-Reply-To: <20040129174325.GA19174@plasma.doom.und> References: <20040128053055.GA22473@plasma.doom.und> <1D4A646A-516C-11D8-8F43-003065F8EC8E@fluffy.co.uk> <20040128233003.GA6482@plasma.doom.und> <67F10E48-5267-11D8-92C0-003065F8EC8E@fluffy.co.uk> <20040129174325.GA19174@plasma.doom.und> Message-ID: <7C12108F-5353-11D8-AAB5-003065F8EC8E@fluffy.co.uk> On 29 Jan 2004, at 17:43, Pascal Lalonde wrote: >>> >>>>> >>>>> And I generated my certificates by hand, like this: >>>>> openssl req -newkey rsa:2048 -nodes -keyout domain.com-key.pem >>>>> -keyform >>>>> PEM -out domain.com-csr.pem -outform PEM >>>> >>>> Did bbstored-config not work? >>> A while ago I was experimenting with OpenSSL, and creating a test CA. >>> Naturally, I had my OPENSSL_CONF variable set. So it would use a >>> different openssl.cnf than the default one. Unsetting this variable >>> made >>> things work. >> >> I will also make the scripts check to see that this variable isn't >> set. > I think it could even be better to include an openssl.cnf with the > package, and override then OPENSSL_CONF var, just in case the default > /etc/ssl/openssl.cnf has been modified or erased for whatever reason. Yes, that's probably quite sensible. > >>> >>> I didn't try to install it as non-root on the other box. Maybe I'll >>> try >>> it when I have more spare time. Could be useful, as users could setup >>> stores for themselves. >> >> Only one use could, though, as it needs to use a well-known port. It >> does work -- the tests run bbstored as a normal user. > Unless you add an option to specify an alternate listening port in > a later version :-) > But I'm not in need of that, at least not now. I'm only suggesting. Hmmm. Not trivial to implement given some other choices. But anyway, you just need to modify one file, so it's not a big deal if I don't do this. Ben From boxbackup at fluffy.co.uk Fri Jan 30 18:42:11 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Fri, 30 Jan 2004 18:42:11 +0000 Subject: [Box Backup] Boxbackup suggestions In-Reply-To: References: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> <5AADECF8-52A7-11D8-92C0-003065F8EC8E@fluffy.co.uk> Message-ID: <0412FC2D-5354-11D8-AAB5-003065F8EC8E@fluffy.co.uk> On 29 Jan 2004, at 22:22, Eduardo Alvarenga wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 29 Jan 2004, Ben Summers wrote: > > >> I'm not sure if you mean that? > > As you can see, my english sucks. > My native language is brazilian portuguese, so please forgive me. > > s/approach/choice/ > > Better? Sorry, I think completely misunderstood your meaning. A cultural thing... > > >>> When the code is small, everything makes sense. Without >>> documentation, you might get lost one day and be forced to remember >>> everything you took a long time to develop. >> >> Hence the contents of the notes directory, and the vast quantities of >> comments in the source files. With the debug version, it is really >> easy to see what has happened when you get an error. The code is not >> small already. >> >> I would very much welcome comments on the code quality, and the >> sustainability of documentation and code. > > I was not judging the code itself. But the software documentation, the > userland stuff. Pity, I was hoping I'd get some comments on the code at some time! But yes, the stuff the user sees is inadequate at the moment. > >>> How about ftp's mget feature? Any possibility to include this? >>> Or to make things better, implement recursive fetches from >>> files/directories directly via 'get': >>> >>> -- >>> get -r remotedir/ localdir/ >>> get rc.* localdir/ >>> get -r foo/bar/* localdir/foo/bar/ >>> -- >> >> Implemented using the 'restore' command, and it's even restartable >> should your transfer get interrupted. > > I'm now getting used to read your 'documentation.txt' files. Sorry. > But something like "restore rc.* localdir/" already works? No wildcards. Everything or nothing. > >>> My idea is to make boxbackup a REAL recovery system and not just a >>> storage where the user might browse thru all their files, like he >>> does >>> every day on his machine, and fetch any file or directory (even >>> recursively) like he was connected to a mirrored ftp server. >> >> I'm not sure I quite follow. > > Then, show us your proposal. bbackupquery is for looking at what's happening in the store for troubleshooting, automated backup verification, and perhaps for system recovery. For retrieving bits and pieces, I plan to integrate into the platform's file browsing UI, and allow different date based views, and a way of seeing all versions of a particular file. Long term plan, though. I'd like to hear better ideas. Ben From boxbackup at fluffy.co.uk Fri Jan 30 18:48:26 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Fri, 30 Jan 2004 18:48:26 +0000 Subject: [Box Backup] Boxbackup suggestions In-Reply-To: <20040130053440.GA13425@plasma.doom.und> References: <0E8106C6-529E-11D8-92C0-003065F8EC8E@fluffy.co.uk> <20040130053440.GA13425@plasma.doom.und> Message-ID: On 30 Jan 2004, at 05:34, Pascal Lalonde wrote: >> >> I'd be interested in hearing any other experiences. It sounds like >> it's >> quite an aggravating thing to install and use? >> > It's not that bad when you get to know what those exceptions mean... I'll make a list and post it on the web site soon! > > Maybe a few "configure variables", or a config.h, to modify things like > the install path, the default config file path, the default listening > port, pid file... > > And to be able to specify some of these parameters on the command-line. The approach I've taken is for 1) Most common options to be set on the command line of the *-config script. 2) Less common options to be set in the generated .config file. 3) Specify alternative config files on the command line as the first parameter, eg /usr/local/bin/bbstored /some/random/config/file.config I think this basically covers everything. I wouldn't want there to be many options to the ./configure script, because otherwise you get into a situation where you don't quite know what the executable is configured to do. So each platform should have a known set of defaults. Is this bad? > > There is something I don't quite understand: why do we have to specify > the user in the config file if we do an "su" anyways? I don't know if > I'm missing something or if you had the intention of dropping > privileges > at startup, and the "su" is a temporary workaround? The su was a temporary workaround for v0.01. Priviledges are dropped from v0.02 onwards -- I just missed altering the documentation to match. > > Of course, what I speak of here are mostly minor details. I think the > most important things right now are error messages, On the web site soon! > and maybe > implementing a minimal "help" command in bbackupquery, to know the > available commands quickly. Agree on that one. I'm going to embed the contents of documentation.txt into the program as soon as I get around to writing the perl script to split it up nicely. There's a lot of work here... Ben From boxbackup at fluffy.co.uk Sat Jan 31 21:45:29 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Sat, 31 Jan 2004 18:45:29 -0300 (BRT) Subject: [Box Backup] How to include a single file? Message-ID: Hi, I'm trying to backup "/bsd" (single file) and it is not working: bbackupd.conf: -- BackupLocations { =09_bsd =09{ =09Path =3D /bsd =09} } -- bbackupquery: -- # bbackupquery=20 Box Backup Query Tool v0.03EXCL, (c) Ben Summers 2003, 2004 * Commercial service provision using this software prohibited, see license= =2E Using configuration file /etc/box/bbackupd.conf Connecting to store... Handshake with store... Login to store... Login complete. query > list _bsd query > -- The same thing happen when I try to specify something like=20 "/usr/local/bin/script.sh". Any ideas? Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 From boxbackup at fluffy.co.uk Sat Jan 31 21:41:07 2004 From: boxbackup at fluffy.co.uk (Ben Summers) Date: Sat, 31 Jan 2004 21:41:07 +0000 Subject: [Box Backup] How to include a single file? In-Reply-To: References: Message-ID: <2D50070E-5436-11D8-A3E0-003065F8EC8E@fluffy.co.uk> On 31 Jan 2004, at 21:45, Eduardo Alvarenga wrote: > Hi, > > I'm trying to backup "/bsd" (single file) and it is not working: > [snip] > > The same thing happen when I try to specify something like > "/usr/local/bin/script.sh". > > > Any ideas? The "Path" must be a directory, not a file. I suggest you create a directory on the same filesystem as the file you want to back up, and hard link the file into it (not symlink). Then backup that directory. Is this a major limitation? Ben From boxbackup at fluffy.co.uk Sat Jan 31 21:59:18 2004 From: boxbackup at fluffy.co.uk (Eduardo Alvarenga) Date: Sat, 31 Jan 2004 18:59:18 -0300 (BRT) Subject: [Box Backup] How to include a single file? In-Reply-To: <2D50070E-5436-11D8-A3E0-003065F8EC8E@fluffy.co.uk> References: <2D50070E-5436-11D8-A3E0-003065F8EC8E@fluffy.co.uk> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 31 Jan 2004, Ben Summers wrote: > > I'm trying to backup "/bsd" (single file) and it is not working: >=20 > The "Path" must be a directory, not a file. I suggest you create a=20 > directory on the same filesystem as the file you want to back up, and=20 > hard link the file into it (not symlink). Then backup that directory. >=20 > Is this a major limitation? Sure. I want to backup some files without touching them. I have some=20 directories which I want only some files to be backuped (temp files=20 come to mind). Regex will be welcome too. If you mind, please change "Path =3D" to something like "Include =3D"=20 beeing it a directory or not. If you have time today, (an of course, IF want to make it) please send=20 me a new snapshot, I have to implement the backup schema today since=20 today is saturday and no one is working here. =20 And, how about splitting boxbackup into 2 files? A server and a client=20 one? Best Regards, --=20 Eduardo A. Alvarenga=20 Analista de Suporte Centro Estrat=E9gico Integrado / SEGUP-PA (91) 259-0555 / 8116-0036 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (OpenBSD) iD8DBQFAHCU4pKK2uJoGDlMRAuBuAJ0d2OZWuPZ49Jmt6KHIRzL7Wi2E8QCfR4UC z5ZQBYwRxjSDKWSSLH6d81Q=3D =3DxHXn -----END PGP SIGNATURE-----