- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Ignite server - building replacement target h...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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-14-2006 12:17 AM
тАО08-14-2006 12:17 AM
I have 7 machines I need to backup with Ignite server then push out images to 7 "new" servers replacement hardware. FYI The old and new hardware is not identical, L class , N class and RP mix.
Previously I have used Ignite on each node to backup to local tape device, and swap the tapes over.
What I would like to do is update the Ignite server with the latest O/S patches and hardware enablement bundles, then take the images of the 7 "old" servers and store to locally connected SAN on the Ignite server.
My question is this .... When I push out those images to "new" servers, will Ignite be able to build the "new" servers referencing the newly updated O/S patch bundles and hardware enablement bundles stored locally on the Ignite server. How is this achieved please?
My logic for doing this would be therefore to avoid patching and updating 7 "old" nodes with later versions of Ignite, O/S patches and hardware bundles and having to reboot them (as they are live production systems) before taking images to local tapes.
Sorry if this is blindingly obvious to those familiar with Ignite server - I don't have a test machine I can make into Ignite server (unfortunately)
All help appreciated
Cheers - Ian
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2006 12:24 AM
тАО08-14-2006 12:24 AM
SolutionBill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2006 12:34 AM
тАО08-14-2006 12:34 AM
Re: Ignite server - building replacement target hardware question
OK so what I was trying to acheive isn't viable then I guess, I'll have to update the individual "old" nodes with all patches/bundles, then store image on central server, then push out to "new" kit form central ignnote server.
Thanks for the clarity Bill :)
Ian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2006 12:36 AM
тАО08-14-2006 12:36 AM
Re: Ignite server - building replacement target hardware question
If your non-OS disks are all on the SAN, it should be fairly easy to get back up an running without a restore of the data. Just vgexport -s -p -m those volume groups before you make your image( also might be a good idea to put them in a second place ). Then you can just vgimport when you get the OS on your new hardware. The reason you will probably have to vgexport vgimport will be that the ctd numbers may changes. Mostly likely the c number will.
Also your images of those 7 servers will be identical restores. You would then need to install the latest patch bundle manually. No way that I know of to automate that with make_net_recovery. Of course this is still fairly trivial. its easy to run swinstall after you get the OS back on the machine.
Now if you did a new install from your ignite server, then you could automate the patch installation aswell. Also keep in mind that if you are moving from cell based to bus based your ignite images will probably not work. But if your moving from bus based to cell based they should work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2006 12:57 AM
тАО08-14-2006 12:57 AM
Re: Ignite server - building replacement target hardware question
I would have only been attemping the VG00 restore, I'm familiar with vgexport/vgimport, it was just the automation of the patch bundles on the source machines that interested me - I got burned once as I ignited from a L-2000 and tried to build a RP-3400, my source ignite image was missing kernel compatability for the PA8700 proc. range, so that's why I wanted to rebuild the target machines with a centrally referenced h/w enablement bundle. I previously found that without adding the h/w enablement bundle to the source server in advance of taking the image, the resulting image was unbootable on the target machine.
I guess Im forced into getting slots for reboots on each node before updating h/w, patches,ignite-ux s/w, and then taking the backup image to later restore on new kit.
Thanks - Ian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2006 04:47 AM
тАО08-14-2006 04:47 AM
Re: Ignite server - building replacement target hardware question
Bill Hassell, sysadmin