Skip to main content

Manually start a data deduplication with PowerShell

In some cases you may want to manually start an deduplication process on your Windows Server 2012 storage devices that are configured for data deduplication.

Here we see the same set of files located in three different areas of our e: drive.

clip_image001

To do this, utilize PowerShell.

Type Get-DedupVolume

clip_image002

Since we have not performed any deduplication, we do not have any savings.

Type: Start-DedupJob –Full –Path e: -Type Optimization

You can get the results by typing Get-DedupJob

clip_image003

The Data Deduplication Service is set to manual because it is either activated via a scheduled task or by PowerShell

clip_image004

By executing Get-DedupStatus –Path e:

clip_image005

Since only files that are greater than 32KB can be optimized by data deduplication, only the files that start with Colors will be processed. The total size of these files are 1053KB per instance. The SavedSpace attribute reflects the removed duplicate data plus the reference pointers for the removed data to a full copy of that data.

Comments

Anonymous said…
That's a great post.
Thanks a lot!
Anonymous said…
Great post.
Thanks!!
Anonymous said…
Just used this and it worked great! Thanks for the info!
Unknown said…
Thanks for this article. Excellent job
Anonymous said…
Brilliant, saves waiting for the schedule to kick in after 3 days

:)

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

How to Access all of the Registry Hives with PowerShell

In Windows PowerShell, there is a PSProvider called Registry .  By default, it gives you access to two registry hives. PS C:\> Get-PSDrive -PSProvider Registry   Name          Used (GB)      Free (GB) Provider       Root                                                CurrentLocation ----          ---------      --------- --------      ------------------ HKCU                                  Registry      HKEY_CURRENT_USER HKLM                                  Registry      HKEY_LOCAL_MACHINE                                                         There are actually 5 registry hives. HKEY_CLASSES_ROOT HKEY_CURRENT_USER HKEY_LOCAL_MACHINE HKEY_USERS HKEY_CURRENT_CONFIG According to Microsoft, here are their intended purposes in life. ( http://support.microsoft.com/kb/256986 ) Folder/predefined key Description HKEY_CURRENT_USER Contains the root of the configuration information for the user who is currently logged on. The user's folders, screen colors, and Co