It would be highly advantageous to include an integrated backup solution within the same license, rather than purchasing backup separately. It would ensure a comprehensive and streamlined approach to data management and protection.
I didn't implement it, but I saw many caveats with Portworx Backup. And today, we have other products that are far ahead of Portworx in terms of their backup implementation. They have not integrated Portworx with Ondat since they are too focused now on Pure Storage APIs and not on users like us.
One area where Portworx can be improved is with data locality. This is not always achieved, especially when we don't use VPS or when we don't have a sufficient number of worker nodes. Portworx generally guarantees data locality, but we have found that with a replica factor of two, we need six worker nodes to ensure data locality. Data locality is important because it allows data pods to find the data locally instead of going over the network. If the data is not locally present, it has to go over the network to get it. So data locality is an area that could be improved. Additionally, the documentation could be better. We have found quite a few bugs, and they need to improve the documentation to address this.
Diretor Comercial at a security firm with 1,001-5,000 employees
Real User
Apr 12, 2023
The integration has room for improvement. Currently, Portworx Enterprise does not support Google Cloud or Oracle Cloud. The price has room for improvement.
Director of Information Technology at a logistics company with 10,001+ employees
Real User
Oct 15, 2021
I would like to see a more native mapping to mainframe-type systems. At some point, the older dinosaur mainframes will either be phased out of the industry, or the mainframes will be built to at least modern standards.
Portworx is the solution for running stateful containers in production, designed with DevOps in mind. With Portworx, users can manage any database or stateful service on any infrastructure using any container scheduler, including Kubernetes, Mesosphere DC/OS, and Docker Swarm. Portworx solves the five most common problems DevOps teams encounter when running stateful services in production: persistence, high availability, data automation, security, and support for multiple data stores and...
It would be highly advantageous to include an integrated backup solution within the same license, rather than purchasing backup separately. It would ensure a comprehensive and streamlined approach to data management and protection.
I didn't implement it, but I saw many caveats with Portworx Backup. And today, we have other products that are far ahead of Portworx in terms of their backup implementation. They have not integrated Portworx with Ondat since they are too focused now on Pure Storage APIs and not on users like us.
One area where Portworx can be improved is with data locality. This is not always achieved, especially when we don't use VPS or when we don't have a sufficient number of worker nodes. Portworx generally guarantees data locality, but we have found that with a replica factor of two, we need six worker nodes to ensure data locality. Data locality is important because it allows data pods to find the data locally instead of going over the network. If the data is not locally present, it has to go over the network to get it. So data locality is an area that could be improved. Additionally, the documentation could be better. We have found quite a few bugs, and they need to improve the documentation to address this.
The integration has room for improvement. Currently, Portworx Enterprise does not support Google Cloud or Oracle Cloud. The price has room for improvement.
I think the vendor could provide more training for new users who may not be familiar with containers.
I would like to see a more native mapping to mainframe-type systems. At some point, the older dinosaur mainframes will either be phased out of the industry, or the mainframes will be built to at least modern standards.