operations wrote:240TB REPO on ReFS
operations wrote:I do not see a memory issue my Backup is at a crawl at the moment but the server that has 256GB ram in it says there is 120GB free, RAM is not an issue I could easily put in 768GB if that would help.
I presume based on what you are saying that converting to Full backups or synthetic fulls will not fix the issue ?
operations wrote:Based on the above and the fact that I have a 240TB REPO on ReFS, I need to do something so I was wondering what direction people are going ..
Migrate to NTFS ?
Run Full or Synthetics but stay on ReFS ?
... I cannot continue as my backup merges are killing my server and resulting backups taking days not a day.
operations wrote:Type of storage?
IBM SVC with 900GB 10K SAS
How many synthetic fulls per week ?
Size of VM causing the issue ?
from 127GB to 5TB
Frequency of backups ?
Last Active full ?
30 days running incr forever no scheduled active fulls hence the merge progress
Space available on disk (REPO)
Cluster size ?
How Much ram ?
Which registry keys + driver are you using ?
No keys + default driver shipped with OS
suprnova wrote:Im not saying this is the silver bullet. I do still have freezes but that means its time for an active full. However, when any public release refs driver from msft it freezes no matter what.
Definitely understand, at the moment even running one incremental merge with [fast clone] makes the repository drive become unstable. Everything was fine for awhile, but now it's back to ground zero. I have your same registry keys, but I am running the latest refs.sys driver.
That will not work! contact MS and get them to help you.
You do have a support contract right?
thomas.raabo wrote:what version of the driver do you have?