make_tape_recovery

[Joe Profaizer]

I'm currently using the command for my ignite tapes:
/opt/ignite/bin/make_tape_recovery -x inc_entire=vg00

I have mirrored systems disks (vg00). What is the downfall if I don't use the "-A" option. Am I not including all files in my ignite process without the "-A" option? If so, what am I not copying?

[Patrick Wallek · Accepted solution]

It talks about this in the make_tape_recovery man page.

Here is the appropriate section from the man page:


Create a system recovery tape with all the files/directories on the disk(s)/volume group(s) containing the files specified by the default essentials file list /opt/ignite/recovery/mnr_essentials or the user defined version of this file, that replaces this file,
/var/opt/ignite/recovery/mnr_essentials.
make_tape_recovery -A
make_tape_recovery -s myserver -A

Create a system recovery tape that includes files from all file systems in the vg00 volume group:
make_tape_recovery -x inc_entire=vg00

make_tape_recovery -s myserver -x inc_entire=vg00


I would NOT recommend using the -A option, rather, I would use the '-x inc_entire=vg00' when using make_tape_recovery. That way you know you will get all files from vg00.

[Jean-Louis Phelix]

Hi,

The -A option is only used to include "essential" files in your archive ( /opt/ignite/recovery/mnr_essentials ), while -x inc_entire=vg00 include whole vg00. In most cases, vg00 contains all essential files (especially if you haven't customized it ...). So your archive is really a good one with your options, while -A option would save a "minimal" archive.

Regards,

Jean-Louis.

[Christopher McCray_1]

No downfall. The command you specified is what you want to grab the entire vg00. The -A option all files directories on the disks/vgs based upon what is in the /opt/ignite/recovery/mnr_essentials file (see man make_tape_recovery). In any case, ignite does not account for mirroring so you would have to redo that in the case of recovering the system.

Hope this helps

Chris

[Bernhard Mueller]

Hi,

then downfall is that there are systems that have an LVM setup which has a non-root volume group which mounts one lvol e.g. under /etc/someapplication_name and another lvol under /someapplication/data_dir

Now the issue is that the default mnr_essential files defines that everything under /etc be included in the recovery archive.
(Which makes sense for a common setup)

However in the above case you would have only a part of this non-root volume group in your archive (the filesytem mounted on /etc/someapplication_name) BUT in the recovery process you would re-create not only the root VG but also this non-root VG on their original disks.

So after recovery you would have to separately restore what was under /someapplication/data_dir because the disks had been "pvcreated" , the lvols had been created but /someapplication/data_dir could not be restored from the recovery image (of course there may be other lvols/filesystems in the non-root volume group which would also be missing)

Regards
Bernhard

[Elif Gius]

Kepp thinking,

If you invoke the command using tha '-A' option it works as follows - if you have e.g. /usr on a different vg (vg01)
than it will also be included in the archive.
Because '/usr' is part of the core, and resides on vg01, the "entire" vg01 will be included in the archive.

If '-A' option is used it will look that make_recovery takes all files/dirs which are in the Core-OS.