When a backup job runs and it cannot find files/directories that previously existed, the backup job will fail and detail the invalid directories in the job log. Also, when the backup job tries to backup e-mails/attachments that were deleted between the time the backup job was setup and when the backup job runs, the backup fails indicating corrupt files. There is no way one person can go through every single directory/mailbox to verify that all of the files exist before running the backup job. Is the software not able to recognize that someone cleaned out a few files and that the files no longer exist, so the backup job doesn't need to look for those files to backup? The 266179, 207001 and 245452 documents basically state to look through the text version of the backup job details and remove all of the directories that someone deleted that day and then run the backup job. That is not a solution to this issue. Does anyone have feedback as to if this is addressed in version 10 or any other ideas? Thanks for your help.
