It is always best practices to use a Veeam controlled job that creates backup copies.
Backup Copy Job, Scale-out-backup-repository Capacity Tier (for object offloading) and Backup 2 Tape Jobs.
For the Backup Copy Jobs you can implement as well (software based) WAN Accelerators from Veeam for low bandwidth/high latency situations.
Your question about the mtree replication I can not answer fully as this is more a matter for Dell to answer.
If making it RWtable destroys the replication, then I would check for other options like Fast Copies and mount the fast copy RWable, replacing it daily with the latest FastCopy of the production replicated data. Or just perform this step when you need it at restore.
Backup Copy Job, Scale-out-backup-repository Capacity Tier (for object offloading) and Backup 2 Tape Jobs.
For the Backup Copy Jobs you can implement as well (software based) WAN Accelerators from Veeam for low bandwidth/high latency situations.
Your question about the mtree replication I can not answer fully as this is more a matter for Dell to answer.
If making it RWtable destroys the replication, then I would check for other options like Fast Copies and mount the fast copy RWable, replacing it daily with the latest FastCopy of the production replicated data. Or just perform this step when you need it at restore.
Statistics: Posted by Andreas Neufert — Jul 29, 2024 1:12 pm






