- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Guidelines for vg setup
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 12:36 AM
тАО11-28-2005 12:36 AM
I'm setting up an Oracle db on EMC Symmetrix. Initially we've reserved 1.5 TB disk space (net) for the db. Is there any advantage, from the performance point of view or otherwise, in splitting the disks into several volume groups rather than defining one big vg ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 12:47 AM
тАО11-28-2005 12:47 AM
Re: Guidelines for vg setup
Performance is determined by the underlying setup of the disk itself. If this is a database with heavy writes, and the underlying disk structure on the EMC is raid 5, then you will encounter performance problems whenever writes get heavy.
I don't see any advantage in either setup beyond that. If you can afford it, try and get data/index/redo logs onto raid 10 configured EMC disk, it this is an (OLTP) system.
When you define the volume groups, don't forget the -p paramter of vgcreate. It lets you define the maximum number of physical disks. Set correctly it can provide you more usuable capacity.
Set to default or too low, and you'll end up building the vg again in the future when you want to expand.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 12:48 AM
тАО11-28-2005 12:48 AM
Re: Guidelines for vg setup
Yes there is, IF, you have 2 or more HBAs connecting to that array. Then you could define the primary/alternate paths to those VGs such that the load is spread across all of them.
Ideally you want at least as many VGs as you have paths - or a multiple of those paths.
And if you make all LUNs available to all HBAs & define all of them in the VGs then your reads will be better because they will always go to the least queued up path.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 01:13 AM
тАО11-28-2005 01:13 AM
Re: Guidelines for vg setup
Example - one of my systems is 1.5TB of SAP on Oracle.
For performance - I only use RAID10 on DMX 1000.
I have 3 vg's - one for sapdata, one for Oracle logs, and one for the rest (SAP/Oracle binaries, etc.).
For backup, My Netbackup server only has to mount the bcv's of the sapdata vg locally - then uses brbackup to backup the db.
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2005 08:58 AM
тАО11-28-2005 08:58 AM
SolutionI've worked with EMC extensively on configuring disks/filesystems, etc. for oracle environments....trust me...you will get better performance (from an oracle perspective) if you split up the data into different VGs and take advantage of the different extent size options and striping size options.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2005 04:53 AM
тАО12-01-2005 04:53 AM
Re: Guidelines for vg setup
Christine's reply leads to another question: EMC recommends creating logical volumes with extent striping (lvcreate -D). Is this what you mean by striping or would you use -i striping on Symmetrix metadisks ? I know this issue has been discussed previously on the forum and there's support for both alternatives.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2005 04:33 AM
тАО12-05-2005 04:33 AM
Re: Guidelines for vg setup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2005 04:38 AM
тАО12-05-2005 04:38 AM
Re: Guidelines for vg setup
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2005 04:51 AM
тАО12-05-2005 04:51 AM
Re: Guidelines for vg setup
I would suggest to create it using -i option only as here you have the option of defining the stripe size which will be in KBs whereas with -D option the minimum size will that of one extent and that for such a large VG can not be less than 16MB or so.
Coming to the point of creating a big VG or multiple, I think you will have a better throughput and easy configuration by having multiple VGs for seperate sort of files. This is because of different usage of different LVOLs. Always divide your requirements in atleast three types for such instances i.e. datafiles, redo logs, archive logs.
You should have different VGs atleast for al of these so that for tuning you can change particular parameters and the others will not be effected from that.
Also from storage part at similar applications we have redo VG's mirrored using raid 0+1 ( In Backend at storage level) and others with Raid5.
Also redo VGs use disks of 15K RPM whereare others are of normal 10K RPM.
The important part as you are using pvlinks would be that you define your disk device files carefully while configuring so that the load is balanced across multiple HBAs. For this you need to use different alternate links properly.
HTH,
Devender