-
- Service Provider
- Posts: 6
- Liked: 2 times
- Joined: Mar 14, 2018 8:31 pm
- Full Name: Jeff Ellingham
- Contact:
Upgrade v5 to v6 Failure
Tried to perform the upgrade from v5.0.3.1060 to v6 today.... What a disaster. The upgrade fails for some unknown reason, setup log provides no information as to why it failed. Currently have a support ticket open with Veeam but no fix so far.
I was able to reinstall v5 but I am now missing all of my Office 365 tenants / repositories. Is there any way to re-add them like B&R and rescan? Word to the wise, never install software on the day it is released.
I was able to reinstall v5 but I am now missing all of my Office 365 tenants / repositories. Is there any way to re-add them like B&R and rescan? Word to the wise, never install software on the day it is released.
-
- Product Manager
- Posts: 9948
- Liked: 2636 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Upgrade v5 to v6 Failure
Hi Jeff
If you followed the 3-2-1 rule from best practice guide, you can restore the vbo server (quick rollback if a vm). Drive C should be enough. Then you are back with your old config with Organizations, repos and backup jobs.
I’m afraid, if you don‘t have a backup or a snapshot, the you have to readd all organizations, readd the backup repos and create the jobs. There is no „config Backup“ as in vbr for this product. Creating a application aware backup with Veeam Agent or VBR is the way to do it. Or doing a snapshot before updating the vbo server in case of a vm.
Another option you should try, is open a case with veeam. There is always the possibility that they have other methods.
If you followed the 3-2-1 rule from best practice guide, you can restore the vbo server (quick rollback if a vm). Drive C should be enough. Then you are back with your old config with Organizations, repos and backup jobs.
I’m afraid, if you don‘t have a backup or a snapshot, the you have to readd all organizations, readd the backup repos and create the jobs. There is no „config Backup“ as in vbr for this product. Creating a application aware backup with Veeam Agent or VBR is the way to do it. Or doing a snapshot before updating the vbo server in case of a vm.
Another option you should try, is open a case with veeam. There is always the possibility that they have other methods.
Product Management Analyst @ Veeam Software
-
- Veteran
- Posts: 1143
- Liked: 302 times
- Joined: Apr 27, 2020 12:46 pm
- Full Name: Natalia Lupacheva
- Contact:
Re: Upgrade v5 to v6 Failure
Hi Jeff,
Also, kindly share your Support case ID so we could monitor your issue.
Thanks!
Also, kindly share your Support case ID so we could monitor your issue.
Thanks!
-
- Product Manager
- Posts: 8195
- Liked: 1323 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Upgrade v5 to v6 Failure
@DMIT
As Natalia mentioned, please let us know the support case ID so we can follow it.
Also, did support asked you to reinstall v5?
As Natalia mentioned, please let us know the support case ID so we can follow it.
Also, did support asked you to reinstall v5?
-
- Service Provider
- Posts: 6
- Liked: 2 times
- Joined: Mar 14, 2018 8:31 pm
- Full Name: Jeff Ellingham
- Contact:
Re: Upgrade v5 to v6 Failure
These are the steps to recover the O365 config and repositories:
1. Stop all Veeam Office 365 Backup services
2. Navigate to: %ProgramData%\Veeam\Backup365
3. There should be folders called BackupConfigDB_'GUID' and BackupProxyDB_'GUID' - Search by date to find the one that is relevant.
4. Rename the existing Proxy.xml and Config.xml to something like Proxy_orig.xml/Config_orig.xml.
5. Replace the two files with the ones located in the respective backup folder.
6. Rename the exiting ProxyDB and ConfigDB folders to something like ProxyDB_orig/ConfigDB_orig
7. Replace the ProxyDB and ConfigDB folders from the backup folders.
8. Restart the Veeam Office 365 Backup services.
Your tenant organizations, repositories and backup settings should be restored.
1. Stop all Veeam Office 365 Backup services
2. Navigate to: %ProgramData%\Veeam\Backup365
3. There should be folders called BackupConfigDB_'GUID' and BackupProxyDB_'GUID' - Search by date to find the one that is relevant.
4. Rename the existing Proxy.xml and Config.xml to something like Proxy_orig.xml/Config_orig.xml.
5. Replace the two files with the ones located in the respective backup folder.
6. Rename the exiting ProxyDB and ConfigDB folders to something like ProxyDB_orig/ConfigDB_orig
7. Replace the ProxyDB and ConfigDB folders from the backup folders.
8. Restart the Veeam Office 365 Backup services.
Your tenant organizations, repositories and backup settings should be restored.
-
- Service Provider
- Posts: 6
- Liked: 2 times
- Joined: Mar 14, 2018 8:31 pm
- Full Name: Jeff Ellingham
- Contact:
Re: Upgrade v5 to v6 Failure
@Mike Resseler - Support ID #02530890
They did not ask for the reinstallation of v5. I restored as we needed to continue the backup of our clients.
They did not ask for the reinstallation of v5. I restored as we needed to continue the backup of our clients.
-
- Product Manager
- Posts: 8195
- Liked: 1323 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Upgrade v5 to v6 Failure
Understood. But the most important question (and thanks for the detailed steps), did everything now go to v6 and was all the config rescued?
-
- Service Provider
- Posts: 6
- Liked: 2 times
- Joined: Mar 14, 2018 8:31 pm
- Full Name: Jeff Ellingham
- Contact:
Re: Upgrade v5 to v6 Failure
@Mike Resseler - The issue was resolved! Disabling the feature "Enable REST service" within options allowed the install to proceed without issue. It might have been an issue with my SSL cert, support is looking into it further.
I just want to say that Matthew (Veeam support guru) was awesome! His level of dedication and attention to detail is exactly why we choose Veeam over any other DR solution. I know I can always count on Veeam support.
I just want to say that Matthew (Veeam support guru) was awesome! His level of dedication and attention to detail is exactly why we choose Veeam over any other DR solution. I know I can always count on Veeam support.
-
- Product Manager
- Posts: 8195
- Liked: 1323 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Upgrade v5 to v6 Failure
Many thanks for letting us know. I will make sure that Matthew gets the praise that he deserves
Cheers
Mike
Cheers
Mike
Who is online
Users browsing this forum: No registered users and 18 guests