Hi Scot,
What bottleneck is indicated in your backup job session details?
I'll try to answer some of your questions, but please note that we are limited in this forum regarding how far we can go in recommending a backup design. I suggest reaching out to a VASP Partner from Veeam to discuss and review your new backup design specific to your environment. They can also provide more information about specific hardware vendors and do the correct sizing for you: https://www.veeam.com/partners/find-a-p ... ?type=VASP
For backup targets, I recommend using Hardened Repositories (with built-in disks) over ReFS. There are currently some known issues with ReFS. If you prefer not to use two Hardened Repository targets, you can also consider options with object storage appliances.
Personally, I would exclude NAS devices as backup targets from my backup design. NAS devices with iSCSI ReFS volumes can work, but be sure to use enterprise-grade NAS devices, not those intended for home use. We don't recommend NAS devices for Hardened Repositories, as they introduce additional attack vectors for malicious actors. However, I am aware of a few customers who are successfully using enterprise NAS systems with FC connections to their Windows/Linux hosts.
We don't recommend creating a "backup" of the entire repository. Backup Copy Jobs are sufficient to maintain a second, independent backup chain on another target, and potentially even in another location.
You may also want to check out our Best Practice Guide to answer some of your questions.
And please also take a look at our calculator for the storage calculation: https://www.veeam.com/calculators/simple/vbr/machines
Best regards,
Fabian
What bottleneck is indicated in your backup job session details?
I'll try to answer some of your questions, but please note that we are limited in this forum regarding how far we can go in recommending a backup design. I suggest reaching out to a VASP Partner from Veeam to discuss and review your new backup design specific to your environment. They can also provide more information about specific hardware vendors and do the correct sizing for you: https://www.veeam.com/partners/find-a-p ... ?type=VASP
For backup targets, I recommend using Hardened Repositories (with built-in disks) over ReFS. There are currently some known issues with ReFS. If you prefer not to use two Hardened Repository targets, you can also consider options with object storage appliances.
Personally, I would exclude NAS devices as backup targets from my backup design. NAS devices with iSCSI ReFS volumes can work, but be sure to use enterprise-grade NAS devices, not those intended for home use. We don't recommend NAS devices for Hardened Repositories, as they introduce additional attack vectors for malicious actors. However, I am aware of a few customers who are successfully using enterprise NAS systems with FC connections to their Windows/Linux hosts.
You can use Backup Copy Jobs to send data to a second repository. If you expect to have 500TB of backup data, it’s best to use two repositories: one for your backup jobs and another for your copy jobs. Don't forget to add enough space for unexpected events such as Active Fulls.And...do you backup your backups? Do you have any kind of backup solution for your repos? If i have 8mo worth of chains and the server and repo falls over, I dont want to lose these backups. But now we are talking about the least expensive 500Tb solution I can find (to backup the backups).
We don't recommend creating a "backup" of the entire repository. Backup Copy Jobs are sufficient to maintain a second, independent backup chain on another target, and potentially even in another location.
You may also want to check out our Best Practice Guide to answer some of your questions.
And please also take a look at our calculator for the storage calculation: https://www.veeam.com/calculators/simple/vbr/machines
Best regards,
Fabian
Statistics: Posted by Mildur — Jul 07, 2025 9:01 am
