Best Practice for MS Server 2012 DeDup Repo

Availability for the Always-On Enterprise

Re: Best Practice for MS Server 2012 DeDup Repo

Veeam Logoby albertwt » Mon Jul 24, 2017 3:28 am

Great, thanks, Guido and tntteam for the confirmation on this backup limitation.
I will not enable the Windows OS deduplication for my Veeam backup repository.
--
/* Veeam software enthusiast user & supporter ! */
albertwt
Expert
 
Posts: 607
Liked: 19 times
Joined: Thu Nov 05, 2009 12:24 pm
Location: Sydney, NSW

Re: Best Practice for MS Server 2012 DeDup Repo

Veeam Logoby Delo123 » Mon Jul 24, 2017 1:46 pm

Are you sure you formatted with /L ?
Delo123
Expert
 
Posts: 348
Liked: 94 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

Re: Best Practice for MS Server 2012 DeDup Repo

Veeam Logoby tntteam » Tue Jul 25, 2017 6:32 am

I think dedup is great on windows, I think the most bad luck you can have is dedup will stop working. Corruption I think is rare.
BTW, win2016 and multi cpu dedup just rocks! It's the storage array that can't go fast egnouth now !!
Also I found out memory consumption to be less on win2016 that 2012.
tntteam
Enthusiast
 
Posts: 46
Liked: 4 times
Joined: Fri Aug 28, 2015 12:40 pm
Full Name: tntteam

Re: Best Practice for MS Server 2012 DeDup Repo

Veeam Logoby Delo123 » Tue Jul 25, 2017 9:04 am

Albert. We have been using dedup from the start and have been happy with 2012 and also 2016. Recently some ntfs bugs have been fixed in 2016 so as long as you keep to some basic rules discussed in these topics i would say you're quite safe. Dedupe certainly saves much more than ReFS, and ReFS has issues too (which will be solved of course in the future). Anyway, having a landing zone (non dedupe) and a secondary repositorie with Dedupe enabled for archiving for me still is the way to go!
Delo123
Expert
 
Posts: 348
Liked: 94 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

Re: Best Practice for MS Server 2012 DeDup Repo

Veeam Logoby Delo123 » Thu Jul 27, 2017 8:25 am

Dedupe still rocks, just checked one of our repositories. Saved 1.2PB on 270TB physical. This is a 2012R2 Server. Even the volumes with incremental only (R,T,V) dedupe quite well

PS C:\Windows\system32> get-dedupstatus

FreeSpace SavedSpace OptimizedFiles InPolicyFiles Volume
--------- ---------- -------------- ------------- ------
39.25 TB 188.58 TB 501 546 Q:
53.06 TB 42.26 TB 6252 6252 V:
54.55 TB 40 TB 72 72 T:
4.99 TB 175.46 TB 1296 1580 U:
52.99 TB 53.19 TB 125453 125453 Y:
53.64 TB 78.41 TB 22 22 S:
48.29 TB 49.36 TB 2430 2430 R:
57.69 TB 132.47 TB 350 351 O:
52.91 TB 62.83 TB 451 451 I:
26.67 TB 272.08 TB 783 783 H:
50.87 TB 64.28 TB 236 236 J:
44.6 TB 95.33 TB 365 365 G:
Delo123
Expert
 
Posts: 348
Liked: 94 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

[MERGED] Server 2016 deduplication -- considered reliable ye

Veeam Logoby cyberswb » Thu Jul 27, 2017 3:28 pm

I've used 2012r2 with deduplication successfully as a Veeam repository, but when I tried it with a 2016 repository server I got problems that went away when I disabled deduplication.

I read a number of people also had this problem and that MS was working on tracking down bugs in 2016 dedupe.

Has this generally been considered fixed or not? I paged back several pages worth of messages in this forum and didn't see anything new mentioning deduplication at all, which of course could mean "fixed" or "broken so long we gave up".
cyberswb
Influencer
 
Posts: 21
Liked: never
Joined: Mon Feb 01, 2010 7:41 pm
Full Name: Shawn Barnhart

Re: [MERGED] Server 2016 deduplication -- considered reliabl

Veeam Logoby Delo123 » Mon Jul 31, 2017 7:07 am

It was actually a NTFS issue and not a dedupe Issue.
From Gostev's Digest:
Good news for Windows Server 2016 deduplication users, but bad news for all NTFS users. Microsoft has finally nailed that phantom data corruption bug that I talked about here before. We actually had quite an exceptional experience working with Windows dedupe team on this bug – they were treating one extremely seriously from the start, and it was one of those rare cases when they pushed us for updates - and not the other way around. So it made me smile when in the end, it appeared that the bug was not even in the dedupe engine, but rather in the NTFS sparse files implementation. As such, Windows dedupe gets to keep its name clean – however, the update is strongly recommend that all NTFS users, and will be included in August "Patch Tuesday". And most importantly – anyone with "Volume bitmap is incorrect" chkdsk error on your NTFS backup repositories, be sure to perform an Active Full backup after installing this patch, because you current backups may not be good. And apply the same logic to any other data that uses Windows dedupe or sparse files (create a new instance of the data).

This includes the patch: https://support.microsoft.com/en-us/hel ... -kb4025334

Ps. Dedupe should be coming to ReFS sometime...
Delo123
Expert
 
Posts: 348
Liked: 94 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

Previous

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Google Feedfetcher, Yahoo [Bot] and 14 guests

cron