Sponsored Content
Operating Systems Linux Red Hat How to Migrate from Single Disk to Many? (RHEL 4.6) Post 302363346 by home4ktt on Tuesday 20th of October 2009 05:22:08 AM
Old 10-20-2009
Lightbulb How to Migrate from Single Disk to Many? (RHEL 4.6)

I have a Red Hat Enterprise 4.6 virtual server built on 1 virtual disk running Oracle Applications on VMware ESX 3.5; the performance of the virtual server is not good because of IO bottlenecks. The ESX server is reporting minimal load, it's the virtual server which is struggling with disk IO because everything is on the one virtual disk.

I can create almost any number of virtual disks to spread the load across but I don't know what the best number and arrangement of disks would be or how to migrate the existing system off the original disk (which is too big and I plan to trash) and onto the new disk arrangement.

I have found out how to move the swap space onto a new disk using 'parted' and 'mkswap'. I tried it on a test system; I don't want to touch the live system until I am very clear about what I am going to do.

I was thinking about having a single new disk with three partitions for "/boot" (100MB), swap space (2GB) and a data backup area (xxMB). And then three (or more?) disks in stripe formation (using LVM) for performance (no fault tolerance required as the virtual disks would be on a RAID5 SAN) to put the main application on with another three-disk stripe for the Oracle database.

Unless I am forced into it, I don't want to create any additional servers to spread the load across. I just want to get better IO performance from the single server that I already have.

Any suggestions regarding the plan?
Remember I can create almost any disk arrangement I need (which is nice).
So what's going to give me the best performance?

And how do I actually migrate everything off the original disk?

Thanks for your suggestions and help.
 

8 More Discussions You Might Find Interesting

1. Solaris

Migrate VxVM boot disks to higher capacity disk

Hi, Im getting a downtime of 4 hrs to do porting of bootdisks. Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage. We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies

2. Linux

RHEL 3 is not supporting SCASI Disk

Hi guys I am having some SCASI Driver issue while installing the RHEL 3 on SunFire X4200 series Server so can anyone help me out as how to get rid off from this problem. (1 Reply)
Discussion started by: daya.pandit
1 Replies

3. Red Hat

RHEL 3 is not supporting SCASI disk

Hi guys I am having some SCASI Driver issue while installing the RHEL 3 on SunFire X4200 series Server so can anyone help me out as how to get rid off from this problem. (2 Replies)
Discussion started by: daya.pandit
2 Replies

4. AIX

disk space shortage, how to migrate to LVM?

Hello I'm working on AIX 6.1. I inherited something I do not know and now I need to bring it into the line. # df -m Filesystem MB blocks Free %Used Mounted on /dev/hd4 | 256.00 | 87.09 | 66% / /dev/hd2 | 4608.00 | 82.45 | 99%... (11 Replies)
Discussion started by: michalwu
11 Replies

5. Red Hat

Does RHEL 5 provide a command to collect RHEL system log in single compress file?

Hi, I heard a command that can collect all RHEL 5 log in a single compress file before I forget. Does any body know...What the command is ? Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies

6. Red Hat

Installation RHEL in External hard disk.

Hi all. Can i install RHEl5 in a external hard disk, work on lenovo T60 laptop. Plz reply me. Tell me the process. (2 Replies)
Discussion started by: nagaraju.kappal
2 Replies

7. BSD

Migrate a Hard Disk

hi Has anyone already tried to migrate a hard disk with FreeBSD using recoverdisk? (1 Reply)
Discussion started by: ccc
1 Replies

8. Red Hat

Disk management in RHEL 6

Hi, I want to Create a patition /home with 100G which be taken from /Archive, Note that we are using Raid 10. Thanks and regards root@mainmgt1 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup-lv_root 94G 69G 20G 78% / tmpfs 24G 668M... (0 Replies)
Discussion started by: stam51
0 Replies
DM(4)							   BSD Kernel Interfaces Manual 						     DM(4)

NAME
dm -- Device-mapper disk driver SYNOPSIS
pseudo-device dm DESCRIPTION
The dm driver provides the capability of creating one or more virtual disks based on the target mapping. This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con- figuration file, and how to partition disks. This driver is used by the Linux lvm2tools to create and manage lvm in NetBSD. Currently, the linear, zero, and error targets are implemented. Each component partition should be offset at least 2 sectors from the begin- ning of the component disk. This avoids potential conflicts between the component disk's disklabel and dm's disklabel. In i386 it is offset by 65 sectors, where 63 sectors are the initial boot sectors and 2 sectors are used for the disklabel which is set to be read-only. In order to compile in support for dm, you must add a line similar to the following to your kernel configuration file: pseudo-device dm #device-mapper disk device dm may create linear mapped devices, zero, and error block devices. Zero and error block devices are used mostly for testing. Linear devices are used to create virtual disks with linearly mapped virtual blocks to blocks on real disk. dm Device-mapper devices are controlled through the /dev/mapper/control device. For controlling this device ioctl(2) calls are used. For the implementation of the communication channel, the proplib(3) library is used. The protocol channel is defined as a proplib dictionary with needed values. For more details, look at sys/dev/dm/netbsd-dm.h. Before any device can be used, every device-mapper disk device must be initialized. For initialization one line must be passed to the kernel driver in the form of a proplib dictionary. Every device can have more than one table active. An example for such a line is: 0 10240 linear /dev/wd1a 384 dm The first parameter is the start sector for the table defined with this line, the second is the length in sectors which is described with this table. The third parameter is the target name. All other parts of this line depend on the chosen target. dm For the linear target, there are two additional parameters: The first parameter describes the disk device to which the device-mapper disk is mapped. The second parameter is the offset on this disk from the start of the disk/partition. SEE ALSO
config(1), proplib(3), MAKEDEV(8), dmsetup(8), fsck(8), lvm(8), mount(8), newfs(8) HISTORY
The device-mapper disk driver first appeared in NetBSD 6.0. AUTHORS
Adam Hamsik <haad@NetBSD.org> implemented the device-mapper driver for NetBSD. Brett Lymn <blymn@NetBSD.org>, Reinoud Zandijk <reinoud@NetBSD.org>, and Bill Stouder-Studenmund <wrstuden@NetBSD.org> provided guidance and answered questions about the NetBSD implementation. BUGS
This driver is still work-in-progress--there can be bugs. BSD
August 30, 2008 BSD
All times are GMT -4. The time now is 03:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy