- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Ignite restoration problem
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
Forums
Discussions
Discussions
Forums
Discussions
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
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
09-28-2010 03:00 AM
09-28-2010 03:00 AM
Ignite restoration problem
I have ignite server with ip address 192.168.1.252 and 172.17.120.251
I have taken network ignite of client 192.168.1.15 on ingitesever using igniteserver ip 192.168.1.252
Now i am trying to restore ingnite of 192.168.15 server on client with ip address 172.17.170.12
I have created db profile (blade 860C) where i have mentioned ip address of client 172.17.120.12 gateway and subnet and igniteserver ip as 172.17.120.251
I am able create files system every thing.
But when archive getting restored i get following error.
nfs mount: retrying: /tmp/ign_configure/archive_nfs
nfs mount: 192.168.1.252: : RPC: Rpcbind failure - RPC: Timed out
nfs mount: giving up on: /tmp/ign_configure/archive_nfs
NOTE: NFS mount (/sbin/fs/nfs/mount -oro
192.168.1.252:/primary_copy/Blade/gba
/tmp/ign_configure/archive_nfs) failed, see messages above.
ERROR: Command "/sbin/fs/nfs/mount -oro
192.168.1.252:/primary_copy/Blade/gba
Here my question is i am mentioning ignite server ip as 172.17.120.251 but image is trying to mount from 192.168.1.252
Thanksin advance.
I do assign points always.
Chandra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2010 01:16 AM
09-29-2010 01:16 AM
Re: Ignite restoration problem
There are two different server . Ignite server and also NFS server ( the server where image is stored ) . Generally is the same server but ignite allow you to configure distinct server . Probably your NFS server have a bad configuration . I have no ignite server on my hand , so it's difficult for me to give you the exact place where you can find this information .
On the server ignite , in the client configuration try to see if a parametre nfs-source exsit and change/check its value : Try to go /var/opt/ignite/clients/[your client]
If you don't find anything , yous can examine the file /var/opt/ignite/INDEX or /var/opt/ignite/data/INDEX
For each file present in this configuration file, try to search the value of nfs-source .
I have to configure an ignite server so let me know if you does not finf this parameter i will give you the exact place .
I have this reply could help you
Regards ,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2010 10:45 AM
09-29-2010 10:45 AM
Re: Ignite restoration problem
change in File archive_cfg (Restore Depot Directory): example (/var/opt/ignite/clients/XXXX/recovery/2010-08-02,10:26/archive_cfg)entry "nfs_source" the Ignite Server IP !!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2010 01:55 PM
09-30-2010 01:55 PM
Re: Ignite restoration problem
For example:
drwxr-xr-x 4 bin bin 1024 Mar 13 2008 0x001B78D216FB
drwxr-xr-x 4 bin bin 1024 Aug 26 16:27 0x001B78D29621
lrwx------ 1 bin bin 14 Sep 5 16:30 auasr122 -> 0x001B78D216FB
lrwx------ 1 bin bin 14 Sep 5 14:30 auast120 -> 0x001B78D29621
cd to the appropriate directory and edit the archive_cfg file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2010 06:07 AM
10-01-2010 06:07 AM
Re: Ignite restoration problem
I think 192.168.1.252 is mentioned over there.
change as per your requirements