Your assumptions are correct.
Replication would work independently.
Target need to be rescanned in order to see the backups.
I would like to mention, that a external storage replication without verification is not seen based on Veeam best practices as a secondary copy of the backups. A secondary chain controlled by Veeam that can check on metadata consistency and handling the chain differently would mean that you would not loose your secondary backup if the first one is somehow broken.
For mtree replication it is best practices to deactivate some of the transport optimizations as Veeam need to flush and write metadata, which forces the mtree replication to throw away the "receipt" and not deactivating it, would slow down the processing. As well it is best practices to deactivate replication until Veeam has written the backups for the same reason. There is no need to change when you are happy with the transport time and data amount transported, it is just an optimization.
Replication would work independently.
Target need to be rescanned in order to see the backups.
I would like to mention, that a external storage replication without verification is not seen based on Veeam best practices as a secondary copy of the backups. A secondary chain controlled by Veeam that can check on metadata consistency and handling the chain differently would mean that you would not loose your secondary backup if the first one is somehow broken.
For mtree replication it is best practices to deactivate some of the transport optimizations as Veeam need to flush and write metadata, which forces the mtree replication to throw away the "receipt" and not deactivating it, would slow down the processing. As well it is best practices to deactivate replication until Veeam has written the backups for the same reason. There is no need to change when you are happy with the transport time and data amount transported, it is just an optimization.
Statistics: Posted by Andreas Neufert — Jul 29, 2024 5:36 am