Comprehensive data protection for all workloads
poulpreben
Service Provider
Posts: 960
Liked: 405 times
Joined: Jul 23, 2012 8:16 am
Full Name: Preben Berg
Contact:

Re: Windows 2019, large REFS and deletes

Post by poulpreben » Nov 07, 2019 7:20 pm

It is capable of it, but I can try to disable it as a test.

Were you able to reproduce the issue with a simple 'fio' test or something, or was it only Veeam that triggered the slowdown?

rhys.hammond
Veeam Vanguard
Posts: 57
Liked: 9 times
Joined: Apr 07, 2013 10:36 pm
Full Name: Rhys Hammond
Location: Brisbane , Australia
Contact:

Re: Windows 2019, large REFS and deletes

Post by rhys.hammond » Nov 08, 2019 12:21 am

Was told by another Veeam SP that regularly emptying the 'System Working Set' using RAMMap fixed their ReFS performance issues on 1809.
Just tried it but unfortunately, the customers disk speed is still 'saw-toothing' and performing very poorly until the next restart.

I'm going to try one last thing before wiping 1809 and loading, going to delete the 1 x 200TB ReFS volume and create 2 x 100TB ReFS volumes.
I don't want to create smaller volumes as ReFS block cloning doesn't work across volumes.
Veeam Certified Architect | Author of http://rhyshammond.com | Veeam Vanguard | vExpert

mkretzer
Expert
Posts: 565
Liked: 126 times
Joined: Dec 17, 2015 7:17 am
Contact:

Re: Windows 2019, large REFS and deletes

Post by mkretzer » Nov 09, 2019 5:08 pm

@poulpreben we only had issues with block cloned Veeam data but we did not did test with > 100 TBs of block cloned non-Veeam data which is necesarry for the issue to happen for us.

poulpreben
Service Provider
Posts: 960
Liked: 405 times
Joined: Jul 23, 2012 8:16 am
Full Name: Preben Berg
Contact:

Re: Windows 2019, large REFS and deletes

Post by poulpreben » Nov 09, 2019 5:29 pm 1 person likes this post

As an isolation step, we ended up taking the old volumes offline and creating new ones. We tested so many things to no avail, and in this case it was easy since the customer has only 30 days of retention.

I guess we’ll see once there is more than 100 TB data on the server again. It’s now running with the 2019-10 Cumulative Update as well. For now it seems super fast.

Ben.online
Lurker
Posts: 1
Liked: never
Joined: Nov 12, 2019 1:30 pm
Contact:

Re: Windows 2019, large REFS and deletes

Post by Ben.online » Nov 14, 2019 3:19 pm

Hello,

We are about to go in production with a Veeam repository Server 2019 build 1809 and this topic does not make me happy.
I thougt the ReFS issues were all resolved but sadly i found this when checking for the refs.sys version from the Server 2019.

a few thing i missed or are unclear to me.

- Are there any reports of these issues on Server 2016 after the .2457 update? And is 2016 just a good for ReFS as a patched 2019 a Gustov said?
- As i understand the server 2019 build 1903 works fine but is core only and support ends mid 2020 is that correct?
- What is best version of Refs.sys in server 2019 build 1809 and has anyone tried to use the refs.sys from build 1903 on a 1809 build?

Gostev
SVP, Product Management
Posts: 24929
Liked: 3620 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Windows 2019, large REFS and deletes

Post by Gostev » Nov 14, 2019 3:35 pm

1. 2016 is a safe choice, this topic is about issues with 2019.
2. Correct.
3. Microsoft will not support this driver swap. For 2019 LTSC, just make sure you have all Windows updates installed.

jasonede
Service Provider
Posts: 34
Liked: 9 times
Joined: Jan 04, 2018 4:51 pm
Contact:

Re: Windows 2019, large REFS and deletes

Post by jasonede » Nov 14, 2019 5:10 pm

Is the latest build of 2019 with all updates fine on ReFS? I'm a little unclear if all issues are resolved or if they're just with very large repositories.

mkretzer
Expert
Posts: 565
Liked: 126 times
Joined: Dec 17, 2015 7:17 am
Contact:

Re: Windows 2019, large REFS and deletes

Post by mkretzer » Nov 14, 2019 5:41 pm

2019 still has issues with larger volumes from what i can tell (even if it is not as bad as before). But 1903 has *really, really* been totally stable for us for the first time since we use REFS (2 years now). All our issues only went away with 1903. But we have backup copy destinations which are ~110 TB big which not once had any issue even with 2016.
So for smaller setups 2016, 2019 should both be find for small repos if you have enough RAM.

Post Reply

Who is online

Users browsing this forum: nmdange and 17 guests