Building new Windows 2016 Veeam Server

Availability for the Always-On Enterprise

Building new Windows 2016 Veeam Server

Veeam Logoby ryanm » Mon Feb 13, 2017 7:36 pm

I'd like to build a new physical Windows 2016 Server to use with Veeam. Would like to utilize the new dedupe capabilities inside of Windows 2016.

Just want to get an opinion as the best settings to use for the repositories. Are using NTFS repositories formatted with this command still the most current Best practice?
format <volume pathname> /A:64K /L from this post https://www.veeam.com/kb2023

These volumes will about 50TB in size once formatted.
ryanm
Novice
 
Posts: 5
Liked: 1 time
Joined: Mon Dec 16, 2013 5:17 pm

Re: Building new Windows 2016 Veeam Server

Veeam Logoby Gostev » Mon Feb 13, 2017 8:01 pm

Yes, Windows Server 2016 does not change these recommendations.
Gostev
Veeam Software
 
Posts: 21039
Liked: 2266 times
Joined: Sun Jan 01, 2006 1:01 am
Full Name: Anton Gostev

Re: Building new Windows 2016 Veeam Server

Veeam Logoby mkretzer » Tue Feb 14, 2017 5:19 am

@ryanm I don't know if you follow this forums posts so a quick warning: Wait for todays MS update before you enable deduplication to avoid data corruption!
mkretzer
Expert
 
Posts: 236
Liked: 54 times
Joined: Thu Dec 17, 2015 7:17 am

Re: Building new Windows 2016 Veeam Server

Veeam Logoby Mike Resseler » Tue Feb 14, 2017 5:21 am

@mkretzer

Is the KB32xxx implemented in todays MS Update cycle? And more importantly, are you aware that they fixed the issues that were in it?
Mike Resseler
Veeam Software
 
Posts: 2604
Liked: 314 times
Joined: Fri Feb 08, 2013 3:08 pm
Location: Belgium, the land of the fries, the beer, the chocolate and the diamonds...
Full Name: Mike Resseler

Re: Building new Windows 2016 Veeam Server

Veeam Logoby mkretzer » Tue Feb 14, 2017 6:34 am

@Mike Not 100 %. But i got an email from microsoft yesterday which sounded like it (at least for our REFS issues and the dedup issues were fixed in the same "problematic" update).
mkretzer
Expert
 
Posts: 236
Liked: 54 times
Joined: Thu Dec 17, 2015 7:17 am

Re: Building new Windows 2016 Veeam Server

Veeam Logoby Mike Resseler » Tue Feb 14, 2017 6:45 am

We had some talks last week with MSFT and the KB indeed solved the ReFS and Dedupe issues but it was shown (and out QC team investigated it) that it breaks something else. Especially on a VBR server with SQL it would make it unusable so that is why I want to be sure that the problem is solved :-)

But if they add it today in the regular update cycle that means they should have solved it.
Mike Resseler
Veeam Software
 
Posts: 2604
Liked: 314 times
Joined: Fri Feb 08, 2013 3:08 pm
Location: Belgium, the land of the fries, the beer, the chocolate and the diamonds...
Full Name: Mike Resseler

Re: Building new Windows 2016 Veeam Server

Veeam Logoby ryanm » Tue Feb 14, 2017 2:05 pm

I am aware of some W2016 corruption issues, but it's my understanding that only effects REFS? Was planning on running NTFS unless everyone suggests other wise.
ryanm
Novice
 
Posts: 5
Liked: 1 time
Joined: Mon Dec 16, 2013 5:17 pm

Re: Building new Windows 2016 Veeam Server

Veeam Logoby mkretzer » Tue Feb 14, 2017 2:50 pm

REFS has no corruption issues that i know of, only instability. The corruption issues are with 2016 NTFS + DEDUP
mkretzer
Expert
 
Posts: 236
Liked: 54 times
Joined: Thu Dec 17, 2015 7:17 am

Re: Building new Windows 2016 Veeam Server

Veeam Logoby kubimike » Tue Feb 14, 2017 8:29 pm

I run ReFS no Windup and don't have issues. I use REFS for its cloning ability. Its when you enable Windows dedup apparently the problem becomes a BIG problem.
kubimike
Expert
 
Posts: 133
Liked: 20 times
Joined: Fri Feb 03, 2017 2:34 pm
Full Name: MikeO

Re: Building new Windows 2016 Veeam Server

Veeam Logoby rendest » Tue Feb 14, 2017 8:34 pm

There are big problems with ReFS in general. Dedup or not.

Either way, seems like Microsoft still hasn't got a clue what went wrong with the update: https://www.onmsft.com/news/microsoft-delays-february-patch-tuesday-update
rendest
Influencer
 
Posts: 18
Liked: 5 times
Joined: Wed Feb 01, 2017 8:36 pm
Full Name: Stef

Re: Building new Windows 2016 Veeam Server

Veeam Logoby vanhovejens » Tue Feb 14, 2017 8:49 pm

ReFS is just terrible to use when there is just a bit latency,,,
We've got quiet good performing storage which handles refs really well (minor performance to ntfs).
The slightly less performing backup storage is usable on NTFS volumes and with ReFS it's just awful,,,
guess ReFS underneath cannot handle with any io waits which results in awfull performance and it makes it just unusable.

@mike feel free contacting us we've already have an open veeam case but were rolling back to ntfs on our 'slower' boxes since we guess that a resolution isn't really in the make at this time...
The latest MS KB is installed on the repo servers only so veeam can still run and we've got the ReFS 'fixes'
vanhovejens
Service Provider
 
Posts: 7
Liked: never
Joined: Fri Apr 05, 2013 4:35 pm
Full Name: Jens Van Hove

Re: Building new Windows 2016 Veeam Server

Veeam Logoby kubimike » Tue Feb 14, 2017 8:52 pm

@rendest like what? I haven't encountered any yet.
kubimike
Expert
 
Posts: 133
Liked: 20 times
Joined: Fri Feb 03, 2017 2:34 pm
Full Name: MikeO

Re: Building new Windows 2016 Veeam Server

Veeam Logoby mkretzer » Wed Feb 15, 2017 5:19 am

mkretzer
Expert
 
Posts: 236
Liked: 54 times
Joined: Thu Dec 17, 2015 7:17 am

Re: Building new Windows 2016 Veeam Server

Veeam Logoby Mike Resseler » Wed Feb 15, 2017 6:42 am

@Jens,

So you have those latest fixes and it is still giving you issues with ReFS? Do you have 4K or 64K?
Mike Resseler
Veeam Software
 
Posts: 2604
Liked: 314 times
Joined: Fri Feb 08, 2013 3:08 pm
Location: Belgium, the land of the fries, the beer, the chocolate and the diamonds...
Full Name: Mike Resseler

Re: Building new Windows 2016 Veeam Server

Veeam Logoby rendest » Wed Feb 15, 2017 8:23 am

(works in same company as Jens)

4K was a complete disaster (see the horror story thread), I wouldn't recommend this to anyone, and I can't imagine why this would be the DEFAULT option.

64K improved A LOT. But that's probably due to the decrease in IO.

Memory leak + crash in the refs code in general was fixed in the KB of Jan 27th, however it didn't help with the filesystem time-outs.

The last KB which had the SQL leak was supposed to help with performance (we installed it since we have seperate repository servers which do not perform SQL queries). Long story short: performance is still poor when experiencing latency (as in, 100ms hiccup, results in a 20sec filesystem time-out where no IO is processed and Veeam is just "me zijn vingers aant draaien").
rendest
Influencer
 
Posts: 18
Liked: 5 times
Joined: Wed Feb 01, 2017 8:36 pm
Full Name: Stef

Next

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Google [Bot], seananaya and 31 guests