External drives can take advantage of the dedup as well. I use 4TB external drives with dedup and each are ~8TB of data on them. It is far cheaper (for me anyway) to grab two 4TB external drives and get ~16TB of storage out of them. They are only running on a per/use basis and dedup is only done periodically when needed and not scheduled (obviously since they are not plugged in most of the time). 8 and 10TB externals are coming down in price and I will eventually migrate to those and retire the 4TB's to a good home somewhere. Until then, the 4TB+Dedup saves me money and practically doubles my storage. Another option if the WD Gold 8TB Datacenter HDD's go down a little more, would be replace the 4TB drives and insert the WD Golds into the current external enclosures and dedup them. Hello, My name is BillyG and I am a data hoarder
I know this is the Windows 10 thread, but I am still using Win 8.1 and would prefer to. So do I use the 8 x64 package or the package from the Win 10 thread? And, how to install it (Win 8 package) without issues (given that I can run things in Admin)? There are 3 .cmd files: Code: Win8.1x64-Data-Dedup-Install.cmd Win8.1x64-Data-Dedup-Un-Install.cmd Disable-Background-Tasks.cmd There is no readme, how to .. I get the Install/ vs Uninstall - But there is not talk of when/ how / if to use/ run the 3rd .cmd?
I can say similar things, but I really see DeDup benefits in areas where I have 5 Win Server ISOs that have 90+ % in common with each other. Give it to MS to fragment stuff like that. In that case, I really feel its stupid to let them take x5 times the space. And the fact that I do not use most of these all the time, it makes sense to archive via DeDup (if I can figure out how to get it installed for starters). Why give the Same Win OS (overlapping) 30 GB when it can be done in 6 GB.
with that few of ISO's it would really benefit you to use Smartversion patches (SVF) from 1 iso to the rest. Whereas I have all of MSDN archived, mostly ISO's there and dedup is more useful with that.
Exactly my point. I have lots of old ISOs that I do not use all the time. Might as well archive them into a DeDup VHD and drop it to the side. Pull an ISO from it during the rare times I need one. Again, each person has to choose their need/ use and some may not like DeDup at all. PS: How do I get this working on my Win 8.1.1 i.e. U3 I think.. ???
Usually you put the deduplication on something that act as a server, no matter if something like an HP microserver using windows, or a NAS using a deduplicated ZFS pool, and then share the data via SMB/FTP/NFS/Whatever. Then the data access is guaranteed transparently to any OS, so no problem there. Also about the disk spinning I'm afraid you have the wrong idea about how the things are working. The deduplication process is a task, that starts in the early morning and that last for few minutes after the initial run that may require hours or even days. Only when you change a large amount of data the deduplication task lasts for long time again. Then there are the weekly process, running Saturday by default that are checking for errors and for freed disk areas, again is matter of few minutes if nothing is wrong and no big amount of data are deleted from the partitions. Also there is a timeout of 3 days to leave untouched the data changed frequently, and you can also exclude whole directories and files by extensions. In short the deduplication has some things that needs to be taken in account (harder data recovery in case of accidental deletions or HW failures for example), but what are you mentioning aren't problems at all. Something like Stabilebit Drivepool, that makes possible to duplicate a whole disk or selected folders in a smarter way than a old school RAID is the perfect companion for the deduplication. If used together intelligently they will provide redundancy and huge amounts of saved space over traditional solutions.
Each OS need its matching package bat are like cmd, both execute command lines well, the dedup package is not for beginners, whom understand it should already know how to install/work with it
My dear friend I've been playing with .BAT since before Win 3.1 when people actually knew what Autoexec.bat did. I've coded device drivers and C++ in the past and written DLLs using Win 32 API before .NET came around and MFC was microsofts crappy attempt at class libraries. I know .BAT & .CMD they are similar, but when there are various releases from various authors with various ".CMD/ .BAT" files with no clear "timeline / chronographical order" or release numbers, one has no idea which release is what, which is stable and working / what is more up to date and bug fixed. I understand fundamentally what is being done. But, given the mix of diverse and unclear "outline" it just confuses an "advanced user" like me as to which package to use and if the Install scripts are fixed/ updated. So I'd really appreciate some clarity on these various releases, where there is no visible and clear "linkage" between the above 2 "sources" I mentioned. So, please realize you are not speaking with a "beginner". I'd appreciate some clarity.
You need to install N packages and enable them Who cares if you do it copying and pasting the commands in a command prompt, launching them in a .bat or .cmd file. Same thing.
Every batch I've seen yet works this way Code: dism /online /norestart /add-package /packagepath:Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab /packagepath:Microsoft-Windows-FileServer-ServerCore-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.cab /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab /packagepath:Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.cab dism /online /enable-feature /featurename:Dedup-Core /all The install part could be split in single lines instead of one line only. Just matter of preferences coding habits, there isn't any accurate v.s.inaccurate thing (assuming the packages are the right ones)
So I did a little comparative analysis of the packages of the Releases from Various Sources using Beyond Compare: Y = Yes, Indicating file is present - Blank space = File not present Y: CRC = Same CRC, Y: Size = Same size, d-CRC = diff CRC I'd love to hear about the pros and cons, whys etc: Which of these file categories are key/ must have, purpose & why? Which are "nice to have" & their purpose - why install/add? Why were some removed? Order of Install/ Add? Do we need /norestart - any pros/cons besides prevent restart? Between 6.3 and 6.4 how do I know which is better fit for my Win 8.1 OS? Pasted from Excel - Can paste as Image if wanted. Source of Package Release Win 8x Thread MSMG 5.2 One Drive Included Files/ Packages in the Release (ignoring Language specific files) W 8.1 W 8 6.3 6.3 6.4 6.2 Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab Y: CRC Y: CRC Y: d-CRC Lg-Size Microsoft-Windows-FileServer-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab Y: Size d-CRC Y: Size d-CRC Y: d-CRC Lg-Size Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab Y: CRC Y: CRC Y: d-CRC Lg-Size Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab Y: Size d-CRC Y: Size d-CRC Y: d-CRC Lg-Size Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab Y Microsoft-Windows-VdsInterop-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384.cab Y Package_2079_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.cab Y: CRC Y: CRC Package_2093_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.cab Y: CRC Y: CRC Package_2117_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.cab Y: CRC Y: CRC Package_2131_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.cab Y: CRC Y: CRC Windows8.1-KB3094197-v2-x64.cab Y Windows8.1-KB3100527-x64.cab Y Windows8.1-KB3127060-x64.cab Y Windows8.1-KB3137923-x64.cab Y Windows8.1-KB3138865-x64.cab Y Install Script - Package Add Order .CMD .BAT dism /online /add-package FS-6.3 > DD-6.3 > 4xKB-6.3 VD-6.4 > FS-6.4 > DD-6.4 dism /online /enable-feature DD-C > FS-SS DD-C /norestart
You are complicating things too far it's easier to test adding one of those and verify working, and it's done all the packages are custom-made, so the difference in hash and size is expected VdsInterop packages is included within FileServer package, so no need for it separately i vote for using MSMG pack and scripts the updates packages in MSMG are not all needed, some are superseded you only need: Package_2117_for_KB3000850, KB3127060, KB3137923 additionally, you also need the July rollup update KB3172614