Hi again Jason,
Thanks for your reply. With your workaround do you have the problem of
the generated tar file's name being corrupt? When my backup completed
(using your method), I then checked the XferLOG in backuppc:
Running: /usr/bin/smbclient-backuppc-hack \\\\matt-pc\\C\$ -U backuppc -E -N -d
1 -c tarmode\ full -Tc - /Documents\ and\ Settings codedb
full backup started for share C$
Xfer PIDs are now 17388,17387
Domain=[PROFACTOR] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tarmode is now full, system, hidden, noreset, verbose
[a few NT_STATUS_SHARING_VIOLATIONS on registry files etc]
tar: dumped 70033 files and directories
Total bytes written: 7595769344
tarExtract: \\matt-pc\C$SECRET-Ubackuppc-E-N-d1-ctarmode full-Tc-/Documents and Settingscodedb./Documents and : checksum error at
create 0 0/0 0 \\matt-pc\C$1gn5bULp-Ubackuppc-E-N-d1-ctarmode full-Tc-/Documents and Settingscodedb./Documents and
tarExtract: : checksum error at
tarExtract: Can't open /backup/backuppc/pc/matt-pc/new/fC$/ for empty output
create 0 0/0 0 .
tarExtract: : checksum error at
[followed by a large sequence of checksum errors]
tarExtract: Can't open /backup/backuppc/pc/matt-pc/new/fC$/ for empty output
create 0 0/0 0 .
tarExtract: Done: 23 errors, 12 filesExist, 0 sizeExist, 45056 sizeExistComp,
12 filesTotal, 0 sizeTotal
where 'SECRET' is my password. The log file reckons:
2007-05-03 09:49:11 full backup started for share C$
2007-05-03 10:11:12 full backup 0 complete, 56597 files, 7579291420 bytes, 53
xferErrs ( bad files, bad shares, 53 other)
but if I browse the backups I only have a single folder called
"\\matt-pc\C$SECRETp-Ubackuppc-E-N-d1-ctarmode full-Tc-" and within that
a folder called "Documents and Settingscodedb." and then inside that a
single file called "Documents and ". So now it would appear the tar is
"ok" but somehow backuppc's extraction isn't working.
I wonder if the unusual name embedded in the tar file is in some way
related to this issue.
Do you (or indee anyone) have any ideas on this?
Once again thanks for your reply,
Matt
Jason M. Kusar wrote:
I had the same problem with my server (CentOS 5). As a workaround
until Red Hat fixes the issue, this perl script will solve the problem:
#!/usr/bin/perl
$service = shift @ARGV;
unshift @ARGV, $ENV{PASSWD};
unshift @ARGV, $service;
exec "/usr/bin/smbclient", @ARGV;
Just put it in /usr/bin and have backuppc point to it instead of
smbclient. It will insert the password from the environment into the
command string. There probably should be some checking of it to guard
against injection attacks, but since I'm the only one with access to
the backup server, I didn't put much thought into it. It does fix the
problem for now though.
--Jason
--
/Matt Godbolt
ProFactor Software
[EMAIL PROTECTED]
DD: +44 (0) 20 8150 6956/
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
