8 | | (1:51:54 PM) CyberAxe: I really need backup/restore to not fail when it runs into a problem with a file but log it and skip. I've been having a problem with long file names on restore and it kills the entire process at any error instead of skipping the problem file and moving on. |
9 | | (1:53:49 PM) zooko: CyberAxe: hm |
10 | | (1:53:53 PM) CyberAxe: This should apply to almost any action. A Try statement vs instead of crash. With 25GB of data to recover going up to 350GB I really don't want to have to monitor the restore/backup for 20+ hours just incase it fails. |
11 | | (1:53:56 PM) zooko: CyberAxe: I saw the issue ticket about the long file names. |
12 | | (1:54:29 PM) zooko: CyberAxe: okay, I don't believe that there is currently an issue ticket about continuing past an error. Would you please open one that says what you just said right there? |
| 8 | (1:51:54 PM) !CyberAxe: I really need backup/restore to not fail when it runs into a problem with a file but log it and skip. I've been having a problem with long file names on restore and it kills the entire process at any error instead of skipping the problem file and moving on. |
| 9 | (1:53:49 PM) zooko: !CyberAxe: hm |
| 10 | (1:53:53 PM) !CyberAxe: This should apply to almost any action. A Try statement vs instead of crash. With 25GB of data to recover going up to 350GB I really don't want to have to monitor the restore/backup for 20+ hours just incase it fails. |
| 11 | (1:53:56 PM) zooko: !CyberAxe: I saw the issue ticket about the long file names. |
| 12 | (1:54:29 PM) zooko: !CyberAxe: okay, I don't believe that there is currently an issue ticket about continuing past an error. Would you please open one that says what you just said right there? |