Comprehensive data protection for all workloads
Post Reply
svallance
Service Provider
Posts: 37
Liked: 13 times
Joined: Apr 12, 2016 12:15 pm
Full Name: Shane Vallance
Contact:

Actual Storage Used on ReFS

Post by svallance »

So, backing up to an ReFS formatted storage allows for fast cloning and spaceless synthetic fulls. We have a couple backups running to the same repository and are seeing great benefits to the actual stored size vs. what windows is reporting the file sizes are. For example a backup job pointing to a ReFS volume with a 2TB full creates a synthetic full that is also 2TB, right click properties on the actual files reports they have a file size of 4TB where as right click properties on the volume they are stored on shows only ~2.15TB used. Its easy to see how much storage is saved that way for a single backup job but what about multiple backup jobs.

If we have 3 backup jobs on ReFS each with a full backup and 1 synthetic full is there a way to tell the actual storage used of the individual jobs? With NTFS deduplication we could use the "get-dedupmetadata" to find the dedupe size/how much storage would be freed up if the files were deleted. Is there something similar with Windows 2016 ReFS?
jdavidson_waters
Service Provider
Posts: 43
Liked: 15 times
Joined: May 07, 2013 2:50 pm
Full Name: James Davidson
Location: Northeast UK
Contact:

Re: Actual Storage Used on ReFS

Post by jdavidson_waters » 1 person likes this post

Unfortunately there's no way to get this information in the current release of Server 2016/ReFS.
Hopefully Microsoft will address this soon.
@jam_davidson
Post Reply

Who is online

Users browsing this forum: No registered users and 282 guests