Why do I still use this piece of !>$*&

[wmconlon]

I can't believe that a squirrely permission or name will cause Retrospect to NOT backup. It really seems like the default for Retrospect is to fail. And only in the unlikely event that the moon and stars are aligned will it actually complete.

 

Most recent case in point (from the log):

 

- 12/30/2005 3:08:42 PM: Copying / on white…

While scanning volume /,

Folder /home/judith/.Trash/0„◊/,

Scanning incomplete, error -24263 (file/directory not found)

 

Huh? I say to myself. Retrospect doesn't back up the files and directories that ARE found, because a file or directory is NOT found????? Who would write such a program?

 

 

So I just:

 

[root@white judith]# cd .Trash/

[root@white .Trash]# ls -al

total 12

drwx------ 3 judith tothepoint 4096 Dec 20 14:10 .

drwxrwx--- 31 judith tothepoint 4096 Dec 20 15:11 ..

drwxr-sr-x 2 judith tothepoint 4096 Dec 20 14:06 0???

...

 

[root@white .Trash]# ls 0?^?^H/

[root@white .Trash]# rm -R 0?^?^H/

rm: remove directory `0\343\177\b/'? y

 

And problem solved.

 

BUT WHY IS THIS A PROBLEM IN THE FIRST PLACE??????

 

So there's a problem with a file. Big deal -- log it and move on. But to halt the backup? Come on, Dantz.

 

BTW, Retrospect Backup Server 6.1.126. The backup client was linux 6.5.108.