06-15-2014 11:46 PM
When a backup job "failed" in Backup Exec 2010 R3, Backup Exec would still run the duplicate job and copy the incomplete backup set to tape. Backup Exec 2014 does no longer do this; the duplicate job is "skipped" when the previous backup job failed.
Now, this is understandable. But we regularly have the situation that we backup a file server with multiple Terabytes in millions of files, and ONE of these files is corrupt, hence the backup job "failed." If we decide to go without this file and want to copy the "incomplete" backup set to tape, we have to go through Storage and select the backup set there; there is no way anymore to run the actual duplicate job.
Btw, in Storage view, in dataset list, you can't see details. So, you have to select a backup set that might be the right and click "Properties." But when you find that this what you were looking for and go back, you're on top of the list again ...
11-10-2014 01:41 PM
Not quite understand your last paragraph. I am trying to find out if it is no longer possible for you to run duplicate job of an incompleted full backup, then what can you do (if there is a workaround).
11-10-2014 06:52 PM