Is it posible to get NFS working from the recovery shell ?

[likid0]

Hi,

Imagine, I have a corrupt /usr, system doesn't boot, no ignite backup, but I have 3rd party backup(legato,tsm,etc)

What I would like to do is..

1.boot to ignites recovery shell
2.loadfiles to get network and nfs server working(seems imposible work)
3.newfs usr lvol
4.mount new /usr via nfs on another server
5.restore files with 3rd party backup tool

Another option:

1.all the same, but just get working nfs client(it should be posible, the ignite recovery mounts with nfs)
2.mount via nfs the old(restored) /usr to a temporary mount point
3.newfs our corrup /usr
4.copy files from temporary mount point to /usr


Has anyone looked into this?

Thnx

[Matti_Kurkela · Accepted solution]

It *may* be possible, but I think it would be rather tricky to do.

If it's possible to add another local disk to the system (or acceptable to overwrite one-half of a mirrored system disk), I would re-install a very basic installation of HP-UX on that disk: Foundation OE and only whatever is needed for the 3rd party backup program to successfully install & run.

Once the backup client is running on the "recovery OS", I would vgimport the original vg00 to the recovery OS (using some other name, e.g. vgrecovery) and mount its root filesystem to a temporary mount point, and other filesystems to appropriate locations within the temp-mounted root filesystem.

Then I could use the 3rd party backup tool as usual to restore files. I would have no problem overwriting anything in the old installation, because none of those files would be actually in use at the time.

Once all the necessary restoration is done, I could simply reboot the system and choose to boot from the old system disk again (with the -lq boot option if I had to sacrifice one half of the mirror for the rescue operation). If it turned out I forgot something (or that the damage was more extensive than originally suspected), it would be easy to reboot back to the "rescue OS" installation and restore more files.

The last step would be to remove the extra disk / re-mirror the system disk, *and* take an Ignite backup of the system :)

This procedure is sufficiently similar to a regular HP-UX installation that you might be able to give good estimates of time required, which would make the bosses happier. It also allows you to use what you're familiar with instead of breaking new ground, which can be kind of stressful in an emergency situation.

MK

[Steven E. Protter]

Shalom,

What you say may work. It is as stated above, very tricky.

With no Ignite backup I would install a new OS on a secondary disk.

This would give me full NFS connectivity. Then I would mount the old corrupt /usr directory and restore the data to it with a third party tool or simple copy command.

Much higher chances of success.

SEP

[likid0]

Thnx Guys, the procedure you mention, works fine I remember a couple of years ago, I had to do something similar, because I had a corrupted /usr(bad disk with a bad mirror) and the ignite image was like 3 years old.

So I restored from ignite the 3 year old image to the mirror disk.

imported the vg00 of the original disk to a temporary /mnt, and restored it with TSM.

Then booted the original disk fine.

But I would have hoped, that HP had got a more or less difficult way of being able to get network and nfs working from a ram shell.

kind of a nfs linux bussy box shell's that are out there.

I can't recall rigth now, when you boot from a install dvd/cd you get the same recovery shell ?