make_net_recovery of an Ignite Server to another Ignite Server and vice versa

[Alzhy]

Any problems to this?

We've now made a standard doing make_net_recovery of servers to a central Ignite Server specially before doing patch applications and upgrades. Now we plan to setup another Ignite Server so each Ignite-Server would be able to back each other up.. Any problems doing a make_netrecovery of an Ignite server to another?

[RAC_1]

Absolutely not.

In make_net_recovery command you specify the volume group that stores the net_recoveries of clients.

If you prepare the net_recoveries in /ignite_net which is in vg00, then you do have any problem, if it is on vg01 you will have to include vg01 in your network recovery.

[Steven E. Protter]

I have three servers backing up to my centralized Ignite server via make_net_recovery scripts.

The centralized server and all others due a weekly make_tape_recovery. The centralized Ignite server makes an image of himself on the production server once a week.

Once we have an off site DR Center, I'm going to use that one for storing Ignite images as well.

It works great. GO FOR IT!

SEP

[Pramod_4]

I would sugest configuring the second server as the ignite server, enable the network boot, replicate only the make_net_recovery archives and related directoris to the second Ignite server.

If you do so, in the event of any of your client crashes and your primary ignite server is unavailable, you have second ignite server available with all the images of your clients on it.

Thanks,
Pramod