This problem is apparently with the latest Samba version. I am trying to
figure out how to downgrade the Samba on my Lenny install to 3.02 (from the 3.2
which is currently installed with Lenny)
+--
|This was sent by ase...@int
I thought this was a pretty serious bug as Samba backups are just plain broken
in the latest release. I am trying to look for a way to downgrade my
installation now.
+--
|This was sent by ase...@intelligenx.com via Backup Cent
Jason Holubiw wrote on 02/20/2009 06:58:44 PM:
> I would prefer samba because it requires no special configuration or
> software installation on the clients, which is a nice plus.
>
> I may end up looking at SFU though...
Rsyncd requires exactly 4 files:
rsync.exe
cygwin1.dll
I upgraded to Lenny and it did this backuppc upgrade as part of it. I tried
using the upgraded config.pl which has the -N samba fix, but it doesn't work.
Basically, like everyone is saying, samba backups are broken because it is
dumping the last directory twice:
NT_STATUS_OBJECT_NAME_NOT_FOU
This is a new error as of at least version 3.1. I was running Etch with a
backport and it worked fine. I believe that was 3.0
+--
|This was sent by ase...@intelligenx.com via Backup Central.
|Forward SPAM to ab...@backupcentra
Thanks for the suggestion. I made a share "cdrive" and adjusted the config
appropriately, however the same error still occurs.
I would prefer samba because it requires no special configuration or
software installation on the clients, which is a nice plus.
I may end up looking at SFU though...
O
On Mon, Feb 16, 2009 at 2:32 PM, Jason Holubiw wrote:
>
> $Conf{BackupFilesOnly} = {
>
> 'e$' => [
>
> '/pictures'
>
> ],
>
I dont use smbclient myself, so this is just a WAG. Have you tried
creating actual "shares" instead of using the builtin drive share (ie
'drive_c' instead of 'c$')
Does anyone have any ideas on how to fix this? My backups have been down
for a month now...
Thanks.
On Mon, Feb 16, 2009 at 1:32 PM, Jason Holubiw wrote:
> I have not found a solution to this problem, and I have found other
> people that have the same issue. This problem started in January w
I have not found a solution to this problem, and I have found other people
that have the same issue. This problem started in January when I moved from
Fedora 8 to Fedora 9.
The issue is that smbclient gets and incorrect path from backuppc when
trying to backup windows clients in the Documents
