Hi, Miles Thompson wrote on 22.05.2007 at 09:08:39 [Re: [BackupPC-users] Time to upgrade from 2.1.2?]: > Martin Sundmacher wrote: > > Miles Thompson schrieb: > >> We used apt-get to fetch and install BackupPC on our Edgy Eft server. > >> The version is apparently 2.1.2 dated 5 Sept, 2005 according to the > >> comments in the main BackupPC file. > >> > >> It's only been running a couple of weeks; would an upgrade be painful? > > > > I did Upgrades to 3.0.0 on 3 Debian-Servers. One is running for weeks > > now without any problems. My last upgrade was yesterday. Ubuntu should > > be similar. > > > > These are all Perl scripts, so what's involved with the upgrade? > > Just grab the new scripts, untar and then copy them over the old ones? > Or is it necessary to re-edit the whole configuration file?
as a rule of thumb, if you installed through the package management system, you should also upgrade through it. This is especially true for BackupPC on Debian, because it uses non-standard paths (/etc/backuppc instead of /etc/BackupPC) and patched scripts. Several people have asked for help recovering from an update attempt via the upgrade script from the tarball, meaning the upgrade is *not* successful that way. For Debian, there's a 3.0.0 package in lenny/sid. As you said, there are no binaries in the package and thus no dependencies not satisfiable within etch or even sarge. It seems to be safe to simply download the 3.0.0 package and install it with 'dpkg -i' (in fact, I just did that on my sarge server - more for the sake of having done it once than because I desperately want the web based configuration editor - and the only thing noteworthy is that you'll have to manually merge the changes you applied to the main config.pl into the new one, because it adds quite a few settings that you need). I don't know about the status of BackupPC in Ubuntu, but I'd guess there's probably a 3.0.0 version somewhere. I'd recommend that for upgrading, regardless of the Ubuntu release it is in. Installing the Debian package in Ubuntu or vice-versa should probably be safe, but updating from one to the other could potentially lead to the same problems you get with the tarball update script. Regards, Holger ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
