I’m looking to configure HBS3 with myQNAPcloud Storage as a cloud repository to backup a few file shares held on my qnap.
I’d like a bit of guidance / best practice advice.
My initial attempt at configuring a backup job resulted in one full backup, then nothing but incremental backups of which nothing was transferred as the data had not changed.
I would like to have a full backup daily regardless of whether the data has changed or not.
I’m coming from a Veeam background and I’m used to incremental backups that then roll up into daily full backups.
Can I achieve something similar with HBS.
I’ve also noticed, that although HBS uploads the data into myQNAPcloud Storage quickly, it seems to only restore that data at about a 10th of the speed it uploaded it. It that right? Restore download speed slower than upload?
I use HBS and myQNAPCloud. I have a few questions…
Why do you want to do full backups every time? If nothing has changed, then what’s the issue? If something has changed, then only the changed items get backed up. You can enable version control which allows you to keep x number of versions on the cloud. So if you changed a file and then wanted later to get the original version back, you can do that. Online storage is not cheap. You could easily fill up your storage space quickly keeping multiple copies of full backups. And if you were to overwrite the full backup, you lose any ability to have version control. I don’t think HBS even allows you to do full backups like that. It is just not efficient. You can enable Smart Versioning which keeps hourly, daily, weekly and monthly backups. I think that is what you are looking for.
As for recovery speed, I’m not sure. It could be dependent on a lot of things. I have not tried recovering from the cloud yet (hope I never have to). I have downloaded stored files from myQNAPCloud and it’s decent speed although it does not fill my 2Gbit/s download pipe…
I think my need for full backups is my way of protecting from backup corruption. Having just one full backup, then incremental backups after that, doesn’t feel right to me.
I think I will look at alternative backup solutions for now.
1.) Do your first backup which is a full backup and make sure versioning is enabled.
2.) Run a data integrity check on the backup. - Verify there is no corruption
3.) Do your subsequent incremental backup
4.) Run a data integrity check again.
Now, I have not attempted to run data integrity checks on my backups, but I am pretty sure you can schedule these to run after the backup is complete. I’m not sure how long they take (I was attempting it once on my main backup to my secondary NAS and it was taking quite a while). I “assume” the first integrity check will take a long time and I assume subsequent checks will take less time - but I am not positive. But that would seem to follow as once the system knows that the base data is good, everything that is added to it incrementally should just need to be checked.
Now, if anything shows as corrupt, you can recover the previous version which was already shown as not corrupt.
You have more efficient backup storage and quicker backups now.