We have veeam o365 writing a few jobs to an REFS drive. Roughly 6 or 7 TB of data.
Now we have created a Windows agent job in B&R to back up those job folders to our hardened repo.
The job has been running about 16 hours, has gone up to 99% and been there for hours, and shows an insane amount of TB processed and copied when in reality only about 4ish TB of data has hit the repo from what I can tell.
Is this normal (we've never done a windows agent job before, only hyper-v)?
Seems to be a bug.
Do you have a case number? If not, please open a case and let our customer support troubleshoot the issue. We cannot investigate such an issue over a forum post. Without a case number, this topic may be deleted by a moderator.
finally completed over 40 hours later. says 2.3 petabytes processed and 587 terabytes transferred lol. Actual is 8 TB (which lines up with what it says was "read" down in the job details. Will upload logs to the case now that it completed.
Thank you for contacting Veeam Support.
My name is xxxxx and I'll be assisting you with this case.
It looks like this was initial run of the job which suppose to take longer time.
All other runs should be incremental and take less time to complete."
Got the private fix (since we weren't quite ready to move to 12.1 which has it included i guess?) but it looks like the windows agent process just isn't nearly as efficient as hyper-v... even the incremental apparently needs to read through the entire volume (40tb in our case) to process and back up ~8tb of data, so it was still going to take too long. Reworked things to move that data into a vm so we can do it all with hyper-v level backup. Thanks guys!
p.s. - I'm not actually following what you mean. If I do a volume backup, that would back up the whole volume (40ish tb) which is exactly not what I want... I only want to back up a few folders (which constitute around 8 tb of data)...
