ignite command option clarification..

[Ganesan R]

Hi,

Can someone clarify the difference between the options -A and -x inc_entire=vg00 with make_tape_recovery command ?

I got little confused with these options. I understand that both will take the entire VG00.

Am I right? or misunderstand? If I don't want to take entire vg00, which options needs to be given with make_tape_recovery? In this case what are the files/directories will be included in the archive and what are the files/directories will be excluded from the archive?

[Ivan Krastev · Accepted solution]

Yes, you are right. Both -A and -x inc_entire=vg00 will add your boor vg to recovery archive.

With option inc_entire you can add an additional volume groups to the archive.

regards,
ivan

[sujit kumar singh]

Hi

#make_tape_recovery -Av -a /dev/rmt/0mn
and
#make_tape_recovery -v -x inc_entire=vg00 -a /dev/rmt/0mn
and
#make_tape_recovery -Avx inc_entire=vg00

are the same.

-A --- include all the lvols as fully included in the root VG (vg00)

-x inc_entire=vg00 --- include all the lvols in the VG vg00.


perhaps the -A option in the latest version of ignite is only for the sake of backward compatibility and sometime is going to be discontinued.

regards
sujit

[James R. Ferguson]

Hi:

The '-A' option as described in the 'make_tape_recovery' manpages causes a selection of volume groups and/or disks that need to be included in the archive in order to archive the essential files.

I prefer to use the '-x' options like:

# /make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

...where my vg00 consists only of the standard HP-UX logical volumes.

Regards!

...JRF...

[Ganesan R]

Hi,

Thanks to all for your replies..

Ok. If I haven't mentioned -A or -x inc_entire=vg00, What files/directories will be included and excluded from default filesytems root, boot, var, opt, home, usr, tmp.

My question is, Will all the files from these filesystems including application related be backed up or some files/dir will be excluded?

[sujit kumar singh]

Hi


I think ii suugest you to run an ignite backupo on any server and have a look .
right now nit near any servers.
regards
sujit

[T G Manikandan]

Ignite/UX product is used as a tool to recover the volume group vg00.
Eventhough there are options to recover the entire system, it is not recommended as it is not efficient with more tapes and time.

The best would be to just ignite vg00 and use the normal backup for the restoration.

To answer your question:

you cannot predict which files would be included.
When you include the -A option,based on the files that are specified and if found with other VG's the entire VG's would be included.


Based on the files that are specified for inclusion, this option determines which disk(s) and/or volume group(s) contain those specified files, and includes all files from those disk(s) and/or volume group(s) in the archive.

[sujit kumar singh]

Hi Ganeshan,

Also on a server on whicg you might have made a successful Ignite tape/ network backup you can have a look at the Ignite Recovery log at

/var/opt/ignite/recovery/archives/latest
for the tape backup

or


/var/opt/ignite/clients/{0xLLA}/recovery/archives/latest


there as you scroll thru the logs which are descriptive , those files/dirs/LVs which are marked as

0 -- not included
1 -- partially included
2 -- Fully Included.


sorry not near a system right now.

regards
sujit

[Ganesan R]

Thanks again to all,

Actually what I would like to know is that when I run #make_tape_recovery -v -I command,

will it take entire filesystem of root,boot,home,tmp,var,usr,opt? or only essential files and exclude other files/directories like application related?

I remember, somewhere I read that it will take only essential files not all the files/dirs.

[T G Manikandan]

If I am not wrong,

without the -A -x option it includes the whole system.

with -A which includes only the essential files /opt/ignite/recovery/mnr_essentials

with -x it includes the entire VG files.

[Avinash20]

I spent couple of time again in the lab to capture some data for your better understanding.

Please find the Lab tests which includes my comments also
+++++++++ Created the filesystems Layout Similar to your Setup ++++++++++++++
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1540096 315808 1214760 21% /
/dev/vg00/lvol1 1490424 57408 1283968 4% /stand
/dev/vg00/lvol8 4718592 2142560 2557248 46% /var
/dev/vg00/lvol7 4882432 1950072 2909576 40% /usr
/dev/vg00/lvol6 5144576 407760 4699848 8% /tmp
/dev/vg00/lvol5 5636096 3240752 2376696 58% /opt
/dev/vg00/lvol4 4096000 16808 4047328 0% /home
/dev/vg00/oracle 327680 1189 306093 0% /oracle
/dev/nehadg/oracle2
655360 16629 598818 3% /oracle/VBP
/dev/vg00/oracle1 327680 1189 306093 0% /oracle/VBP/102_64


1. Lets try the command which you tried
# make_tape_recovery -Av -p
* Creating local directories for configuration files and archive.
======= 02/22/07 01:33:34 IST Started make_tape_recovery. (Thu Feb 22
01:33:34 IST 2007)
@(#)Ignite-UX Revision C.6.10.97
@(#)ignite/net_recovery (opt) $Revision: 10.834 $ $Date: 2006/06/14
13:47:40 $

* Testing for necessary pax patch.
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
2 v /dev/nehadg 0x03 /dev/dsk/c0t0d0
/dev/nehadg/rajlv
/dev/nehadg/lvol1
/dev/nehadg/oracle2 /oracle/VBP 2
2 v /dev/vg00 0x00 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /home 2
/dev/vg00/lvol5 /opt 2
/dev/vg00/lvol6 /tmp 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
/dev/vg00/oracle /oracle 2
/dev/vg00/oracle1 /oracle/VBP/102_64 2

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2007-02-22,01:33/system_cfg nehadg vg00


++++++++ Comments by me +++++++++++
If we take backup like the above command, we are taking complete backup of vg00 and nehadg.
If you restore this ignite backup, it will restore all the data in vg00 and nehadg from the
ignite tape. So you will loose the data if anything modified in agenda volumes
+++++++++++++++++++++++++++++++++++

[Avinash20]

2. Lets take including only vg00 with -x inc_entire=vg00

# make_tape_recovery v -x inc_entire=vg00 -p
* Creating local directories for configuration files and archive.
======= 02/22/07 01:34:00 IST Started make_tape_recovery. (Thu Feb 22
01:34:00 IST 2007)
@(#)Ignite-UX Revision C.6.10.97
@(#)ignite/net_recovery (opt) $Revision: 10.834 $ $Date: 2006/06/14
13:47:40 $

* Testing for necessary pax patch.
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
1 v /dev/nehadg 0x03 /dev/dsk/c0t0d0
/dev/nehadg/rajlv
/dev/nehadg/lvol1
/dev/nehadg/oracle2 /oracle/VBP 1
2 v /dev/vg00 0x00 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /home 2
/dev/vg00/lvol5 /opt 2
/dev/vg00/lvol6 /tmp 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
/dev/vg00/oracle /oracle 2
/dev/vg00/oracle1 /oracle/VBP/102_64 2

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
WARNING: The volume group /dev/nehadg will be only partially included in the
System Recovery Archive. This means that not all files and
directories on this volume group will be restored when the archive is
installed. This message can be suppressed using the "-P s" option for
make_tape_recovery. See make_tape_recovery(1M) for more details.

* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2007-02-22,01:34/system_cfg nehadg vg00


++++++++ Comments by me +++++++++++
If you take Ignite backup with the command in step 2, we are taking the entire vg00 backup
+ a partial data from nehadg from this mount point (/oracle/VBP). Actually we take backup
of only mountpoints from that directory no actual data

If you restore this ignite image, during the restore we do pvcreate/vgcreate/lvcreate/mkfs
on nehadg also. See this warning in man page of make_tape_recovery
....
Disks Will be Reformatted
If any file from a disk or volume group is included in the recovery
archive, that disk (or all disks in the volume group) will be
reformatted during the recovery, and only the files included will be
recovered. Any files that were not included in the archive, will
have to be restored from normal backups.
.....

[Avinash20]

***********
I faced this situation once and forced to restore the data from backup. Often we get cases
once customer lost the data. This time I want to be more proactive since I know what problems
you are going to face.
See this Ignite News Letter (Point 3)
ignite_ux_news_45.htm
***********


In the current setup you can take the backup with any of the below Steps
Step 3. # make_tape_recovery -v -x inc_entire=vg00 -x exclude=/oracle/VBP -p
* Creating local directories for configuration files and archive.

======= 02/22/07 01:34:29 IST Started make_tape_recovery. (Thu Feb 22
01:34:29 IST 2007)
@(#)Ignite-UX Revision C.6.10.97
@(#)ignite/net_recovery (opt) $Revision: 10.834 $ $Date: 2006/06/14
13:47:40 $

* Testing for necessary pax patch.
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
0 v /dev/nehadg 0x03 /dev/dsk/c0t0d0
/dev/nehadg/rajlv
/dev/nehadg/lvol1
/dev/nehadg/oracle2 /oracle/VBP 0
1 v /dev/vg00 0x00 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /home 2
/dev/vg00/lvol5 /opt 2
/dev/vg00/lvol6 /tmp 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
/dev/vg00/oracle /oracle 2
/dev/vg00/oracle1 /oracle/VBP/102_64 0

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
WARNING: The volume group /dev/vg00 will be only partially included in the
System Recovery Archive. This means that not all files and
directories on this volume group will be restored when the archive is
installed. This message can be suppressed using the "-P s" option for
make_tape_recovery. See make_tape_recovery(1M) for more details.

* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2007-02-22,01:34/system_cfg vg00
* Backing Up Volume Group /dev/nehadg
* /usr/sbin/vgcfgbackup /dev/nehadg
* Creating Map Files for Volume Group /dev/nehadg
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/nehadg.mapfile /dev/nehadg

* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00


+++++ Comments by me++++++++++++++
In this backup you won't touch anything from nehadg so there won't be any issues with restore.
If /oracle filesystem modified consistently, then you need to restore /oracle and /oracle/VBP/102_64
filesystems after the ignite restore.

If there won't be any modifications to /oracle filesystems then you can use this option
+++++++++++++++++++++++++++++++++++

[Avinash20]

Step 4. Take only OS filesystems backup
# make_tape_recovery -v -x inc_entire=vg00 -x exclude=/oracle -p

* Creating local directories for configuration files and archive.

======= 02/22/07 01:35:12 IST Started make_tape_recovery. (Thu Feb 22
01:35:12 IST 2007)
@(#)Ignite-UX Revision C.6.10.97
@(#)ignite/net_recovery (opt) $Revision: 10.834 $ $Date: 2006/06/14
13:47:40 $

* Testing for necessary pax patch.
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
0 v /dev/nehadg 0x03 /dev/dsk/c0t0d0
/dev/nehadg/rajlv
/dev/nehadg/lvol1
/dev/nehadg/oracle2 /oracle/VBP 0
1 v /dev/vg00 0x00 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /home 2
/dev/vg00/lvol5 /opt 2
/dev/vg00/lvol6 /tmp 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
/dev/vg00/oracle /oracle 0
/dev/vg00/oracle1 /oracle/VBP/102_64 0

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
WARNING: The volume group /dev/vg00 will be only partially included in the
System Recovery Archive. This means that not all files and
directories on this volume group will be restored when the archive is
installed. This message can be suppressed using the "-P s" option for
make_tape_recovery. See make_tape_recovery(1M) for more details.

* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2007-02-22,01:35/system_cfg vg00
* Backing Up Volume Group /dev/nehadg
* /usr/sbin/vgcfgbackup /dev/nehadg
* Creating Map Files for Volume Group /dev/nehadg
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/nehadg.mapfile /dev/nehadg

* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/lbin/make_arch_config -c
/var/opt/ignite/recovery/2007-02-22,01:35/archive_cfg -g
/var/opt/ignite/recovery/2007-02-22,01:35/flist -n 2007-02-22,01:35 -r
pa -b 64 -d Recovery\ Archive -t 1 -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews


++++ Comments by me ++++++++++++++++
In this case you only take backup of OS filesystems. After the ignite restore customer need to
restore all other non-os filesystems from their regular backups
++++++++++++++++++++++++++++++++++++

[Avinash20]

Note: Ignite backup is only meant for OS Backup/Recovery. For Non-OS filesystems customer need
to take backup with either native OS Backup utitilies(like tar,cpio,fbackup) or other backup
solutions.


I would strongly suggest not to use this type of configurations. Its because if customer
takes ignite backup without knowing all these details with either Step 1 or Step 2 they end
up in loosing their oracle data after the ignite restore.


Instead would suggest the following type of configuration
++
Don't mount any logical volumes of vg00 under some other volume groups mount points
In my case /dev/vg00/lvol12(its mount point /oracle/VBP/102_64) will under
/oracle/VBP(whose logical volume belongs to vg02 /dev/vg02/lvol2)
++

You can either do the following options
Mount the /dev/vg00/lvol12 to Some other directory
or
Create /oralce/VBP/102_64 filesystem under /dev/vg02

Note: If you are taking the complete vg00 backup, after the ignite restore you need to restore the NON-OS data from the backup if those files are modified after customer taken the ignite backup