How to have it ignore file-name errors when backing up?

[mlevin77]

Please help... I'm restoring using Retrospect 6.1 and it gets half-way through a 300 Gig backup with this error (copied from the Log):

 

∆ Retrospect version 6.1.230

launched at 5/11/2010 10:28 AM

+ Retrospect Driver Update, version 6.1.15.101

 

+ Executing Restore from Backup at 5/11/2010 10:44 AM

To volume Technicians Shared Space

 

- 5/11/2010 10:44:19 AM: Restoring from TU RAID set 3

Can't write file „...Go To Web‰, error -43 (file/folder not found), path: „Shared Items/Levin Server Common Share/Mike's Backups off floating drive/Taisaku's backup - 45 gigs/èëóï¬/ÉAÉCÉRÉì/ OS9 icons/ÉLÉÉÉâÉNÉ^Ã…[ÇΩÇÃ/FRIENDS Icons/...Go To Web‰.

Can't write file „...Mail Me‰, error -43 (file/folder not found), path: „Shared Items/Levin Server Common Share/Mike's Backups off floating drive/Taisaku's backup - 45 gigs/èëóï¬/ÉAÉCÉRÉì/ OS9 icons/ÉLÉÉÉâÉNÉ^Ã…[ÇΩÇÃ/FRIENDS Icons/...Mail Me‰.

Trouble writing folder ...!!!, error -43 (file/folder not found)

5/11/2010 12:31:16 PM: Execution incomplete.

Remaining: 11779 files, 33.3 GB

Completed: 39064 files, 76.2 GB

Performance: 729.7 MB/minute

Duration: 01:46:55

 

Basically, it came across some files with a crazy name (I think this user was using a Japanese font...) - they got put into the backup ok but restoring is giving an error -43 and the whole thing stops! How do I

 

1) make it ignore files with illegal names, or

2) make it keep going if it fails on one file instead of stopping,

 

and

 

3) how do I continue the restore "intelligently" so that it doesn't have to rewrite the 150 gigs it did before it stopped? I'm doing this over the network so it's slow...

 

is it possible? what is this error -43 and how do I get past it?

 

thank you!!!

 

Mike

 

[twickland]

The -43 error indicates that Retrospect can't find the folder on the destination volume to which it wants to restore certain files. In your example, the folder was supposed to have the name "...!!!" which is not allowed under OS X because it begins with a period. My guess is that Retrospect sent the command to create the folder but because the name was illegal, the folder was not created; Retrospect's subsequent command to write a file to that folder failed because the folder did not exist, generating the -43 error.

 

Your log suggests that this folder was originally created under OS 9, so perhaps it isn't necessary for you to restore it at this point.

 

My first thought is that you may be able to solve your problem by changing your settings in System Preferences> International to enable file/folder names with the correct characters.

 

Alternatively, you might perform your restore by deselecting those folders that seem problematic.

 

You don't say what kind of restore you were performing. If it was "restore entire disk" or "replace corresponding files" and if your subsequent restore is one of those types, Retrospect will recognize the files that were restored previously and will not try to restore them again.

 

(If, on the other hand, you were restoring to a new folder, you would then need to define that folder as a destination subvolume for your subsequent restores in order to avoid restoring everything a second time.)

 

To deselect unwanted files, initiate a restore from a backup, choosing either "restore entire disk" or "replace corresponding files" on the destination. When the matching has completed and the restore window appears, click on "Files chosen" and uncheck any folders you don't want to restore. (Those files already restored will have a diamond in front of the name.)

 

Keep us posted as to whether you have success.

[mlevin77]

The -43 error indicates that Retrospect can't find the folder on the destination volume to which it wants to restore certain files. In your example, the folder was supposed to have the name "...!!!" which is not allowed under OS X because it begins with a period.

My first thought is that you may be able to solve your problem by changing your settings in System Preferences> International to enable file/folder names with the correct characters.

Alternatively, you might perform your restore by deselecting those folders that seem problematic.

Keep us posted as to whether you have success.

 

thank you!! I was able to deselect that subfolder and everything went fine.

 

Mike