How to add a new physical windows server as repository server

[apolloxm]

Hello,
we are using v11a. We are planning to upgrade to v12. All VBR roles installed in one VM server. On the same server,the repository come from two iscsi disks which connected to QNAP. Per Veeam best practice, the repository server should be a physical server.so, we are planning to add new physical windows server as repository server. The iscsi will disconnect from VM and reconnect to this new physical server.all the back up job and back up copy jobs are not change .How can achieve this goal? When we need to add this physical server before the migration to V12 or after the migration? Thanks

[tyler.jurgens]

Before or after doesn't really matter. Personally, I'd do it before, if only for the mantra of "change one thing at a time". That way you can ensure your jobs work before you take the plunge to 12. Or upgrade to 12, then change your repository after you ensure the upgrade to 12 went smoothly. Don't do both at once.

Add the new physical Windows server to your Veeam. Add your iSCSI volumes. Add the repositories to your Veeam under the new repository server. Map the jobs to the new repositories. Essentially the same as this KB here: https://www.veeam.com/kb1729

[apolloxm]

Hello,

Is https://www.veeam.com/kb1729 this still valid for V12? we cannot see the V12 in the kb article?

[Mildur]

Yes, still valid.
For V12, we normally recommend to use the new "move backup" feature for migration data to a new storage. You can see that recommendation in the note box. But you don't need to use the Move feature if you just want to reconnect the iSCSI LUNs to a new server. You don't have "new storage".

Let me ask our KB team if we can add V12 to the affected products in this kb.

Best,
Fabian