ashleyw wrote:great - I've just added a new repository using the same server as previously but a new 60TB drive formatted as ReFS and now i see the option greyed out as expected.. great stuff.
So in my case the issue seems to be if you have an existing windows 2016 server hosting a Re-FS file system and you run an in-place upgrade, then there doesn't seem to be a way in the UI for it to properly detect the Re-FS file system. So I think if I switch the new backup jobs to that one then I should be good!
Yeah, that's what I was trying to say in this post
, sorry if that wasn't completely clear. There's simply no way to upgrade an existing, already created repo to support block clone, even if it was created previously on a properly supported ReFS volume. You can create a new repository on the same volume, move the files there (which would be basically instant since it's the same volume), and then remap all of the existing backups to this "new" repo, however, block clone still won't be enabled on the backup chain until the next full is created, either actively or synthetically.