Thanks eric and Alexander for the input.
We can move most things with out worrying too much about down time within reason of course, however its the Centos servers which connect upto our Centos run machinery which runs 24/7 and takes quite a lot of timing to shut this machinery down correctly. Our file server / exchange / dcs / sql etc etc is not an issue hopefully should be relatively straight forward, he says touching wood.
If we decided to change the source servers IP range from say 192.9.200.* to 192.168.0.* for arguaments sake in the NEW DESTINATION when we bring it online, I notice the option for seperate virtual networks and differant IP addressing on the rep job.
If for speed of the initial seed job we ran it on the existing site on the same 192.9.200.* then took it over to the new destination 192.168.0.* site, would I then be able to change the IP addressing options within the rep job to take into account that its then on a differant subnet. (just about to read up on this but always best to ask those that know it in side out)
This isnt a 100% definate, Im just trying to get my head around our options before hand, I would also create a few mickey mouse test rep jobs first to try the options out and see how things do and dont work, but just wanted to know what will and wont work with veeam.
Hopefully that makes sense.