When I upgraded to v6 GA, that failed, leaving me with no installed copy of M365 Backup!
I restored the server from backup and tried again a few times. I couldn't get the upgrade to install.
I ended up doing a fresh installation of M365 Backup v6.
I tried to restore the configdb/proxydb data files but the service wouldn't start. I set up all 65 orgs again from scratch
Is there a supported method of performing a database backup and restore? I don't really want to go through this process again
Hi Natalia,
That is basically what I did. I have backups of the server.
* When the v6 upgrade failed I restored the server and tried again, multiple times.
* I then tried installing the new version clean and restoring the old config files over the top. The VBO365 service wouldn't start.
* I also tried just adding the existing proxy servers to the new installation. The KB2649 article about migrating to a new server seems to indicate all you have to do is add the existing proxy servers and then the organizations should appear? That didn't happen for me.
Since this is a test-dev environment and I wanted to get v6 running, I recreated the 65 orgs and their backup jobs, which took some time. It would be great if there was a more streamlined configuration backup and restore procedure, where you can restore the same or a previous version config (for example install v6 and restore a config backup from v5).
Applying the previous configuration doesn't work in this case. In the KB, step #5 says that you need to add your organization to VB365 manually. We don't store your organization credentials, and therefore cannot re-add your tenant automatically.
Configuration backup is on our roadmap, and it's one of my personal favorites from the list of to-do features.
Also, please consider contacting our support if you experience issues with the upgrade (or any other) - this one call could help you save hours of time, and our engineers are always happy to assist and resolve your problems.
Today you can protect the VB365 Server with VBR or Veeam Agent. In case you lost the server, you can restore it with OS and the entire VB365 configuration/data.
Make sure to use Application Aware processing in the job settings.
