You will have to run pre-clone/cfgclone/post clone stuffs, because your Server Names are different.
Unless you are going to keep server names same and going to make changes at network level to force traffic to DR site (in case of failure) you will have to run pre-clone and post clone stuff.
Thanks Pravin, Kandra, and ALL,
Supposing the two servers (PROD & DR) are of different network, and I will make the server name the same?
So it is possible to run it pre-made out of the box style?
My goal really is to avoid doing tasks of pre-clone/cfgclone/post clone tasks, because it took sometime.
if the network is different and the host names remain the same, all you have to run after restoring is autoconfi.
I unsure how to make same name even if its different network. Also DNS server can not resolve it properly if there are two servers with the same name, I guess
Thanks Michael and ALL,
Why do I need to run autoconfig when everything seems the same?
Just like a mirror image server.
Hi Kanda and ALL,
I can disconnect my DR server from the network and make it "stand-alone" so I can use the same PROD server name.
And when disaster comes, I will shutdown the PROD and attach the DR server to the network, so it will not see duplicate server name.
Is this a feasible and possible solution?
It is possible and we do it. But you need to identify how you are going to get latest file system on the DR servers. ( latest database files/log and out files etc)
other wise this possible. You will have to take help of Network/DNS folks to route incoming connection to new servers.
But again running autoconfig will clear all dangling issue ( if any)
Thanks Pravin and ALL
You mean by autoconfig , It conotes running of pre-clone/cfgclone/post clone tasks as well or just autoconfig alone will do?