What is our primary use case?
I've used it for a variety of use cases, including backing up data for some banking and telecom customers. One of the most common use cases is backing up two appliance applications after a backup.
I use it for disaster recovery because, for many enterprises in our country, the backup solution is one way to have disaster recovery. We have replication disaster recovery for using backup, and it is in this case that I deployed some mini-solution backup.
How has it helped my organization?
This solution is just for disaster recovery purposes. Businesses need to have a disaster recovery solution in place, especially those with many computers. This solution can be used for replication or backup. It is mandatory for many telecommunications enterprises and some banks.
What is most valuable?
The most valuable feature is replication because, using NetBackup replication, we can have disaster recovery of the data we have.
What needs improvement?
The improvement of Veritas NetBackup is the way we have to back up many infrastructures, such as Nutanix, and OpenStack, and new operating systems and applications, such as MySQL, Postgres, and MariaDB. This is a new improvement that has been added to NetBackup. We have also made some improvements to the cloud.
For how long have I used the solution?
I first deployed the version 5.0. I also deploy it for many clients. My country is Côte d'Ivoire, and I have deployed this solution here. I have also deployed it in Mauritius, Singapore, Guinea, and many other countries.
What do I think about the stability of the solution?
The Ethernet backup solution is stable, quite stable. But, for some features like BAMINI-TO-Restore, the new version doesn't have the appropriate support. We have some issues when attempting to create a desktop, especially for a specific version of Linux.
With Windows, we didn't face any problems. But when it came to Linux and Solaris, we experienced many troubles when attempting restores for a certain period.
But, for Oracle, Exchange, SQL, and so on, I found it satisfactory for performing restores. It's mainly the BAMINI-TO-Restore component that caused some trouble, both for Linux and Solaris restores.
What do I think about the scalability of the solution?
There is a big change in Veritas. In the past, we could easily change servers or appliances and continue working by restoring the catalog. We could change servers from Linux to Linux or Linux to Solaris and perform catalog restores to continue working. But with the new version, we are forced to engage Veritas' professional services, which is too expensive. Sometimes, we've received quotes exceeding $100,000 for a catalog migration.
This expense was unnecessary in the past. For instance, we used to install a new release of Linux and simply restore the catalog, and the system would function well. But with the latest version, it's no longer feasible.
For instance, if we want to migrate from appliance 5030 to 5060 or even just 5050, we are compelled to engage Veritas consultants due to the intricate data manipulation involved. This additional expense is quite expensive. In the past, these devices didn't even exist, and we could easily restore the catalog, resulting in a fully functional system. However, the new version demands expensive expertise for such tasks, which I find unacceptable for our clients.
How are customer service and support?
Currently, I find the setup problematic. When I compare the support we receive now to what we had in the past, it's clear that the support has become less responsive and reactive.
So when we had some trouble with the solution, we had many difficulties in getting the satisfaction in a short time. The support level goes down. There are three levels of support, but we get the basic level of support.
Because when I open a support case, I've usually already checked all the technical notes available on the Veritas site. Surprisingly, the support team often provides me with the same documents I've already reviewed. And when I try to escalate the issue for a quicker resolution, they are not ready to do so. So, in my experience, the support quality is not good for me.
How would you rate customer service and support?
How was the initial setup?
I deployed it back on-site in 2007. The initial deployment was not complex. We didn't encounter any complexities for the data types we usually work with, such as data SAP and other data in our area. But, with new types of data, like net earnings or OpenStack, which are relatively new for us, there might be some challenges. But with documentation, we can do it.
What about the implementation team?
In my company, I'm the expert responsible for designing solutions, creating architectures, and handling deployments.
I am involved in the entire process, right from the beginning to the end. I receive offers to design solutions and architectures. After that, when we have a clear view, I handle the deployment of the solution.
What's my experience with pricing, setup cost, and licensing?
As for the price, it's quite expensive, actually. It is expensive. If you want to make a comparison, for example, with Acronis Backup or Avamar, other solutions used here, NetBackup is indeed on the costly side.
The NetBackup appliance, specifically the appliance license is expensive. That's why some clients opt for alternatives like Veeam for virtual machine backup.
What other advice do I have?
Overall, I would rate the solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises