Ignite server setup

[itrc55]

Hi,

i want to make ignite server on rx2660 for ignite backup only not for boot, to take ignite backup of 16 servers. i read the Ignite-UX Administration Guide but still i don't understand something.

which step from below i can skipped when i need to configure ignite server for backup only ?

There are three steps to set up the server:                    
                                                        
 1.  Set up IP addresses - These are temporary                  
     addresses that will be used to boot the client             
     from the server to prepare for the installation.           
                                                                 
 2.  Set up DHCP addresses (optional) - These addresses          
     will be used for the rest of the installation after         
     the client has been booted.                                 
                                                                 
 3.  Set up software - This involves setting up a                
     software depot which contains Core OS software.

And what is the Booting IP Addresses ??

And after finish from ignite server setup how i can start to take ignite backup for all servers

Thanks

[Arunabha Banerjee]

Hi,

I belive you are trying to setup Ignite server for network recovery. Please follow the below steps:

Server setup
**************
1.Check if the HP-UX installation utilities (Ignite-UX) are installed
#swlist | grep IGNITE
  IGNITE                        C.7.11.444     HP-UX Installation Utilities (Ignite-UX)
OR
# swlist Ignite-UX
# Initializing...
# Contacting target "ignitesrv"...
#
# Target:  ignitesrv:/
#

# Ignite-UX                                                   C.7.11.444     HP-UX System Installation Services
 Ignite-UX.BOOT-COMMON-IA                 C.7.11.444     Common Boot Components for IPF clients
 Ignite-UX.BOOT-COMMON-PA               C.7.11.444     Common Boot Components for PA-RISC clients
 Ignite-UX.BOOT-KRN-11-11                   C.7.11.444     Installation Boot Kernel for B.11.11 clients
 Ignite-UX.BOOT-KRN-11-23                   C.7.11.444     Installation Boot Kernel for B.11.23 clients
 Ignite-UX.BOOT-KRN-11-31                   C.7.11.444     Installation Boot Kernel for B.11.31 clients
 Ignite-UX.BOOT-SERVICES                    C.7.11.444     Network Boot Services for System Installations
 Ignite-UX.CD-TOOLS                                C.7.11.444     Tools for creating CD media
 Ignite-UX.CD-TOOLS-DOC                      C.7.11.444     Documentation for CD-TOOLS
 Ignite-UX.CD-TOOLS-SRC                      C.7.11.444     Source for CD-TOOLS
 Ignite-UX.DVD-TOOLS                              C.7.11.444     Tools for creating DVD media
 Ignite-UX.DVD-TOOLS-DOC                    C.7.11.444     Documentation for DVD-TOOLS
 Ignite-UX.DVD-TOOLS-SRC                    C.7.11.444     Source for DVD-TOOLS
 Ignite-UX.FILE-SRV-11-11                       C.7.11.444     File Archives Used By Clients During HP-UX Install
 Ignite-UX.FILE-SRV-11-23                       C.7.11.444     File Archives Used By Clients During HP-UX Install
 Ignite-UX.FILE-SRV-11-31                       C.7.11.444     File Archives Used By Clients During HP-UX Install
 Ignite-UX.IGNITE                                        C.7.11.444     Graphical Ignite User Interface for Installations
 Ignite-UX.IGNT-ENG-A-MAN                    C.7.11.444     Ignite-UX Manual Pages
 Ignite-UX.IGNT-JPN-E-MAN                     C.7.11.444     Ignite-UX Japanese EUC Manual Pages
 Ignite-UX.IGNT-JPN-S-MAN                     C.7.11.444     Ignite-UX Japanese SJIS Manual Pages
 Ignite-UX.MGMT-TOOLS                           C.7.11.444     Tools for Managing Data Files on an Ignition Server
 Ignite-UX.RECOVERY                               C.7.11.444     System disaster recovery tools

2.If not: download Install the HP-UX installation utilities (Ignite-UX)
# swinstall -s /var/opt/Ignite-UX-11-ALL_C.7.11.444.depot

3.Run the script
# /opt/ignite/lbin/pkg_rec_depot
Or
# /opt/ignite/lbin/pkg_rec_depot -f -a

4.Setup the Ignite servers default values
# /opt/ignite/lbin/setup_server -n

5.Enable tftp and bootpd
# vi /etc/inetd.conf
...
tftp        dgram  udp  wait   root /usr/lbin/tftpd    tftpd \
        /opt/ignite\
        /var/opt/ignite
bootps      dgram  udp  wait   root /usr/lbin/bootpd   bootpd -d 3
...

6.Reread inetd config
# inetd -c

7.Check the default values of the Ignite installation
# instl_adm
...
server="2xx.4x.1xx.1xx"
netmask[]="255.255.255.240"
route_gateway[0]="2xx.4x.1xx.1xx"
route_destination[0]="default"
sd_server="2xx.4x.1xx.1xx"
...

8.Configure the ignite parameters to be only a boot helper that points to the "real" Ignite-UX server
# cd /opt/ignite/boot
# instl_adm -d > instl_adm.config
# vi instl_adm.config

instl_adm.config:

# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
#       and "end instl_adm defaults" will not be preserved.
server="172.16.18.50"
netmask[]="255.255.255.0"
route_gateway[0]="172.16.18.1"
route_destination[0]="default"
# end instl_adm defaults.

Where:

172.16.18.50 is the IP of the Ignite-UX server
255.255.255.0 is the netmask of the subnet the boot helper is part of
172.16.18.1 is the gateway of the subnet the boot helper is part of
 

9.Install the new parameters
# instl_adm -f instl_adm.config

10.On the ignite server create and share the archive directory for the client you want to backup
# mkdir -p /var/opt/ignite/recovery/archives/hostname
# chown bin:bin /var/opt/ignite/recovery/archives/hostname
# vi /etc/exports
Add the following entries
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/hostname -anon=2,access=hostname

# exportfs -av
# showmount -a
# showmount -e

Below steps for HP-UX 11.31 only
*************************************
# vi /etc/dfs/dfstab
share -F nfs -o anon=2 /var/opt/ignite/clients
share -F nfs -o sec=sys,anon=2,rw=/var/opt/ignite/recovery/archive​s/<client>

# shareall

11. Add Ignite clinet to /etc/hosts
# vi /etc/hosts
10.x.x.x client.hostname

Client setup
**************
1. Add Ignite server to /etc/hosts
10.x.x.x ignitesrv

2.To upgrade the Ignite client version from Ignite server
# /usr/sbin/swinstall -x mount_all_filesystems=false -s ignitesrv:/var/opt/ignite/depots/recovery_cmds "*"

3.Run the make_net_recovery command from client
# /opt/ignite/bin/make_net_recovery -Av -s ignitesrv
OR
# /opt/ignite/bin/make_net_recovery -Av -s igniteserver.domain -x inc_entire=/dev/vg00

Please let me know if you face any problem to setup the server and client as per the above steps.

[itrc55]

Hi,

Thank you so much for your support, but i facing some issue.

before that, do i need to run the ignite GUI server setup before or after this steps ?

on step 3, do I need to implement this step when the ignite it's already installed ?

>

# /opt/ignite/lbin/pkg_rec_depot -f -a
Usage:  pkg_rec_depot [-f] [-?]

  -f  Force rebuild of depot even if the version is current
  -?  Display this help screen

This script creates a depot containing the filesets needed for a client
to run make_net_recovery or make_tape_recovery.  Filesets are packaged 'in
place' on the current system.

# /opt/ignite/lbin/pkg_rec_depot
       * Depot: /var/opt/ignite/depots/recovery_cmds is up to date - no action r                                                                                        equired.
<

on step 4,

>

# /opt/ignite/lbin/setup_server -n
Program completed successfully.

<

on step 5, what is the " -d 3" on bootps ?

on step 7, i facing this output, do i need add other info and what is the (sd_server="2xx.4x.1xx.1xx")

>

# instl_adm
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
#       and "end instl_adm defaults" will not be preserved.
server="10.14.170.33"
# end instl_adm defaults.
<

on step 8, what do you mean whit step 8 "Configure the ignite parameters to be only a boot helper that points to the "real" Ignite-UX server" ?

and when i edit this file # vi instl_adm.config i need to add this information only

erver="172.16.18.50"
netmask[]="255.255.255.0"
route_gateway[0]="172.16.18.1"
route_destination[0]="default" 

on step 10, my system is 11.31 do i skip this steps ?

>

# vi /etc/exports
Add the following entries
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/hostname -anon=2,access=hostname

# exportfs -av
# showmount -a
# showmount -e

<

and execute this steps

>

# mkdir -p /var/opt/ignite/recovery/archives/hostname   ===> for each client i want to take backup
# chown bin:bin /var/opt/ignite/recovery/archives/hostname

# vi /etc/dfs/dfstab
share -F nfs -o anon=2 /var/opt/ignite/clients
share -F nfs -o sec=sys,anon=2,rw=/var/opt/ignite/recovery/archive​s/<client>

# shareall

<

Thanks for your support

[itrc55]

Hi,

i facing this message when i try to shareall

# shareall
Usage: share [-o options] [-d description] pathname [resource]

and i try direct share
# share -F nfs -o sec=sys,anon=2,rw=/var/opt/ignite/recovery/archives/server1
Usage: share [-o options] [-d description] pathname [resource]

Thanks

[itrc55]

Hi,

i facing this error message when i try to make ignite backup from client

* Creating The Networking Archive

nfs mount: servera:/var/opt/ignite/recovery/archives/serverb: Permission denied
ERROR:   Unable to mount or write servera:/var/opt/ignite/recovery/archives/serverb
         On servera you may need to:
         mkdir -p /var/opt/ignite/recovery/archives/serverb
         chown bin:bin /var/opt/ignite/recovery/archives/serverb

         If the OS on servera is 11.31 or later, vi /etc/dfs/dfstab. The /etc/dfs/dfstab file on "servera" should contain the entry: "share -F nfs -o
         sec=sys,anon=2,rw=<client> /var/opt/ignite/recovery/archives/serverb". Where <client> is replaced by a fully qualified client name.
         After editing the /etc/dfs/dfstab file, run "shareall -F nfs"
         If you need to change the owner of the directory,
         you will also need to re-share the directory.

         Otherwise, vi /etc/exports. The /etc/exports file on "servera" should contain the entry: "/var/opt/ignite/recovery/archives/serverb-anon=2,access=serverb".
         After editing the /etc/exports file, run exportfs -av
         If you need to change the owner of the directory,
         you will also need to re-export the directory.

         See make_net_recovery(1M) for more information.
ERROR:   Failed to Create NFS mount Archive directory.

On client server

# more /etc/hosts

10.x.x.x            serverb
10.x.x.x            serverb-mgt

10.x.x.x            servera
127.0.0.1          localhost       loopback


On ignite server

# more /etc/dfs/dfstab

share -F nfs -o anon=2 /var/opt/ignite/clients
share -F nfs -o sec=sys,anon=2,rw=serverb /var/opt/ignite/recovery/archives/serverb

# more /etc/hosts

10.x.x.x    servera
10.x.x.x    servera-mgt
10.x.x.x    serverb
10.x.x.x    serverb-mgt
127.0.0.1  localhost       loopback

# cd  /var/opt/ignite/recovery/archives
# ll
drwxr-xr-x   2 bin        bin             96 Jul 18 09:08 serverb

Thanks

[Dennis Handly]

>share -F nfs -o sec=sys,anon=2,rw=serverb /var/opt/ignite/recovery/archives/serverb

Are you using the FQDN for serverb above?

[Arunabha Banerjee]

Qus: on step 3, do I need to implement this step when the ignite it's already installed ?

Ans: No you don't need to run

Qus: on step 5, what is the " -d 3" on bootps ?

Ans: Don't need to add " -d 3"

bootps      dgram  udp wait   root /usr/lbin/bootpd   bootpd

Qus: on step 7, i facing this output, do i need add other info and what is the (sd_server="2xx.4x.1xx.1xx)

Ans: Please add ignite server IP.

server="172.16.18.50"
netmask[]="255.255.255.0"
route_gateway[0]="172.16.18.1"
route_destination[0]="default"
sd_server="172.16.18.50"

172.16.18.50 is the ip of the boot helper
255.255.255.0 is the netmask of the subnet the boot helper is part of
172.16.18.1 is the gateway of the subnet the boot helper is part of
172.16.18.50 is the ip of the Ignite-UX server

Qus: on step 8, what do you mean whit step 8 "Configure the ignite parameters to be only a boot helper that points to the "real" Ignite-UX server" ?

Ans: If the client is not in the same subnet as the Ignite-UX server and the clients need to be booted from the network (the client is currently not running HP-UX 9.x or later), a boot helper needs to be installed. The boot helper must be on a HP-UX system within the subnet of the Ignite-UX client

Qus: on step 10, my system is 11.31 do i skip this steps ?

Ans: Yes you can skip this steps

As your Ignite server HP-UX version is 11.31, Please follow this steps:

Configure the "real" Ignite-UX server to be able to transfer the boot files over nfs

# vi /etc/dfs/dfstab
...
# use nfs instead of tftp
share -F nfs -o ro /opt/ignite/data
share -F nfs -o ro /var/opt/ignite/data
share -F nfs -o anon=2 /var/opt/ignite/clients
share -F nfs -o anon=2 /var/opt/ignite/scripts

# shareall

On the ignite server create and share the archive directory for the client you want to backup

# mkdir -p /ignite/recovery/archives/hostname
# chown bin:bin /ignite/recovery/archives/hostname
# vi /etc/dfs/dfstab
...
share -F nfs -o sec=sys,anon=2,rw=hostname.domain /ignite/recovery/archives/hostname
# exportfs -av

Run the make_net_recovery command from client
# /opt/ignite/bin/make_net_recovery -s igniteserver.domain -a igniteserver.domain:/ignite/recovery/archives/hostname

[itrc55]

Hi,

i still facing this error message when i try to make ignite backup from client

* Creating The Networking Archive

nfs mount: servera:/var/opt/ignite/recovery/archives/serverb: Permission denied
ERROR:   Unable to mount or write servera:/var/opt/ignite/recovery/archives/serverb
         On servera you may need to:
         mkdir -p /var/opt/ignite/recovery/archives/serverb
         chown bin:bin /var/opt/ignite/recovery/archives/serverb

         If the OS on servera is 11.31 or later, vi /etc/dfs/dfstab. The /etc/dfs/dfstab file on "servera" should contain the entry: "share -F nfs -o
         sec=sys,anon=2,rw=<client> /var/opt/ignite/recovery/archives/serverb". Where <client> is replaced by a fully qualified client name.
         After editing the /etc/dfs/dfstab file, run "shareall -F nfs"
         If you need to change the owner of the directory,
         you will also need to re-share the directory.

         Otherwise, vi /etc/exports. The /etc/exports file on "servera" should contain the entry: "/var/opt/ignite/recovery/archives/serverb-anon=2,access=serverb".
         After editing the /etc/exports file, run exportfs -av
         If you need to change the owner of the directory,
         you will also need to re-export the directory.

         See make_net_recovery(1M) for more information.
ERROR:   Failed to Create NFS mount Archive directory.

Thanks

[Arunabha Banerjee]

Please share /etc/dfs/dfstab and /etc/exports from Ignite server. Also share /etc/hosts file from both client and server.

[itrc55]

Hi,

Thanks so much i can now take ignite backup successfully. i will give you the kudos.

but i still have two questions:

1. how to take ignite backup for two system on different subnet

ignite server ip : 192.168.1.1

client 1 ip: 192.168.1.5

client 2 ip: 172.168.10.10

2. how to take backup on filesystem from san disk

Thanks a lot

[Arunabha Banerjee]

Hi,

For your question no 1 you need add add gateway and route. Please consult with your network team.

For your question no 2 if you have any other VG other than root VG like "datavg" then you need to execute following command # make_net_recovery -Av -s IgniteServer -x inc_entire=/dev/vg00 /dev/datavg

But it is always recommended that you should take only root VG (vg00) backup through Ignite. And for other VG you should use tar or any third party backup utility.

[Steven E. Protter]

Shalom,

Ignite is designed for the boot disk. rootdg in VxVM vg00 in most LVM shops.

It can back up almost anything. I've gotten clean backups of oracle databases so long as the database is down when the backup is cut.

Ignite is a cumbersome tool for doing anything other than the boot disk. Its really good at that. There are better tools for backing up your data.

SEP

[itrc55]

Hi,

i configure the ignite server successfully but after take a backup on all clients server i facing this message after backup finish

=======  07/25/11 10:47:19 WAT  make_net_recovery completed successfully!
nfs umount: nfs_unmount: /var/opt/ignite/recovery/client_mnt: is busy
umount: return error 1.
ERROR:   Unable to unmount /var/opt/ignite/recovery/client_mnt

How to make system unmount this /var/opt/ignite/recovery/client_mnt automatically because i can unmounted manually ?

Thanks

[Dennis Handly]

>How to make system unmount this /var/opt/ignite/recovery/client_mnt automatically

You can use the automounter to mount it and that will automatically unmount it.

Have you tried fuser to see who is still using that filesystem?  Anyone cd into a directory there?

[jit1986it]

Thank U so much!!, I configured it....

If you run the TYI screen, it will be bit faster, and no need to do manual changes..

BR

Roy

HP

[pradeep m]

Ignite-uX Server configuration is very well documented in HP Ignite-UX Guided Troubleshooting. You can use this for your future reference. 

Click here to view HP Ignite-UX Guided Troubleshooting

For step by step instructions for server configutation, From the above link, choose Configuration / How-To Guide -> Ignite-UX Server Side Configuration

To access all other available HP Guided Troubleshooting guides, visit:

www.hp.com/support/hpgt  and choose the appropriate products.