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
metaimport(1M)						  System Administration Commands					    metaimport(1M)

NAME
metaimport - imports disk sets into existing Solaris Volume Manager configurations SYNOPSIS
metaimport -s setname [-n] [-f] [-v] [disks]... metaimport -r [-v] [disks]... metaimport -V metaimport -? DESCRIPTION
The metaimport command allows the importing of disk sets, including replicated disk sets, into an existing Solaris Volume Manager configu- ration. Replicated disk sets are disk sets created using remote replication software. The default Solaris Volume Manager configuration specifies a maximum number of disk sets that can be configured. The metaimport command fails if importing the disk set would result in exceeding the number of disk sets configured on the system. To increase the number of disk sets allowed on a system, see the . Use metaset(1M) or metastat(1M) to view the configuration of the imported set. You must run metaimport as root. metaimport requires a functional Solaris Volume Manager configuration before it runs. OPTIONS
The following options are supported: -f Force the import, even if a quorum of replicas from the imported disk set is not available. This option could result in cor- rupt configurations and should only be used when metaimport fails with the "Insufficient quorum detected; exiting" error. If only a partial disk set is available, this option might be necessary to successfully import. Some or all data could be cor- rupted or unavailable when importing a partial set or a set lacking a replica quorum. -n Does not actually perform the operation, but shows the output or errors that would have resulted from the operation, had it been run. -r Report on the non-configured disk sets found on the system. If no disk device or LUN is specified, metaimport reports on all non-configured disk sets attached to the system. When the name of one disk is specified, metaimport reports on the disk set (or virtual LUN) containing the specified disk. If two or more disks are specified, metaimport reports on the set (or sets, if they belong to different disk sets) containing the specified disks. If two or more disks are specified, metaimport reports on the set (or sets, if they belong to different disk sets) containing the specified disks. This option can be used in conjunction with the -v option to give verbose output on each disk set reported. -s setname Specify the disk set name to use when importing. The imported disk set will be called setname, without regard to the name it may have had on a different system. -v Verbose. Provides detailed information about the metadb replica location and status. It also provides detailed information about the disk set configuration and status similar to the "metastat -c" output. -V Version information. -? Display a help message. EXAMPLES
Example 1 Importing a Disk Set The following example creates a disk set called blue and identifies c1t5d0 as a disk containing a state database replica from the disk set being imported. # metaimport -s blue c1t5d0 Example 2 Reporting Disk Sets to Import The following example scans all disks and LUNs attached to the system and configured as part of the system. It scans for disks that could be part of a disk set to be imported. Components that are already part of the Solaris Volume Manager configuration are ignored. This use of metaimport provides suggested forms of the metaimport command to use to actually import the disk sets that have been found. You can specify a component on the command line to reduce the scope of the scan and generate results more quickly. # metaimport -r EXIT STATUS
0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), attributes(5) SunOS 5.11 28 Oct 2005 metaimport(1M)
All times are GMT -4. The time now is 10:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy