[BackupPC-devel] [BackupPC-users] Error Rsync Unexpected empty share name skipped

[Holger Parplies]

Hi,

[...]
-full backup started for directory /tecno
-unexpected empty share name skipped
-Backup aborted

well, have you got an empty share name in your configuration? Hint: a share
named '' (the empty string) does not make any sense. Further hint: BackupPC
says you do, so you probably do. If it's not clear, you want to look at the
value of $Conf {RsyncShareName} ...

I believe you've actually found a bug in BackupPC_dump, though. Apparently,
an empty (or duplicate) share name generates a warning only, unless it is
the last share for the host, in which case it causes the backup to fail.
That does not make sense. It should either always be a fatal error or never.
Patch attached (one of these days, I'll have a look at git ...).

[...]
Negotiated protocol version 28
Xfer PIDs are now 16298,16299
[ saltate 47 righe ]
Done: 37 files, 85325611 bytes
[...]

I think the first thing to do is get rsync to talk in US English, I
don't think backuppc will understand any other language.

Actually, the line quoted above would seem to be generated by
BackupPC::CGI::View ;-), but I agree that quoting foreign language
diagnostic messages tends to be confusing. While for tar/smb xfer
language is important (because the diagnostic output is parsed),
I believe for rsync(d), that is not the case (but I might be
mistaken).

Regards,
Holger