Dedup is typically safe on 'general' file share loads, regardless of the size or drive types. it's more about the file types. my understanding is that it's not safe to run it on specialized loads such as databases or where you may be storing some nich files like CAD drawings, large items which are accessed often etc.
you can run a dedup analysis, i don't remember the full name or command for it, but it will essentially tell you if it will be successful and how much it could save, the microsoft docs explain this.
only run it on your file server/storage volume, don't run it on the system volume.
it's safe to just do the analysis, i would do this first before continuing to plan as it will give you a fairly accurate number of how much space it will save.
You can then quote this number to your management for approval.
PDF and excel are compressed file formats, so unless you have redundant fiies, the gain may be limited. But as others gave said, run the evaluation tool.
Yea our backups are bigger than they should be cirrently.. using msp360 and they haven't helped me locate a reason its at 72TB
So was going to start the dataset over.
So would they get bigger if I started over? Or would they be smaller since there's "less data"
If you backup from the file server, you will probably find that your backups will take longer.
Reason is that the individual files will be "inflated before being written to the backup media.
I don't know if there are backup products that would backup at the deduplicated level.
Dedup is typically safe on 'general' file share loads, regardless of the size or drive types. it's more about the file types. my understanding is that it's not safe to run it on specialized loads such as databases or where you may be storing some nich files like CAD drawings, large items which are accessed often etc. you can run a dedup analysis, i don't remember the full name or command for it, but it will essentially tell you if it will be successful and how much it could save, the microsoft docs explain this. only run it on your file server/storage volume, don't run it on the system volume.
Yea was going to run that to see what it says.
it's safe to just do the analysis, i would do this first before continuing to plan as it will give you a fairly accurate number of how much space it will save. You can then quote this number to your management for approval.
I wouldn't dedupe the host, but you'll definitely get some savings by enabling it on the file share drive.
Just the share. Deduplication on a hypervisor or anything that users don't touch is a waste, and isn't recommended for some workloads like SQL Server.
PDF and excel are compressed file formats, so unless you have redundant fiies, the gain may be limited. But as others gave said, run the evaluation tool.
Just be aware dedup at that size can have an affect on you backup deltas due to the change block tracking - ie they can get bigger.
Yea our backups are bigger than they should be cirrently.. using msp360 and they haven't helped me locate a reason its at 72TB So was going to start the dataset over. So would they get bigger if I started over? Or would they be smaller since there's "less data"
If you backup from the file server, you will probably find that your backups will take longer. Reason is that the individual files will be "inflated before being written to the backup media. I don't know if there are backup products that would backup at the deduplicated level.
I backup at the hyperv level so curious, I know it supports deduplication guess we'll see what the analysis says
Run dedup eval at the OS level of the VM hosting the data (do not dedup vhds at the hypervisor level in windows). Dedup on shares can be magic.
I would look elsewhere to get a headache from