When I quickly setup Veeam 365 Backup, I had to use on premise disk that I had available. I have since purchased basic storage and am trying to move my backup repository from the temporary storage to the new storage.
I’m using the recommended Move-VBOEntityData tool and it is horrible. I have migrations in excess of 60 hours to move a 50 GB mailbox backup. And it isn’t my hardware. Performance tests show that read/write performance is exponentially faster. The tool itself in combination with the JetDB architecture is the problem.
And while using this tool, I can’t do backups. Which put in me in an untenable situation of no backups for 2-3 weeks while I try to complete this migration. Researching this in the R&D Forums show others having the same performance issue.
Because of that, I am done. I am already competitive bidding 365 backup solutions, and I will be bailing on the Veeam 365 backup platform as soon as I can.
Repository management is a critical operation, and from what I can research, on premise repository management is an overlooked operation that is not taken seriously. Veeam wants me to use object storage in the cloud, which is not an option for us.
If you are looking to move your JetDB repositories do not use this tool. Use the second option of copying your JetDBs as a file copy, and accept that you are copying over the whitespace. You will be operational a lot faster.
Just putting this out there as a review and as a cautionary tale.
