It is not clear to me what exactly do you want. I assume you have DD Boost device, right? And you have remote side with DD unit too? Then defined device on remote unit and use it as target to clone source and that's it. I'm not sure why do you talk of IP change (unless you are actually moving DD unit and changing IP of that?).
now i have a NW server managing local DD and the performing lone controlled replication to another DD box that should be sent to the DR site
now we need to remove the replication box from the main site to ship it to the DR then reconnect it to the NW, and of course the IP will be changed ....
how we could connect it again keeping the cloned data it contains
Clear. I never did this, but top of my head here it goes (assuming IP changes and hostname.domain remains the same):
1) Disable cloning in NW
2) Disable devices in NW for DD box where cloning is going (you will need to unmount them first)
3) On DD to be removed, change IP and shut it down (you may wish to do this over serial cable). Before you do this, check if you are using hosts table there and make relevant updates. Same applies to to other DD box, DNS and /etc/hosts on backup infra or clients if they had this IP listed.
4) Power up DD box on DR site and check connectivity:
a) check ping from DD box in DR towards DD box in DC and backup infra
b) check ping from DD box in DC and backup infra towards DD box in DR
5) Enable and mount devices from DR
6) Test some small SSID restore using cloned data (so that DD in DR is used)
So the DD boost devices must be mounted onto a NetWorker Storage Node (on primary site can be NetWorker Server) but at DR site the DDboost devices must be mounted on another storage Node. Do we need to consider NetWorker Storage Node Names, IP's ?
ble1
4 Operator
•
14.4K Posts
0
February 10th, 2014 04:00
It is not clear to me what exactly do you want. I assume you have DD Boost device, right? And you have remote side with DD unit too? Then defined device on remote unit and use it as target to clone source and that's it. I'm not sure why do you talk of IP change (unless you are actually moving DD unit and changing IP of that?).
Mhmd_Saad
8 Posts
0
February 11th, 2014 00:00
Hi Hrvoje,
now i have a NW server managing local DD and the performing lone controlled replication to another DD box that should be sent to the DR site
now we need to remove the replication box from the main site to ship it to the DR then reconnect it to the NW, and of course the IP will be changed ....
how we could connect it again keeping the cloned data it contains
hope that be clear ...
ble1
4 Operator
•
14.4K Posts
0
February 11th, 2014 03:00
Hi,
Clear. I never did this, but top of my head here it goes (assuming IP changes and hostname.domain remains the same):
1) Disable cloning in NW
2) Disable devices in NW for DD box where cloning is going (you will need to unmount them first)
3) On DD to be removed, change IP and shut it down (you may wish to do this over serial cable). Before you do this, check if you are using hosts table there and make relevant updates. Same applies to to other DD box, DNS and /etc/hosts on backup infra or clients if they had this IP listed.
4) Power up DD box on DR site and check connectivity:
a) check ping from DD box in DR towards DD box in DC and backup infra
b) check ping from DD box in DC and backup infra towards DD box in DR
5) Enable and mount devices from DR
6) Test some small SSID restore using cloned data (so that DD in DR is used)
7) Enable CCR
Benz_Dell
6 Posts
0
February 23rd, 2016 10:00
Hi,
So the DD boost devices must be mounted onto a NetWorker Storage Node (on primary site can be NetWorker Server) but at DR site the DDboost devices must be mounted on another storage Node. Do we need to consider NetWorker Storage Node Names, IP's ?