my task was to migrate a backup from a local jet-db to a new objectstorage/bucket. Downloaded the powershell provided by kb3067 and executed it (btw, very elegant way to guide through the needed parameters, nice implementation). The job(s) get started and everything works for 1 or 2 hours when suddenly the backup proxy service is stopped. Digged a bit and found the culprit:
Exception of Type System.OutOfMemoryException
But that exception was thrown by the backup-job (same or, different target/bucket), not the migration-job. Now on that proxy we have 20 GBs of RAM installed, some other veeam-services are running there as well. Now I wonder how much that migration job consumes or how much memory should be reserved in general. The data is transferred through a 80 Mbit/s connection, so surprised that you need that much memory in any case.
I'd suggest you first install the cumulative patch that we released today. It includes a couple of fixes/optimizations to the data move mechanism which may resolve the OutOfMemory problem.
It is important to remember that Veeam Backup for Microsoft 365 and Veeam Backup & Replication are separate backup products designed to operate separately from each other.
yes, but here they are talking about compatibility regarding the explorers and not in terms of process tolerance / proxies. so it should be ok in general I'd say. Am I wrong?
Yes, you are. Both products are resource-intensive and unless there's a need (i.e. in a service provider scenario) we do not recommend hosting both VBR and VB365 on the same machine.
