Hello,
The array allows you to extend the vdisk size by adding a drive and using the extend feature. There is no way through the firmware to decrease a vdisk size.
If you no longer want the vdisk to have all 4 disks, you will need to perform a full backup, verify your data, and then delete the vdisk. You can then recreate a new vdisk using only the 3 drives and restore data from backup.
Cheers,
Shawn
Hi,
We have an oldish HP MSA p2000 g3 iscsi as a backup target.
Yesterday I enabled MPIO to get more troughput since our backups are gettin quite big.
I ran in to problems. First, my archive backups vere corrupted. After that I formatted the volume and send backups there again. During the night server has bsod'ed and in morning the whole volume was not readable and windows is asking to forma it. I think I might have an fundamental error in my mpio config. The archive volume has windows deduplication enabled.
The setup is following:
I have 24x900gb disks in two raid6 vdisks.
Management interfaces are assigned to 192.168.100.0 network.
A1 and B1 port has been assigned to 192.168.100.0 network
A2 and B2 port has been assigned to 10.100.11.0 network
Backup server is running win2012 r2
Nic1 has been assigned to 192.168.100.0 network
Nic2 has been assigned to 10.100.11.0 network
MPIO is enabled in windows server.
connecting to storage:
From backup server, start iscsi initiator
go to discovery tab, click discover portal
enter A1 port ip address, OK
go to targets tab, Storage now appears in "discovered targets".
Click connect and Properties.
Click add session, select enable multi-path, click advanced. Select "Microsoft iSCSI Initiator" as local adapter, Nic1 IP as initiator IP, B1 ip as target IP.
Add two more sessions like above, Nic2 -> A1, Nic2 -> B2.
At properties, click devices -> MPIO -> select Least Queue Depth as load balance policy.
Close everything and start computer management.
Under disk drives, I now have two HP P2000 G3 iSCSI Multi-Path Disk Devices.
Right click -> properties, uncheck "Enable write caching on the device", go to MPIO tab, select Least Queue Depth for MPIO Policy. Repeat for another disk.
Some observations, that puzzles me.
When I now copy large files over iSCSI, the copy is extremely fast. However, it seems that the file is actually being cached in the memory and after the copy "finishes", it is actually still being transferred for tens of seconds (observed from task manager -> performance).
For some reason in isci initiator -> target -> properties, in the sessions tab, in the identifiers, some of the identifiers has Data Digest automatically set to "CRC32", some has "None Specified". Also, since this morning I now have five identifiers. Nic1 -> B2 seems to be double.
Some questions:
Is it ok to have multiple storage ports in the same subnet or should each port be in its own subnet? Is it ok to have iSCSI ports in the same subnet than management ports?
In iscsi initiator, in discovery tab, should I add each IP address to target portals or only A1, or A1 and B1?
In isci initiator target -> properties -> Should I add so many sessions, or just have Nic1 -> A1 and Nic2 -> B2 or something else?
In the device manager, is it OK to disable caching, for maximum stability?
Thanks in advance, please ask for more detail if needed.
E:typos
There are couple of things missing like you haven't mentioned total how many drives present in the system and how many vdisk present in the system.
I see you have mentioned " 1 disk failed. I replaced the disk (Disk 5 in RAID5) with a new disk. I cleared the META DATA and Added the disk as spare." -> If the Disk 5 failed and you have replaced it then the status of the new drive should be in AVAIL state. I am not able to understand how you have cleared metadata of the new drive? are you sure you have cleared metadata of the new drive or some other drive in the same RAID5 vdisk?
Coming to next portion of the issue statement "
The rebuild started and after a while 2 disk become on status LEFTOVR. I thought the new disk is a defect one and I buyed a second new disk. This give also this message. In the log I see :
Vdisk reconstruct failed. Command failed. (error code: 1). (vdisk: VDISK_RAID5, SN: )" -----> If the rebuild started then possible you have done everything properly but Vdisk reconstruction failed due to other drives having issue. So eventhough you replace failed drive again and again vdisk reconstruction will never complete until we figure out what is the other drive part of the vdisk having issue which is not allowing vdisk reconstruction to get complete
It's difficult to say anything without checking complete log file. So I would suggest you to log a support case with HPE support or else provide me the MSA log in private chat
Note: Never clear metadata when you find your vdisk in QTOF or Offline state. Also if there are situations where multiple drive having hardware errors then also you shouldn't clear metadata instead involve expert to check further.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hello,
It is not recommended to have the management ports and the host ports on the same network. As a best practice the host ports should be in a seperate vlan.
You need to be careful on your MPIO configuration. NIC1 has two ports while NIC2 has two ports. Be careful that the backup application is correctly configured for two NICs since they are on seperate networks.
When you see the two P2000 devices in Disk Manager are they the two vdisks on the P2000 or have you replicated the P2000? If the MPIO and the iSCSI initiator is not configured correctly, this can happen. Especailly since you say "in the morning I now have five identifiers"
The other concern is how you have the backup configured. You should not be caching on the host side like you describe. However, that is something that is occurring on the software layer or within your host configuration and is not due to the array.
I woiuld suggest going through and checking your host side configuration and then review the software configuration. I personally do not like to cache streaming data unless I have enough CPU and memory to cache and destage that data quickly. Otherwise you can create a bottleneck that causes other problems.
Cheers,
Shawn
HI Shawn, thank you for your reply.
Do you mean, that each of iSCSI port (from A1 to B4) should be in it's own vlan/subnet?
A1 10.10.1.1. A2 10.10.2.1, A3 10.10.3.1, A4 10.10.4.1, B1 10.10.5.1, B2 10.10.6.1, B3 10.10.7.1, B4 10.10.8.1
I'm using Veeam Backup&replication to do the backups. As far as I know it does not care about underlying network, as long as OS can connect them.
I have two vdisks in p2000, and they are the ones that show in disk manager. I have no replication configured in P2000, it's a standalone device.
I have not noticed caching before I installed MPIO, so I kinda assumed it's somehow related to that. I have dual xeon cpus and 48gigs mem on backup server, and it has no additional roles, so resources should be adequate.
With two nics on backup server, two vdisks on the P2000 ("active" backup and backup archive), what would be the best practice to configure nics? I'm backing up a vmware cluster which is in the 192.168.100.0 network.
I have an MSA 2040 SAN with two controllers and I'm able to access controller A via the web management page. I can ping and access it via telnet and am looking to restart the management controller using the commands. However, I am wondering whether during this period does the SAN go offline or is it just the management controller that I am restarting and access to the disks is unaffected?
No impact in production if you restart management controller. However you should plan if you have repliacation configured before you go for management controller restart.
You shouldn't restart Storage Controller without proper plan but management Controller you can restart.
MC = Management Controller
SC = Storage Controller
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************************
Hello Narjis,
Good Day.
As I understand the issue here, It seems to be multiple HDDs failed during the first HDD rebuilding.
So it would be easier if you could share the Store. logs from SMU.
using the below steps to analyze and update what has caused the HDDs to go to Leftover state.
Login to SMU --> TOOLS --> SAVE logs.
Regards,
Ashoka S
Hello,
The issues you are having are host based issues / configuration problems.
From the host side there are considerations.
If you have two NICs configured on two different subnets how are you handling failover?
Using VEAM are there two backups or one? Since you mentioned active and archive you have to consider how the archive is working? Is that using a VEAM snapshot of the active backup?
On the host side, MPIO failover should be configured so that you can perform path failover. With two different subnets you will have to consider carefully how that path failover is working. You will need to confirm and test that your failover pathing policy is actually working correctly. You also need to check and confirm the queue depth and multipathing policies are set correctly for your server and NICs. For example MRU or RR? This will depend on hardware and OS versions.
It sounds like the server can handle the load once configured correctly for VEAM and ESXi. However, be aware that with newer versions of ESXi ATS/VAAI may not be compatable with the P2000 firwmare. You should review SPOCK for the latest firmware compatability with the P2000 and ESXi to ocnfirm.
Sorry I cannot give a more firm answer but there are a lot of configuration unknowns here which makes answering your questions fully very difficult.
Cheers,
Shawn
Hi ! I have an MSA 1510i with 2 controller and I want to setup the iSCSI params.
I found an step by step guide and my final configuration is working with 1 pc for the tests.
But I can't found some explanation about the number of portals / portal group needs for an correct setup.
My actual setup :
- 2 arrays with 1 target by array
- On each port (SA0,SA1,SB0,SB1) 2 IP Adress with 2 portals on each IP
- for the targets :
Target 1 : portal group "main" with 4 portals of SA0 and portal group "back" with 4 portals of SB0
Target 2 : portal group "main" with 4 portals of SA1 and portal group "back" with 4 portals of SB1
and for finish , 1 initiator allowed to all target (1 pc connected for the moment)
Planned use : HP C7000 with 10 BL460C G1 with ESXi (regardless of hardware setup of switch etc)
If I understand correctly the bases of iSCSI, I need 1 initiator by BL460C. But my setup (ports, portals groups etc) is good for the setup or I need to setup more portals / ip / portal group / anything else ?
Thanks a lot !
Kind regards
Hello,
I first have to caution you on the age of this product. The MSA1510i went End of Support Life 21 December 2015. Additionally, the MSA1510i only supported ESXi 3.5. Newer versions of ESXi which use ATS would likely be incompatable with the array.
The way you are setting up the target portals is incorrect. Redundant data path portals will be SB0 and SB1. So you would have SA0 and SB0 as a target and SA1 and SB1 as another. Please refer to the following link which will perhaps help with your configuration. http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c01503404-1.pdf
I still suggest you consider using a new product which will have spare parts, new hard drives and supportability with new firmware and features. The MSA1050 has currently released new firmware and would likely fit your needs. Plus the performance would be much better!
Cheers,
Shawn
Thanks for reply, I planed to use this san for education and tests only and I have get it at lowest price, so the end of support is not important for me.
Okay, the portal maping is more sense like as you have suggest for redundant data paths, my first approch was one controler for one array but it seems to not be good.
I have follow an guide like you give the link but nowhere I found some details about the number of portal need for x server (1 for 1 server, 1 for 1 physical lan port on server ...)
I suppose the correct setup is 1 portal (ip:port like 10.10.10.10:3260 for exemple) for 1 physical lan on server but I'm not sure..
Thanks a lot
Cheers,
Nicolas
Announcing New MSA 2050/2052/1050 Controller firmware!!!
Yesterday we published new controller firmware for the MSA 2050/2052/1050. The new firmware and release notes are now available on the MSA Firmware site (www.hpe.com/storage/MSAFirmware).
VL270R001-01 (MSA 2050/2052)
VE270R001-01 (MSA 1050)
Hi, I have a HP MSA 2040 with a SAS connection on HP DL380 G9 servers running Windows Server 2016 Datacenter and the connectivity between the Windows server and the MSA 2040 is only 6 GB \ s while it should be 12 GB \ s. The two controllers on the MSA 2040 are 12 GB \ s and the 8644 12 GB \ s. On the servers I have HP h241 HBA 12 GB \ s cards. But it only works for 6 GB \ s.
Where can I find firmware for older products like MSA2000 or MSA2000G2.
Hi guys,
How are you?
I´m configuring a new MSA 2050 but I´m having problems creating the pools. It´s simple, I have 2 x SSD disks and 6 x 1.2 TB SAS.
The objective is to create 2 RAIDs: Raid 1 with SSD and Raid 5 with SAS disks but I can´t because the MSA says that I need a license... (performance Tier License).
I don´t need to create a singles pool with both types of disks, etc I only need to create 2 separate RAIDs.
I´ve been reading that I can do this with linear configuration but When I´m creating a pool I cannot see this option.
How Can I enable / configure this 2 independent RAIDs?
Thanks a lot for your help.
Remove the un-used SSD half of the slot and then try to create the Virtual DIsk Group with SAS drives as you want in Pool. It's possible that Controller is thinking SSD drive available in system without Performance Tier License so it's not allowing to create new VDG. So after you create the new VDG in Pool A then insert the SSD and try to configure SSD read-cache
Please refer the below forum discussion as well where I have fixed similar issue,
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hi!
Thanks for your quick response;
I did all this steps:
1. Remove all pools.
2. Extract SSD disks.
3. Create a new Pool with all SAS DIsks (Raid5)
4. Connect 2 SSD disks.
5. Try to create a Raid 1 pool with this 2 SSD disks.
6. It doesn´t work.
I have again the same problem, the storage system says that I need performance tier license.
But I don´t need to create a Read Cache I only need to create another Raid with this 2 SSD disks but totally independent form the another Raid5 with SAS disks.
What Can I do?
Many thanks for your help.