* Kai Hauser ([EMAIL PROTECTED]) disait : > HI, thanks for your quick response ...
Welcome. > >This release fixes a lot of bugs and comes in a better shape than 0.5.x. > > > >1: http://www.backup-manager.org/releases/06 > >2: http://www.backports.org/package.php?search=backup-manager > > > huh? and let the bug be there? or do you want to drop the package from > stable completely? No, sarge's packages cannot be updated for fixes other than security ones. If you want to use sarge's version, you have to deal with some issues, that's sad but real. As backup-manager was very young at the time of the sarge release, you've got a pretty old/buggy version of the program. That's why I strongly advice to use the backport, which is the real "stable" version of backup-manager (branch 0.6). You really have to consider backup-manager versions prior to 0.6 as beta software. > >Moreover, in 0.6.2, you can do mysql backups within backup-manager, > >which is safer than copy by hand mysql files. > > > in which way it is safer? > i read that just copy the files is the fastest way for backups (and quit > safe if mysqld is shut down) otherwise i would had taken mysqldump. It's better because: 1/ you don't have to shut down the mysql server when backing up the databases. 2/ you aren't bound to a given version of mysql (sql dumps are better than binary files) 3/ you have backups that are necessary coherent: you don't have a database snapshot taken in a middle of query. see the manpage of mysqldump, and take care to the --opt switch which can be used within backup-manager. > >Isn't there a circular symlink in your fs? > > > > $ find /sdb -type l > > > the only circular symlink was /var/www/vhosts/test/httpdocs/vhosts -> > /var/www/vhosts That's enough for leading to an infinite loop when parsing recursively /var/www/vhosts... > i had this that i could browse http://test/vhosts an can see all vhosts > on that server. > the copy command (cp -Rp /var/www/) copied the symlink, in /sdb/backups > it was still a symlink to /var/www/vhosts/. Here we are. You then put a point in BM_ARCHIVE_REPOSITORY that lead to your /var/www/vhosts sub-directory. During the purging phase, backup-manager parses recursively the repository in order to purge old archives. The fact is that in versions prior to 0.6.2, there is a bug that can make backup-manager drop files that are not archives. As you put a symlink by hand from your repository to your /var/www directory, backup-manager entered here, and droped files. To conclude: 1/ consider the repository as a quarantine place, where only archives are allowed to be, drop the symlinks from there and stop copying symlinks there. 2/ again, upgrade to 0.6.2, you'll sleep better ;) > (/sdb/backups/daily/www/vhosts/test/httpdocs/vhosts -> /var/www/vhosts/ > ) and backup-manager followed that link, then followed > /var/www/vhosts/test/httpdocs/vhosts -> /var/www/vhosts and so on. > > but the deletion of the files also occurred on an other server, the > symlink there was /var/www/phpmyadmin -> /usr/share/phpmyadmin :-( > all files were recursively deleted in /usr/share/phpmyadmin !!! All the problem you are speaking about are due first, to backup-manager 0.5.x which drops files in a dumb maner, but also to the fact that you put symlinks everywhere in your file system. That's IMHO a bad thing to do. Please consider removing them, if you design well your stuff, I'm sure you can drop a lot of useless symlinks. Moreover, you *have* to drop all of the circular symlinks. > >You don't use /var/www/vhosts as the archives repository, do you? > >If so, that's a bad idea. > > > No i use /sdb/backups/ as repository, it pasted the backup-mananger.conf > file to make that clear, sorry if i didn't explained enough. Yes, but with the symlink inside, it's like /var/www/vhosts was a sub-directory of the repo, sadly... > >My advice would be to upgrade to 0.6.2-0bpo1, sarge version is > >deprecated and full of known bugs. > > > mmm ok what is your advice for all the people that doesn't know that bug? backup-manager 0.5.x lives in sarge since the first sarge release, and you are the first that report having destroyed all his data with the program. I understand this had happen to you because of an unlucky situation (the symlinks) but most of the people just use /var/archives as a repository (as suggested by the debian package) and don't put (circular) symlinks inside. Most of the people don't have such bad experience with it. > i spend more than 6 hours today to get all the sites on the servers > running again and this was only possible with backups i had made by hand. > if i had no backups all sites would be trashed, with a tool which claims > to prevent exactly this :-D I'm feel truly sad reading that, and again, I advice you to use the backport, and try the last *real stable version* of backup-manager, that is 0.6.2. But drop the symlinks from the repository if you want to sleep well. Kind regards, -- Alexis Sukrieh <[EMAIL PROTECTED]> 0x1EE5DD34 Debian http://www.debian.org Backup Manager http://www.backup-manager.org
signature.asc
Description: Digital signature
