This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Direct Connect Restore Failure

Hi All,

So I tried to recover to a spare server from my core using a crossover cable and a spare NIC but it fails.

It seems to go as expected. It sees the DR server booted with the USB, maps the volumes and starts the recovery but then fails with a "THE CORE IS UNREACHABLE VIA (regular LAN address of core here).

So for example I assigned a static IP outside of my LAN to a spare NIC on the server, lets call it 10.10.10.1
I then assigned the NIC on the USB booted DR server an address of 10.10.10.2

The recovery console forced me to add a gateway and DNS to the DR address so I used the core IP.

From the core I started a recovery and added the DR server address of 10.10.10.2 which it found and mapped the drives. However when the recovery fails it fails referencing the regular LAN IP of the core. In this case we can call it 172.16.16.1 as an example. The point is it's not the IP's used in the recovery process.

Am I missing something here?

Parents Reply Children
No Data