Repository capacity

[frankive]

Hi.
We have a customer who wants a 8 TB fileserver (no sql etc), just plain fileserver.
They want the following policy for backup.
28 days back in time
Monthly full backup next 12 months.
Yearly the next 5 years.

I am planning to buy a HPE ML110 with Windows Server 2016 Standard with deduplication and perpahs 20 TB raw discspace.

Any though on this?

[veremin]

Any though on this?

Are you looking for comments regarding storage device or job configuration?

I am planning to buy a HPE ML110 with Windows Server 2016 Standard with deduplication and perpahs 20 TB raw discspace.

Have you checked this thread already? WS 2016 deduplication might not be stable enough at the moment to guarantee safety to your client's backups.

[frankive]

Is win 2012 R2 deduplication to prefer regarding stability in dedup?
yes, looking for commencts regarding storage, recommened capacity on the repository with 8 TB production data and the retention in the previos post.

[iftikarsaeedi]

For repository capacity calculation visit this link http://rps.dewin.me/.
Deduplication of windows 2016 with Veeam follow this KB https://www.veeam.com/kb2023
Always remember that Deduplication ratio which you will get always depends on your raw data.

[ian0x0r]

If you are going to get server 2016 it would be worth having a read up about ReFS integration with Veeam as well https://www.veeam.com/blog/advanced-ref ... suite.html

If you know what your daily change rate is you can use the restore point simulator that was already posted to see if 20TB is enough in terms of capacity, it might not be. Also take a look at the Veeam best practice guide https://bp.veeam.expert/ to make sure the server is appropriately sized in terms of memory and CPU etc.

Also have a look through the forums for people who have had some issues with windows dedupe in particular when backing up large VMs.

Preparation is key

Ian