Maintain control of your Microsoft Office 365 email data
Post Reply
Lennydk87
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?

Post by Lennydk87 » Aug 28, 2019 3:14 pm

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.

Polina
Veeam Software
Posts: 838
Liked: 118 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: Moving VBO 365 3.0 from server 2016 to 2019?

Post by Polina » Aug 28, 2019 5:22 pm

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.

Lennydk87
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?

Post by Lennydk87 » Aug 28, 2019 5:33 pm

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!!!

Polina
Veeam Software
Posts: 838
Liked: 118 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: Moving VBO 365 3.0 from server 2016 to 2019?

Post by Polina » Aug 29, 2019 5:16 pm

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!

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests