Azure Backup Reviews

Our customers have VMs on their test environment that are backed up with Azure Backup for short retention, around one month. They need a machine that does not need integration with backup over BPE.

The most valuable feature is that it's very simple to configure which is very useful. It's not complex to configure it. 

I would like for the backup of VMs to be improved. The first thing our customers require is for me to back up their VM. I would like to do the backup using the integration. But I don't think the customers I am managing are ready for this yet. 

I have been using Azure Backup for around two to three years. 

It is stable. There are no problems regarding the backups. Some customers require a double copy of the backup. From on-prem to Azure or from Azure to on-prem or to another site. In these cases, it is necessary to use other software to perform the backup. 

The scalability is a great improvement that is offered on the cloud. With a few clicks, you can scale up resources. 

When you open a ticket, it is transferred to India. We've had problems that have taken two or three days to resolve. Their response time isn't so fast.  

I have used Commvault, Veeam, NetBackup - a lot of other softwares. The difference between these solutions and Azure is that they offered better options for backup across hybrid environments. It depends on what the customer is looking for. 

The initial setup is very simple. The time it takes to deploy depends on the environment. For a medium deployment, it will usually take one day to deploy. 

In my opinion, the price should be a little lower to be more competitive with other software. It depends on the customer's environment and subscription.

I would rate Azure an eight out of ten. 

To make it a ten, it should have the ability to extend the retention and to perform a copy of the data outside of the subscription - with no additional costs. There is a cost for downloading data on Azure or on-prem. If I would like to have a copy on-prem I need to pay more for the data. Azure should modify its policies. 

I am a consultant. We discuss what the customer is looking for and we'll recommend this solution based on their environment. Azure is easy and simple to configure. It's easy to use. If there are other requirements, I would recommend another software. 

Currently, I'm working on a project in a desktop environment where this is one of the solutions that is being used. It is a public-cloud deployment model.

We are using this solution to back up VMs and data from our customers.

The most valuable feature of this solution is the integration with cloud services. I do not have to use an external application, such as Veeam, to back up files or VMs. It works like a standard backup, which is very useful when you want to provide a secure backup environment for your customer.

This solution allows me to restore either the VM or the data, depending on what is needed.

Technical support for this solution is good but it can still be improved.

The user interface is a little bit confusing and it could be better. It took some time to learn, although I was able to read about it and adapt. For a customer without backup experience, it will take longer to get used to. The same goes for customers without cloud backup experience because the options differ from what existed in their on-premises solution.

The price of this solution is something they should focus on improving.

The backend of this type of solution is complex, so stability and security can always be improved.

This solution is stable and I haven't faced any issues while using it. It is as stable as Windows is, or as Linux is, so it is stable.

When I was working for HP we had our own private cloud for the customers, and it is not easy to stabilize everything, especially if you have several data centers around the world and you need to synchronize them. Once you add a new feature and it has to be deployed in all of them, it can be very messy.

This is a scalable solution.

Usually, my customers are small to medium-sized businesses with between ten and fifty users.

Technical support for this solution is very good. I can either ask questions in the forum or raise a call, and people reply to me right away. It is great.

I have used support from many big companies in the past, such as HP and Fuji. Also, when I first implemented this solution, people suggested that I do not take support from Microsoft. Rather, I should purchase a support contract from another company. I opted to test the Microsoft support, and I found that I am very satisfied with it. I would rate them between seven and eight out of ten.

Previously, we used other backup solutions, but this is our first cloud backup solution. We used to use NetBackup and a backup solution from HP, but these were on-premises deployments.

We chose Microsoft for this solution because they developed a data center in Switzerland, and the people there gave me a good feeling about it. I am really satisfied with this solution and support.

This is an easy solution to implement. I didn't need to obtain or read a lot of information. If you have experience in IT then you will find it easy to set up a basic configuration.

Deployment time for this solution depends on the environment. As an example, the last deployment that I performed was for a company with twenty-five users. It took five days to complete. Some of the time, of course, was spent in preparation. The deployment itself is really easy and short.

I implement this solution for my customers.

It may take several years before a customer sees ROI, but they will immediately gain in terms of security, stability, and automation.

The pricing of this solution is ok, but I'm expecting that the price will decrease in the future.  

I have used many different backup solutions, and in my experience, none of them will do everything. Each of them has pros and cons. You have to choose a backup solution based on several aspects including your knowledge, the price, the license, the support, how long the backup will be deployed, the agent, the stability, the scalability, and what it is that you are backing up. For example, in the past, the HP solution that I used did not support backing up a mailbox.

For our customers, we only needed a simple backup solution. With Azure Backup, it was easy because I didn't have to search for an external solution. I did not have high expectations, but it matched them and does what I need it to.

I came from a Unix environment in the past, and I was not really a Microsoft or Windows users. Now, however, I'm more confident with Microsoft products. I worked for HPE for a long time in a private cloud environment, and I really appreciate services that are well-integrated with each other and can be used right away, without having a great deal of Microsoft experience.

There are some services that different customers do not require, but everybody needs to have a backup solution as a prerequisite, whether they operate on-premises on in the cloud.

This is a simple backup solution. To understand, you can consider Unix as an example. We used to have a single backup command that worked from the command line interface, and it was sufficient. Then, dedicated backup applications were released. They were more complex with new features, handled new infrastructure, and handled new applications, but with that came bigger expectations. In this case, my expectations are small and Azure backup is sufficient for my customers. If tomorrow, for example, the customer's requirements change, then I may advise them to use Veeam, NetApp Cloud Backup, or another solution. 

My advice to anyone who is implementing this solution is to test the restore process regularly and to manage the backup of the data depending on the certainty of the restore. Even if the backup completes successfully and is stable, it doesn't mean that the data is not corrupted. This is the same advice that I would give for an on-premises backup. Be vigilant on that.

When it comes to this type of solution, sometimes you have to dedicate a specific engineer for a long time. They will train themselves and know everything about the backup. They will be able to troubleshoot and answer questions about the solution.

I would rate this solution a seven out of ten.

We provide solutions with Microsoft. The principal use is as a backup solution for the the Azure environment because we use 365 solutions.

This solution is deployed on cloud.

The most valuable features will depend on the environment and if you're using the cloud platform, or if you want to keep your backup on-premise.

I would like to see more automation, integration, and security. The price could be better.

I have been using this solution since 2004.

It's stable.

I haven't had any issues with technical support.

Installation is straightforward.

The price should be cheaper, but it's affordable if you use the yearly subscription.

I would rate this solution 5 out of 10.

The primary use case is for restoration purposes, disaster recovery, and to back up our normal processes for example restoration.

If any virtual machines go down then we can just recover from the previous restore point.

The most valuable feature is the ease in which it backs up our data. I would say that the process is quite simple.

The compression rate is not as good as some competing products, so it needs improvement. We have read that the compression rate is 20%, whereas Commvault is 60% to 70%.

We have a concern with the backup when were are working with VMs that are running in Barracuda Firewall because it usually fails. This is a prominent issue. If I have 100 VMs then two or three of the backups fail.

I have been using Azure Backup for approximately five years.

This solution is stable.

We have not had much experience the scalability or integration with other solutions.

We have more than 10 clients and we have approximately 500 individual machines.

We haven't contacted technical support because we have not had any issues.

Previously, we did not use any other solution. We have been using this one from the beginning.

The initial setup was quite simple.

If I have to configure a backup for one virtual machine it only takes five minutes.

This solution doesn't require any maintenance. If we have a problem Microsoft handles it.

We completed the implementation and we have not used a vendor or integrator to assist us

I am not aware of the pricing, as it is handled by the accounts department.

Currently, we are evaluating Commvault. I have read that it is good. We will consider other solutions that may be available with better facilities.

The setup is a very simple and easy process, it's easy to learn and use, and it is not very complicated to configure. Overall, it's a simple process.

I would rate this solution an eight out of ten.

I use Azure Backup in my client's company.

We are happy with this product and have not found any issues while using it.

We have been working with Azure Backup for less than one year.

This is a stable solution.

This is a scalable product. My clients are small and medium-sized companies.

The support is good.

The initial setup is easy.

The price is somewhat high and could be lower.

I am currently evaluating Acronis Backup. If there is something better then we will switch to using it.

I would rate this solution an eight out of ten.

We are a solution provider and this is one of the products that we implement for our clients.

Our customers use this solution for backing up their data to the cloud.

Azure Backup has given me the opportunity to offer a non-hardware backup solution to my customers. I try to improve their productivity by offering them this alternative if it is suitable for their scenario. We often conduct a PoC to see if it works for them.

My customers are very happy with Azure Backup.

The scalability is very good because it will scale to whatever we need.

The encryption is very good and I feel like the data is totally secure.

Customers often ask if it is possible to connect another device, and it is something that is very easy to do. There is no hassle.

It is easy to schedule backups.

I am happy with the documentation.

The price of this solution should be lowered because it is the biggest complaint from my customers.

Technical support is in need of improvement.

I have been working with Azure Backup for two years.

Azure Backup is easy to scale and it will scale up as much as you need it to. Also, I don't need to worry about whether it is serialized or not because the data is always structured.

My customers are small and medium-sized businesses.

Technical support by Microsoft can be improved. 

The deployment is not complicated and easy to do.

This is an expensive solution in the Bangladesh marketplace.

This is a product that I recommend for backing up data on the cloud. It is easy to use and manage, even for somebody with no backup knowledge. Overall, I think that everybody will be happy with it.

I would rate this solution a seven out of ten.

We primarily use the solution for disaster recovery.

The solution is cost-effective.

The backup features are very useful.

The solution overall is very reliable.

The interface needs improvement and it doesn't offer as many features as other third-party backup solutions.

The solution is still in its infancy; it's not a mature product yet.

The stability of the solution is good. 

The scalability of the solution is good.

As Microsoft partners, we get support when we need it. We've been satisfied with them so far.

Previously we were using Windows Network Backup as well as Veeam. Right now, we are testing Azure.

The initial setup is pretty easy. You literally load an agent from the servers to whatever machines you want to backup. It's pretty intuitive when you go into Azure to set it up. Deployment times depend on the bandwidth, and in South Africa, that can vary. It might take up to a day or so. Once you do your full backup, you're only doing incremental backups going forward, so it's just the initial setup and backup that might take a while.

I handled the implementation myself.

We're Microsoft partners.

We had issues before where there were no Azure Data Centers in South Africa. From a compliance point of view, backing up to outside the country was a bit of an issue. Now Microsoft has two data centers in South Africa, so it is no longer a problem.

I'd recommend the solution to others, but only if they have decent and reliable bandwidth. They should also make sure their alerts and monitoring are all set up to notify if the backups fail or succeed.

I'd rate the solution eight out of ten.

We have been this as our default backup solution since we migrated to Azure. We have both Windows and Linux systems in our environment.

This solution allows us to take complete Windows backups on a schedule that we choose. This can be hourly, daily, or weekly.

The MARS agent makes it easy to use.

There is no MARS agent for Linux, which is a problem for us because we have systems that use Linux Red Hat and Ubuntu.

There are other things missing in Azure that require us to use third-party tools. We would prefer to use Azure alone because it would be easier, as well as more secure.

The time required to restore files should be a little faster. It takes quite a long time to restore files at the moment.

We began using Azure Backup about six months ago.

Technical support is very supportive and they are giving me the best that they can do.

We began using Azure Backup as soon as we migrated to Azure from on-premises, AWS, and Oracle workloads.

We have no complaints about the deployment process, and everything installed fine.

We are currently evaluating options to back up our Linux filesystems.

While Azure Backup works well for our Windows systems, because it is not working with Linux, it is only doing half of the job that we need. If we had a MARS agent that worked for Linux then I would rate this solution a least an eight out of ten. It would allow us to use Azure as the only backup tool, without having to use products by third-parties.

I would rate this solution a five out of ten.