Veeam Data Platform Reviews

I started working with Veeam because of its replication capabilities. Later on when version 7 was released, with the addition of the tape support, I started migrating to pure Veeam environments.

Tape support is still not performing as expected (at least for my opinion) as Veeam relates to tape backup as a repository instead of a long term archive. Schedule options can be improved.

No but you need to pay attention to small things that make a big difference. 

Usually it runs very smoothly.

No, I have one rule regarding Veeam, use proxy!

I used to work with Symantec backup exec / System recovery, IBM FastBack and Arcserve each one of them has its strength and weaknesses. The reason I switched to Veeam was the native support for virtual environments.

Pretty straightforward and intuitive.

I'm an integrator so I can't rate myself.

I've tested CA ARCserve High Availability (formally XoSoft) IBM FastBack (formally FilesX) and Double-Take Availability.

Granular restore and Vmware integration.

We are able to restore VM very fast, with 0 downtime.

More APIs with storage from different vendors.

2 years.

Issues with deployment - none.

Issues with stability - none

Issues with scalability - none.

Very good.

Very good.

HP Data Protector, we switched because Veeam was easier to manage and deploy.

Straightforward.

In-house one, my team has excellent expertise.

Almost instantly.

Like 9000€.

None.

Don't hesite to contact a Partner and ask them for a demo, you will love it!

Backup, Restore, Replication

Very fast & reliable backup, less management, fast restores

Being able to do both VMware & Hyper-V backups at the same time. At the moment, as far as I know, you can only do one or the other.

3 - 3.5 years

No deployment problems, super easy.

No stability problems, very stable.

No scalability issues, easy to scale.

Very good.

Very good.

Yes, Symantec Backup Exe. It never worked well work virtualization. Backups always failed & spent too much time trying to figure out why it did not work & how to fix it.

Easy, very straight forward using current technologies.

In-House

I think about $8,500

Yes, VMware backup solution, Acronis, Symantec

Go ahead, super easy & good product

2-in-1: backup and replication

Sandbox and Open FIles

Instant VM Recovery

I believe none.

For almost 3 Years.

No.

No.

No.

Good.

Good.

Was using Symantec.

No, very user friendly.

In-house.

we implemented as demo lab for ours partners to test.

Was an NFR.

No.

If they have any doubts, first try a POC... Will help to decide.

We use Veeam Backup Replication to backup our system data.

Veeam Backup Replication could improve by having more comparably with other hardware with the immutable copy feature.

I have been using Veeam Backup & Replication for approximately three years.

Veeam Backup Replication is stable.

I have found Veeam Backup Replication to be scalable.

The support that we have been receiving has been perfect.

The initial setup is simple to do in Veeam Backup Replication.

The single licensing model for the customers is a benefit, it includes many features such as ransomware and other protections.

The price of Veeam Backup Replication is reasonable.

I rate Veeam Backup & Replication a ten out of ten.

We are using Veeam Backup Replication for server and virtual backups.

The integration of Veeam Backup Replication is very good.

The parallel backup process from the Veeam server to Veeam has some limitations. The number of parallel backups should be increased and the compressional is very low. Sometimes it is half or one-third, but other backup solutions' compression levels are very high.

I have been using Veeam Backup Replication for approximately two years.

I have found Veeam Backup Replication to be stable.

The solution is scalable. However, with other systems, such as physical Linux servers, the integration with different applications is not very good and there can be some issues. Sometimes they are not fully integrated with the application.

 In my case, there is no technical support needed.

The Veeam Backup Replication initial setup was very easy.

I did the deployment myself.

We use the community edition of the Veeam Backup Replication and it is a software-based license. It can be a little expensive.

We did not evaluate other options.

I would recommend this solution.

I rate Veeam Backup Replication a seven out of ten.

The most valuable feature of this product is that you can replicate VM between different platforms or different VMware clusters

The product is still limited in terms of support for environments other than VMware or Microsoft.

I haven't seen any problems with the stability of this solution.

Scalability depends but it's much better than it used to be.

The technical support does not compare well to other providers.

The setup is straightforward, but for bigger customers it can be harder.

I would rate this solution eight out of ten.

We use this solution to backup our files and virtual machines. 

We use this solution to backup information for our customers. We back up our customers' servers and store the information on local networks. This way, if something goes wrong, we can easily recover the information from our backups.

We have 40 machines that we backup with this solution.

Its backup capabilities in general are great.

My problem with backup software is the following: The main advantage that all of this software strives for is the ability to store data on a proprietary file system. When you look at the backup files stored in Veeam and other solutions, you cannot directly see the real files. Instead, you see a file structure where the backups are stored inside. This means if you lose the configuration of your backup machine, you only have files stored in a kind of file system that you just cannot get data from. I prefer backup solutions that allow me to regularly look at my backup files — to see the actual files.

I prefer a software backup solution that allows me to easily define my origin data, including data files, folders, and virtual machines. On the targets, they are stored exactly how they are. If it's a virtual machine file, I can find the virtual machine file stored somewhere. I cannot find my folders in a file structure that I don't understand what's in it. I understand why many backup solutions have this kind of file structure; however, this means I also have to have a full backup of the recovery system of my definition configurations.

I don't really like the proprietary file system or file structure, I always prefer the most simple functionalities where I can define this server, this file, these folders, backing up for this target, etc. I am not a fan of cloud storage for backups. Otherwise, I have to have another backup solution or my SAS backup cloud. In short, I am making backups of backups of backups. For me, that's a nightmare.

I have been using Veeam Backup & Replication for roughly two years.

Both the scalability and the stability of Veeam Backup & Replication are good.

Normally, I never need to contact technical support. I guess I would need to if I were using Azure cloud storage, but I don't use Azure for storing backups. As I said, I don't trust the cloud for backups.

We also use some other solutions, but they are open-source, not commercial solutions. We still use a lot of open-source backup solutions because they actually do what we need. They grab data from one place and they store it where we want without storing it in a special data structure. They store the files exactly as they came from the origin; they go to the target and that's it.

The initial setup is straightforward.

We don't pay for this solution, our customers do.

One thing that I enjoy with some open-source solutions is that they're normally the fastest to implement.

With open source solutions, if I have a server and I need to backup something into a folder, either an internet folder, a shared folder on the local network, or a local storage folder, I do not have to have these folders open on the origin system. I only open these folders at the time of transmitting the files, and then they are closed automatically. This means I do not have these folders open if I don't need them because it's safer that way to prevent ransomware attacks and so on.

As I said, don't trust the cloud. If you use the cloud, be sure to have a backup of the cloud. Testing is much more preferable on-premises. This on-premise location can be the local office of the company where you are doing it from, and also remote offices. Just don't use a cloud where you don't know where the server is. 

On-premises, when I say "cloud", I mean the internet. I can have an office in London, and if I want to back up on-premise, I do it on the local storage. I don't use general clouds like Azure. I have a server where I know where it is in some location and I remotely back up into that server. I don't buy storage on clouds. I'm really not a good customer for that. I don't trust them. They're excellent, they are really what people say are the future, but I have experienced too many disruptions on clouds. If I go into a software solution where I have to move the cloud, this obligates me to also have a solution to backup the cloud. I don't want to have these two solutions going from the office to the cloud and then also backing up the cloud — it's a nightmare.

Overall, on a scale from one to ten, I would give this solution a rating of eight.