-
- Veteran
- Posts: 942
- Liked: 53 times
- Joined: Nov 05, 2009 12:24 pm
- Location: Sydney, NSW
- Contact:
Best Practice in VBR Deduplication Repository ?
Hi All,
I'm using Veeam Backup 9.5 Update 1 on Windows Server 2012 R2 running as VM with 2x iSCSI LUN presented as 30 TB NTFS partition.
I'd like to know what is the best practice for deploying & configuring Veeam Backup Repository so that I can use deduplication to maximize the use of the disk space on the backup repository safely?
Do I need to turn on deduplication feature on the both 2x NTFS drive or this is not needed anymore?
Any help and suggestion would be appreciated.
Thanks
I'm using Veeam Backup 9.5 Update 1 on Windows Server 2012 R2 running as VM with 2x iSCSI LUN presented as 30 TB NTFS partition.
I'd like to know what is the best practice for deploying & configuring Veeam Backup Repository so that I can use deduplication to maximize the use of the disk space on the backup repository safely?
Do I need to turn on deduplication feature on the both 2x NTFS drive or this is not needed anymore?
Any help and suggestion would be appreciated.
Thanks
--
/* Veeam software enthusiast user & supporter ! */
/* Veeam software enthusiast user & supporter ! */
-
- Product Manager
- Posts: 5797
- Liked: 1215 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Best Practice in VBR Deduplication Repository ?
Have a look at veeam-backup-replication-f2/best-practi ... 14002.html
However depending on the amount of data the default deduplication in Windows 2012 may not be the best option.
However depending on the amount of data the default deduplication in Windows 2012 may not be the best option.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Veteran
- Posts: 361
- Liked: 109 times
- Joined: Dec 28, 2012 5:20 pm
- Full Name: Guido Meijers
- Contact:
Re: Best Practice in VBR Deduplication Repository ?
Whatever you do, do not forget to format your volumes with the /L parameter and use 64K allocation size!
Also you can have a closer look on scale-out repositories to see if you might want to split full and incremental backups over both volumes to allow for longer dedupe cycles on the full extents...
*from a happy 2012/2016 dedupe user
Also you can have a closer look on scale-out repositories to see if you might want to split full and incremental backups over both volumes to allow for longer dedupe cycles on the full extents...
*from a happy 2012/2016 dedupe user
-
- Veteran
- Posts: 942
- Liked: 53 times
- Joined: Nov 05, 2009 12:24 pm
- Location: Sydney, NSW
- Contact:
Re: Best Practice in VBR Deduplication Repository ?
Hi Guido,
Thanks for the sharing. The Veeam backup itself is running Win 2012 R2 VM.
My current VBR repo is running as 2x 30 TB iSCSI LUN presented as NTFS partition from QNAP NAS.
Do I need to have VBR Enterprise Plus to utilize both backup LUNs with SOBR (Scale Out Backup Repository)?
Thanks for the sharing. The Veeam backup itself is running Win 2012 R2 VM.
My current VBR repo is running as 2x 30 TB iSCSI LUN presented as NTFS partition from QNAP NAS.
Do I need to have VBR Enterprise Plus to utilize both backup LUNs with SOBR (Scale Out Backup Repository)?
--
/* Veeam software enthusiast user & supporter ! */
/* Veeam software enthusiast user & supporter ! */
-
- Veteran
- Posts: 361
- Liked: 109 times
- Joined: Dec 28, 2012 5:20 pm
- Full Name: Guido Meijers
- Contact:
Re: Best Practice in VBR Deduplication Repository ?
I sadly can't tell you since we are on Enterprise Plus. But I believe without a limited number of scale-outs is possible (but I'm not sure). Anyway, should be fairly easy to test.
Install a repository as usual ob both and once you are done you can create the SOBR. In the wizard all you have to do is add both extents and then choose the performance option, now you can select on of the extents for fulls, the other one for incrementals.
Depending on your ISCSI backend you could even do different striping for both volumes (Raid 6 for fulls, Raid 10 for Incrementals) or something like that, but that's a different story of course...
Here are some examples of our Repos (you can see the difference in full / incrementals by the number of files:
PS C:\Windows\system32> Get-Dedupstatus
FreeSpace SavedSpace OptimizedFiles InPolicyFiles Volume
--------- ---------- -------------- ------------- ------
27.41 TB 111.82 TB 317 317 T:
36.4 TB 88.82 TB 8303 8310 P:
23.67 TB 94.01 TB 482 542 Q:
21.39 TB 113.53 TB 449 552 O:
44.68 TB 77.98 TB 7779 7780 V:
8.81 TB 140.11 TB 9665 11175 R:
Install a repository as usual ob both and once you are done you can create the SOBR. In the wizard all you have to do is add both extents and then choose the performance option, now you can select on of the extents for fulls, the other one for incrementals.
Depending on your ISCSI backend you could even do different striping for both volumes (Raid 6 for fulls, Raid 10 for Incrementals) or something like that, but that's a different story of course...
Here are some examples of our Repos (you can see the difference in full / incrementals by the number of files:
PS C:\Windows\system32> Get-Dedupstatus
FreeSpace SavedSpace OptimizedFiles InPolicyFiles Volume
--------- ---------- -------------- ------------- ------
27.41 TB 111.82 TB 317 317 T:
36.4 TB 88.82 TB 8303 8310 P:
23.67 TB 94.01 TB 482 542 Q:
21.39 TB 113.53 TB 449 552 O:
44.68 TB 77.98 TB 7779 7780 V:
8.81 TB 140.11 TB 9665 11175 R:
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Best Practice in VBR Deduplication Repository ?
Enterprise edition allows you to have up to 4 extents (with only 3 of them being in online state at any given moment). Thanks.
Who is online
Users browsing this forum: Bing [Bot] and 29 guests