- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: MSA1000 Best Practices
MSA Storage
1753519
Members
4978
Online
108795
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО05-23-2004 01:20 AM
тАО05-23-2004 01:20 AM
MSA1000 Best Practices
We are just purchasing our first MSA1000s and want to understand how best to set up the disks, arrays and logical disks. We have four servers - two SQL, one exchange and two File. I've two dedicated 2 disk RAID1 arrays on Shelf 1, Bus 0 & 1 and on Shelves 2 & 3 on bus 2 & 3. Two RAID5s that are striped down and across all three shelves - one array is 12 x 15k 72Gb and the other is 10 x 10k 145Gb. The 72Gb array has three logicals - 2 x SQL and 1 x Exchange and the 145 Gb array has two 650 Gb logicals for the file servers. Does this repesent best practice?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-23-2004 04:59 AM
тАО05-23-2004 04:59 AM
Re: MSA1000 Best Practices
Hey, that sounds pretty reasonable. I guess you have put multiple logical disks into one disk array in order to save parity space which would be 'wasted' if you used multiple, smaller disk array with one logical disk each.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2004 02:26 AM
тАО05-24-2004 02:26 AM
Re: MSA1000 Best Practices
Mike,
The disk configuration sounds fine. I think what you're really asking for is configuration best practices for the SAN in general - this would include the SAN switches as well as the MSA1000. I am not familiar with the MSA1000; I have HSG80's. Here are my recommendations based on experience and educated guesses!!
1. If at all possible, setup a test environment. While HP makes everything sound easy, it rarely is. I have lost data because I couldn't test things out.
2. Zone based on OS. Even if you anticipate only using Windows, zone. Once you put it in, everyone is going to want to use it.
3. Get a SAN appliance. While you can manage the SAN by ver, very careful documentation the appliance makes management much more reliable and easier to plan with. In my mind a must - that's coming from a person without an appliance :-((
4. You didn't mention it, but an absolute must is to have dual-redundancy at the MSA1000 - dual controllers.
5. Get agreement on a standard downtime schedule. Keeping your SAN up-to-date is very important. If you can't get the downtime schedule, it makes the testing environment critical so that you can test the upgrade procedures online with systems up.
HTH,
Spike
The disk configuration sounds fine. I think what you're really asking for is configuration best practices for the SAN in general - this would include the SAN switches as well as the MSA1000. I am not familiar with the MSA1000; I have HSG80's. Here are my recommendations based on experience and educated guesses!!
1. If at all possible, setup a test environment. While HP makes everything sound easy, it rarely is. I have lost data because I couldn't test things out.
2. Zone based on OS. Even if you anticipate only using Windows, zone. Once you put it in, everyone is going to want to use it.
3. Get a SAN appliance. While you can manage the SAN by ver, very careful documentation the appliance makes management much more reliable and easier to plan with. In my mind a must - that's coming from a person without an appliance :-((
4. You didn't mention it, but an absolute must is to have dual-redundancy at the MSA1000 - dual controllers.
5. Get agreement on a standard downtime schedule. Keeping your SAN up-to-date is very important. If you can't get the downtime schedule, it makes the testing environment critical so that you can test the upgrade procedures online with systems up.
HTH,
Spike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2004 02:49 AM
тАО05-24-2004 02:49 AM
Re: MSA1000 Best Practices
Maybe I should has said - the MSA1000 is to supliment two of our EVAs so the SAN is well established and we're trying to setup the MSA1000 in our lab so we can test, test, test! We just want to make sure we are following best practice cause I shure as hell can't find anyting on the HP site that deals with this specific issue on the MSA.
Thanks for the input guy's!
Mike
Thanks for the input guy's!
Mike
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