What is our primary use case?
We were using Dell PowerStore as a block device for VMware infrastructure and in iSCSI Target for a couple of secret server clusters installed at a hardware level. Apart from that, regarding the workload, which is currently more or less 40% for SQL Servers and 60% for the production of VMware machines. We have a small workload on VMware machines to manage a typical number crunching machine and application server. Now, we have six machines running a couple of MongoDB servers. Honestly, our bottleneck is not the PowerStore. Our actual bottleneck is the networking size because we noticed how we got some barriers in LACP algorithms, indicating we have two mixes on every motherboard> However, we are not able to fulfill the double connection. We also have a part of our experience infrastructure, but instead of 25 gigabit, it functions on 10 gigabit. Sometimes, during evenings or on Fridays, we use Rubrik for protection when we run it. When Rubrik works against Dell PowerStore and MongoDB, along with SQL Server, we noticed that PowerStore's QLC is normal while its CPU and compression levels are good. But, we do face a delay in CAPA and the server. So definitely, we noticed that maybe we need to upgrade everything to 25 gigabit, and still, if it doesn't work, then we may consider FortiGate's networking. Dell Compellent was our storage before, and now we are pushing the Ethernet to the maximum with PowerStore.
What is most valuable?
Three years ago, I was a little scared about PowerStore because I have been working with storage solutions for many years and have a habit of maintaining additional storage machines, firmware, interfaces, and so on. I noticed that PowerStore is a totally virtualized solution. PowerStore runs container, docker, and so on, and the firmware is managed in a different manner, which is a good point for total virtualization of the firmware and so on. But on the contrary, it's like a black box for me. It is different to work on PowerStore compared to IBM. I worked in the past with IBM ESS 800 Shark Storage. The type of super virtualization in PowerStore is a startup feature. A digital machine is present inside the storage server when this startup feature is launched. This digital machine can be managed entirely remotely, with an automatic download available from Dell. We started with the solution's initial version three years ago, and now we are working on one of its latest versions.
What needs improvement?
Now we are not pushing the PowerStore to its maximum capability, so we are down in respect of the limit of PowerStore we use in our organization. For now, the slackness is ours, not PowerStore's. I'm not able to tell what can be improved since we are not pushing to its maximum speed. Also, we haven't experienced any downtime, and we switched from primary to secondary and so on, and there has been no problem. Initially, we had some problems with the firmware, and it was a serious problem. But, after six months, we upgraded two or three times, after which we didn't experience any problems. So, we never faced any problems or significant failures for two and a half years. We have a double installation, including primary and secondary ones. Also, in the initial six months, even if we had some errors, we never got a stop error. We never stop. Hence, we never stop the protection system. We only have a secondary type of error, which is for one of the parts of the solution but never for the software side.
The only thing is that with PowerStore, we don't have a solution for the file object. Because of this, we have been investigating Zephyr and another solution. We are also thinking of not buying anything in our data center. We are also evaluating a proposal from a provider named Wasabi, which provides an alternative to Amazon S3. Also, we want to follow a totally different approach so that there is no more spending or investments inside our hardware infrastructure, and we depend on just pushing it with the help of an external provider. Vaulting is another approach we may opt for, but we may not do it now since we are using Rubrik for vaulting. A good improvement for PowerStore would be to have an embedded vaulting feature. Currently, two providers of block devices offer vaulting capabilities, allowing for signing within multiple objects or on a partition. In such cases, this feature would be beneficial if you want to freeze a part of your storage or apply differential computing. This strategy involves preparing a disk for a machine and deploying ten machines based on multiple basic installations.
For how long have I used the solution?
I have been using Dell PowerStore for more than three years. I am a customer using the solution.
What do I think about the stability of the solution?
The stability has been excellent in the last two years after the initial six months. Stability-wise, I rate the solution a ten out of ten.
What do I think about the scalability of the solution?
I am unable to comment on the solution's scalability since we have no plans in our company to scale up and also because we are only using half of the potential of the solution. I cannot tell if adding another node to the solution is easy or not.
How are customer service and support?
The solution's technical support is excellent. I rate the technical support a ten out of ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We were previously using Dell Compellent in our organization. Before that, I worked in a different company using HPE 3PAR.
How was the initial setup?
The initial setup was complex and difficult, and we had to rely on the assistance of an Italian partner in Bologna under the name Cinetica. We initially planned for four days over two weeks, with two days set aside for the first week to prepare all the necessary networks for networking and another two days for the second week to start up PowerStore. However, the process took more than ten days, and we received a machine with firmware series one dot from Dell's headquarters. I cannot recall if it was one dot zero one or one dot zero two, but we encountered an issue during the initial setup. After completing the initial setup, we immediately switched to Dell PowerStore Version 2. If the machine had arrived with pre-installed PowerStore Version 2, we might not have encountered this initial problem. The main issue arose in the mapping and network features from the volume exposed by PowerStore, including MLAG, LACP, and the corner configuration in the internet reports. A large number of cables and fiber also made it difficult to align the procedures, with a ton of files on the console level.
If I were to install the latest version of the solution in 2023, with the last firmware and its additions, the setup process could be more reasonable. It would be possible to start the entire high-availability solution in four days with a double installation. However, the complexity is also related to the fact that if all production environments require at least a couple of PowerStore solutions, even if only one can be purchased, it is normal to have a high-vulnerability environment. I rate the setup process a three on a scale of one to ten, where one is difficult and ten is easy.
Regarding the deployment process timeline, during the dry run testing, we created an initial copy of a portion of SQL Server storage that Compellent was managing. During this phase, we were required to run the exact production workload without any interruptions to the production environment. This phase took us approximately one month. After completing the dry run, we decided to copy the storage from Rubrik to restore all the data to the logical number allocated to PowerStore. We then made adjustments because it was an iSCSI target, which meant changing the worldwide domain in the iSCSI target for the SQL Server machine.
What's my experience with pricing, setup cost, and licensing?
Our organization spent two months considering its budget and economics. We got TRESIO and Excel's expected storage size and special compression, and because of this, we could save some money since the compression is working very well. In the end, we bought a solution that was half the size of the initial solution, and we got a compression ratio of about five to one, which was a win-win solution. With compression, we were able to have a solution within our company's budget. We include a clause in the contract with Dell that states if the compression ratio is not met, we will adjust the workload accordingly. In this scenario, Dell support will provide additional hard drives free of charge to be added to the PowerStore. There was Dell's competitor on our side, and they were supportive of our decision to give hard drives to buy to improve the functioning.
Which other solutions did I evaluate?
It's important to note that we evaluated another option quite different from a manufacturer, CentOS. However, we cannot say that we were able to make a fair evaluation between a small manufacturer and Dell, as economics played a significant role in our decision-making process. If I can freely test other environments, I would test solutions from IBM and Lenovo. IBM is a large manufacturer, and CentOS is a competing technology. VMware provides a software-based shared mapping storage technology, which emulates disk storage. CentOS is attempting to emulate VMware's vSAN technology.
What other advice do I have?
It isn't easy for me to rate the solution because inside my infrastructure, PowerStore is the biggest one, and the other storage solutions we use only for secondary and unimportant projects using storage like NETGEAR. It is very difficult to give an evaluation considering my current infrastructure because I have only a PowerStore in my company. Earlier, I was able to make comparisons because I was using HPE 3PAR and IBM solutions in my previous company. Dell PowerStore is better than HPE 3PAR since there are a lot of changes and updates needed in 3PAR. I rate the overall solution an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.