HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- building if the machine crashes
Operating System - Linux
1827845
Members
1224
Online
109969
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
12-31-2006 02:08 AM
12-31-2006 02:08 AM
building if the machine crashes
i wanted to know the options available in case if the machine crashes and not recoverable..since we have two platforms (one HP-UX and other Linux) and since we are new to Linux, I have this concern.HP-UX, we take the ignite so works like a charm. what shd i do for linux in that situation? here is a listing from the /boot and /root. this linux box runs redhat AS 3.
#cd /boot
# ll
total 10887
lrwxrwxrwx 1 root root 30 Nov 15 00:30 System.map -> System.map-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 580154 Oct 13 15:12 System.map-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 607622 Oct 13 15:04 System.map-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 48951 Oct 13 15:12 config-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 49066 Oct 13 15:04 config-2.4.21-47.0.1.ELsmp
drwxr-xr-x 2 root root 1024 Nov 15 00:25 grub
-rw-r--r-- 1 root root 317967 Nov 15 00:22 initrd-2.4.21-47.0.1.EL.img
-rw-r--r-- 1 root root 327354 Nov 15 00:22 initrd-2.4.21-47.0.1.ELsmp.img
-rw-r--r-- 1 root root 547 Oct 27 19:02 kernel.h
drwx------ 2 root root 12288 Oct 27 18:51 lost+found
-rw-r--r-- 1 root root 23108 Sep 11 2003 message
-rw-r--r-- 1 root root 21282 Sep 11 2003 message.ja
-rwxr-xr-x 1 root root 2912724 Oct 13 15:12 vmlinux-2.4.21-47.0.1.EL
-rwxr-xr-x 1 root root 3551892 Oct 13 15:04 vmlinux-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 1260061 Oct 13 15:12 vmlinuz-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 1368127 Oct 13 15:04 vmlinuz-2.4.21-47.0.1.ELsmp
[/boot] 06:59:55
# cd /root
[~] 07:00:09
# ll
total 64
-rw-r--r-- 1 root root 2284 Oct 27 18:58 anaconda-ks.cfg
-rw-r--r-- 1 fchodack ibmaod 1259 Dec 17 12:53 csdpWasKeyFile.jks
-rwxrwxrwx 1 root root 0 Dec 18 12:47 exportLTPAkey.0
-rw-r--r-- 1 root root 31725 Oct 27 18:58 install.log
-rw-r--r-- 1 root root 5230 Oct 27 18:58 install.log.syslog
-rw-r--r-- 1 root root 2352 Oct 27 18:59 kickstart.log
-rwxrwxrwx 1 root root 960 Dec 18 12:46 ltpa.key
-rwxr-xr-x 1 root root 960 Dec 18 14:20 ltpakey.txt
-rw-r--r-- 1 root root 2804 Nov 29 11:05 vpd.properties
[~] 07:00:11
#
Happy new year!!!! and thanks in advance
Best Regards
brian
#cd /boot
# ll
total 10887
lrwxrwxrwx 1 root root 30 Nov 15 00:30 System.map -> System.map-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 580154 Oct 13 15:12 System.map-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 607622 Oct 13 15:04 System.map-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 48951 Oct 13 15:12 config-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 49066 Oct 13 15:04 config-2.4.21-47.0.1.ELsmp
drwxr-xr-x 2 root root 1024 Nov 15 00:25 grub
-rw-r--r-- 1 root root 317967 Nov 15 00:22 initrd-2.4.21-47.0.1.EL.img
-rw-r--r-- 1 root root 327354 Nov 15 00:22 initrd-2.4.21-47.0.1.ELsmp.img
-rw-r--r-- 1 root root 547 Oct 27 19:02 kernel.h
drwx------ 2 root root 12288 Oct 27 18:51 lost+found
-rw-r--r-- 1 root root 23108 Sep 11 2003 message
-rw-r--r-- 1 root root 21282 Sep 11 2003 message.ja
-rwxr-xr-x 1 root root 2912724 Oct 13 15:12 vmlinux-2.4.21-47.0.1.EL
-rwxr-xr-x 1 root root 3551892 Oct 13 15:04 vmlinux-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 1260061 Oct 13 15:12 vmlinuz-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 1368127 Oct 13 15:04 vmlinuz-2.4.21-47.0.1.ELsmp
[/boot] 06:59:55
# cd /root
[~] 07:00:09
# ll
total 64
-rw-r--r-- 1 root root 2284 Oct 27 18:58 anaconda-ks.cfg
-rw-r--r-- 1 fchodack ibmaod 1259 Dec 17 12:53 csdpWasKeyFile.jks
-rwxrwxrwx 1 root root 0 Dec 18 12:47 exportLTPAkey.0
-rw-r--r-- 1 root root 31725 Oct 27 18:58 install.log
-rw-r--r-- 1 root root 5230 Oct 27 18:58 install.log.syslog
-rw-r--r-- 1 root root 2352 Oct 27 18:59 kickstart.log
-rwxrwxrwx 1 root root 960 Dec 18 12:46 ltpa.key
-rwxr-xr-x 1 root root 960 Dec 18 14:20 ltpakey.txt
-rw-r--r-- 1 root root 2804 Nov 29 11:05 vpd.properties
[~] 07:00:11
#
Happy new year!!!! and thanks in advance
Best Regards
brian
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2006 03:25 AM
12-31-2006 03:25 AM
Re: building if the machine crashes
Hi brian,
one of the ways is with backup - after crash install base OS with same partitions and mount points and after that restore complete OS from backup. I use that many times and make full recover for about 20-25 min. Another way is with clonning disk images - http://sourceforge.net/projects/g4l
regards,
ivan
one of the ways is with backup - after crash install base OS with same partitions and mount points and after that restore complete OS from backup. I use that many times and make full recover for about 20-25 min. Another way is with clonning disk images - http://sourceforge.net/projects/g4l
regards,
ivan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2006 01:51 PM
12-31-2006 01:51 PM
Re: building if the machine crashes
Using kickstart and RPM you can create a floppy or DHCP server that can boot a system and install a standard image on a linux box. This provides a standard OS image in a very short time and then ftp, nfs or data protector can be used to restore application data.
Emil
Emil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2006 05:35 PM
12-31-2006 05:35 PM
Re: building if the machine crashes
If you have many custom applications/configuration using full disk image will be preferable, IMHO.
You can use Norton Ghost or Mondo/Mindi rescue (http://www.mondorescue.org/), for example.
You can use Norton Ghost or Mondo/Mindi rescue (http://www.mondorescue.org/), for example.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP