-
- Novice
- Posts: 9
- Liked: 1 time
- Joined: Sep 19, 2017 10:00 am
- Full Name: Lennart Ingemann Nielsen
- Contact:
Moving VBO 365 3.0 from server 2016 to 2019?
Hello,
We're in the process of moving our Veeam Backup O365 server from Server 2016 to server 2019.
But as I read the KB for version 1.5 and 2, thats not possible, it shall be the SAME OS on the new server?!?!?
Is this still the same in 3.0, why cant you move it to a newer OS, often thats the reason why migrating?!
The repo. is on a NAS it self.
We're in the process of moving our Veeam Backup O365 server from Server 2016 to server 2019.
But as I read the KB for version 1.5 and 2, thats not possible, it shall be the SAME OS on the new server?!?!?
Is this still the same in 3.0, why cant you move it to a newer OS, often thats the reason why migrating?!
The repo. is on a NAS it self.
-
- Veeam Software
- Posts: 3195
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Moving VBO 365 3.0 from server 2016 to 2019?
Hi Lennart,
The KB article is relevant for v3 as well. Migration to a newer OS potentially can result in issues with the configuration databases. A clean installation is the recommended way.
The KB article is relevant for v3 as well. Migration to a newer OS potentially can result in issues with the configuration databases. A clean installation is the recommended way.
-
- Novice
- Posts: 9
- Liked: 1 time
- Joined: Sep 19, 2017 10:00 am
- Full Name: Lennart Ingemann Nielsen
- Contact:
Re: Moving VBO 365 3.0 from server 2016 to 2019?
Hello Polina,
Okay, is it possible to do a clean install on the new server and preserve the restore points etc.?
We can configure the config the same, no problem, but we dont want to lose restorepoints/backup!!!
Okay, is it possible to do a clean install on the new server and preserve the restore points etc.?
We can configure the config the same, no problem, but we dont want to lose restorepoints/backup!!!
-
- Veeam Software
- Posts: 3195
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Moving VBO 365 3.0 from server 2016 to 2019?
Lennart,
To make my previous response more accurate: the difference in OS versions might affect product's configuration databases if you decided to go with the VBO server migration itself.
With a clean installation, to move only the repository data you can follow the steps described in the KB. While our QC has not specifically tested moving repositories between Server 2016 and 2019, we expect everything to go smoothly. (As always, it's recommended to keep a copy of your current production data until you ensure that the new VBO server is up and running and all backup databases are in the correct state.)
Previous restore points will be available as soon as the organization is added to the scope (right-click it and check point-in-time states).
Thanks!
To make my previous response more accurate: the difference in OS versions might affect product's configuration databases if you decided to go with the VBO server migration itself.
With a clean installation, to move only the repository data you can follow the steps described in the KB. While our QC has not specifically tested moving repositories between Server 2016 and 2019, we expect everything to go smoothly. (As always, it's recommended to keep a copy of your current production data until you ensure that the new VBO server is up and running and all backup databases are in the correct state.)
Previous restore points will be available as soon as the organization is added to the scope (right-click it and check point-in-time states).
Thanks!
-
- Service Provider
- Posts: 25
- Liked: 2 times
- Joined: Nov 27, 2014 2:20 pm
- Full Name: Timo Wende
- Contact:
[MERGED] Howto migrate VBO365 to a new server?
Dear Community,
I'm going to migrate our VBO365 (3.0.0.422) server running on 2008 R2 to a new server runnning Windows Server 2019.
My first thought was: Simply setup the new server, install VBO365 and export/import the configuration backup along with moving the repositories.
Unfortunately there's no option to export a configuration backup. Or did I miss something?
Did anyone a successful migration of VBO365 between servers including a change of the underlaying operating system?
Thanks a lot!
Timo
I'm going to migrate our VBO365 (3.0.0.422) server running on 2008 R2 to a new server runnning Windows Server 2019.
My first thought was: Simply setup the new server, install VBO365 and export/import the configuration backup along with moving the repositories.
Unfortunately there's no option to export a configuration backup. Or did I miss something?
Did anyone a successful migration of VBO365 between servers including a change of the underlaying operating system?
Thanks a lot!
Timo
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Moving VBO 365 3.0 from server 2016 to 2019?
Timo, please review the existing thread for more info, and the KB being referenced here is this one.
Who is online
Users browsing this forum: Semrush [Bot] and 7 guests