JaySt wrote:quick reminder about the RefsVirtualSyntheticDisabled registry value. if i understand correctly, this disables fast clone functionality on ReFS volumes. I have not tried it myself.
If you like to switch due to fast-clone problems, It could be an option to not re-format a repository to NTFS but just keep data for a while and use ReFS without fastclone by setting this value. Right?
I still have hopes there will be a fix.... eventually...
thomas.raabo wrote:Yes but it DOES NOT disable general interaction with the API - integrity streams are still getting pushed by veeam
Ok, but are you saying you expect to still see issues when this registry value is used?
DaStivi wrote:as far as i understand right now:
- never go up to more than 64TB per REFS Volume!!!! (issues starts directly -> slow performance etc..) True
- only use forward incr. forever (no syn fulls, this is primary the root cause of many problems, refs would make syn fulls "fast" because it just repointers tables... but basically this looks like to be a big issue, because more syn fulls means more and more pointers to be made and taken care of it) Not sure I agree, more chance of corruption not to mention slow restores.
- never let the refs volume get full, i guess leave at least 10, better 15 or 20% of free space I wouldn't let any volume get full
- don't backup very large vms to refs (vms bigger couple of TBs) I have an 8TB job that runs synthetics daily. As long as I run an active full every 2 months no issues.
- when formating refs make totally sure that you select 64k Block size!! -> 64k was default till server 2012r2, but now with server 2016 "default" settings is 4k be carefull to select 64k there!!!
DaStivi wrote:i've couple of Veeam installations where refs does its job very good, and i've installations where i had big troubles with refs and gone back to ntfs now!
kubimike wrote:Get the beta driver, apply all the settings mentioned in this thread.
Lunatic Magnet wrote:Based on threads earlier around page 35-39 several people stated that the beta driver was included in the July Cumulative updates. My server was built in September and has the latest updates and it states that KB4025334 isn't applicable. My refs.sys driver version is 10.0.14393.1770.
The MS article says Specify the indicated values in the following subkey: Is that indicating they should already be there? In my case they are not.
Users browsing this forum: No registered users and 40 guests