About make_recovery

[WERWERS]

I have installed ignite, i want to create a recovery tape, My tape driver is DDS4,(24GB /tape) ,but my VG00 is so large,about 50GB !
1)Can I use make_recovery to backup the VG00? and will the system notice me to change another tape?
2)Must I run it in single user mode?

[Rajeev Shukla]

Yes your system will prompt you to change the tape.
also its recomended to run in single user mode but not necessary.

Rajeev

[WERWERS]

In single user mode, shall i mount all system?

[V.Tamilvanan]

Hi,
Yes. The system will notice you to change the media.
It is not mandatory to run in single user mode. You can run on multi-user also.

My one cent suggestion : When u take a backup of vg00 about 50 GB on DDS4 it is definitely going to take a very long time and your recovery time will very very high. So why don't you exclude the directories or FS which are not part of OS hwen u take ignit backup. You can use other backup utility like fbackup,tar,DP,cpio,dump for taking other FS.
See the man pages of make_tape_recovery.

Just a thought.

HTH

[Patrick Wallek]

I would use make_tape_recovery, rather than make_recovery as make_recovery will eventually go away.

Use the following command:

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

In order to be prompted you will have to run the command interacitvely from either the console or some other session.

[Patrick Wallek]

If you do it in single-user mode, yes you definitely need to mount all the filesystems.

[Con O'Kelly]

Hi

I wouldn't be inclined to backup 50GB with ignite. If you have put additional Logical Volumes in VG00 rather than just the normal OS ones then you can exclude some of them from the ignite backup as follows:

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

You can use multiple "-x exclude=" parameters.
You could also use "-i include=" instead of the -x options.

Cheers
Con

[WERWERS]

Can you tell me how long it will spend in backuping about 50GB on DDS4? And can you tell me how to backup VG00 by use make_tape_recovery? Thank you in advance.

# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 204800 43887 151011 23% /
/dev/vg00/lvol1 299157 31583 237658 12% /stand
/dev/vg00/lvol8 2609152 177688 2279809 7% /var
/dev/vg00/lvol7 1032192 722650 290215 71% /usr
/dev/vg01/lvol1 35553280 24523008 10948624 69% /u03
/dev/vg00/lvol10 26755072 24008736 2703476 90% /u02
/dev/vg00/lvol9 2457600 1212296 1167510 51% /u01
/dev/vg00/lvol4 409600 4158 380189 1% /tmp
/dev/vg100/lvol30 49152000 13819800 35056168 28% /oradata
/dev/vg00/lvol6 647168 549954 91178 86% /opt
/dev/vg00/lvol5 262144 87151 164112 35% /home
/dev/vg00/lvo40 16547840 15280074 1228212 93% /backuporadata

[twang]

1. We daily backup oracle data 23 GB using DDS4 tape drive + DDS3 tape + fbackup: ~55 mins
2. You may use following command to create ignite tape for whole vg00 as:
# make_tape_recovery -A

[Steven E. Protter]

Okay.

1) Don't run the Ignite backup in single user mode.

2) Don't extend the backup to vg100 because the backup of the oracle databases will be useless.

3) If the oracle datafiles exceed 2 Gig they will be excluded from the archive unless you install the pax patch PHCO_26422

4) If you install the pax patch you might not be able to recover your system becasue pax_iux which is used to unpack images in Ignite doesn't hadle files bigger than 2 Gig. It just hangs and doesn't let you know why.

5)I would not use Ignite to create a multi-tape backup set. Its designed to reocver the boot volume not the data.

Alternate strategy:

Use the Ignite command in prior posts.
Shut the database and use fbackup to back up vg100 and the rest of the system.

Then recovery is decoupled and two step.

You boot off the Ignite tape,
It lays down the empty volume groups, then you restore from fbackup.

You only need to do the make_tape_recovery when you change the system, ie install patches, change vg config. This is probably less fequent than the need to backup the oracle data.

By decoupling you keep it to one tape and have a more flexible schedule. fbackup does prompt and handle multip tape backups well unless you run it in cron.

SEP

[Con O'Kelly]

Hi Kevin

My thoughts would be to exclude your /u01 /u02 & /backuporadata filesystems from the ignite the backup as I'm assuming they're oracle filesystems.
Use the commands given above to exclude them ie -x exlcude=/u01 etc.

Complete command
#make_tape_recovery -a /dev/rmt/0mn -x inc_entire=vg00 -x exclude=/u01 -x exclude=/u02 -x exclude=/backuporadata -I -v

Backup the rest of system using backup utilities such as fbackup, OmniBack etc.
Remember with Oracle you have to ensure it is shutdown prior to backup or look at hot backups.

Cheers
Con

[Con O'Kelly]

One point I should have emphasised is that its advisable to use a "-I (capital i)" option in the make_tape_recovery as this will allow you to interact with the ignite recovery should you need to. (i.e you may wish to resize Filesystems etc)

Cheers
Con

[Steven E. Protter]

Con,

You can interact with an Ignite recovery whether or not you use the option.

There is a prompt after booting from the tape that lets you make modifications. If something is out of whack on recovery, say disks have been radically re-arranged you'll end up at that prompt anyway.

Good points in the thread though.

SEP

[yogesh_4]

Hi,
1. make_tape_recovery command will ask u to insert the second tape.
2. To give this command u need not to go to the single user mode.
3. Your root volume group is 50GB. With #make_tape_recovery -i option you can select which logical volume to be inculded in back , so I feel you can just include system related lvols.

[Con O'Kelly]

Thanks Steve. Must admit I'd always been operating under the assumption that you had to use the -I option for an interactive recovery.

Cheers
Con

[WERWERS]

Thank you everyone.
I shall do as follow,
1)#make_tape_recovery -a /dev/rmt/0mn -x inc_entire=vg00 -x exclude=/u01 -x exclude=/u02 -x exclude=/backuporadata -I -v

2)fbackup u01,u02,backuporadata
If one data file is large than 2GB,can I use fbackup?

[Helen French]

For the last question:

Yes, fbackup can be used to copy files which has sizes more than 2GB. I would consider moving to a more stable backup product - OB, Veritas etc. Also, make sure that you have all the latest patches installed.

[WERWERS]

New problem!!!(I can not use the tape.)
# ioscan -funC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/0/1/0.6.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/0mnb /dev/rmt/c0t6d0BESTn /dev/rmt/c0t6d0DDSb
/dev/rmt/0mb /dev/rmt/c0t6d0BEST /dev/rmt/c0t6d0BESTnb /dev/rmt/c0t6d0DDSn
/dev/rmt/0mn /dev/rmt/c0t6d0BESTb /dev/rmt/c0t6d0DDS /dev/rmt/c0t6d0DDSnb
# ./make_tape_recovery
* Creating local directories for configuration files and archive.

======= 06/13/03 14:11:03 EAT Started ./make_tape_recovery. (Fri Jun 13
14:11:03 EAT 2003)
@(#) Ignite-UX Revision B.3.4.115
@(#) net_recovery (opt) $Revision: 10.547 $

* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
ERROR: Failed to open tape device /dev/rmt/0mn:No such device or address
(errno = 6).
ERROR: Check tape device failed.

======= 06/13/03 14:11:09 EAT make_tape_recovery completed unsuccessfully

[Steven E. Protter]

Hi kevin,

Enjoyed working on your issue.

as noted fbackup does files bigger than 2 Gig. As to whether its an Enterprise tool, I leave that up the management. If you have to use it, it WILL work.

Please take a look at this.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x022718276953d61190040090279cd0f9,00.html

Thanks.

SEP

[WERWERS]

New problem!!!(I can not use the tape.)

[Michael Tully]

Let's check that the drive is working correctly.

Make sure that the tapes stays loaded, compatible media to your drive.

Run a couple of fuctional tests.
# mt -t /dev/rmt/0m rew
# mt -t /dev/rmt/0m offl

if okay, try a simple tar archive:

# tar cvf dev/rmt/0m /stand/vmunix

Are you using a new tape for the make_recovery ?

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"

[WERWERS]

Thank you,Michael Tully,
I shall try it later.

[WERWERS]

./make_tape_recovery -a /dev/rmt/0mn -x inc_entire=vg00 -x exclude=/u01 -x exclude=/u02 -x exclude=/backuporadata -I -v

* Creating local directories for configuration files and archive.

======= 06/13/03 19:13:56 EAT Started ./make_tape_recovery. (Fri Jun 13
19:13:56 EAT 2003)
@(#) Ignite-UX Revision B.3.4.115
@(#) net_recovery (opt) $Revision: 10.547 $

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

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

* Number of Archives to Save = 2

NOTE: vgdisplay -v unsuccessful

In? dsk/vg name minor# Associated disks/mountpoints
0 v /dev/vg100 0x04 /dev/dsk/c0t10d0 /dev/dsk/c0t12d0 /dev/dsk/c0t14d0
/dev/vg100/lvol30 /oradata 0
1 v /dev/vg00 0x00 /dev/dsk/c1t2d0 /dev/dsk/c2t2d0 /dev/dsk/c0t8d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /tmp 2
/dev/vg00/lvol5 /home 2
/dev/vg00/lvol6 /opt 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
/dev/vg00/lvol9 /u01 0
/dev/vg00/lvol10 /u02 0
/dev/vg00/lvo40 /backuporadata 0
0 v /dev/vg01 0x01 /dev/dsk/c1t0d0 /dev/dsk/c2t0d0
/dev/vg01/lvol1 /u03 0
0 v /dev/vg11 0x02 /dev/dsk/c0t9d0 /dev/dsk/c0t11d0 /dev/dsk/c0t13d0 /dev/dsk/c0t15d0

** 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
NOTE: vgdisplay -v unsuccessful
* 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/2003-06-13,19:13/system_cfg vg00
ERROR: "/var/opt/ignite/recovery/2003-06-13,19:13/system_cfg", line 232:
Illegal character: "e"
ERROR: "/var/opt/ignite/recovery/2003-06-13,19:13/system_cfg", line 232:
syntax error
ERROR: Problems were encountered while parsing config file:
"/var/opt/ignite/recovery/2003-06-13,19:13/system_cfg".
instl_adm: Config file: "/var/opt/ignite/recovery/2003-06-13,19:13/system_cfg" cannot be parsed.
ERROR: System error, /opt/ignite/bin/instl_adm failed checking
/var/opt/ignite/recovery/2003-06-13,19:13/system_cfg

======= 06/13/03 19:14:10 EAT make_tape_recovery completed unsuccessfully
#


Help me!!!!

[WERWERS]

Why did I run make_tape_recovery??
Who can help me?
Thank you in advance.

[Michael Tully]

The key to your current problem is the 'vgdisplay -v unsuccessful' message. Please run 'vgdisplay -v' from the command line and see what it does. Post any messages back here.

Also are you running the 'make_tape_recovery' whilst all filesystems are mounted or are you in single-user mode?

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"