Quantcast
Channel: All MSA Storage posts
Viewing all 8378 articles
Browse latest View live
↧

Re: Feedback to configuration

February 27, 2019, 7:50 am
$
0
0

Hello,

The use of the MSA2012 SAS is where the problem lies. This array has entered the End of Support Life. This means there is no further support, testing, or qualification with new OS, servers, switches, HBAs, etc.

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c05403140

Instead of trying to figure out a configuration with the MSA2012 SAS, you should be considering ppurchasing a new array such as the MSA2050 SAS or MSA1050 SAS. Then you would be able to get support and your servers, OS, and SAN would be tested and qualififed. Which means the configuration you are attempting to create would work to meet your production needs.

As mentioned, please review configuration details on SPOCK. Here is a direct link to the MSA2050 SAS: https://h20272.www2.hpe.com/spock2/cont/configsetresultview?repositoryId=256192&navId=0&source=Constraint

Cheers,
Shawn

I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.

↧
Search

Re: Feedback to configuration

February 27, 2019, 8:17 am
$
0
0

Please refer the link below to understand hardware requirement for Microsoft Storage Spaces Direct which you want to implement,

https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-hardware-requirements

As we have informed you earlier, MSA2000sa support matrix will not support SAS HBAs which may be required to communicate with DL380 G8 or DL380 G9 and DL380 G10 Servers. Hence you can't use MSA2000sa with these servers. 

Now coming to your query, you need use some Storage or external JBODs as per the above supported link to use as Microsoft Storage Spaces Direct. That will be completely different discussion which will be no more applicable for this forum as this forum only related to MSA topics.

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS!thumb below!

***********************************************************************************

↧
↧

Re: Feedback to configuration

February 27, 2019, 10:47 am
↧

Expanding diskgroup

February 27, 2019, 12:03 pm
$
0
0

Hello guys, i need a little bit of a guidance/best practice. The company I work for has MSA2040 has 2 disk groups, collegue that worked before me made 1 disk group with 12 disk and other one with 4 disks because customer didnt have enough money to buy all disks at once when he did configuration.

  Customer purchased the rest of disk few days back, and i want to remake second disk group.

I spent some time reading the refference guide but I just want to make sure Iam on the right track:

When i delete second disk group - data from it will automatically drain to first disk group if there is enough space (vdrain), after that i should just recreate second disk group and add it to pool?

 

↧

Re: Expanding diskgroup

February 27, 2019, 4:16 pm
$
0
0

Hello Filip,

Consider your options.

Option 1: Add the new drives and create a third disk-group which you can then add to a volume to expand the volume size. This offers you the option of adding space without deleting a disk-group causing a vdraim operation.

Option 2: You can delete the disk-group and allow the vdrain (or moved) operation to occur. Before taking this step be sure you have enough space to allow all the data in the smaller disk-group to be moved into the larger disk-group. Until the data has completed the move you will not be able to delete the smaller disk-group. So timing may be a key factor. Plan to do this activity during a time of little or no host IO so that the drain operation has top priority and can occur quickly. This will better protect your system while the drain operation is in process. Once the drain has completed you can create a new disk-group with your new drives.

Option 3: Backup all data and delete the pool. Then recreate the disk-group(s) with the correct number of drives and restore your data from backup. This option would allow you to set up multiple pools to utilize both controllers.

I would also suggest making sure your array is healthy and all disk-groups are fault tolerant before any action is taken. I also am a strong supporter of backups when performing these kinds of activites.

Good luck!

Cheers,
Shawn

I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.

↧
↧

Re: Feedback to configuration

February 27, 2019, 11:40 pm
$
0
0

 

If you have no further query and you are satisfied with answers then kindly mark the forum as resolved so that everyone can get the update who are all following your forum.

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS!thumb below!

***********************************************************************************

↧

Re: Expanding diskgroup

February 28, 2019, 12:11 am
$
0
0

hi

from your description I understand you have one pool and two virtual disk groups

if you delete one disk group consider creating a new pool and puting the new disk group in it

in this way you can load balance one pool a controller A and the other on controller B

Regards

Give a KUDO if this helps

 

↧

MSA 2040 Deletion of GROUP/Volume

February 28, 2019, 12:17 am
$
0
0

Hi,

I have setup an MSA 2040 SAN storage which has been running well within our production environment.  I followed an online guide which I found very usefull.  However, that was over a year ago and the system has been working well in production since.

ALthough I have successfully completed the above I am still pretty new to SAN storage and don't get to play around with it as much as I should so excuse me if I use the wrong terminology, etc., etc.  I am in search of some guidance.

I initially seutp a Virtual Pool containing 4x600gb sas drives.

I then created two additional Linear pools containing 8x 600gb sas drives each.  All three pool can be seen within VMware

I have migrated the servers from the virtual pool over to the linears pools.  All good so far.

Now there are also three volumes, these seem to match the three pools mentioned above.

What I am trying to do is delete the VIRTUAL Pool and recreate it with 1.2tb disks.

Would I need to remove the volume group? Or can I just remove the disk group associated with the Virtual Pool?

There is no data on the Virtual pool, i'm 100% confident that the virtual pool is empty.

Will this effect either of the Linear groups?

This enitre environment is running in production.  Any help/advice would be greatly appreciated.

Thanks

↧
Search

Re: P2000 G3 connecting to 3 hosts

February 28, 2019, 1:17 am
↧
↧

Re: MSA 2040 Deletion of GROUP/Volume

February 28, 2019, 1:25 am
$
0
0

hi

what you said is correct you can delete the virtual disk group this disk group is part of pool A

I understand you want to replace 4 X 600GB drives with 4 X 1.2TB drives.

you can do this but you can also add your old 600GB drives to your existing linear disk groups

up to 16 drives per linear disk group

Regards

Give a KUDO if this helps

 

↧

Re: MSA 2040 Deletion of GROUP/Volume

February 28, 2019, 1:30 am
$
0
0

Thank you giladzzz.

This won't effect the other two linear groups that are currently running?

Your help is appreciated.

↧

Re: Feedback to configuration

February 28, 2019, 1:38 am
$
0
0

I am not shure if it makes much or exactly sense to invest in a additional MSA2050 SAS or MSA1050 SAS for Gen 8 to build a failover cluster or to invest instead in two new ProLiant DL-series and local storage and build a failover cluster with Microsoft direct storage spaces direct.

↧

Re: MSA 2040 Deletion of GROUP/Volume

February 28, 2019, 1:42 am
$
0
0

Hi

if what you described is correct it will not effect existing linear disk groups

to make sure first remove mapping from the volume on the virtual disk group 

to check that it disapears from your servers with no affect

Regards

 

↧
↧

Re: MSA 2040 Deletion of GROUP/Volume

February 28, 2019, 1:44 am
↧

Re: Expanding diskgroup

February 28, 2019, 9:43 am
$
0
0

Thanks alot for your reply Ill consider my options in next few days and prolly do the migration next weekend.

Ill let you know how everything went.

Thank you once more, Cheers!

↧
Search

MSA EXPANSION QUESTIONS-

March 1, 2019, 8:08 am
$
0
0

New to SAM, MSA2040, and VMWare....and struggling. 
I just added a second storage unit to our MSA2040. It is assembled with 24 900GB drives (as was the first). I have a few questions, and might not be finding the proper terminology so please be patient.

Current: MSA2040 w/ 24 900GB drives, using RAID10 (w/ 2 spares), 2 Volumes on A, 1 Volume on B. 
I've added a shelf with another 24 900GB Drives, and would like create 2 very large volumes (for speed; (6) Windows2016Server Operating systems reside on one of the volumes, and CAD files are stored/manipulated on the others).

Can I format the new shelf/drives while my users are up and running on the existing MSA2040 (this is ALL production), and if so can the user impact and length of time to format 10TB  be estimated? This is a production system and it could affect 50+ users' productivity. 

Plan (nutshelled): 
[]Set up a new Volume 004 for Pool A (on dgA02) that is +/- 5TB… called Vol0004.
[]'Migrate’ the data on Vol003 (currently Pool B dgB01) to the (new and empty) Vol0004 (Pool A, dgA02).
[]This leaves an assigned (empty) Vol0003 and unnamed space that has not been committed to a Volume (only RAIDed) on Pool B.
[]remove the empty volume from VMware
[]Delete Vol0003 (or expand it into the ‘un -named’ space on B) and Pool B is now 10TB.
[]Create Vol0005 with 10TB on Pool B (or expand Vol003 @ 10TB) using BOTH dgB01 and dgB02.
[]Migrate all the data on Vol0001, Vol0002, Vol0004 (Pool A) onto the new (now 10TB) Vol0005/Pool B.
[]Remove these from VMware: Vol0001, Vol0002, Vol0003
[]Delete Vol0001, Vol0002, Vol0003, and create a new Vol0005 (using dgA01 and dgA02).
[]Vol0005 (dgAo1, dgA02) is now also 10TB.
[]Migrate some data for load balancing (best guess).

↧

Re: MSA EXPANSION QUESTIONS-

March 1, 2019, 9:12 am
$
0
0

Hello,

You can format the new drives while in production with no impact to current users. Just to clarify a little further. Whether you chose to use virtual or linear you will will create a disk-group on the array. You can chose an online option or an offline option. Chosing online lets you use the disk-group immediately from the host side. If you decide to chose the offline init all the parity and stripes need to be laid out before you can present to the host and allow host access. Either option is fine and neither will impact your current users. Online init offers immediate host access while offline means you have to wait. I personally use online init because it is faster.

Your plan for adding disk-groups and volumes looks good. A couple words of caution.

First recommendation is to take a full backup of all your data.

Be sure you have enough space on Vol0004 to fit all the current data in Vol003.

I would not expand volumes but delete and recreate. As long as your data is backed up this is quicker and provides you a more robust layout of your Pools.

Besure before you begin moving data and creating new disk-groups, that all your drives and the array are at the latest firmware versions.

A couple of guides you may be interested in.

SMU: https://support.hpe.com/hpsc/doc/public/display?docId=c04220794

MSA2040 Best Practices: https://h20195.www2.hpe.com/v2/GetPDF.aspx/4AA4-6892ENW.pdf

MSA and VMware vSphere Best Practices: https://h20195.www2.hpe.com/v2/getpdf.aspx/4aa4-7060enw.pdf

MSA Firmware & Release Notes: https://h41111.www4.hpe.com/storage/msafirmware.html

Good luck!

Cheers,
Shawn

I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.

↧
↧

P2000 G3 Increase Cooling

March 6, 2019, 3:30 am
$
0
0

Hi,

Does anyone know how to increase the cooling, or overriding the default speeds.  GUI\CLI?

The memory controller Temp A / B are around 70-74 degrees and producing warnings.

The fans are consist spinning at 380-ish RPM and capable of running much higher.

All my fans are working and no faults present, just overworked unit.

Left/Right PSU temp is 39 and onboard temp are around 53-55, so seems like the controller cards are cooking.

Im happy to increase the cooling to max as its sitting in the corner of a datacentre in the dark.  I have no warrenty left, so happy to apply any hacks until the unit dies.

Any help would be amazing.

 

↧

Re: P2000 G3 Increase Cooling

March 6, 2019, 9:16 am
$
0
0

Hello,

There is no command to increase the cooling or speed of the fans. However, check where the unit is sitting to make sure there is proper air flow. You mention sitting in a corner. Be sure that the system can draw air in the front and blow air out the back without any obsturctions. Often if you can clear cables, wires or other objects from the back of the system it will help lower the temperature. I have seen units where there is so much blockage at the back of the system the hot air was being recyled back into the array.

Cheers,
Shawn

I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.

↧

SAN MSA2040

March 8, 2019, 1:50 pm
$
0
0

Hi,

How to setup unsuccessful login attempts and send as email alerts in MSA 2040 SMU. Please let me know. Thank you.

 

 

↧
Viewing all 8378 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>