Share your experience using Dell ProtectPoint [EOL]

The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.

Use our online form to submit your review. It's quick and you can post anonymously.

Your review helps others learn about this solution
The PeerSpot community is built upon trust and sharing with peers.
It's good for your career
In today's digital world, your review shows you have valuable expertise.
You can influence the market
Vendors read their reviews and make improvements based on your feedback.
Examples of the 83,000+ reviews on PeerSpot:

Cassandra Cinar - PeerSpot reviewer
Senior Director Data Center Services at a media company with 5,001-10,000 employees
Real User
Top 10
Provides excellent visibility and helps reduce costs and time
Pros and Cons
  • "The features I find most helpful in Commvault are its ability to perform incremental backups and significantly reduce backup times for our diverse multi-architecture, multi-environment environment."
  • "Commvault could benefit from increased automation to streamline processes and enhance predictability."

What is our primary use case?

Commvault handles our backups across both cloud and data center environments. It manages our short-term backups on-premises, followed by a transfer to disaster recovery for data older than 30 days, ultimately migrating them to long-term storage.

We are seeking a solution for secure and encrypted backups that comply with both our information security policy and the data retention requirements for database archive logs. Additionally, these backups must fulfill all customer service level agreements for all storage under our responsibility, including NAS, SAN, and any other backup methods specified in our service catalog.

Our deployment model is a hybrid of public cloud, private cloud, and on-premises infrastructure. We primarily use AWS as our main cloud provider, with Azure as a secondary option.

How has it helped my organization?

We use intuitive administrative tools that readily reveal the volume of backed-up data. Our Commvault CommCell servers alert us to failed backups and provide detailed information. This transparency allows our managed service provider to easily grasp our pre-established thresholds and readily scale up with new technologies.

We're highly satisfied with Commvault's automated data security and management policies. They meet our stringent requirements for secure and private data storage, including anti-ransomware protection and encryption. Notably, they also ensure compliance with GDPR for backups stored in Europe and other regions, fulfilling our regulatory obligations.

Threat Scan's ability to scan backup data for threats is invaluable because it proactively identifies and neutralizes certain viruses and threats that may originate from our G Suite or be reported by our security incident response team, preventing potential outages.

Commvault provides excellent visibility across our entire organization's data. They perform regular health checks, informing us of areas of strength and offering recommendations for improvement. These recommendations may include upgrading to newer product versions or addressing issues identified during the checks.

It is important for our organization that Commvault provides a unified platform for recovery across cloud, on-premises, and software-as-a-service workloads. This is particularly important because many of our existing cloud environments rely on basic backups that are insufficient for our needs. Commvault empowers us to address this issue. We have implemented it not only in our own operating company but also across the corporate structure, rolling it out to virtually all AWS users. This is because the standard backup methods, such as snapshot backups, fail to meet our stringent requirements for recovery, service level agreements, and crucial functionalities like threat detection and other security features. Commvault ensures a robust and comprehensive backup infrastructure that satisfies all our essential needs.

It has improved our organization by ensuring we meet our infrastructure requirements, adhere to our vulnerability methodology, and achieve service level agreements for both backup and storage requirements.

The quarterly risk analysis allows us to effectively manage the lifecycle of both data and backups. It also sheds light on the types of data and backups we have, providing valuable insights.

Commvault's risk analysis is one of the tools we use to meet our compliance requirements and implement the necessary controls for immediate security policy action.

To ensure comprehensive data protection and comply with international regulations like GDPR, we rely on Commvault alongside our established financial systems and SOC-compliant practices.

Commvault has helped us reduce our organization's data management costs by 75 percent, particularly for long-term backups. We ditched tapes and virtual tapes thanks to Commvault, replacing them with a fully disk-based backup system and cloud backups in AWS and Azure.

By implementing Commvault, we've significantly reduced our backup times. This is achieved through a combination of incremental backups and data aging. Aged data is then moved to cheaper disk or cloud storage, ensuring cost-effective long-term retention while still meeting our recovery SLAs. While the overall time savings may be around 10-15 percent, the main benefit is not keeping everything on expensive primary storage and efficiently aging it out. Consequently, retrieving data from the Azure bucket typically takes five days or more, reflecting our agreed-upon SLA.

It has reduced our recovery point objective, allowing us to store more backups. However, new regulatory and compliance requirements mandate that some backups cannot be deleted and must be retained indefinitely. To address this while still improving efficiency, we've implemented solutions for long-term data storage and improved data management practices.

Commvault has helped our organization not only decrease our threat detection time but also improve threat prevention to such an extent that we often avoid facing the full impact of a threat altogether. By preventing these incidents, we're often unsure of the precise amount of time saved, but the benefit is clear: we don't need to activate disaster recovery mechanisms.

It has not only helped us reduce our recovery time objective, but it has also ensured that our backups and long-term storage are secure, thanks to its comprehensive capabilities.

In terms of total cost of ownership, Commvault has enabled us to significantly reduce both hardware and media costs for storage and backup. After factoring in encryption and compression, the total savings amount to close to 80 percent.

It has been able to reduce downtime, but having a quick recovery plan and policy and SLAs that are published are met regularly.

What is most valuable?

The features I find most helpful in Commvault are its ability to perform incremental backups and significantly reduce backup times for our diverse multi-architecture, multi-environment environment. This includes everything from Cisco equipment to IBM equipment, as well as SAN and NAS storage. Commvault allows us to back up these systems quickly and efficiently, and even recover data at equally impressive speeds.

What needs improvement?

Commvault could benefit from increased automation to streamline processes and enhance predictability. This includes automating routine tasks where appropriate, which would improve efficiency and reduce the need for support tickets. Additionally, when support is required, automating elements of the process and providing faster data access would enable quicker issue identification and resolution, preventing potential SLAs from being breached.

For how long have I used the solution?

I have been using Commvault Cloud for seven years.

What do I think about the stability of the solution?

We haven't had problems, so Commvault is a very stable product from our perspective.

What do I think about the scalability of the solution?

Commvault is highly scalable. We've successfully extended its reach by replicating the on-premises environment in the cloud and leveraging additional capacity across other utilized environments. This flexibility aligns well with the subscription licensing model.

How are customer service and support?

We don't send many support tickets because Commvault is very reliable. We mainly handle user inquiries about how to use the product, conduct regular quarterly reviews, and provide dedicated technical account management.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Our primary backup solution has been Commvault, although different teams have utilized IBM Tivoli and other capabilities like Rubrik in the past. Commvault's stability and cost-effectiveness have solidified its position as our preferred choice.

How was the initial setup?

The initial deployment was straightforward, except for some network connectivity issues related to specific aspects of connectivity, e.g., bandwidth, latency, and routing. Thankfully, there were no significant problems with the tool itself.

Our strategy was to be able to connect globally, from our data centers to our cloud solution.

Our deployment involved six individuals: two working on AWS, two on-premises, and two at the disaster recovery site.

What about the implementation team?

We implemented our solution using Accenture, our third-party managed service provider. This was beneficial because we could leverage our existing relationship and account team, who were familiar with our environment. Their expertise proved invaluable during upgrades and major changes. Furthermore, we obtained the necessary technical skills and support from both Commvault and Accenture.

What was our ROI?

Preventative measures against outages limit their impact on customers, thereby maintaining near-perfect SLAs. This translates to increased customer satisfaction and minimal business disruption, which essentially constitutes our return on investment.

What's my experience with pricing, setup cost, and licensing?

Using a subscription-based license has been advantageous. We've been able to significantly reduce costs by tailoring our spending to our actual usage. This is a stark contrast to the earlier model with its prohibitively high fixed-price licenses.

Which other solutions did I evaluate?

After evaluating Rubrik, we compared it to our existing backup solutions: AWS backups used by other teams and the IBM Tivoli TSM environment. The key differences between these options lie in their deployment and recovery capabilities. Some solutions are cloud-based, while others require on-premises infrastructure. Additionally, some have limitations in recovering data from specific environments, making them less suitable for multi-site backup scenarios.

What other advice do I have?

I would rate Commvault Cloud a ten out of ten.

Transitioning from various solutions made implementation quite smooth. However, due to its extended use, we lack a comprehensive baseline for evaluation. We simply don't have enough prior cases to compare Commvault's implementation difficulty against.

Our company has implemented a large-scale global deployment with 5,000 endpoints across multiple data centers, regions, locations, and cloud providers.

We perform standard upgrades on both the Commvault servers and the storage environments NAS and SAN we deploy. These upgrades are determined by the operating system requirements of the Commvault servers. For short-term backups, we utilize on-premise storage, while long-term backups leverage AWS cloud storage.

While customer references are valuable, the ability to tailor our environment to meet our specific needs is equally important. This means defining the backup architecture based on the specific requirements of each application, like SIP shares and databases. Each application has unique needs, so understanding those requirements is crucial for crafting the right architecture to fulfill them.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Derrick Brockel - PeerSpot reviewer
Senior Manager of Operations at a comms service provider with 10,001+ employees
Real User
Top 5Leaderboard
Good GUI, easy setup, and fast recovery
Pros and Cons
  • "Zerto offered a very good front-end GUI for orchestration. The graphic interface was very good."
  • "The replication layer can probably be improved."

What is our primary use case?

It was a pilot. We did a bake-off between Zerto and RP for VM, which was an EMC product. It was to fail over 130 Oracle databases.

We wanted to handle disaster recovery for our data center. Zerto was mainly a failover product. We did not use any security layering.

How has it helped my organization?

When we tested it, it had more functions than what we used it for, but it was a very good BCDR product. We liked the reliability and availability.

Zerto enables you to do disaster recovery (DR) in the cloud, but we did not use that feature. We used Zerto to help protect VMs in our environment. It was strong in that aspect. I would rate it an eight out of ten there.

Zerto's speed of recovery was comparable. There was no synchronous and asynchronous replication. If I had to give it a number, it would be a seven out of ten. It was the same as others. There was not much difference.

It was easy to migrate data. There was some initial configuration in syncing, but it was easy. I would rate it an eight out of ten in terms of the ease of migration.

Zerto’s ability to keep our users collaborating with one another during a data migration was good. I would rate it a seven out of ten in this aspect as well as in terms of its impact on RTOs.

Zerto helps reduce downtime in any situation. We can bring up a database in minutes. It probably takes five minutes for the final sync. The cost of downtime depends on the database. It may be 50,000 if you have call center people sitting around. Normally, most of our small outages like that ranged in the tens of thousands.

Zerto did save time in a data recovery situation. We did not have ransomware, but there were times we had database corruption where the users would corrupt the database, and the database would not start. It would do snapshotting. It was not necessarily ransomware, but it was testing upgrades or Oracle upgrades. The data recovery happened within five minutes, if not sooner. A normal restore would probably be four to eight hours if we had to restore from a tape and apply logs.

Zerto helps to reduce an organization's DR testing. You can spin off an extra database pretty quickly and have users test against the third or fourth copy. It saves one to three days of testing depending on test cycles. You could do sequential testing. I would probably measure it more in days than hours. All of that time can be used by a DBA to do something else.

Zerto reduces the number of staff involved in a data recovery situation. One person could probably orchestrate it now versus one to three people.

It did not reduce the number of staff involved in overall backup and DR management because we are pretty thin. We would not have gotten rid of anybody.

What is most valuable?

Zerto offered a very good front-end GUI for orchestration. The graphic interface was very good.

What needs improvement?

The replication layer can probably be improved.

For how long have I used the solution?

We ran the pilot for about nine months. 

What do I think about the stability of the solution?

I would rate it a seven out of ten in terms of stability.

What do I think about the scalability of the solution?

I would rate it a seven out of ten in terms of scalability.

In terms of our environment, we had 130 databases, 35 prods, and 2 data centers. In terms of end users, in our call centers, we had probably 10,000 users who accessed the databases.

How are customer service and support?

They are good. 

How would you rate customer service and support?

Neutral

Which solution did I use previously and why did I switch?

We used VMware SRM. We used Veritas clustering, which was a Veritas/Symantec product. We then went virtual, so we went from physical to virtual infrastructure, and we went from HP-UX to Red Hat infrastructure. Zerto was probably 50% easier than others.

Zerto has not replaced any backup solution.

How was the initial setup?

It is a private cloud deployment. It is all VMware vSphere.

Its initial setup was straightforward. It was not as complicated as any other product. It took two to three weeks.

In terms of the implementation strategy, we wanted to reduce our synchronous synchronization. We wanted a better RTO, so we went to an asynchronous replication on private network infrastructure for faster syncing. There were a few technical aspects, but we took our time to lay out the network infrastructure.

In terms of maintenance, you have to patch it and upgrade it. We have a team of four for backup and storage.

What about the implementation team?

Zerto helped us. They had very good staff. We got great support. I would rate them a seven out of ten.

We had two people working on that project, primary and secondary. We did use some of the networking team, maybe a half-person worth of time, because it is a little network intensive.

What was our ROI?

It is hard to measure an ROI. It is more like an insurance policy. You may or may not use your insurance policy, but it provides comfort to management. There may also be some soft cost.

What's my experience with pricing, setup cost, and licensing?

It was a little higher. We were in a corporate agreement, and we had a software package that included RP for VM. It is easy to compare pricing when you are already in a corporate agreement. Zerto lost on the pricing scorecard.

Which other solutions did I evaluate?

We evaluated Zerto and RP for VM, which was an EMC product. They were different in replication logic and how they did journaling.

In Zerto, the replication is done through vSphere, and they did not license that product, so at any point, they could have probably lost it. We licensed RP for VM. We felt more comfortable with an EMC replication product because it was Dell and VMware combined or merged. The replication in Zerto was good, but it was using VMware hypervisor replication.

What other advice do I have?

To those evaluating this solution, I would recommend doing an architectural design and implementing best practices. Involve your network team early and use Zerto's expertise.

I would rate Zerto an eight out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate