Backing up "Documents" in Windows 10
Posted: 03 Jan 2021, 13:54
Morning all,
I've been experimenting with Cobian for a few months now and largely, it satisfies my needs.
However, there is one "undocumented" feature I have found. I believe is because of the way Windows 10 works (same for Windows 8.1, as far as my tests have found) and not really an issue with Cobian 11
If I configure a Full backup of the entire Documents folder on my Windows 10 Pro 64bit build and trigger a backup, Cobian backs up the entire folder as requested, compiles and emails a log file exactly as expected. If I then use Windows explorer to view the backup folder Cobian has created (I don't have compression or encryption switched on) instead of the being called something like... Documents 2020-12-27 13;38 (Full) it is called Documents with a timestamp identical to the Documents folder on my PC. If I login to the console of my NAS drive and examine the folder using the (Linux) file explorer I can see that the folder is named as I expected, but the timestamp is still same as the "Documents" folder on my PC. Subsequent "Full" backups produces additional "Documents" folders, which is likely to make restoring files from specific backup sessions a little bit tricky.
If I "clone" the Full Backup and change the backup type to Differential and then run this, then the software behaves exactly as expected with correctly named folders.
The "log" files sent via email, do contain the correct (as far as Cobian 11 is concerned) folder names on both full and differential backups, and as they are presented as links, the Windows explorer can browse the folders.
Has anyone a strategy to avoid this behaviour?
Regards,
Brian
I've been experimenting with Cobian for a few months now and largely, it satisfies my needs.
However, there is one "undocumented" feature I have found. I believe is because of the way Windows 10 works (same for Windows 8.1, as far as my tests have found) and not really an issue with Cobian 11
If I configure a Full backup of the entire Documents folder on my Windows 10 Pro 64bit build and trigger a backup, Cobian backs up the entire folder as requested, compiles and emails a log file exactly as expected. If I then use Windows explorer to view the backup folder Cobian has created (I don't have compression or encryption switched on) instead of the being called something like... Documents 2020-12-27 13;38 (Full) it is called Documents with a timestamp identical to the Documents folder on my PC. If I login to the console of my NAS drive and examine the folder using the (Linux) file explorer I can see that the folder is named as I expected, but the timestamp is still same as the "Documents" folder on my PC. Subsequent "Full" backups produces additional "Documents" folders, which is likely to make restoring files from specific backup sessions a little bit tricky.
If I "clone" the Full Backup and change the backup type to Differential and then run this, then the software behaves exactly as expected with correctly named folders.
The "log" files sent via email, do contain the correct (as far as Cobian 11 is concerned) folder names on both full and differential backups, and as they are presented as links, the Windows explorer can browse the folders.
Has anyone a strategy to avoid this behaviour?
Regards,
Brian