[FEATURE REQUEST] override errors and warnings in queue

[fredscal]

Hello.

I am using TC for backups (copy w/ overwrite all older), which mean I have very long copy queues, sometimes taking up to 24h to complete.

That the operation is interrupted at least on the first occurence of every possible error or warning (write protection, too long path name, invalid characters, etc.), and requires me to respond to the prompt before resuming, is very bothersome.

Is there a way to 'tell' TC to automatically skip errors and ignore warnings, without prompting the user even once, and then log the errors in a textfile or something ? In other words, is there a way to force the queue to completion no matter what ?

That would make TC the ultimate backup tool for me !

[milo1012]

I'm not sure if you are aware of the SkippedFileCopy option.
http://www.ghisler.ch/board/viewtopic.php?t=40658&highlight=skippedfilecopy
http://www.ghisler.ch/board/viewtopic.php?t=39708&highlight=skippedfilecopy
This is enabled by default in TC since 8.50, so write protected files will be either prompted up front or at the very end.

But it seems that it only works for "locked" files so far. For too long path names you can use the ini option
LongNameCopy=1

For invalid characters you will still get a prompt in the middle of the operation (or did this change for TC 9?).

[Horst.Epp]

For such operations I've integrated Fast Copy into TC
and set its "Nonstop" option.
https://ipmsg.org/tools/fastcopy.html.en

Example for the Copy command button parameters:
/auto_close /cmd=diff /estimate %P%S /to="%T"

[ghisler(Author)]

SkippedFileCopy does not work with queues. Why? The queue sets a fix copy order, TC can't just ignore this and rearrange the files.

[fredscal]

Thank you all for your precise and to-the-point answers.

For such operations I've integrated Fast Copy into TC
and set its "Nonstop" option.

Thanks. I'll look into it.

SkippedFileCopy does not work with queues. Why? The queue sets a fix copy order, TC can't just ignore this and rearrange the files.

How about a "log errors" feature ? Just skip the problematic files and go on with the queue ?

I know it seems hardly justifiable, but hear me out: I'd rather spend an hour after my backup completes to correct the few encountered problems, than waste whole days because the queue prompts me when I'm away...

So, I've added FEATURE REQUEST to this thread's title.

1Kthanks, and congratulations for the great work !