Operating System - HP-UX
1833188 Members
3113 Online
110051 Solutions
New Discussion

make_tape_recovery install problem

 
Giorgio Tassi
Occasional Advisor

make_tape_recovery install problem

I need to replicate a system environment on another server and to do it I did a make_tape_recovery of original machine to clone the other one.
Then I install the O.S. from tape modifying only filesystems value, but after first boot I receive the login prompt of the original server and it asks me to type a password(but I didn't set one at installation time).
And scrolling up the boot output I can see that no /var/adm/syslog/ directory exist so syslogd didn't start.
Do anyone can help or suggest me a way to solve the problem?
Thanks.
3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: make_tape_recovery install problem

When you boot off that tape, there is a prompt that comes up after the kernel loads.

You need to hit a key on the console to invoke the Ignite Interface. You need to do some customization,chagning the hostname and such.

My best guess at this point is that the /var filesystem isn't big enough. Probably a disk layout issue. There should be install logs on the box in /opt/ignite or /var/ignite that will tell you more about what happened.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Patrick Wallek
Honored Contributor

Re: make_tape_recovery install problem

There are 2 other things that you probably should have changed as well --

1) The hostname of the system.
2) The IP Address of the system.

Since you only changed filesystem layout info, your new machine came up with the original machines name and IP address.

You also got the root password from the original machine even though you did not set one within ignite.

I do not know why the /var/adm/syslog directory would not be created. Was that in a separate filesystem / logical volume / volume group on the original system? You could just create the syslog directory and try starting syslogd again.

Did the make_tape_recovery complete successfully on the original machine? If /var/adm/syslog does not exist on the new machine I would also make sure that there aren't other directories that did not get restored for some reason.

Giorgio Tassi
Occasional Advisor

Re: make_tape_recovery install problem

Sorry! I've forgotten to add -x inc_entire=vg00 in make_tape_recovery string, so only essential FS were backed up.
Thanks for your help.