rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] SpecialFileError, UpdateError


From: roland
Subject: Re: [rdiff-backup-users] SpecialFileError, UpdateError
Date: Tue, 6 Jun 2006 10:37:44 +0200

Hello Felix,

SpecialFileError home/felix/.gxine/socket Socket error: AF_UNIX path too long
this is non critical error - you can just skip backing up sockets with --exclude-sockets .
typically, applications create them automatically.

UpdateError var/log/secure Updated mirror temp file /mnt/hda/share/t41.klee/root/var/log/rdiff-backup.tmp.10546 does not match source
doesn`t sound good.....

of data.  The destination is a LinkStation (a 400 MHz MIPSel computer
with the backup HD) and, as it looks, its CPU is utilized more than 90%
during that hour.
do you use that storage via nfs mount or smb mount this time ?

I wonder whether I should simply revert to "rsnapshot" or "star" for doing backups
main advantage of rdiff-backup is it`s really small sized increments.
if you can live with bigger increments, then other solutions _may_ be better.

regards
roland




----- Original Message ----- From: "Felix E. Klee" <address@hidden>
To: <address@hidden>
Sent: Tuesday, June 06, 2006 9:46 AM
Subject: [rdiff-backup-users] SpecialFileError, UpdateError


I got these when running rdiff-backup:

SpecialFileError home/felix/.gxine/socket Socket error: AF_UNIX path too long UpdateError var/log/secure Updated mirror temp file /mnt/hda/share/t41.klee/root/var/log/rdiff-backup.tmp.10546 does not match source
 SpecialFileError var/run/acpid.socket Socket error: AF_UNIX path too long

Note that this particular backup was run only for about the fifth time,
and already it breaks.  But I don't plan to use rdiff-backup any longer,
anyway: As said before it takes approximately an hour when running the
backup on 6 to 7GB of data, even when the changes comprise only a few MB
of data.  The destination is a LinkStation (a 400 MHz MIPSel computer
with the backup HD) and, as it looks, its CPU is utilized more than 90%
during that hour.  I wonder whether I should simply revert to
"rsnapshot" or "star" for doing backups, the latter making it very
simple and safe to encrypt and move around backup data (e.g. to copy it
to DVDs) as it is stored in TAR archives (which are a bit of a pain when
playing back data, though).

--
Felix E. Klee


_______________________________________________
rdiff-backup-users mailing list at address@hidden
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki





reply via email to

[Prev in Thread] Current Thread [Next in Thread]