Why is UrBackup hashing files when all is set to "raw"?

Server
1

Why is UrBackup hashing files when all is set to “raw”? I set things to"raw" because I am trying to conserve CPU and I have tons of disk space available.

Capture.JPG1090×322 94.3 KB

Capture2.jpg977×434 34.6 KB

1 Like
2

I’d like an answer to this as well.

Same issue my CPU has been pegged now that we have over 50 systems on this machine but we have more than enough storage to just do Raw backups

1 Like
3

Below is from a debug log, it states that it is doing the transfer without hashing, however it may be that the files are hashed so that they can be compared to during incremental backups?

2019-07-13 13:23:41: BCSS-XXXX: Doing backup without hashed transfer…
2019-07-13 13:23:41: BCSS-XXXX: Loading file list…
2019-07-13 13:23:41: Flushing FileClient…
2019-07-13 13:23:43: Flushing FileClient…
2019-07-13 13:23:43: Flushing FileClient…
2019-07-13 13:23:43: BCSS-XXXX: Started loading files…
2019-07-13 13:23:46: Starting shadowcopy “C”.
2019-07-13 13:23:46: Loading file “BOOTNXT”
2019-07-13 13:23:46: Flushing FileClient…
2019-07-13 13:23:46: GT: Loaded file “BOOTNXT”
2019-07-13 13:23:46: PT: Hashing file “BOOTNXT”
2019-07-13 13:23:46: Loading file “CCCP-20151102_1349.txt”
2019-07-13 13:23:46: HT: Copying file: “/RAID10/UrBackup/BCSS-XXXX/190713-1301/C/BOOTNXT”
2019-07-13 13:23:46: GT: Loaded file “CCCP-20151102_1349.txt”
2019-07-13 13:23:46: HT: Copying file to “/RAID10/UrBackup/BCSS-XXXX/190713-1301/C/BOOTNXT”
2019-07-13 13:23:46: PT: Hashing file “CCCP-20151102_1349.txt”
2019-07-13 13:23:46: Loading file “CiscoUserAgent.sdf”