Postroom-online Ltd. Is the UK's No.1 print finishing supplier, specialising in the supply and maintenance of mailroom and print finishing machines. Our specialist product range includes folder inserters, paper folding machines, booklet makers, business card cutters, creasing machines, perforators and a wide ride range of punches, cutters and trimmers. Aleratec 1:10 USB 3.0 Flash Drive Duplicator Mini V2 for Windows & Mac, Black. 4.1 out of 5 stars 8. Get it as soon as Thu, Apr 8. Mar 24, 2021 Arkane Studio’s Deathloop To Be Released on May 21. IMAGE CREDIT @ Arkane Studio We haven’t heard much about Arkane Studio’s Deathloop yet, but it has been confirmed that the first-person shooter is headed for the next generation of Gen consoles. A couple of days ago, Bethesda Softworks’ YouTube channel announced a new release date and released a trailer for Death Loop that features a.

1. Window Duplicator Machine
2. Window Duplicator Kit

the Backup Utility for Windows

** Version 3.7.6 Released May 25, 2020 **

Automatically backup files, directories, even entire drives!

Karen's Replicator copies selected files from one drive/folder to another. Source and Destination folders can reside anywhere on your network.

Options include:

• Repeated copies at intervals as short as a few minutes, or as long as several months
• Copying only the files that have changed
• Removing folders and files from the destination if they have been deleted from the source
• Ability to exclude files, specifying which files should not be copied
• Ability to exclude days, specifying which days a job should be skipped

I apologize that there is not a formal manual available describing the use of Karen's Replicator. There is a helpfile that can be viewed by clicking the Help button after the application is installed. Also available are Karen's own wordsdescribing Replicator available by reading her newsletter (links below). Plus, several people have made helpfulYouTube videos (links below).

For more information, read these back issues of Karen's Power Tools newsletter:

Helpful YouTube videos made by Replicator users:
Thank you!

Download

Window Duplicator Machine

Knowledge Base (FAQ)

Window Duplicator Kit

• Click here for commonly asked and answered questions.

I can't find Replicator!

You've installed Replicator, but when you run it, or after you restart your computer and it's supposed to be running, it can't be found?

Replicator is probably running minimized with only a System Tray icon indicating it is running, but that little icon is hidden in the Windows 10 'I don't wanna see this every day' system tray area.

Please see this knowledge base article: I installed Replicator and set it to minimize to system tray, but now I can't see it's running.

Known Problems

• See project workboard at https://phabricator.karenware.com/project/view/1/
• To report a problem, please open a ticket at https://helpdesk.karenware.com/open.php

Enhancements/Bugs Fixed

Version 3.7.6 2020-05-25 [View Workboard]

1. Fixed logic error in ApiFolderExists(): On some machines reports a missing folder as exists, so the destination folder isn't created. Literally: Error 3 - The system cannot find the path specified
2. Now able save Unicode characters to the log file
3. Delay removed from most progress strings while running

Version 3.7.5 2019-11-02[View Workboard]

1. T14 Free Space progress bar and Global Exclusions now work for drives accessed using the direct UNC ? prefix on Source and Destination Folder path names.
2. T139 Pause Job button added. Also added warning dialog when pausing or aborting a job when a file copy is still in progress.
3. T176 Job index # column added so you can sort back to how it was after accidentally sorting by another column.
4. T177 Warning dialog when minimizing to System Tray because Windows 10 hides those icons by default and that confuses everyone eventually.
5. T178 Added FAQ button to main window which will ask the user if they want to open the frequently asked and answered questions page on our website.

Version 3.7.4 2019-02-18[View Workboard]

1. T127 Replicator window falls behind others after Browse for Folder

Version 3.7.3 2019-01-14[View Workboard]

1. T119 Removed debug keystrokes like F8 because was causing problem for user.
2. T121 All Replicator windows now include version number in the caption.
3. T120 Installer now makes a (optional) backup copy of Replicator settings before installation.
4. T122 Installer now checks for running Replicator process and requires it to be closed before installation.

Version 3.7.2 2019-01-09[View Workboard]

1. T29 Verified can copy really long pathnames.
2. T36 Setting destination subfolders' timestamps to match source folders.
3. T75 Improved progress indication when running job:
   • Updating display only once per second improves performance
   • Abbreviating byte counts to traditional KB/MB/GB/TB based on 1024 bytes per KB, etc.
   • Added file copy throughput in bytes/second (abbreviated based on 1024 bytes per KB, too)
4. T108 Greatly improved performance by offloading file copy to operating system.
5. T113 Fixed bug where settings were not saved if the system was rebooted without first exiting Replicator.
6. T116 Replicating source folder attributes so custom icons will work on destination folders when Desktop.ini is replicated.

Version 3.7.1 2018-12-06[View Workboard]

1. T61 Fixed Reset Grand Totals button function on Other Settings.
2. T102 Added /QUIT switch to command line start options to force Replicator to close after completed jobs specified on the command line, or when Exit clicked, without regard to the Warn User configuration option.
3. T107 Forcing Replicator to close without Warn User dialog when system is shutting down, user is logging off, or application being closed by Task Manager. Added Other Settings option: Minimize Window Instead of Closing, which will minimize the window if user clicks upper-right X to close the window. Can be combined with Minimize to System Tray option.

Version 3.7 2018-10-03

1. T1 Explicitly creates Settings, Log File, and Job Destination directories to avoid Path Not Found errors on Windows 10 v.1703, Windows 8.1, some versions of Windows Server, and similarly on machines where destination directory structure access control lists disallow reading directories farther up the tree.
2. Windows version reported in log file correct for Windows 7 and Windows 8. When running Replicator on Windows 10, the Win32 API reports the manifest version as Windows 8 -- because that was the last version of Windows on which the API GetVersionEx wasn't deprecated. The version reported is actual the version of the Windows for which the executable was prepared. Windows 10 uses a modern manifest system for which Replicator hasn't yet been specifically prepared.

Previous Versions

• Version 3.6.9: Not exactly sure.. (FB post about it)
• Version 3.6.8: Fixed bug that prevented you from editing a job immediately after changing the order jobs are displayed in the Settings Window. Also made change that might help prevent a 'race' condition that rarely kept the 'Run Highlighted Jobs Now' button from being enabled after more than one job was selected using the <Click>-<Shift>+<Click> technique.
• Version 3.6.7: Fixed bug I recently introduced, that caused only the first wildcard to be processed, when a filter contains more than one wildcard.
• Version 3.6.6: Allowed program to browse unlimited number of network providers, domains, servers and shares. Previously this had been limited to approximately 16 of each type of object.
• Version 3.6.5: Fixed bug (that I introduced in version 3.6.2) that cause log entries describing errors to mysteriously end with the extraneous characters 'par'.
• Version 3.6.4: Changes the way the programs creates shortcuts. Hopefully it will cause the shortcuts to display their icons more reliably.
• Version 3.6.3: Program now detects source files whose contents are locked (as opposed to the file being locked) before attempting to copy the file. This prevents zero-length destination files in those cases where the source file is accessible, but its contents are not.
• Version 3.6.2: Fixed bug that caused the program to write incorrect log entries when the text contained a curly bracket ('{' or '}'). Note: This fixes the way new log entries containing curly brackets are written. If you already have such an entry in your log file, created by an older version of the Replicator, you'll need to erase your old log file in order to see the new entries.
• Version 3.5.12: Fixed two typos, and added workaround that should help certain buggy visual themes display correctly.
• Version 3.5.10: Added two options to make the program cooperate better with screen readers. Now, there's an option on the 'Other Settings' dialog that allows you to disable the 'Past Due' warning dialog. Another new options allows the user to disable the program's Beep sound, and substitute a window 'flash' instead, if desired.
• Version 3.5.9: Made another change to try to fix Weekday Name tag bug. Note: This bug only affects those are using tags in their Destination Folder names, and whose country starts counting weekdays from some day other than Sunday.
• Version 3.5.8: Made changes to Weekday Name tags, hoping to make it work correctly with non-U.S. versions of Windows where first day of week is not Sunday. May have fixed the problem, or may have made it worse.
• Version 3.5.7: Made Global Exclusions case-insensitive.
• Version 3.5.5: Program now updates progress bar, showing 100% copied, when finished copying small files. Also added additional code to ensure program sets Windows' current directory to the program's own installation folder, when a job has finished (this may prevent drives appearing to be in use after a Replicator job has finished).
• Version 3.5.3: Added restriction on form of Destination folder. It can no longer end, or begin, with a space character.
• Version 3.5.2: Fixed (recently introduced) bug that prevented settings from remembering value of checkmark 'Copy Files Only if Changed or Added'.
• Version 3.5.1: Fixed bug that sometimes caused file copy and disk free space progress bars to not be displayed.
• Version 3.5.0: Added job option (which is on by default) that causes destination files to be temporarily renamed, while a new copy is created. If the new copy is successful, the old version of the destination file is deleted. Otherwise, the old copy is restored to its original name.
• Version 3.4.11: Fixed bug that prevented some source files from being opened when run under Windows 95, Windows 98, Windows 98 SE and Windows ME. Also made some improvements to the logging code.
• Version 3.4.10: Fixed bug that prevented program from displaying the settings folder, in the About window, when running under Windows 95, Windows 95 SE and Windows ME.
• Version 3.4.9: Increased the space, on the View Log window, where the name of the log file is displayed. This should help prevent the truncation of the name when the path is long.
• Version 3.4.8: Added a help file to the Replicator. Now, you can press the <F1> key while viewing most of the program's windows, or click any of the many 'Help' buttons, to view the help file's contents.
• Version 3.4.7: Fixed long-time bug that prevented the Replicator from copying files that were being written to by another program. It's still possible for another program to prevent the Replicator from accessing an open file. But if the other program cooperates, the Replicator will now take what it can get.
• Version 3.4.6: $Recycle.bin (Vista's Recycle Bin folder) is now added to existing Global Exclusions. Earlier releases only added this entry to newly created Global Exclusions (created when the program is run for the first time).
• Version 3.4.5: Fixed very serious bug in version 3.4.4, that could cause some files to be left open, and some files to fail to be copied. Please upgrade immediately to version 3.4.5 (or later), if you are currently using version 3.4.4.
• Version 3.4.4: Re-enabled progress bar updates of bytes copied, free space remaining.
• Version 3.4.3: Worked around Windows bug (misunderstanding?) that prevented program from sending folders to the recycle bin when run on versions of Windows that support the NTFS file system. Also reinstated support for sub-folders and file names containing Unicode characters, on a trial basis.
• Version 3.4.2: Made another attempt to fix log file bug. Hopefully, log entries will no longer run together from time to time. Note: This fix only effects log entries made after this version is installed. It doesn't 'repair' older entries.
• Version 3.4.1: Fixed a bug that corrupted the log file when a user erased the file.
• Version 3.4: Made several changes to allow program to run as normal user under Windows Vista. These include the location where settings are stored, and the default location of the program's log file.
• Version 3.3.5: Added additional sections to the program's manifest, to make it explicit that the program should run under the security identify of the program launching the program.
• Version 3.3.4: Fixed bug that prevented users from deleting Global Exclusion rules. Also fixed cosmetic problem that prevented the Add/Edit/Delete jobs tab from being visible, when no jobs have been defined, until you clicked the 'Other Settings' tab first.
• Version 3.3.3: Worked around Windows bug that prevented some files from being moved to Recycle Bin on disks that support Unicode file names.
• Version 3.3.2: Fixed bug that prevented some custom file filters from working correctly. Also tidied up the log entry describing the file selection method.
• Version 3.3.1: Improved ability to test Global Exclusions, including ones that have been entered but not yet saved.
• Version 3.3: Activated 'Global Exclusions' feature, which allows you to specify folders and files that will be skipped by all jobs. Also fixed display bug that obscured the progress bars when a job was run via a command line parameter (including those in shortcuts).
• Version 3.2.6: More changes to fixed remaining 'Error 5 - Access Denied' problems. Also fixed problem that prevented update of one of two progress bars while job is running.
• Version 3.2.5: I think I've finally fixed an elusive bug that caused some jobs to fail with 'Error 5 - Access Denied' when the job copied from a folder on a local disk, to a folder on a network disk specified using a UNC-style file name (ServerShare..). Also added option in Other Settings to automatically start the Replicator when any user logs on, or only when a particular user logs on (previously, the auto-start feature only worked for a particular user).
• Version 3.2.4: Fixed bug that could cause a system to run out of 'Paged Pool Memory' (Windows error 1450) if tens of thousands of folders were copied.
• Version 3.2.3: Fixed bug that caused file copies on some systems running Windows 9x or Windows ME to fail with 'error 13 invalid data'.
• Version 3.2.2: Fixed bug that caused program to hang if a job was scheduled to run automatically, but the schedule options excluded all seven days in a week.
• Version 3.2.1: Fixed bug that prevented program from deleting folders, when 'Replicate File and Folder Deletions' option was selected.
• Version 3.2: Added option (under 'Other Settings') to automatically launch the program each time Windows starts.
• Version 3.1: Worked around a Windows limitation that was preventing the program from copying more than 32,767 files from any single folder.
• Version 3.0: Added several new features. You can now specify the amount of information added to the log file.
• Version 2.2.3: Suppresses a lot of unnecessary log entries, when creating a new file.
• Version 2.2.2: Caused program to update on-screen 'Last Run' and 'Next Run' display automatically after a scheduled job is run (previously, this occurred only after a manual job was run). Also fixed the tab order of controls on the Settings window, making it easier to use with keyboard alone (no mouse).
• Version 2.2.1: Fixed bug that caused program to ignore excluded days of week.
• Version 2.2: Caused program to check for the accessibility of top-level source folder several times while running a job (previously, this check was only made at the beginning of a job). This allows the job to be aborted if the source drive is disconnected or becomes unavailable after the job has started.
• Version 2.1.3: Fixed bug that prevented 'Run All Enabled Jobs Now' button from being enabled when the program started.
• Version 2.1.2: Fixed bug that broke the Replicator's ability to be run the first job in the job list, from a shortcut or command line.
• Version 2.1.1: Fixed bug that could cause program to fail when adding your first job.
• Version 2.1: Can now Duplicate jobs. Also added Next Run and Last Run to main window's job display, allow user to sort and resize the columns.
• Version 2.0.7: Fixed bug that caused program to display warning message (Settings File Could Not Be Opened) the first time the program is run. Also added two new command line switches: /view (display Replicator log) and /erase (Erase/Purge Replicator log).
• Version 2.0.6: Fixed cosmetic problem that sometimes caused on-screen progress information to appear jumbled.
• Version 2.0.5: If new version is installed into a new folder (not the same folder as previous version) program will now offer to migrate settings (jobs and filers). Also fixed problem that caused program to sometimes display wrong job name when deleting a job (selected job was deleted, but wrong name might be displayed in confirmation dialog).
• Version 2.0.4: Major new release, now supports 'exclusion' file filters, filters that specify which files to skip. Also lets you determine which days of the week a file, or group of files, should be copied. Additional features include a color-coded log file, the ability to run the program from the command line, and the creation of desktop shortcuts that instantly run particular job(s).
• Version 1.8.10: Fixed bug that could cause program to crash when launched minimized.
• Version 1.8.9: When minimized, and icon displayed in System Tray, single-clicking System Tray icon with left mouse button now restores main window.
• Version 1.8.8: Fixed bug that could cause Replicator to overlook new files when only one job has been defined, and that job does not include subdirectories.
• Version 1.8.7: Fixed problem that occasionally caused runtime error 75, when attempting to delete a read-only or non-existent folder.
• Version 1.8.6: Fixed bug that caused <dow> tag (day of week) to always be replaced by '2' instead of actual day of week (1 - 7).
• Version 1.8: Now logs Windows error messages when copy fails. Also warns user if 'Replicate Folder and File Deletions' option is selected.
• Version 1.7.2: Fixed bug that caused 'Copy only if newer' option to misbehave. Also added 'Day of Week' option to new variable destination feature.
• Version 1.7.1: Fixed bug that caused error message to appear when trying to view empty log file. Thanks to reader Dave Bourassa for spotting this.
• Version 1.7: Added default choices for Past Due dialog. Further improved root folder detection, improving support for empty CD-RW drives as Destination Folder.
• Version 1.6: Fixed bug that prevented versions 1.4 and 1.5 from creating a new folder in the root directory of a drive. Program will now delete subfolders in destination, if corresponding folder has been deleted in source, and 'Replicate Folder and File Deletions' option is selected. Previously, only file deletions were replicated, and option was named 'Replicate File Deletions'.
• Version 1.5.1: Changed Past Due Job dialog so that it only displays once (no matter how many jobs are past due) if the 20-second time expires before a user responds.
• Version 1.5: Program now skips job immediately, if source directory doesn't exist or is offline.
• Version 1.4.1: Program now loads large log files (several hundred KB) much faster.
• Version 1.4: Added warning message if program exited while jobs are still scheduled.
• Version 1.3: Enabled program to see and copy hidden folders.
• Version 1.2: Past Due dialog now times out after 20 seconds, allowing program to start and run unattended.
• Version 1.1: Fixed bug that prevented File Filters from filtering out unwanted files. Also, improved support for disabled jobs.

Applies to Windows Server (Semi-Annual Channel), Windows Server 2016

This topic explains how to install Data Deduplication, evaluate workloads for deduplication, and enable Data Deduplication on specific volumes.

Note

If you're planning to run Data Deduplication in a Failover Cluster, every node in the cluster must have the Data Deduplication server role installed.

Install Data Deduplication

Important

KB4025334 contains a roll up of fixes for Data Deduplication, including important reliability fixes, and we strongly recommend installing it when using Data Deduplication with Windows Server 2016.

Install Data Deduplication by using Server Manager

1. In the Add Roles and Feature wizard, select Server Roles, and then select Data Deduplication.
2. Click Next until the Install button is active, and then click Install.

Install Data Deduplication by using PowerShell

To install Data Deduplication, run the following PowerShell command as an administrator:Install-WindowsFeature -Name FS-Data-Deduplication

To install Data Deduplication in a Nano Server installation:

1. Create a Nano Server installation with the Storage installed as described in Getting Started with Nano Server.

2. From a server running Windows Server 2016 in any mode other than Nano Server, or from a Windows PC with the Remote Server Administration Tools (RSAT) installed, install Data Deduplication with an explicit reference to the Nano Server instance (replace 'MyNanoServer' with the real name of the Nano Server instance):

   
   -- OR --
   Connect remotely to the Nano Server instance with PowerShell remoting and install Data Deduplication by using DISM:

Enable Data Deduplication

Determine which workloads are candidates for Data Deduplication

Data Deduplication can effectively minimize the costs of a server application's data consumption by reducing the amount of disk space consumed by redundant data. Before enabling deduplication, it is important that you understand the characteristics of your workload to ensure that you get the maximum performance out of your storage. There are two classes of workloads to consider:

• Recommended workloads that have been proven to have both datasets that benefit highly from deduplication and have resource consumption patterns that are compatible with Data Deduplication's post-processing model. We recommend that you always enable Data Deduplication on these workloads:
  • General purpose file servers (GPFS) serving shares such as team shares, user home folders, work folders, and software development shares.
  • Virtualized desktop infrastructure (VDI) servers.
  • Virtualized backup applications, such as Microsoft Data Protection Manager (DPM).
• Workloads that might benefit from deduplication, but aren't always good candidates for deduplication. For example, the following workloads could work well with deduplication, but you should evaluate the benefits of deduplication first:
  • General purpose Hyper-V hosts
  • SQL servers
  • Line-of-business (LOB) servers

Evaluate workloads for Data Deduplication

Important

If you are running a recommended workload, you can skip this section and go to Enable Data Deduplication for your workload.

To determine whether a workload works well with deduplication, answer the following questions. If you're unsure about a workload, consider doing a pilot deployment of Data Deduplication on a test dataset for your workload to see how it performs.

1. Does my workload's dataset have enough duplication to benefit from enabling deduplication?Before enabling Data Deduplication for a workload, investigate how much duplication your workload's dataset has by using the Data Deduplication Savings Evaluation tool, or DDPEval. After installing Data Deduplication, you can find this tool at C:WindowsSystem32DDPEval.exe. DDPEval can evaluate the potential for optimization against directly connected volumes (including local drives or Cluster Shared Volumes) and mapped or unmapped network shares. Running DDPEval.exe will return an output similar to the following: Data Deduplication Savings Evaluation ToolCopyright 2011-2012 Microsoft Corporation. All Rights Reserved.Evaluated folder: E:TestProcessed files: 34Processed files size: 12.03MBOptimized files size: 4.02MBSpace savings: 8.01MBSpace savings percent: 66Optimized files size (no compression): 11.47MBSpace savings (no compression): 571.53KBSpace savings percent (no compression): 4Files with duplication: 2Files excluded by policy: 20Files excluded by error: 0

2. What do my workload's I/O patterns to its dataset look like? What performance do I have for my workload?Data Deduplication optimizes files as a periodic job, rather than when the file is written to disk. As a result, it is important to examine is a workload's expected read patterns to the deduplicated volume. Because Data Deduplication moves file content into the Chunk Store and attempts to organize the Chunk Store by file as much as possible, read operations perform best when they are applied to sequential ranges of a file.

   Database-like workloads typically have more random read patterns than sequential read patterns because databases do not typically guarantee that the database layout will be optimal for all possible queries that may be run. Because the sections of the Chunk Store may exist all over the volume, accessing data ranges in the Chunk Store for database queries may introduce additional latency. High performance workloads are particularly sensitive to this extra latency, but other database-like workloads might not be.

   Note

   These concerns primarily apply to storage workloads on volumes made up of traditional rotational storage media (also known as Hard Disk drives, or HDDs). All-flash storage infrastructure (also known as Solid State Disk drives, or SSDs), is less affected by random I/O patterns because one of the properties of flash media is equal access time to all locations on the media. Therefore, deduplication will not introduce the same amount of latency for reads to a workload's datasets stored on all-flash media as it would on traditional rotational storage media.

3. What are the resource requirements of my workload on the server?Because Data Deduplication uses a post-processing model, Data Deduplication periodically needs to have sufficient system resources to complete its optimization and other jobs. This means that workloads that have idle time, such as in the evening or on weekends, are excellent candidates for deduplication, and workloads that run all day, every day may not be. Workloads that have no idle time may still be good candidates for deduplication if the workload does not have high resource requirements on the server.

Enable Data Deduplication

Before enabling Data Deduplication, you must choose the Usage Type that most closely resembles your workload. There are three Usage Types included with Data Deduplication.

• Default - tuned specifically for general purpose file servers
• Hyper-V - tuned specifically for VDI servers
• Backup - tuned specifically for virtualized backup applications, such as Microsoft DPM

Enable Data Deduplication by using Server Manager

1. Select File and Storage Services in Server Manager.
2. Select Volumes from File and Storage Services.
3. Right-click the desired volume and select Configure Data Deduplication.
4. Select the desired Usage Type from the drop-down box and select OK.
5. If you are running a recommended workload, you're done. For other workloads, see Other considerations.

Note

You can find more information on excluding file extensions or folders and selecting the deduplication schedule, including why you would want to do this, in Configuring Data Deduplication.

Enable Data Deduplication by using PowerShell

1. With an administrator context, run the following PowerShell command:

2. If you are running a recommended workload, you're done. For other workloads, see Other considerations.

Note

The Data Deduplication PowerShell cmdlets, including Enable-DedupVolume, can be run remotely by appending the -CimSession parameter with a CIM Session. This is particularly useful for running the Data Deduplication PowerShell cmdlets remotely against a Nano Server instance. To create a new CIM Session run New-CimSession.

Other considerations

Important How to download movies on macbook.

If you are running a recommended workload, you can skip this section.

• Data Deduplication's Usage Types give sensible defaults for recommended workloads, but they also provide a good starting point for all workloads. For workloads other than the recommended workloads, it is possible to modify Data Deduplication's advanced settings to improve deduplication performance.
• If your workload has high resource requirements on your server, the Data Deduplication jobs should be scheduled to run during the expected idle times for that workload. This is particularly important when running deduplication on a hyper-converged host, because running Data Deduplication during expected working hours can starve VMs.
• If your workload does not have high resource requirements, or if it is more important that optimization jobs complete than workload requests be served, the memory, CPU, and priority of the Data Deduplication jobs can be adjusted.

Frequently asked questions (FAQ)

Diablo 2 blessed aim. I want to run Data Deduplication on the dataset for X workload. Is this supported?Aside from workloads that are known not to interoperate with Data Deduplication, we fully support the data integrity of Data Deduplication with any workload. Recommended workloads are supported by Microsoft for performance as well. The performance of other workloads depends greatly on what they are doing on your server. You must determine what performance impacts Data Deduplication has on your workload, and if this is acceptable for this workload.

What are the volume sizing requirements for deduplicated volumes?In Windows Server 2012 and Windows Server 2012 R2, volumes had to be carefully sized to ensure that Data Deduplication could keep up with the churn on the volume. This typically meant that the average maximum size of a deduplicated volume for a high-churn workload was 1-2 TB, and the absolute maximum recommended size was 10 TB. In Windows Server 2016, these limitations were removed. For more information, see What's new in Data Deduplication.

Do I need to modify the schedule or other Data Deduplication settings for recommended workloads?No, the provided Usage Types were created to provide reasonable defaults for recommended workloads.

What are the memory requirements for Data Deduplication?At a minimum, Data Deduplication should have 300 MB + 50 MB for each TB of logical data. For instance, if you are optimizing a 10 TB volume, you would need a minimum of 800 MB of memory allocated for deduplication (300 MB + 50 MB * 10 = 300 MB + 500 MB = 800 MB). While Data Deduplication can optimize a volume with this low amount of memory, having such constrained resources will slow down Data Deduplication's jobs.

Optimally, Data Deduplication should have 1 GB of memory for every 1 TB of logical data. For instance, if you are optimizing a 10 TB volume, you would optimally need 10 GB of memory allocated for Data Deduplication (1 GB * 10). This ratio will ensure the maximum performance for Data Deduplication jobs.

What are the storage requirements for Data Deduplication?In Windows Server 2016, Data Deduplication can support volume sizes up to 64 TB. For more information, view What's new in Data Deduplication.