- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- IO capacity on nPars and vPars
HPE 9000 and HPE e3000 Servers
1755766
Members
3014
Online
108838
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
07-08-2008 12:01 AM
07-08-2008 12:01 AM
Have a number of large databases on an RP8420 which are struggling to push through backups to tape when running multiple drives.
The main culprit is a pair of vPars on the same nPar (made up of one cell only). We were looking at moving Databases from one vPar to another to spread the IO load.
Question: Does a bottleneck on one vpar on a cell affect the other vpars on the same cell?
Share and Enjoy! Ian
The main culprit is a pair of vPars on the same nPar (made up of one cell only). We were looking at moving Databases from one vPar to another to spread the IO load.
Question: Does a bottleneck on one vpar on a cell affect the other vpars on the same cell?
Share and Enjoy! Ian
Building a dumber user
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 05:26 AM
07-09-2008 05:26 AM
Solution
Generally speaking, the 2 vPars should be isolated from each other as far as bottlenecks are concerned. No shared I/O devices. If you are using WLM and sharing processors, you could impact the other vPar, but you should be able to see that happening using WLM tools.
Possible issues could be both vPars accessing the same fiber switch and the switch causing a bottle neck, but in most cases the tape drive can't process data fast enough to overload the fiber network or the server for that matter.
If you are attempting to backup both servers across the LAN at the same time, you might be bottle necking in the LAN enviornment, but again, the tape drive is usually the limiting factor.
What tools have you used to determine a bottle neck?
Rob...
Possible issues could be both vPars accessing the same fiber switch and the switch causing a bottle neck, but in most cases the tape drive can't process data fast enough to overload the fiber network or the server for that matter.
If you are attempting to backup both servers across the LAN at the same time, you might be bottle necking in the LAN enviornment, but again, the tape drive is usually the limiting factor.
What tools have you used to determine a bottle neck?
Rob...
IF you do it more than twice, write a script.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP