Make Recovery

[Steve Lewis]

Who agrees with me that make_recovery should be placed on the support/recovery/install CD as a separate stand-alone executable?

Time and time again I go to a customer site and find that the root disk isn't mirrored. They won't give me the down time to run a copyutil and there isn't enough free space in vg00 to install ignite (inc make_recovery). It would be SO useful to be able to mount a CD and run make_recovery to tape without installing any software and without shutting down the system. Of course if they had mirrored the root disk in the first place...

[Thierry Poels_1]

might be a good idea!

But on the other hand instead of blaming HP, you could also blame the customer for a bad setup ;)

regards,
Thierry.

[Wieslaw Krajewski]

Hi,

Probably you are right. But, didn't you think about other possibilities, like for example:
1. Installing ignite with make_recovery in another file system and then using symbolic links,
2. Or installing ignite on another system which could be configured as NFS server and using make_recovery via NFS.
Of course, these are just fastand brief remarks.

[Vincenzo Restuccia]

Try with make_net_recovery,(from remote host).

[Steve Lewis]

Thanks for the input. make_net_recovery is the closest to a solution but still doesn't cater for single system installations. Reading the man page it seems that you require ignite to be installed on the servers to be recovered, in which case you may as well run make_recovery in the first place. Correct me if I'm wrong. Make_boot_tape is a possibility in this case.
I wasn't having a go at HP. My quarrel is with VARs and end-users who cut the configuration down to the bare minimum in order to cut costs etc.
In the end it seems to boil down to the need to keep proper control of one's configuration at all times. But I still think my idea is best.