Hi, all,

I recently reinstalled BackupPC on a new backup server, and it's running
well (backing up over 1 TB of data daily/weekly). That is, except for some
errors for one of the backed up client partitions. Here is an extract of
the XferLOG (things in angle brackets are my own munging; the f<1>/f<2>...
sequence corresponds to <long_path_...>):

[...]
  create d 775  3864/112         880 <long_path_below_backed_up_dir>
  same     664  3864/112          12
<long_path_below_backed_up_dir>/6304166_1.txt
  pool   l 777  3864/112          97
<long_path_below_backed_up_dir>/6304166_1.wa
  same     664  3864/112          12
<long_path_below_backed_up_dir>/6304229_1.txt
  pool   l 777  3864/112          97
<long_path_below_backed_up_dir>/6304229_1.wa
  same     664  3864/112          12
<long_path_below_backed_up_dir>/6304491_1.txt
  pool   l 777  3864/112          97
<long_path_below_backed_up_dir>/6304491_1.wa
  same     664  3864/112          12
<long_path_below_backed_up_dir>/6304672_1.txt
  pool   l 777  3864/112          97
<long_path_below_backed_up_dir>/6304672_1.wa
  same     664  3864/112          12
<long_path_below_backed_up_dir>/6304847_1.txt
Unable to link
/backup/BackupPC/pc/burdata01lx_home/3/f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6304847_1.txt
 to
/backup/BackupPC/pc/burdata01lx_home/new//f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6304847_1.txt
  pool   l 777  3864/112          97
<long_path_below_backed_up_dir>/6304847_1.wa
  same     664  3864/112          12
<long_path_below_backed_up_dir>/6305204_1.txt
Unable to link
/backup/BackupPC/pc/burdata01lx_home/3/f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305204_1.txt
 to
/backup/BackupPC/pc/burdata01lx_home/new//f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305204_1.txt
  pool   l 777  3864/112          97
<long_path_below_backed_up_dir>/6305204_1.wa
  same     664  3864/112          12
<long_path_below_backed_up_dir>/6305239_1.txt
Unable to link
/backup/BackupPC/pc/burdata01lx_home/3/f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305239_1.txt
 to
/backup/BackupPC/pc/burdata01lx_home/new//f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305239_1.txt
  pool   l 777  3864/112          97
<long_path_below_backed_up_dir>/6305239_1.wa
  same     664  3864/112          12
<long_path_below_backed_up_dir>/6305623_1.txt
Unable to link
/backup/BackupPC/pc/burdata01lx_home/3/f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305623_1.txt
 to
/backup/BackupPC/pc/burdata01lx_home/new//f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305623_1.txt
  pool   l 777  3864/112          97
<long_path_below_backed_up_dir>/6305623_1.wa
[...]

Indeed, those files that were not linked are not in the BackupPC data
directory and aren't available for restore on the CGI interface. It looks
like BackupPC is trying to make a link from the previous full (3) to the
new one. I've verified that the file in the previous full exists. The only
notable thing I see is perhaps an excess of forward slashes, literal in the
"new//" (but this shouldn't really matter...), and a URL-mangled one (%2f).

All the other partitions are backed up without errors, and as you can see,
not all files in the same directory present this error... So I'm stumped.
Has anyone seen this before?

Bernardo Rechea




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Reply via email to