Migrating physical B&R server to VM, but not repositories

[pkelly_sts]

I'm about to migrate our physical v8 B&R server to a newly-created VM v8 B&R server, but the original server is intended to remain as the repository/tape server.

Most of the migration instructions I've seen linked to look straightforward enough, but I think all of them assume that ALL functionality is migrated.

Am I able to achieve the above, or will things go haywire with the existing (migrated) jobs if I'm not migrating the repositories as well?

Any pointers to previously related discussions appreciated...

Paul

[foggy]

Paul, provided those roles were assigned to "This server" in your old v8 installation, you would need to add it to the new console after the migration and assign required roles to it (repositories rescan/jobs mapping will be required).

[pkelly_sts]

OK, so "This Server" is effectively a "relative path", so if the "This Server" role is effectively transferred to the "current" server, there should be no issue (i.e. no complaints of duplicate server name etc.) if I then add the original server back in, purely as a repository / tape server, which as you say, I'd then just need to resscan & re-map jobs?

[foggy]

Correct.

[pkelly_sts]

Thanks for the confirmation.

Actually, what should I need to do to the original server, uninstall Veeam completely then re-add it as a server to the new one, choosing the repository/proxy/tape server roles?

[foggy]

Yes. However, if the new instance version is the same (including patch level), you can just disable all the jobs on the old one and add it to the new console.

[pkelly_sts]

Ah, excellent - leaves me with a useful fall-back should there be any issues...

[pkelly_sts]

OK, I've started the migration process but all the repositories from the original B&R server are still listed as present in "This Server". What's the easiest/safest way to politely inform Veeam that they're actually on /that/ (original) server?

I've already added the original server as a Windows server & all installed components were detected.

[foggy]

Add new repository pointing to the original server and change repository for your jobs using the procedure outlined in the thread I've referred above.