When using HBS to back up NAS data to cloud (eg. OneDrive), are there upper limits to be aware of around the number of files/directories to be backed up?
Also, does individually selecting multiple sub-directories (as opposed to selecting the parent directory) force HBS to process each selected sub-directory sequentially?
I am trying to backup a NAS directory containing thousands of files in sub-directories to OneDrive, with no version management - simply a clone of the data in case of NAS data loss. Each time I run the backup, it compares the source and destination to then replicate changes (adds, deletes, etc.) in the source to the backup copy. The comparison takes hours, and I think has resulted in the NAS memory being consumed to the point that the NAS stops processing altogether, and needs to be rebooted.
There should be no limits. If you don’t have version management selected, you are going to basically be doing a full backup of every file on the NAS each time you run the backup. HBS does not do incremental backups unless version management is selected. The replication you are saying is happening is not happening without version management turned on. Instead, it is taking so long because it is backing up every single file over and over and over each time.
Actually, I think HBS does compare files at both locations and then only transfers the needed changes. If you have thousands of files, this will still take a long time, especially over a slow connection or with limited cpu or memory.
Thank you for the replies. I can confirm that subsequent backups are not full backups all over again. In the Advanced setting section of Policies under Rules there are options to “Only back up updated files” and “Remove deleted data from the destination”
I tested this by creating smaller backup job and rerunning it immediately after the first backup finished and it took only a few minutes to run the compare and copied no files as nothing had changed.
It is the sheer number of files that I have in the source that is taking so long to compare. I was curious if this would cause excessive memory usage, to the point where the NAS pretty much stops responding.