If you were talking to someone whose organization is considering Azure Backup, what would you say?
How would you rate it and why? Any other tips or advice?
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.