Perhaps your error handling will be more granular, so you only catch one try when it explodes? You can do this (without repeating yourself) by refactoring the code of the offensive code to a useful method - i.e.
TryCopyFile(path1);
TryCopyFile(path2);
TryCopyFile(path3);
TryCopyFile () , .