Azure Backup Reviews

We use the solution for VMs and SQL servers. 

I like the product's restoration cases. 

The tool's backup should be faster. Azure Backup's support should be faster.

I have been working on the product for four years. 

Azure Backup's stability is good. 

My company has around 1,000 users for Azure Backup. 

Azure Backup's setup is straightforward and gets completed in 10-15 minutes. We need to identify the backup frequency and configure it. We would need around six to seven people to handle the tool's deployment and maintenance. 

A consultant helped us with the deployment. 

I would rate Azure Backup an eight out of ten. 

Our primary use case is for backups.

The solution helped us use R2 RBO to back up frequently and avoid losing data if we had system issues.

The most valuable features are the integrations because we are using Azure Cloud, which backs it up with all the Azure components.

Azure Backup is constantly improving its features. However, it can be further improved by continuously meeting its compliance requirements.

We have been using the solution for three years.

The solution is stable.

I rate the solution an eight out of ten.

We use Azure Backup to backup VMs.

The most valuable feature of Azure Backup is its ease of use and good integration with other Azure services.

The Azure Backup support for on-premises service is limited.

The file-level restore procedure should be more straightforward.

I have been using Azure Backup for approximately three years.

Azure Backup is stable.

Azure Backup can scale and it is easy to do.

The initial setup of Azure Backup is straightforward. It took 15 minutes to do the deployment.

I rate the initial setup of Azure Backup a four out of five.

I did the implementation of the solution.

I rate Azure Backup a seven out of ten.

We use Azure Backup to have a backup on the cloud and save our backup.

There is only one feature, and that is the backup.

Actually, there is no issue. It simply saves your backup outside of your premises.

I would like to see better pricing.

I have working with Azure Backup for two years.

We are always working with the latest version.

Azure Backup is a stable product.

Azure Backup is scalable. It is easily expandable. To expand it is paid as you go.

Our technical IT department is the only one who uses it. In our company, there are four users. There is one manager, one assistant, and two staff members.

Technical support is very good.

Previously, we used standard company products.

I've used Avast before, but it's been ten years.

It's been five or six years since I have used McAffe MOVE AnfiVirus.

The initial setup is straightforward.

It is simply straightforward. You are not required to do anything.

I would rate my experience with the setup a five out of five.

It is all done in-house. There is no need for technical assistance.

Pay as you go is the pricing model.

I would rate Azure Backup a ten out of ten.

We use Commvault for on premises clients and the Azure Backup for cloud-based clients.

This solution is easy to configure and restore. It is a Microsoft product so is easily compatible with other solutions.

The restoration of permissions is a functionality that could be improved. If I want to restore permissions, I should be able to do this. 

Secondly, there is a limitation of 99 files restores per day which means that we can't complete a huge file restore. We would like Azure to increase the number of the possible file restorations.

I have been using this solution for five years.

This is a stable solution. 

This is a scalable solution besides the limitations on file restorations.

It takes a long time to resolve support tickets with the Microsoft support team. They could offer faster resolution of tickets. I would rate them a two out of five. 

Neutral

We use Azure Backup alongside Commvault Hyperscale X. The latter offers a compression ratio that is much higher compared to Azure Backup. There are no limitations on file restorations using Commvault. 

Azure Backup is free and we are only charged for storage. Commvault is definitely costly compared to Azure Backup.

The initial setup of this solution is straightforward, 

Azure offers competitive pricing and charges us only for the storage space that we use. 

We generally use the solution for VM backups. 

With a couple of buttons, we can configure a VM for a backup and use the wall service, the storage wall service, pretty seamlessly. 

From a day-to-day operation perspective, the installation and configuration of the Azure Backup and the backup timing are great. It offers a non-intrusive backup - like a snapshot type of backup. This way, we don't see any impact when running the backup and the job runs without any problem unless the VM host itself is having some problems. 

From the stability aspect of it, the execution aspect, I don't see any issues.

I didn't see any kind of major flaws or anything. The only thing I would say that could be improved is the reporting. It can be a little more customized or something like that. Maybe they need a little bit more on the dashboard view. The reporting and governance can be a little more fine-tuned.

I've used the solution for 18 months or so.

The solution is stable. The performance is great There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

We haven't really used technical support in the past. We went with them due to the fact that it's not a complicated use case for us, so we haven't really seen any issue. We haven't really dealt with Azure Backup-related troubleshooting or anything.

I work for a client who pays for the solution. My understanding is the costs vary year to year. I don't really have any visibility, however. 

If you're hosting a majority of your platform in Azure, this solution should be okay. Azure Backup is probably the easiest solution to with, rather than bringing another third party into the mix. As a consolidated solution, the Azure Backup will work well - if your native cloud platform is Azure.

I'd rate the solution seven out of ten.

Customers nowadays are planning to migrate their workloads from on-premises to the cloud, like Azure. Microsoft offers Azure Backup as a service, which allows backup for virtual machines, SQL databases, HANA databases, and even file shares. 

If the customer's workloads are supported by Azure, we recommend Azure Backup as a service. However, for workloads not supported by Azure Backup, we look for third-party investment solutions.

One notable feature is that snapshots are computed in less time, enabling faster system recovery. Even for large systems, we can recover them in less time. For example, if it's a recent backup, it can be done in less than 15 minutes.

Another benefit is that the backup utilization is not high. Comparing the pricing with other technologies, Azure Backup is more affordable for customers.

One feature is VMware backup with replication. Many customers are interested in this. Additionally, Azure Backup allows customers to extend their retention period for more than five or ten years, which is beneficial compared to other enterprise backup solutions. The monitoring capability is also good. 

Moreover, encryption is maintained by Microsoft if we follow the platform team management system. This is crucial as customers want to ensure the security of their data on Azure. The configuration is user-friendly, and we have control over backup storage utilization and VM consumption. 

When it comes to improvements, Microsoft should provide us with an option to explore the logs. So if there's any failure by seeing the error, in some cases, we will be able to resolve it. But 50% of the cases are being handled by Microsoft itself, like getting the logs from the back end. That's the one thing that I've seen that has to be enhanced from Microsoft's end.

Azure Backup is limited to certain workloads. It would be helpful if Microsoft focused on enabling backups for Oracle and other unsupported databases.

We have multiple customers, and we categorize the Commvault infrastructure based on customer mix. We have more than ten Comsources, and we distribute the load accordingly. Based on client utilization, we configure the backup equally across the media agents.

The stability is good. I didn't find any challenges. The installations also work as expected. The customers do not have any concerns about it.

Customer service and support vary based on the issue. I've had personal experiences where some issues took more than fifteen days to resolve while others were resolved in one or two days. Overall, it's good, but there is room for improvement based on my personal experience.

The initial setup is very simple. We have to have an idea of the networking cost structure and the configuration. We also have to get confirmation from the customer about what kind of retention they are looking for.

We can also have the data deployed to other regions, which is a nice feature. If there is any disaster in the primary region, we'll be able to read the data from a secondary region. That's also one of the very good features offered by Azure Backup. 

The deployment process is quite easy in Azure. Enabling backup for any VM takes less than five minutes. We just need to create a vault and discover the VM for backup. So, in terms of deployment, it's straightforward and user-friendly.

I haven't found the need for much maintenance. In comparison to other backup solutions where we maintain our own infrastructure, Azure Backup handles everything. We simply create a library, assign a policy, and associate the VM with the trusted backup vault. Microsoft manages everything, and there are no limitations in terms of storage utilization.

Comparing the pricing with other technologies, Azure Backup is more affordable for customers. It follows a pay-as-you-go model, where we pay according to our consumption.

In terms of Azure Backup, there is no special license required. We only need to pay for the amount of data we consume and the data transferred across the network. The pricing is calculated based on these two factors. There is no explicit license cost. We just need to allocate a budget for storage and related expenses.

When it comes to advice, it's important to understand the specific requirements of the customer. If the customer requires backups for VMs, SQL, and SAP HANA, Microsoft's Azure Backup can be a suitable choice. 

However, if there are other workloads that are not supported by Microsoft, alternative backup solutions should be considered. The decision depends on the specific requirements. Azure Backup offers services related to cost, storage utilization, encryption, and scalability.

Overall, I would rate the solution a seven out of ten.

Azure Backup is very simple to use and user-friendly. From the technical side, features like the tenant and the restoration part are much better. It's a Microsoft tool, and all the info we have based on the VMs will be built on the Azure platform. It's easy for us to do the backup in its OEM tool.

Azure Backup has some drawbacks. We can't have the granular level restoration, particularly for the Azure files. Sometimes, indexing doesn't happen in the Azure files. That's why we are keen to have a solution that can consider all the applications, all the OS, and the legacy applications.

One of the disadvantages of Azure Backup is that it doesn't have a MAC backup. In Azure, we cannot take the MAC backup for Mac devices.

Azure Backup's licensing model is very challenging because it doesn't give a clear picture. Whenever we go to the vendor or the OEM to buy some of the workloads, we have to take everything. We have to pay for the VMs and the storage in the Azure platform. Hence, the licensing model should be very simple for the end user to get things easily.

I have been working with Azure Backup for three years.

I rate Azure Backup a nine out of ten for stability.

I rate Azure Backup an eight and a half out of ten for scalability. Two thousand five hundred users use the solution in my company.

We have partner support from Azure Backup. Usually, we can see support in the stipulated time. We get the support based on the SLA timeline.

Positive

Since Azure Backup is a very user-friendly solution, its initial setup is very simple and shouldn't be a challenge for anyone.

We implemented the solution through our technical team.

We do not have any additional costs for Azure Backup.

Sometimes the solution has a huge bandwidth. However, it lags and does not completely perform when it has low bandwidth.

We have around 11 people involved in the maintenance of Azure Backup. Out of these 11 people, five people are from the solution architecture, and the rest are tech support partners.

Overall, I rate Azure Backup an eight out of ten.