HI, thanks for your quick response ...
Alexis Sukrieh schrieb:
tags 363511 + sarge
thanks
* Kai Hauser ([EMAIL PROTECTED]) disait :
Package: backup-manager
Version: 0.5.7-1sarge1
I would suggest to upgrade to the last stable version [1] of
backup-manager (0.6.2) which is available as a backported package [2] for
sarge.
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?
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.
there is a problem with files which contains blanks in their names.
/usr/sbin/backup-manager: line 213: [:
/sdb/backups/daily/www/vhosts/domain1/httpdocs/images/cust_img/abendstimmung:
binary operator expected
/usr/sbin/backup-manager: line 217: [:
/sdb/backups/daily/www/vhosts/domain1/httpdocs/images/cust_img/abendstimmung:
binary operator expected
/usr/sbin/backup-manager: line 181: [:
/sdb/backups/daily/www/vhosts/domain1/httpdocs/images/cust_img/abendstimmung:
binary operator expected
...
/usr/sbin/backup-manager: line 188: [: 50009222017240950001: integer
expression expected
I'm pretty sure this is fixed in the last stable release.
there is also a problem with symlinks, it seems that backup-manager
follows them if even though BM_DUMP_SYMLINKS="false"
This works gently in current versions, symlinks are not followed.
/usr/sbin/backup-manager: line 181: [:
/sdb/backups/daily/www/vhosts/test/httpdocs/vhosts is a symlink to
/var/www/vhosts/
I had to kill backup-manager by hand otherwise it would still run.
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
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/.
(/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 !!!
I dont know which of both bugs it was but all files in /var/www/vhosts
expect folders and .hidden files got deleted.
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.
You have to use a dedicated place to store your archives.
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?
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
Best regards.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
