Skip to main content
  • EN

Hi Folks,

 

First off don’t ask 😁 “why do you want to do this” 🙂, I don’t but I have no choice as the customer is going to do this and I can’t convince them otherwise. However, they are asking about consequences 😞, 

So a customer has an M365 multitenant backup. They want to rename the server and give it a new IP. The proxies and repositories will remain the same.

They are not leveraging S3 only old style repos and they have no portal my understanding is that there is no database that has recorded the console’s hostname and IP (unlike VBR) so changing the name and IP should not have any affect (only perhaps firewall stuff if they have any rules tied to the old IP).

Is this correct? 

Thanks

 

Hi Geoff

You must reset the entire VB365 configuration when you rename the server.

Renaming its hostname leads to this error:

https://www.veeam.com/kb4296

 

I answered the same questions once in the forum:

(1) What is the impact of changing hostname of Veeam Backup for Microsoft Office 365 server?

 

Best,

Fabian

Ok but they won’t have to  re-add the organization etc like they would have had to do if they were migrating? 

oh wait, if one has to recreate the backup jobs then…. 

The kb article explains it:

Open the Veeam Backup for Microsoft 365 console and re-add the Organization(s), Repositories, and Backup Jobs.

 

It’s a complete reset of the entire configuration. Especially for a multi tenant server this will be a real big consequence. Adding all Tenants and their jobs again. Together with the repositories.

We are working on optimizing that process. But I don’t expect any news this year. If they need to rename now, they will have to reconfigure the entire server.

 

Best,

Fabian

 

ugh read to the end re-add organization :)

Thanks, I will tell them “don't do this” :) 

Geoff, I think you need new customers based on the last couple of posts about what your customers want to do…..

For the time being, it's best to wait until we have a more improved process, if it's possible for them, of course. :)

I am sure they will ask now about migrating the Cloud Connect server off of that server (this has been going back and forth for a while now). 

I assume using this methodology should work: https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ad=in-text-link&_gl=1*1vcwcws*_ga*MTMwNTg0NDUyNC4xNjg3ODAyODk4*_ga_PMJS81E58L*MTY4OTE2NzEwOS42My4xLjE2ODkxNzA5OTQuNjAuMC4w&ver=120

 

But there is also VSPC attached to that Cloud Connect so I guess one would have to disconnect and then re-add the newly migrated Cloud Connect server. 

They don’t care about the M365 being linked to Cloud Connect, no portal and no tenant explorer restores needed (why it was installed on the CC in the first place then 🙂?) but… 

 

So Migrate the CC server to new Server, then reconnect VSPC so it can install its agent? The SQL server is separate and both VSCP and VCC databases are hosted on it.

 

 

Our solution architects wrote a guide on how to migrate VCC. It may involve additional steps.

https://bp.veeam.com/sp/MSP/M_Operate/migrate-vcc.html
 

Migration of the VSPC is documented here:

https://helpcenter.veeam.com/docs/vac/deployment/migrate.html?ver=70#migrating-veeam-service-provider-console-server

Thanks I somehow missed the first one! Thanks. The second one I have seen i.e. the export and import of certificates. 

The additional steps is potentially always fun :) 

Comment


Terms & Conditions