Ignite UX

[Carla Breuer]

I am going to run a make_tape_recovery command for the first time in our new machine. The macine is an HP L1000 rp5400 running HPUX 11.0.
The machine is configured with all lvm's on vg00. What is the best options to use to get only the core elements on the ignite tape??? Points to all!

Thanx,

Carla

[James R. Ferguson]

Hi Carla:

To archive the contents of vg00 do:

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

The '-I' option will cause the recovery to be interactive should you ever boot from the tape. This will obviate the need to "pounce" on the process during the initial 10-seconds to otherwise interact with it.

Do a man 'make_tape_recovery' for more information.

Regards!

...JRF...

[Jim Mallett]

This will create an Ignite tape of just vg00, assuming your DDS drive is /dev/rmt/0mn :

make_tape_recovery -x inc_entire=vg00

If you're running OmniBack or any other databases you'll want to bring them down while this is running.

man make_tape_recovery for details.

Good luck... Jim

[John Meissner]

make_tape_recovery -Av -x inc_entire vg00 -x inc_entire vg01

you can pass as many -x inc_entire's as you want in order to specify all the volume groups you wish to backup.

[John Meissner]

(i forgot to put "=" (equal signs) in my statement....

-x inc_entire=vg00 etc......

[Dario_1]

Hi Carla:

You can try this:

make_tape_recovery -Av -x inc_entire=vg00

The -x option will allow you to include different vg's.

Regards,

Dario

[Carla Breuer]

I want to back this up to a DLT drive. Is this supported?

[Bill Douglass]

Yes, the make_tape_recovery man page states that all DS and DLT drives are supported.

[Carla Breuer]

Jim, we are running a Home grown Financial system that is a UNIVERSE/PICK database in both machines. We do not have to take this down in our production system, an HP 9000 H50 running HPUX 10.2 using make_recovery command. We have never had any problems with me running this during production. The test box is not in production yet, but we want to go live before month end.Is make_tape_recovery different in this manner? Will I have to run make_tape_recovery with the users off the system? Points coming very soon.

Thanx,

Carla

[Carla Breuer]

Just one more thing I don't think I made clear. The vendor that configured the new machine put all my application data and logical volumes in vg00. vg00 is all there is. No vg01 or vg##. My old machine is not configured like this. On vg00 are lvol's /, /stand, /var, /uv, /usr, /tmp, /opt, /home. None of the Application data resided on vg00. All other lvols were on vg01. Is make_tape_recovery going to try to back up my application data too or is there a way to only back up the lvols I have listed here?

Thanx,

Carla

[James R. Ferguson]

Hi (again) Carla:

You do not need to do anything special to run 'make_tape_recovery' to create a recoverable image of vg00. The few files that should be actively changing while Ignite runs should be log (information-only) files, assuming that you are not archiving non-standard files and directories. Remember, the copy mechanism used by Ignite is nothing more than 'pax' (tar's cousin) and as such has no "intelligence" or like 'fbackup'.

At most you may note some warning messages from the Ignite process describing non-existent files. This is often seen. These are files that were present when Ignite first created a list of files to archive, but were removed before Ignite's 'pax' copy could process them.

Regards!

...JRF...

[James R. Ferguson · Accepted solution]

Hi (again) Carla:

I just saw your additional post. A server with one volume group (vg00) containing appliation data is a server I would rebuild immediately!

From a recovery, a backup, and a performance perspective, I would most certainly want a segregation of operating system and application.

In the interim, you can use the *exclude* option to exclude the application data from your recovery. Add:

-x exclude=file|dir

...to your Ignite 'make_tape_recovery' command.

Regards!

...JRF...

[Dario_1]

Carla:

Select the volume you want to include in your backup with the -x include=volumegroup then as Pete mentioned, use -x exclude=directory or file to exclude what you don't want to include.

Regards,

Dario

[Jim Mallett]

Carla,

James has it covered up above... my comment regarding the database issue was because I was thinking in terms of my environment. My OmniBack database exists on VG00 and needs to be down when doing a make_tape_recovery.
I've done make_tape_recovery's while users are on the system and have not had any issues.

Jim

[Dario_1]

Correction. Was JAMES who replied not Pete. I got confused with the salad. Sorry James.

Dario

[Carla Breuer]

Thank you James, I have been screaming that since the box was delivered. Sometimes all you need is somebody to concur outside the office. Finally, the powers that be are going to make the vendor fix this.

[Carla Breuer]

Ok, so if I wanted to exclude more than one directory for example /ACCT and /PAYROLL how would I list these in the command. Would I separate the directories with a comma /ACCT, /PAYROLL or just spaces? Apparently we only have to physical disks and were are using mirroring therefore we were told we could only have one volume group. Does this sound right?

Thanx,

Carla

[James R. Ferguson]

Hi Carla:

To exclude multiple directories, specify multiple '-x exclude file|dir' arguments.

While mirroring is implemented at the *logical volume* level, not a physical disk level, to be effective, you don't want mirror copies to reside on the same physical volumes. The 'strict' allocation policy established when you 'lvcreate' a logical volume controls the enforcement of this. Hence, to mirror the logical volumes of vg00, you need *two* physical disks. I can only guess that you don't have enough disks to mirror both vg00 and your application data. Disks are cheap compared to data loss and/or lost performance.

Regards!

...JRF...