make_tape_recovery -A

[Raymond Cushing]

In the forum I have seen many examples of how to use make_tape_recovery. Some use the -A option and some do not. I don't have a clear understanding of what it really does.
Why would I want to use it?
Why would I want to omit it?
Is there any kind of general recommendation or consensus of when to use it?

[Jeff Schussele]

Hi Raymond,

You only use -A when you want to backup only the "default essentials" files defined in /opt/ignite/recovery/mnr_essentials - either the default out of the box or that file created or modified by you. Creates a smaller tape, but would require some SA work post-restore to fill the gaps not backed up

Normally I just use
make_tape_recovery -Ivx inc_entire=vg00
assuming my tape drive is /dev/rmt/0mn

HTH,
Jeff

[Sundar_7]

If you dont use -A option with make_tape_recovery only minimal set of files are include in the recovery tape.

With -A option, entire VG00 is included. If /usr file system is not part of VG00, then the volume group the /usr is on will also be included in the archive.

I would recommend -A option with any recovery tape.

Following are the files included in the tape if -A option is not specified

/.profile, /.rhosts,
/dev, /etc, /sbin,

/usr/bin, /usr/sbin,
/usr/lib, /usr/obam,
/usr/sam, /usr/share,
/usr/ccs, /usr/conf,
/usr/lbin, /usr/contrib,
/usr/local, /usr/newconfig

/var/adm/sw/security, /var/opt/ignite/local/manifest,
/var/adm/sw/products, /var/adm/sw/save,
/var/adm/sw/sessions/swconfig.last,
/var/adm/sw/sessions/swmodify.last,
/var/adm/sw/sessions/swlist.last,
/var/adm/sw/swconfig.log,
/var/adm/sw/getdate.templ,
/var/adm/sw/defaults.patchfilters,
/var/adm/sw/ui/preferences, /var/adm/sw/targets,
/var/adm/sw/software, /var/adm/sbtab,
/var/opt/ignite/recovery,
/var/adm/cron, /var/spool/cron,
/opt/ignite/bin/print_manifest,
/opt/ignite/share/man/man1m.Z/print_manifest.1m,
/opt/upgrade, /opt/dce

[Raymond Cushing]

What happens if I use both the -A option and -x inc_entire=vg00 ?

[Jeff Schussele]

Hi,

You'd get all of vg00 plus any of the essentials files that happened to reside outside of vg00.

Rgds,
Jeff

[Sundar_7]

The only disadvantage I see in using inc_entire=vg00 instead of -A option is that if your /usr is outside of vg00 (say in vg01) then it wont be included in the recovery tape.

The end result of -A and inc_entire will be the same except in cases where you have /usr in a non-root vg.

If your /usr is in root vg, then -A and inc_entire yeilds the same result.

[Raymond Cushing]

So as long as I'm not foolish enough to move essential files outside of vg00, I don't need -A as long as I use -x inc_entire=vg00. But there wouldn't be any real harm?

Thanks. That's the information I'm looking for.

[Seth Parker]

I looking to clarify what I'm reading here.

1. Jeff's response seems to state that the -A *only* includes the default files and nothing else.

2. Sundar's response is the opposite, that only if you don't use the -A do you get the default files.

I've always used -A for my backups and the man page has the following in the examples section:

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_essential

make_tape_recovery -A

make_tape_recovery -s myserver -A

***********************

This seems to agree with Sundar's explanation (and what I always thought), but it's easy to misunderstand technical docs at times. Comments?

Regards,
Seth

[Binubaby]

Hi,

#make_tape_recovery includes the following
-Boot image
-LVM configurationinformation for vg00
-Critical files and Directories in vg00

#make_tape_recovery -A option - includes
All of the file and directories of vg00 (root volume group)in the archive

regards

Binu