Operating System - HP-UX
1752729
Members
5521
Online
108789
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
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
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
02-17-2011 11:12 PM
02-17-2011 11:12 PM
Re: ignite
Hello Jona,
You need to ensure all teh configuration is fine as said above. Such as /etc/hosts entires and DNS entry of your client in teh network, DNS entry should work with forward and reverse lookup ( IP & hostname vice versa). Ensure nfs daemon is running on server as well as client.
Then perfrom folwllowing steps to configure your client for Ignite netrecovery.
Add new ignite client on ignite servers in your environment
Add client to /etc/exports on ignite server
Example
/var/opt/ignite/recovery/archives/client_name -anon=2,access=client_name
Create recovery archive directory on Ignite server
Eg.
# mkdir /var/opt/ignite/recovery/archives/client_name
# chown bin:bin /var/opt/ignite/recovery/archives/ client_name
Add the /var/opt/ignite/clients//recovery/archive_content file, with the following contents (ensure file is owned by bin:bin and is world readable):
inc_entire /dev/vg00
Once server is added to the ignite server, create a full Ignite-UX backup of the vg00 volume group to both ignite servers.
# make_net_recovery â s Ignite_server â v
Verify and check
HTH,
Regards,
INH
You need to ensure all teh configuration is fine as said above. Such as /etc/hosts entires and DNS entry of your client in teh network, DNS entry should work with forward and reverse lookup ( IP & hostname vice versa). Ensure nfs daemon is running on server as well as client.
Then perfrom folwllowing steps to configure your client for Ignite netrecovery.
Add new ignite client on ignite servers in your environment
Add client to /etc/exports on ignite server
Example
/var/opt/ignite/recovery/archives/client_name -anon=2,access=client_name
Create recovery archive directory on Ignite server
Eg.
# mkdir /var/opt/ignite/recovery/archives/client_name
# chown bin:bin /var/opt/ignite/recovery/archives/ client_name
Add the /var/opt/ignite/clients/
inc_entire /dev/vg00
Once server is added to the ignite server, create a full Ignite-UX backup of the vg00 volume group to both ignite servers.
# make_net_recovery â s Ignite_server â v
Verify and check
HTH,
Regards,
INH
Knowledge is power
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2011 03:24 AM
02-18-2011 03:24 AM
Re: ignite
Hi,
Tnx all, I have cheked & found in etc/hosts entry was not there so i put the entry in both client & server , now i am able to ping by name & ip from both client & server.& again reexport the.. but now working ..
in client if i fire showmount -a it showes the following error
"showmount: xxxx02: RPC: Program not registered"
yesterday i have restarted nfs.core & nfs.client on client machine. so what you suggest now shall i restart nfs.server in server machine?
REgards,
Jona
Tnx all, I have cheked & found in etc/hosts entry was not there so i put the entry in both client & server , now i am able to ping by name & ip from both client & server.& again reexport the.. but now working ..
in client if i fire showmount -a it showes the following error
"showmount: xxxx02: RPC: Program not registered"
yesterday i have restarted nfs.core & nfs.client on client machine. so what you suggest now shall i restart nfs.server in server machine?
REgards,
Jona
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2011 03:25 AM
02-18-2011 03:25 AM
Re: ignite
Jona same problem is our envirnment ... i am also facing the sam problem .... you can also check my thread..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2011 09:30 PM
02-21-2011 09:30 PM
Re: ignite
HI Manix,
I am able to do it.. i choose another server & make it as ignite server. Thank you .
Regards,
Jona
I am able to do it.. i choose another server & make it as ignite server. Thank you .
Regards,
Jona
- « Previous
- Next »
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