after ignite restore can't log in

[Louis McCurry]

Just had to do a restore from a make_recovery tape. Resore seemed to go fine but I couldn't log on with any user id or password. Brought the system down to single user and reset the root password. Brought system backup, could login but discovered none of the /home directory was rebuilt. Any suggestions.
Also, am I going to have to reset every user password. Did something fail on the restore that I did not notice?

[Paula J Frazer-Campbell]

Hi

Yes I think is the answer -

1. Look at the files on the ignite tape and see if the /home dir is there - also the passwd etc.

2. Redo the ignite.

It it possible that you did not include the dirs /home and /etc in your make_tape_recovery.


Paula

[steven Burgess_2]

When was your ignite tape created?

/home should be backed up weekly, have you checked your last recent full backup for the contents

[steven Burgess_2]

next recovery try the options

make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

[Helen French]

Hi,

Enter '-A' option when you do the ignite backup next time inorder to include the entire vg00.

Now, check the /etc/passwd and see if your user's home directories are in another VG ? If you find any mismatch in /etc/passwd, try copying it from a recent backup.

What type of error r u getting while trying to login ?

HTH,
Shiju

[Louis McCurry]

recovery tape was made 24 hours ago. Home is in the vg00 group. The passwd file is in /etc but it has * in the password section of the user line. Now I have fears of what else may be missing. This is a production server so should I do a restore from TSM which passes over this system each night?

[Paula J Frazer-Campbell]

Hi

Are you running a trusted system?

Paula

[Louis McCurry]

No, it's a stand alone system but I just discovered there is no /etc/shadow file. This is really strange.
I'm restoring individual file systems in vg00 from a tsm backup. All this time I thought the make_recovery would prevent all of this.

[Darrell Allen]

Hi,

Unfortunately, this isn't going to be of much help for your current problem but perhaps it will help you in the future.

From the searchs I've just run on HP's site, it appears trusted systems should not be a problem with Ignite. However, I did find one post stating "some of the old versions did have issues with trusted systems which only show up during recovery".

Are you running a relatively new version of Ignite? You should consider getting the latest and using make_tape_recovery as make_recovery is being phased out.

Could you post the command line you are using to make the tape?

Darrell

[Louis McCurry]

The command in use is:
/opt/ignite/bin/check_recovery
/opt/ignite/bin/make_recovery -v
-d /dev/rmt/2mn

Obviously something isn't correct with this as I had to do many, many restores to get the system correct, including the /tcb/auth directory which was the source of the login problems.
Any light that could shed on the make_recovery issue would be appreciated. I've been doing these for sometime and this is the first time I had to rely on one, now I'm real concerned.

[Martin Burnett_2]

Hello,

From the command you are using the make_recovery tape will only make a minimum core OS recovery tape. This would include:
Core OS data:
/.profile /.rhosts
/dev /etc
/sbin /stand
/usr(partial) /var (partial)
/opt/upgrade /opt/dce

Noncore Data:
/usr (some parts)
/opt (some parts)
/var (most parts)

This form of make_recovery was designed to install a minimum OS as quickly as possible and then restore the remainder of the system from backup (such as Omniback) tape.

As stated in the threads above if you wanted to back up the entire vg00 you needed to use the "-A" option on your make_recovery command. You did not post what version of ignite you are using and it does make a difference.

Further make_recovery was designed to restore non-interactively. If you interact (interrupt the restore and use the Configuration TUI) with the restore using older versions of ignite, by default, the following configuration files will not be restored:

/etc/fstab /etc/lvmtab
/etc/ioconfig
Primary/Alternate boot paths
network configurations

Ignite restores these files using the /etc/usr/newconfig versions of the files. Newer versions of ignite (3.3 and above) have been changed so that this behaviour does not occur.

I hope you have been able to restore your system completely by now. I would strongly urge you to upgrade to the newer version of Ignite. The make_recovery command has been changed to make_tape_recovery and it's functionality has been increased dramatically. For instance you can now use make_tape_recovery and archive not just vg00 but any other volume groups you have on your system in their entirety using the -x inc_entire=vgXX option.

Martin

[Darrell Allen]

Hi,

Sorry, it sounds like you had a long night.

Here's the make_recovery command line I formerly used:
make_recovery -A -d /dev/rmt/0mn

Here's the make_tape_recovery command line I use now:
make_tape_recovery -a /dev/rmt/0mn -I -v -x inc_entire=vg00

I also strongly suggest you upgrade to the latest Ignite and begin using make_tape_recovery.

Incidentally, you are running a trusted system since the Trusted Computing Base (tcb) was required for login. There is no /etc/shadow in HPUX. The /tcb directory structure is used instead and has much more functionality than a password shadow file.

Darrell