- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: make_net_recovery to an unknown ignite server
Operating System - HP-UX
1753532
Members
5735
Online
108795
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
Discussions
Discussions
Forums
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
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
тАО01-26-2011 08:50 AM
тАО01-26-2011 08:50 AM
make_net_recovery to an unknown ignite server
Quick question. We have servers in one Datacenter DC-A that we would like to clone to another Datacenter DC-B. Obviously they are on different networks. Servers in DC-A are igniting to ignite servers in DC-A. We have stood up a new ignite server in DC-B that we want to run ignites too. Anyone see issues with doing this? Would the ignite clients need to be reconfigured? Or is it as simple as just specifying the new target ignite server in DC-B via the make_net_recovery command?
All help is appreciated.
Mark.
All help is appreciated.
Mark.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-26-2011 09:16 AM
тАО01-26-2011 09:16 AM
Re: make_net_recovery to an unknown ignite server
Hi,
When you recover from an Ignite you have a screen that allows change unique parameters of server in case of a clonation (i.e: LAN configuration, hostname, etc).
Also keep on mind that:
Ignite backup is an image of the Operating System. Either use Ignite server to manage images or tape. make_net_recovery or make_tape_recovery respectively.
Golden images can be used to install HP-UX on multiple servers using the same prepared image or a cloned image.
Datailed info:
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01942571/c01942571.pdf
Rgds.
When you recover from an Ignite you have a screen that allows change unique parameters of server in case of a clonation (i.e: LAN configuration, hostname, etc).
Also keep on mind that:
Ignite backup is an image of the Operating System. Either use Ignite server to manage images or tape. make_net_recovery or make_tape_recovery respectively.
Golden images can be used to install HP-UX on multiple servers using the same prepared image or a cloned image.
Datailed info:
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01942571/c01942571.pdf
Rgds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-26-2011 11:13 AM
тАО01-26-2011 11:13 AM
Re: make_net_recovery to an unknown ignite server
there are a couple ways to do this.
1) specify ignite server DC-B in the make_net_recovery -s "ignite_at_DC-B"...
beware that ignite uses NFS, so depending on your WAN bandwidth (assuming DC-A and DC-B are on WAN connections), you the make_net_recovery may take awhile or even fail.
2) ftp the ignite images from ignite server DC-A to ignite server DC-B
3) some other kind of auto file copy solution to replicate the images from A to B.
you will need to then modify some ignite files in order to boot and build a clone.
4) create a make_tape_recovery and ship the tape to siteB ....
1) specify ignite server DC-B in the make_net_recovery -s "ignite_at_DC-B"...
beware that ignite uses NFS, so depending on your WAN bandwidth (assuming DC-A and DC-B are on WAN connections), you the make_net_recovery may take awhile or even fail.
2) ftp the ignite images from ignite server DC-A to ignite server DC-B
3) some other kind of auto file copy solution to replicate the images from A to B.
you will need to then modify some ignite files in order to boot and build a clone.
4) create a make_tape_recovery and ship the tape to siteB ....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-26-2011 11:30 AM
тАО01-26-2011 11:30 AM
Re: make_net_recovery to an unknown ignite server
You simply specify the Ignite Server on DC-B for your DC-A Ignite Clients. You also need to specify the NFS repository Location (properly exported of course) on DC-B for your DC-A Client's archives.
In a Recovery/Clone Operation on DC-B, All you have to do is follow the IUX Faq on cloning a system via net_recovery archives and make tweaks to your NFS exports for the target machine in DC-B... It is well documented there.... /opt/ignite/share/doc/FAQ Section 11.2
Cheers!
In a Recovery/Clone Operation on DC-B, All you have to do is follow the IUX Faq on cloning a system via net_recovery archives and make tweaks to your NFS exports for the target machine in DC-B... It is well documented there.... /opt/ignite/share/doc/FAQ Section 11.2
Cheers!
Hakuna Matata.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP