Operating System - HP-UX
1837650 Members
2896 Online
110117 Solutions
New Discussion

High level view at disk slicing

 
SOLVED
Go to solution
Ratzie
Super Advisor

High level view at disk slicing

I am very new to the world of HP having dabbled in SUN.
I have been tasked with building a backup server that closely resembles the production server as possible.
Heres the problem...
total different hardware platform, I will have 4 76GB drives as compared to the 18 15GB drives on the production server, will not have mirroring, and it has a database on it.

So where do I start?
I am attatching a snap shot of the bdf command

But where I go from there is a nightmare!
4 REPLIES 4
Joshua Scott
Honored Contributor

Re: High level view at disk slicing

Post the specs of the two systems (model number, external devices if applicable, model numbers of the external storage enclosures).

also, i didn't see the attachment, I don't think it posted.
What are the chances...
John Poff
Honored Contributor

Re: High level view at disk slicing

Hi,

Your bdf attachment didn't make it.

The first question is, how much disk space does your database take up on the production box?

You could use one disk in the backup box for your root volume group, vg00, and the other three for one or more volume groups for your database. The trick will be to see if 3 x 76Gb is enough space.

If so, you can use Ignite-UX to create a system backup of the production box and use that to clone the backup box, putting your vg00 on one of the 76 Gb disks. Next you can do some LVM work to use the other three disks for your database, and then copy or restore the database information over to the backup box.

If you don't have enough disk space to use one of the four 76 Gb disks for vg00, you might need to see if you can get another disk in the box. What model is your backup system?

Don't worry. It's not a nightmare. There are plenty of us out here who have done this before. Just think of all the fun new stuff you are about to learn!

JP
Ratzie
Super Advisor

Re: High level view at disk slicing

Here is the bdf
Let me know if you need anything else

It is HP B.11.00 U 9000/800
Hein van den Heuvel
Honored Contributor
Solution

Re: High level view at disk slicing


It looks like your volume groups mapped one-on-one to physical device.
It looks likes, judging by the mountpoint names, that each disk - vg had a single DB, with 5 active DB's?
Or is that 1 db ("acdb") with 5 directory with database files?

I'd suggest you start with 1 volume on 1 disk with system and oracle AND backup volumes.
You do still need the backups right? That would fit.
I would put the other three disks STRIPED into a second volume group. Personally I'd stripe at 1MB, 4MB or more, not at the 64 KB you often see. All you want is a chance to spread the disk IO a little over those 3 disks.

With a little trimming on those dbbkup lvols this would requires 40GB on the vg00 and 78GB on the VG01 untrimmed or also some 40GB if you can trim the lvols to be more that 60%, less than 90% full.

Those 'lvolX' names are just names.
You can change them at will, as long as you adapt the mount command to match.

To be able to back-map in you mind between production and this backup system you might want to have the new names reflect the like changing /vg01/lvol1 into vg00/lvol10 or even vg00/lvol_01_1.
And change /vgdb2/lvol1 into /vgdb/lvol_db2_1 or a simple /vg01/db2.

Attached a spreadsheet with your mountpoints re-arranged.

hth,
Hein.