Yes I am doing it through the UI. Can't understand why I can create a folder, delete a folder but not a parent one.
All I can think of is that there is a dependency hanging with the parent folder that's precluding deletion.
The only issue with mapping the back-up is that, as admin, I have access to all. On the PC it is more convenient to map only the folders that matter to each user. Allowing the back-up to be seen confuses things a little (I know I can restrict the permissions to just me but still).
True, but you can temporarily map the HDD for the purposes of cleanup and then delete the map.
Out of interest. When Volume 1 "photos" is backed up to Volume 2 "photos", is it simply a case that all files with the same name are replaced, new files are added and files no longer on Volume 1 will remain as they are on the back-up folder?
If your DNS-320 HDDs are both configured as "Standard Volumes" and you scheduled a recurring incremental backup, then:
- New files in the source HDD are copied to the destination HDD
- Modified files in the source HDD overwrite files in the destination HDD
- Files deleted in the source HDD are not removed from the destination HDD
I personally run nightly incremental backups, and once a month I use a free third party software product installed on a PC to remove files/directories on the backup HDD that were previously deleted from the source HDD. The incremental backup ensures I don't lose files that I accidentally deleted, and the monthly sync activity gives me time to review the deletions before permanently deleting files/directories from the backup.
This approach also removes the need to manually go into the backup HDD and delete files and directories. The only time I manually manipulate the backup HDD is if I am reorganizing the source HDD directory structure (i.e. moving or renaming large directories). Rather than having the backup copy everything again, I restructure the backup HDD manually to avoid the wear and tear on the HDDs from unnecessary copying.