Hello, after the backup, the server takes the HASH records of the files on the same disk, which is a situation reduces performance.
My suggestion is to take the HASH records to a different disk. I think that using an SSD for HASH will provide a great performance.
What do you think?
Why don’t you try mounting a different disk where the urbackup db is stored? Hashing performance will be dependent on CPU too.
DB located in OS disk (SSD)
In the task manager, all loads are at low or normal levels. However, HDD is 100%
DB doesn’t have to be on OS disk - try mounting a different disk at /var/urbackup
That’s normal since hashing is reading all of the backup’s files back from the storage to hash them.
I also want this not to be normal
so if the hash data is saved to a different disk it will increase the overall performance
This is not the topic/suggestion
You don’t understand. The hash data is stored on the SSD already. But creating the hashes requires reading the backed up files, which is always going to be reading from where the files are i.e. the HDDs (unless you back up to SSDs, but…)
I don’t really understand the purpose of this request.
If the bottleneck is uploading and then reading files on the server HDD (rather than hashing and db ops) then you could mount a fast SDD on tmp and set the flag in advanced settings for ‘Temporary files as file backup buffer’.
Hash recods in backup folder with same folder tree
