HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_tape_recovery install problem
Operating System - HP-UX
1833188
Members
3113
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2004 03:56 AM
08-02-2004 03:56 AM
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.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2004 04:01 AM
08-02-2004 04:01 AM
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
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
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2004 04:23 AM
08-02-2004 04:23 AM
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.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2004 08:44 PM
08-02-2004 08:44 PM
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.
Thanks for your help.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP