make_tape_recovery.

[fizan]

team,

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 3145728 707336 2421584 23% /
/dev/vg00/lvol1 819200 189384 624928 23% /stand
/dev/vg00/lvol9 4399104 3037200 1351296 69% /usr
/dev/vg00/lvol7 4710400 3918872 785392 83% /var
/dev/vg00/lvol6 1048576 703040 342848 67% /tmp
/dev/vg00/oracle_lv
4202496 3153296 983658 76% /oracle
/dev/vg00/lvol8 3538944 2610216 921480 74% /opt
/dev/vg00/lvol4 2097152 770400 1326744 37% /home

if i run a make_tape_recover for a system-state backup whether it will include all the lvol in the vg00?
how much space will it require to have vg00 backup? using make_tape_recovery.
whther it will take an image copy or it will work like fbackup?

[R.K. #]

Hi Fizan,

>>whether it will include all the lvol in the vg00?
Depends what option do you give. Attached is man page of make_tape_recovery

>>how much space will it require to have vg00 backup?
From bdf you can see the space occupied by VG00 and the option you give while taking ignite backup.

>>whther it will take an image copy or it will work like fbackup?
Not fbackup....It will take a backup which you can view using tar.

[R.K. #]

Hi...

You can use following command:
# /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -x inc_entire=vg00

-a --> tape drive address
-I --> Interactive at recovery
-v --> verbose
-x inc_entire --> option to include full

Note:
When the -I (uppercase i) option is speciï¬ ed, booting from the tape will always present the interac-
tive menus. This option is useful when making conï¬ guration changes during the recov-
ery, and may also help prevent an accidental system recovery from a recovery tape.

[fizan]

# diskinfo /dev/dsk/c2t1d0
diskinfo: Character device required
# diskinfo /dev/rdsk/c2t1d0
SCSI describe of /dev/rdsk/c2t1d0:
vendor: HP 36.4G
product id: MAU3036NC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512
# diskinfo /dev/rdsk/c2t0d0
SCSI describe of /dev/rdsk/c2t0d0:
vendor: HP 36.4G
product id: MAU3036NC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512
--------------------------------------------
these two are the disks in vg00 of capacity 35GB, and mirrored between two disks, so how much space will it take for run a make_tape_recovery.

[R.K. #]

Hi Again,

You can check space required space roughly by two ways:

FIRST:
From bdf see the "used kb" for all lvols in vg00 and add them.
Your output says approx 12 GB (please verify)

SECOND:
From:
#vgdisplay vg00

Size occupied by VG00 = (PE_size)*(Alloc PE) Mb
This will be the size of VG00

>> disks in vg00 of capacity 35GB
Disks can be very large in capacity...but the data in them may be very small in size. So from disk size we cannot guess the data size.


Regds..

[fizan]

Rk,

now to consider in vg00 all the lv are mirrored, so how while takin make_tape it uses 12Gb or 6gb only sir?

[R.K. #]

Hi Fizan,

Do NOT relate between mirroring and backup.

We take backup of VG or LV or any directory or any file and NOT disks on wich they are present.

So if total size of your VG00 is 12 GB, that means data size is 12GB and backup will done for this 12 GB

Size of VG00 = 12 gb
Size of mirror of VG00 = 12 gb

Backup to be taken = VG00 = 12 gb
(and NOT 24 gb)

Regds..

[Raj D.]

Fizan,
IF you have vg00 space 12 GB , make_tape_recovery will backed up 12GB.
( It also depend what type of tape you will be using)

To Check Space:
# vgdisplay vg00 | grep -i -e "Free PE" -e "PE Size"
# Multiply both to get vg00 space.
However used space would be less than that and can be found from bdf.

To take backup you can use:

# /opt/ignite/bin/make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn #[ Where /dev/rmt/0mn is tape drive ]


Hth,
Raj.

[Viveki]

>>>> if i run a make_tape_recover for a system-state backup whether it will include all the lvol in the vg00?

You need to use the below command to take backup of full root disk volume group

/opt/ignite/bin/make_tape_recovery -Av

>>>how much space will it require to have vg00 backup?

It depends purely on the data in the vg.

>>> whther it will take an image copy or it will work like fbackup?

It is not like an fbackup. You need to boot from the tape to recover the system.

To extract/view a single file from the recovery archive:

# mt -f /dev/rmt/0mn rew
# mt -t /dev/rmt/0mn fsf 1
# tar -xvf /dev/rmt/0m filename

The above example is for PARISC systems. For Itanium systems,

# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 22
# tar -tvf /dev/rmt/0mn

[Steven E. Protter]

Shalom,

make_tape_recovery stores temp files in /var and writes directly to tape.

It doesn't care how much space is needed and will prompt for a second tape if the first one is full.

It is better though to include as shown above the option to only include vg00.

Problem though is oracle_lv

You made it part of vg00.

Ignite can't get clean oracle database backups unless oracle is down at time of backup.

So either down the oracle database or exclude it from the archive.

SEP