Folder(s) defined to "Backup Source" do not appear within "Select files and folders to recover"
What to backup (Backup Source) clearly shows the folders to be backedup. Wheh I attempt to recover a file within one of the folders, the folder of interest is not included.
In the current issue, I need to recover a file from within the MCAT folder. You'll see the MCAT folder in the first of two screenshots "A1", BUT NOT in the screenshot of "Select files and folders to recover", attachment "A2".
Any ideas as to what might be the cause?
Thanks,
Bill


- Se connecter pour poster des commentaires

You suggested:
As a test, try doing a file/folder backup as a new task, and just select just the MCAT folder. Run the backup and then attempt a recovery from that new task - anything listed then?
Works perfectly! All folders AND files contained in MCAT folder appear in the "Select files and folders to recover" tree . As a further test, I recoverd one of the files.
I did have a problem a couple of years ago with a Windows copy operation that created copies with the " wiht ~ in the name ". I did a selective search in the MCAT tree but didn't find any. Nor, did I see any .tmp files. The fact that the test you suggested worked perfectly is further evidence that those attributes are not present in MCAT.
Can you suggest additional tests that might flush out the problem?
Thanks,
Bill
- Se connecter pour poster des commentaires

The only thing that comes to mind (with the current info and knowledge of your proble), is that your existing backup task may somehow have been modified or corrupted at some point in time. Since you had success backing up that specific folder, the next logical step would be to create a new backup task for "disks and parititions" and create a new disk backup. Backup your entire drive (as you had been doing with the old backup). When done, verify if the backup files are in the mcat folder now or not. If they are, I'd kill the old backup task (you can keep the old backups for posterity and/or at least until you have some new backup history with your new task and then delete the old ones or more them elsewhere if you want ... or leave them where they are - totally up to you). Hopefully the, just creating a new backup task and running it will work as planned and you'll be good to go.
- Se connecter pour poster des commentaires

Curious. Is the backup with the missing files a "full" backup or an "incremental" backup?
- Se connecter pour poster des commentaires

I have two systems running daily backups to the NAS. The attached screenshot is the NAS directory where you see both data and image backups from both systems. The "office" creates an image twice a week and the remaining 5 are "full" data folder/file backups. Similarly for the "Kitchen" system.
With the suspicion that the "Data" backup(s) are somehow corrupted, I will begin with your suggestion of creating a new "full" backup of desired folders/files as a replacement for "Office(7)-DATA-Sat-End". BTW, none of the other Office "DATA" tib's contain the MCAT folder either. There was some cloning of the backup jobs when I had to recreate the tasks going from 2010 to 2016, so maybe that's when the problem really started.
You understand that the "Image" backups have everything, it's just the "DATA" tib's that seem to be in error.
I'll post back as soon as I can test a new "full" data backup.
Thanks,
Bill
Graeagle, California USA
Fichier attaché | Taille |
---|---|
345522-127330.jpg | 155.72 Ko |
- Se connecter pour poster des commentaires

It would appear that I had a "set" of corrupted folder/file backup tasks. Whether the original cloning activity when I upgraded to 2016 is the source of the corruption is, I suppose, anyone's guess.
Anyway, I created a new folder/file backup task that included the folders that were missing and that gave rise to the current issue. I executed that task successfully and verified by direct inspection of the folders that the files were retrievable. With that, I cloned the newly created task, adjusted according to the desired naming and scheduling and executed. It too completed successfully and its contents also verified.
I really appreciate your help.
Thanks,
Bill
Graeagle, California USA
- Se connecter pour poster des commentaires

Glad to hear that the issue has been resolved. We'll probably never know exactly what caused the corruption, but at least we know you can create new and working backup tasks again. Always important to go back and validate a backup by doing an actual recovery from time to time - I don't even trush the "validate" options because you just don't really know until you go to recover and get a successful result.
- Se connecter pour poster des commentaires