how to do ignite backup where there is no tape ?

[DnD_1]

hi guys,

i need to do the ignite backup for one of our server, where it has no tape !

so i was wondering, is there anyway we can do the ignite by network ? i saw the command, make_net_recovery, but I quite blur on how to commanding it

could anyone helps me on this ?

thanks !!!!!!!!!!!

[Rasheed Tamton]

Hi,

It is possible with archive on a server through network. Any server with extra storage can be used as Ignite server.

man make_net_recovery
would give you the info.

The command is:
/opt/ignite/bin/make_net_recovery -vs ignitsrv -x inc_entire=vg00

Regards.

[Rasheed Tamton]

Please see the links below:

http://www.docs.hp.com/en/IUX/

http://www.docs.hp.com/en/5992-3336/index.html

[Asif Sharif]

Hi,

http://docs.hp.com/en/B2355-90772/index.html

see the

Tape Recovery with make_net_recovery
Tape Recovery with No Tape Boot Support
http://docs.hp.com/en/B2355-90772/ch11s05.html

Regards,
Asif Sharif

[Vihang. · Accepted solution]

Hi,

You can take ignite backup of one server on any other server using make_net_recovery. I will give you some rough steps. You can find the details in the docs posted by others.

On the server which has extra space, perform below steps.

# mkdir /clientname (this directory should be created in a filesystem having sufficient space)
# vi /etc/exports
Add the /clientname in the file.
# exportfs -av (this will export the /clientname filesystem nfs mountable on other servers)

On the client whose ignite backup u need to take, perform the below steps.
# make_net_recovery -x inc_entire=vg00 -s -a -v
This will create an archive of the vg00 of your client in the /clientname directory on your server. You can add another vg also if you like using one more -x=inc_entire=vgname. Please note that I havent given you steps which you need to take for network configuration & making sure your ignite server & client can see each other over the network.

Regards,
Vihang.

[DnD_1]

Hi

Thanks all !!!

What if I want to exclude some others logical volume ?

Let say I backup the VG05 but want to exluded the LV02 as below,

/dev/vg5/lv02

How do I do it ?

Thanks!!!

[Rasheed Tamton]

>/dev/vg5/lv02

Why you would want to copy vg5! Ignite is meant for booting the OS either from tape or from the network. At the maximum you can include the full vg00 (option: inc_entire=vg00)

If you do NOT use the inc_entire=vg00, it would only backup the minimal required files and file systems from the VG00.

For backing up the other VGs, it is better to use the other backup tools like fbackup.

Rgds.

[Rasheed Tamton]

Check the -i (interactive) option of make_net_recovery, it would start the GUI and allow you to selectively choose the file systems. I think you would be more comfortable if you use it with the -i option.

See the man below:


-i Causes make_net_recovery to run interactively to allow selection of files and directories that are to be included in the recovery archive. The options -x, -A and -f are not allowed with -i. It is preferable to use the ignite GUI menu command on the Ignite-UX server when running interactive make_net_recovery session. Running it from ignite ensures that any server configuration of NFS mounts is already done. It also provides a better progress reportand an easier to use interface.

[Rasheed Tamton]

If you want the command

-x exclude=file|directory
-x exclude=/path

/opt/ignite/bin/make_net_recovery -s ingite-server -x inc_entire=vg00 -x exclude=file|dir

Including and Excluding From Archive
The contents of the archive may be controlled from the contents file
(see -f). The full path for the contents file (archive_content) is /var/opt/ignite/clients/0xLLA/recovery/archive_content on the Ignite-UX Server.

[DnD_1]

hi,

i want to backup the others because it consist of our oracle and charging software

see below

You have mail.
md1:/home/mduser$bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 163840 53876 103104 34% /
/dev/vg00/lvol1 111637 31332 69141 31% /stand
/dev/vg00/lvol8 7176192 4137821 2855182 59% /var
/dev/vg00/lvol5 983040 732339 235049 76% /usr
/dev/vg00/lvol4 3080192 2475953 594253 81% /tmp
/dev/Vg00/lvol10 85327872 38805032 46232048 46% /storage
/dev/vg02/lvol7 32768000 16027721 16146854 50% /opt/charging
/dev/vg01/lvol1 70656000 13383520 57102272 19% /opt/oracle

so for the command, i can issue...

/opt/ignite/bin/make_net_recovery -x inc_entire=vg00 -x inc_entire=vg02 -s 10.15.136.4 -x exclude=/storage -a10.15.136.4:/backup -v

(backup vg00 and vg02, and exclude the storage)

is it correct ? it seem a bit long does it ?

[Rasheed Tamton]

/opt/ignite/bin/make_net_recovery -x inc_entire=vg00 -x inc_entire=vg02 -x exclude=/storage -s 10.15.136.4 -a 10.15.136.4:/backup -v

> (backup vg00 and vg02, and exclude the storage)

Yes. vg00/vg02 will be entirely backed up and the /storage will be excluded from the backup. If you are not using the default directory to archive on the ignite server, then you have to use the -a option.

>/dev/vg02/lvol7 32768000 16027721 16146854 50% /opt/charging
VG02 is having lvol7 (?). LVOL7 only!
The size is almost 16GB, you have to make sure the /backup has enough space to hold the backup and if there are largefiles you have to enable the file system to largefiles enabled.

You can also use the -i (interactive) with GUI, if you are not comfortable enough.

[DnD_1]

hi rasheed..

thanks !!

how do i start the GUI i ? sorry for my low unix skills :(

[Rasheed Tamton]

make_net_recovery -s ignite-server -i

If your X is working it would give you GUI, otherwise you will get a CHUI

You can also do from the ignite server side with the command ignite
Export your display.
Start ignite
ignite_server # /opt/ignite/bin/ignite

Regards.

[Vihang.]

Hi DnD,

Your command should work absolutely fine. You can use the GUI as mentioned by others, but I always prefer the command line :-D

Regards,
Vihang.

[Deepak Kr]

One more help!!

http://www.docs.hp.com/en/5992-3336/ch08s03.html#v1501609

See all screens here...

[DnD_1]

hi again.

i run the command, and got the following errors.

both have nfs running.

pls helps ?

the server - 10.15.136.69
#exportfs -av
re-exported /cdr/work/proc/ELR_backup

the client - 10.15.136.15
where i run the command :
./make_net_recovery -x inc_entire=vg00 -x exclude=/elr/cdr_backup -s 10.15.136.69 -a 10.15.136.69:/cdr/work/proc/ELR_backup


====================================
# ./make_net_recovery -x inc_entire=vg00 -x exclude=/elr/cdr_backup -s 10.15.136.69 -a 10.15.136.69:/cdr/work/proc/ELR_backup
* Creating NFS mount directories for configuration files.
Permission denied
ERROR: Could not NFS mount directory /var/opt/ignite/clients on 10.15.136.69.
The exports file on 10.15.136.69 should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that /var/opt/ignite/clients
has been exported using the "exportfs -av" command.
ERROR: Failed mounting directory /var/opt/ignite/recovery/client_mnt:/Error 0
(errno = 0)
ERROR: Failed to create NFS mount directories for configuration files.

======= 08/25/08 15:44:37 METDST make_net_recovery completed unsuccessfully

[Rasheed Tamton]

Did you put

/var/opt/ignite/clients -anon=2

in the /etc/exports file. If not, add the above line on the /etc/exports and re-ren exportfs -av

rgds.

[Rasheed Tamton]

Hi,

If you have still the problem, just check the below thread:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1219672538872+28353475&threadId=1060231


rgds.

[DnD_1]

hi rasheed,

on the ignite server..

#cat /etc/exports
/var/opt/ignite/clients - anon=2

#exportfs -av
re-exported /var/opt/ignite/clients

on the cliet side (when i want the ignite)

#cat /etc/exports
/var/opt/ignite/clients - anon=2
/cdr/work/proc/ELR_backup

#exportfs -av
re-exported /cdr/work/proc/ELR_backup

still get the same error....

[DnD_1]

ok, problem solved.

but another issue came up...

i have check as per swagentd.log....the hosts look fine though..

error msg....anyone can suggest anything ?


======= 08/25/08 16:13:58 METDST Started ./make_net_recovery. (Mon Aug 25
16:13:58 METDST 2008)
@(#) Ignite-UX Revision C.6.1.44
@(#) net_recovery (opt) $Revision: 10.672 $

* Testing for necessary pax patch.
* Passed pax tests.
* Checking Versions of Recovery Tools
ERROR: "10.15.136.69:/": You do not have the required permissions to
select this target. Check permissions using the "swacl"
command or see your system administrator for assistance. Or,
to manage applications designed and packaged for nonprivileged
mode, see the "run_as_superuser" option in the "sd" man page.
ERROR: More information may be found in the daemon logfile on this
target (default location is
10.15.136.69:/var/adm/sw/swagentd.log).
ERROR: "10.15.136.69:/": You do not have the required permissions to
select this target. Check permissions using the "swacl"
command or see your system administrator for assistance. Or,
to manage applications designed and packaged for nonprivileged
mode, see the "run_as_superuser" option in the "sd" man page.
ERROR: More information may be found in the daemon logfile on this
target (default location is
10.15.136.69:/var/adm/sw/swagentd.log).
ERROR: The Ignite-UX filesets RECOVERY and MGMT-TOOLS on 10.15.136.69 do not match.
ERROR: Cannot retrieve Ignite-UX version from 10.15.136.69.
ERROR: Retrieving Ignite-UX version on the server:10.15.136.69 failed.

======= 08/25/08 16:14:25 METDST make_net_recovery completed unsuccessfully


# tail -30 /var/adm/sw/swagentd.log
* Started list agent on "/" for root@10.15.136.15, pid=4001,
08/25/08 16:08:16 METDST
WARNING: Security access denied to file "//var/adm/sw/products/INDEX".
ERROR: The target "/" could not be opened. pid=4001 08/25/08 16:08:17
METDST
* Agent pid=4001 completed. 08/25/08 16:08:17 METDST
WARNING: An attempt to get the network host entry for "10.15.136.15"
failed. This may result in denial of access to users and
agents at this host. Check the spelling of this name, then
your "/etc/hosts" file, or your "/etc/resolv.conf" file and
DNS resolver configuration. The nslookup program may be
helpful in isolating this problem.
* Started list agent on "/" for root@10.15.136.15, pid=5484,
08/25/08 16:14:24 METDST
WARNING: Security access denied to file "//var/adm/sw/products/INDEX".
ERROR: The target "/" could not be opened. pid=5484 08/25/08 16:14:24
METDST
* Agent pid=5484 completed. 08/25/08 16:14:24 METDST
WARNING: An attempt to get the network host entry for "10.15.136.15"
failed. This may result in denial of access to users and
agents at this host. Check the spelling of this name, then
your "/etc/hosts" file, or your "/etc/resolv.conf" file and
DNS resolver configuration. The nslookup program may be
helpful in isolating this problem.
* Started list agent on "/" for root@10.15.136.15, pid=5485,
08/25/08 16:14:25 METDST
WARNING: Security access denied to file "//var/adm/sw/products/INDEX".
ERROR: The target "/" could not be opened. pid=5485 08/25/08 16:14:25
METDST
* Agent pid=5485 completed. 08/25/08 16:14:25 METDST

[Tim Nelson]

Have you modified the swacl permissions ? or did you have Bastille do it ?

Post the below from your depot server:
swacl -l host

[Steven E. Protter]

Shalom,

You need full read-write permissions to the NFS share you do your make_net_recovery to.

Doing it to an NFS share with complex permissions is a bad idea.

You need to be confident the write is going to work right every time you do it.

SEP

[DnD_1]

hi...

the swacl -l host.....pls guide..

ignite server.
# swacl -l host
#
# swacl Host Access Control List
#
# For host: cg1
#
# Date: Tue Aug 26 08:58:16 2008
#

# Object Ownership: User= root
# Group=sys
# Realm=cg1
#
# default_realm=cg1
any_other:-r---


server where i want the ignite
# swacl -l host
#
# swacl Host Access Control List
#
# For host: ELR1
#
# Date: Tue Aug 26 09:02:14 2008
#

# Object Ownership: User= root
# Group=sys
# Realm=ELR1
#
# default_realm=ELR1
any_other:-r---
You have mail in /var/mail/elr

[Rasheed Tamton]

Hi DnD (a name should be more bettr) ;-)


Your swacl looks ok.

I would recommend to put the hostnames in your name service files, either in /etc/hosts or dns/nis/ldap and make sure that you can resolve the hostnames by pinging from both ends.

You can also try starting the swagentd by the cmd
swagentd -r

rgds.

[Rasheed Tamton]

>Rasheed:You can also try starting the swagentd by the cmd

I meant re-starting the swagentd
/usr/sbin/swagentd -r