Migrate replication jobs from v8 to v9

[notesguru99]

All,
I have 2 b&r serves in production on v8. I have purchased a new v9 server to replace one of the v8 servers.

I'm wondering what is the best way to continue with my replication jobs? I have quite a few vm's replicating but obviously can't replicate between 8 and 9 servers, so it seems.

Should I upgrade my v8 servers to v9 - then retire and replace one of them with my new v9 server?

Or should I just update the one server to v9 then re-create the replication jobs?

Is Veeam smart enough to 'see' the replica vm's already exist and use the disks/vm's already replicated, or will it start to rpelicate the entire machine again?

I am basically trying to avoid creating replicas from scratch again!!

TIA
Stuart

[DGrinev]

Hi Stuart,

Before migration make sure you do backup of Veeam config database, also disable all jobs schedule for the maintenance time.
Then the recommended approach would be to upgrade your old server to version 9 and start Migrating configuration database to another installation.

Thanks!

[notesguru99]

just read the help on replica seeding and replica mapping!!

useful stuff here

https://helpcenter.veeam.com/docs/backu ... tml?ver=95

and here

https://helpcenter.veeam.com/docs/backu ... tml?ver=95

[notesguru99]

Hi DGrinev

I thought about that too, but I am changing the way my backups are scheduled and how they are maintained too. I suppose I could have migrated the config then just deleted my backup jobs and recreated them because my replica jobs would have been fine!!

Thanks for the advice,

Stuart

[ori]

Hello,
At my DR site I have a Veeam v8 server dedicated for replication jobs.
I need to migrate the jobs to a new 9.5 server that also uses new proxies and new replica metadata repositories.

Would Configuration Database migration (after I update the source server to 9.5) work for this case?
Would I be able to point the migrated jobs to the new proxies and repositories without impacting the replication incremental flow?

Is there an alternative way to do it (except replica seeding which takes a lot of time)?

[DGrinev]

Hi Ori,

Before you start migration process be sure that all jobs have been stopped and the configuration backup completed.

Would I be able to point the migrated jobs to the new proxies and repositories without impacting the replication incremental flow?

Yes, you should be able to do it.

Please review existing discussion for additional information. Thanks!

[ori]

Does the configuration backup also migrates the replica metadata or should I move it manually?

[DGrinev]

The replica metadata stored in the repository you've chosen during the job creation, you don't need to move it manually.

[ori]

Sorry, I am missing something.. my new 9.5 server is not connected (and will not be connected) to the repositories chosen in the v8 jobs. I have provisioned new repositories for the 9.5 infrastructure.
What repository will the v9 jobs point to after the configuration restore?

[DGrinev]

After configuration restore all previously used infrastructure components will appear and jobs will try to target v8 repository.
Why don't you want to upgrade v8 to v9.5 and keep backup infrastructure with the configuration?
Also, new Veeam infrastructure will be hosted on the same hardware? Thanks!