What is our primary use case?
In terms of use cases, I'm very familiar with the environment and the platform. I've been using it for the past six years. I mainly rely on it to manage the users on the platform and resolve any issues they may encounter. If there's a problem beyond my expertise, I open a support case.
How has it helped my organization?
In terms of backup installation and business continuity, VM has been invaluable. There was a time when we had an issue with one of our systems, and Veeam became unavailable. This particular Azure machine is utilized in about six or seven countries. All I had to do was log into my Veeam account in that location, activate the Continuity and Recovery (CR) feature, and everyone could resume working. It involved changing the IP address or the capabilities of the application server since the assessment is based on the application server's availability in another location. The IP addresses would vary.
So, I informed the application department to make the necessary modifications, and they immediately restarted the system for use.
What is most valuable?
Security is one of the most valuable aspects. In VM Backup, encryption is enabled as well. Depending on your backup job, you can increase security by setting up encryption and assigning a password.
The encryption password is used to protect the backup files. Even if someone gains access to the backup job or files, they won't be able to utilize them without the password.
What needs improvement?
In terms of improvement for VM, I believe we should focus on reducing data leakage and addressing a specific issue. There's a situation where VMs run on different locks. It's running on the VM while having a relationship with nearby solutions running on the same server and storage. This creates a bottleneck that needs to be eliminated. The efficiency of the solution should be improved.
For how long have I used the solution?
I have been using it for six years. We are currently using version 11 in our environment. It's located in a different place.
What do I think about the stability of the solution?
It's very stable. I would rate it as a nine.
What do I think about the scalability of the solution?
In terms of scalability, it is fantastic. I would give it an eight for scalability. Currently, we have around 500 users utilizing it for the HQ. We plan to expand the usage in the future.
I've recently tried using version 12. Although I haven't used it for long, I find it nice. I'm currently using it for one of our main offices at the HQ. It hasn't been fully deployed yet, but we're considering deploying it before the end of the year. The plan is to scale it within our HQ infrastructure because that's where we have the highest workload and need more information about different features available in version 12.
How are customer service and support?
The technical support is fantastic. When I encounter an issue, I simply need to contact the engineer who guides me through the process of uploading the logs. They analyze the logs and most of the time, they are able to provide a solution. The log analysis is crucial in identifying any problems specific to our environment. Sometimes, there may be delays if the issue requires further investigation, but the engineers are proactive in communicating and resolving the problem in a timely manner.
However, there might be instances where the problem lies with our internet connection, and in those cases, the support team may not be able to identify the issue solely through log analysis. In such situations, a remote session is highly beneficial as it allows them to have a deeper understanding of our environment, and combined with my own knowledge, it speeds up the analysis process and enables a prompt resolution. I appreciate the importance of a remote session in such cases as it facilitates faster analysis and helps in finding a timely resolution.
How would you rate customer service and support?
How was the initial setup?
The initial setup is very simple. I would rate my experience with the setup ten out of ten. I've been setting it up myself since 2015 for each of our countries. I handle remote activities and upgrades without needing to involve the team of engineers. It's a straightforward process, and I haven't encountered any difficulties.
What about the implementation team?
I work with my company's IT team to handle the deployment. It's done in-house. The deployment process takes around an hour.
Typically, I discuss the deployment process with my manager or attend a meeting to discuss the solution and get approval. It's not a cumbersome process and is quite straightforward.
What's my experience with pricing, setup cost, and licensing?
I would give it an eight. The only problem we face is when our support expires, and we need to renew. If we're purchasing a new license, that's when difficulties arise.
There are no additional costs or hidden fees. It's a straightforward pricing structure.
Which other solutions did I evaluate?
We tried using Micro Focus. Veeam Backup & Replication provides us with more than what we actually need, especially because of the application solutions it offers. Micro Focus, on the other hand, only focused on backup without additional application features.
What other advice do I have?
In terms of stability and efficiency, I highly recommend it. I've already introduced it to two or three different companies where my colleagues work, although I'm not sure if they have already adopted and purchased it.
Which deployment model are you using for this solution?
On-premises
*Disclosure: My company does not have a business relationship with this vendor other than being a customer.