What advice do you have for others considering Azure Backup?

Reporting and analytics improvements with AI technology would be helpful. The setup process is brief and user-friendly with clear steps at each stage. I'd rate the solution ten out of ten.

We use the solution to protect specific data types or environments, such as an SQL database, a normal VM, or a file share. I suggest Azure Backup for a small or medium environment with 30 to 40 VMs. For a big environment, I suggest third-party backup tools, which are more flexible and manageable because they come with single dashboards. Overall, I rate Azure Backup an eight out of ten.

I would recommend Azure Backup to other users. Overall, I rate the solution a seven out of ten.

I can restore VMs easily with Azure Backup, although I don't need to do it regularly. However, I have tested it, and it works exactly as expected. Azure Backup is our top choice for data protection, offering native backup for critical systems like SAP HANA and SQL. Its automation capabilities ensure seamless backups, significantly improving our organization's data management efficiency. The most beneficial feature of Azure Backup for our data protection strategy has been centralization through Backup Center, allowing us to manage and monitor all backups in one place. Azure Backup meets our compliance requirements by encrypting all backups at rest, ensuring data protection. Additionally, role-based access control allows us to manage who can access the backups. Maintaining backups and restores with Azure Backup is straightforward, especially compared to more complex solutions like NetBackup and data domains. Before implementing Azure Backup, it is crucial to understand your business requirements, including recovery objectives like RPO and RTO. This cloud-native solution is straightforward to set up and manage, but aligning it with your specific needs ensures optimal performance and effectiveness. Overall, I would rate Azure Backup as a nine out of ten.

The solution's features are enough to meet our company's use cases. Whether I recommend the solution to others or not is something that depends on the necessity of those who plan to use it. I recommend the solution to those who have a simple infrastructure. I rate the overall solution a nine out of ten.

As with any backup software, it's crucial to thoroughly test the recovery process to ensure it functions as intended. Sometimes, the issue might simply be forgetting to configure your service principal names (SPNs). SPNs can be somewhat similar to DNS names. When you enter "Google.com," you expect to receive an IP address. Similarly, when dealing with service principal names, you specify the HTTP or another service on a particular machine and expect to validate it with a certificate. It is an essential step that should not be overlooked. If these configurations are forgotten, it could result in backups that cannot be restored, which is far from ideal. Therefore, rigorous testing is essential to validate the effectiveness of your backup strategy. Overall, I would rate it nine out of ten.

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

With Azure backup, there is an on-premises option using your Azure Stack, but my experience on that is limited since I deal with Azure cloud-based backups. If anyone plans to adopt Azure Backup, first understand your backup requirements. Especially if you operate in a multi-regional environment if your workloads are spread over multiple regions and subscriptions, it makes sense to have a cloud-based backup on Azure, especially if you operate in a multi-regional environment. That helps you scale out as required and simplifies the deployment of web-based or Azure-native applications. The word of caution is to be vigilant about your backup consumption and be proactive in choosing the right tier so that it remains cost-effective for you. I rate Azure Backup an eight out of ten. The solution is great with cloud-native applications. But if you go into a hybrid environment or a multi-cloud environment, that's when there are complexities. Moreover, you need to be vigilant about what you're using. Otherwise, the cost can spiral out of control.

We can use the solution if we don't plan to work in a multi-cloud environment. It meets our requirements. Azure Backup might not be the right product for us if we want a higher disaster recovery capability. Overall, I rate the tool a seven out of ten.

I would rate Azure Backup an eight out of ten.

I rate Azure Backup nine out of 10. You should plan what you want to back up so you can implement the solution quicker.

If you are new to the cloud and looking for a solution with essential backup support, go for Azure. But if you want advanced features, then this is not recommended. I was looking for Ransomware Protection and had to move away from Azure as it does not have such advanced features. I rate it a seven out of ten.

It's important to ensure that the capabilities you require are available in your region. Feature availability per region is the most important thing. You can't do a design for Azure in North America and then think that it's going to work everywhere. Azure is not consistent so you may be forced to buy third-party products that you didn't budget for. I rate this solution nine out of 10.

I rate the solution an eight out of ten.

I rate Azure Backup a seven out of ten.

I would rate Azure Backup a ten out of ten.

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.

I would rate this solution 5 out of 10.

We are working in our own environment, assisting KPMG users and firm members. We also have internal companies. I am an Azure Architect. It's useful, it works, and it's fairly reliable. The only issue right now isn't a big one, but our users sometimes need faster recovery, faster restoring of services, and faster restoring of data. I would rate Azure Backup a nine out of ten.

We are a customer with an enterprise agreement. I do not backups myself. I don't know the versions we are using. I'd rate the solution at an eight out of ten.

It's important to know what you'll be getting from whoever provides you with the solution because it's important that support is included. This product has really helped me in scaling up my company. We love this solution and think everyone should have it. As a provider and a user, I rate this solution 10 out of 10.

On a scale from one to ten, I would give Azure Backup a seven.

It's a competitor to Amazon. I would recommend this solution to others. I would rate Azure Backup a nine out of ten.

I would rate this solution an eight out of ten.

It is really a valuable product. Most of the organizations nowadays, especially in North America, prefer Microsoft products over the Linux environment. There are, however, some people who use the Linux environment as well. Overall, I would rate Azure Backup an eight out of ten. It meets the day-to-day requirements of most of the IT people, and it can be automated.

I would recommend this solution to other companies because it's an enterprise product that suits all requirements. On a scale from one to ten, I would give this solution a rating of eight.

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.

We are simply using the solution as a customer. We don't have any professional affiliation with Azure. We simply use a lot of Microsoft products, including its OS and Office suite. We have a site where do backups, but we do not do anything on a big scale on the cloud. I'm not sure of which version of the solution we're using. I'd recommend the solution to other organizations to try. It's a very good solution. I'd rate the solution seven out of ten. The product should be more non-technical. If it as more user-friendly, I would rate it higher.

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.

I would rate it a ten out of ten and I would definitely recommend it.

It is easy to configure a solution at any time, from anywhere. I can also restore the data, easily, without any complication. You can implement it in a very short time. The lesson learned in the beginning is that you can implement a solution in a very short time. I would rate it a seven out of ten. It has some good features. You can sort the data in many ways and at anytime. But it is not user-friendly. To be frank, it is not a software and a service. Software and service is easier and not complicated but infrastructure is more complicated. A platform lies somewhere in between. It's a platform and service.

My advice to anybody who is considering this solution is that if you can afford it, then I would highly recommend it because the service provides very good value. The software is very capable but the information available for support is limited. I would rate this solution a seven out of ten.

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.

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.

To this point, I have not run across any issues that are blocking. My advice to anybody who is considering this solution is to go ahead and use it. It works and it's a good service on the platform. It is just one of the building blocks that we use every day on Azure, so I can't see any reason to move to another one. I would rate this solution a nine out of ten.

Before doing a backup or getting any cloud solutions, you must first check the environment and the systems. Most companies will have computers in a workgroup. Each must have its own domain and Active Directory. You will have to do the know-how technologies inside the company for the basic configuration. Then they can choose and start. You know longer have to use storage that will stay inside the office because anyone can unplug it and take it with them. With a cloud solution, you can specify which MAC address, user, environment, or region can get the data from the server. I have been using Microsoft for 16 years. I am very familiar with all of the Microsoft technology. Now they have the cloud, Microsoft Office 365 and Microsoft Azure, so we transfer and we have been awarded the digital technology transformation three times. We are a cybersecurity company that cares about security for our clients. As a gold partner and CSP partner, we have our portal. If a client needs 100 Azure servers then I can create them directly for him, without having to contact Microsoft or anyone. I can create them and the charges will come to me monthly. Also, I can choose the mode of payment, be it monthly or annually. There is also the rebate and the cashback that will come with yearly or monthly billing. I don't see any problems with Azure. It gives our clients peace of mind. Data is important. I would rate this solution a ten out of ten.

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.

This is a solution that I might recommend, depending on the customer's requirements. If they need application-level backup then I will not even consider it. However, if they need infrastructure backup for Azure, then, of course, it is a good option. Generally speaking, I recommend this solution. Overall, the service is good for certain use cases, but it is short of functionality when you consider the competitors. I would rate this solution a five out of ten.

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.