What is your primary use case for Azure Backup?

We use Azure for our application and back end software. Most of our servers are on Azure. We have our fleet management and system tracking, and all the data from our thousands of clients are connected to Azure. We provide each client with their own backup solution to help them with disaster recovery.

We can implement Azure Backup for any customer who wants to back up their servers, whether on-premises, AWS, or any other cloud. We can implement the solution in such scenarios if the customer doesn't have an existing backup in place.

Like any backup product, we use Azure Backup to have a secure backup and restore it. Azure backup itself is provisioned on the Azure portal with the Azure products. We are a gold partner with Microsoft, and we use all Microsoft products in our enterprise.

I use Azure Backup primarily for backing up virtual machines, storage accounts, and SQL databases.

The principal use cases of the solution are attached to SQL databases and virtual machines.

The main use case is to back up my on-premises machines, essentially resembling the traditional backup software that has been included with Windows operating systems for the past three decades. In this specific case, it's a cloud-based solution. This cloud-based backup service also offers regional redundancy. For instance, if you're using the South UK region as your primary location for backups, you have the option to mirror your backups to another designated region. In the past, this secondary region used to be highly customizable, but now specific regions are designated as partners. For instance, Western North Europe may be a partner region. This means you are constrained to using specific partner regions for redundancy. If the primary region encounters issues, the secondary region will seamlessly take over the backup load.

Azure Backup is best suited for people who have their workloads on Azure. 80% of the use case is for people using compute instances or compute capacity on Azure. There is a smaller use case for people who want scalable storage, which some can scale up and down, even though their workloads may not be in Azure and maybe a data center workload instead. Azure backup is a good solution if one needs scalable workloads on a cost-effective platform. Those are two primary use cases.

The product is a part of our cloud infrastructure strategy.

We use the solution for VMs and SQL servers.

We use Azure Backup to back up Azure servers and databases. It isn't used for active data storage.

We used it for the backup of virtual machines.

We use this solution for across-the-board data protection. That includes VMs, and storage pools for basically any level of recoverability whether for files, storage pools or transactional data. I'm an enterprise architect.

Our primary use case is for backups.

We use Azure Backup to backup VMs.

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

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

We generally use the solution for VM backups.

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.

We use Azure Backup to backup and restore virtual machines as well as SQL Databases.

The main use case is to back up the virtual machines.

Our primary use case of Azure Backup is for data on our application servers. We host our ERP systems with SQL for backend software. We've been in partnership with Microsoft for more than 15 years. I'm the CEO and the CIO.

I use Azure Backup to backup Microsoft Domain Controller for my client. The need was to protect the domain controllers as they were critical controls for Watson Web. So, even if a hacker attacked the firm with a ransom through Watson Web, it would be possible to recover the data from Azure because the data would have been protected.

We use Azure databases and we run a backup script for it.

I use Azure Backup in my client's company.

I have created a virtual machine that I use as a testbed to validate the Azure backup and restore functionality.

We use this solution to back up our private environment and virtual machines.

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.

We primarily use the solution for its backup functionality. It's the number one reason we utilize the product.

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

The primary use case is to have in Azure or backup with a machine on-prem.

We use it to backup on-premise data to Azure. We can backup the whole virtual machine to Azure if we need offsite backup. If you don't have any backup solution on-premise data center, you can rely on Azure Backup to do a backup to Azure, to the cloud. That means from on-premise to cloud backup, for data and virtual machines.

We use Azure Backup as part of our disaster recovery solution. If there is a problem in the entire building then we can restore our data from over the cloud.

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.

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.

We are a Microsoft reseller for everything that has to do with the cloud and migrating from on-premises infrastructure. Azure Backup is one of the solutions that we implement for our clients. Our primary use case is to assist schools with moving their on-premises workloads to the cloud. We use the backup facility as it's provided by the platform to help them move everything they run on VMware, Hyper-V, or physical servers.

Currently, I have Many Azure VMs for clients, and We are doing the backup, disaster recovery, and tactical replication for all of them. We install the backup stack for our clients. We explain the situation and have our technical team complete the installation for the clients. With set up managed retention using the backup policy. We do retention, and we do security. The level of security is high on it. Most of our clients used to have Mac storage in all of their offices, such as NAS (network-attached storage) by 20, or 30 terabytes. We have informed our clients, rather than keep their storage on-premises and risking it getting damaged with no disaster recovery, it would be better to synchronize it and move it to the cloud. Some of the clients will keep it on the cloud while some others have to keep it on-premises and on the cloud at the same time for direct synchronization. The backup is configured as replication or synchronized between both of them. When we install for the client, they have a full solution. All of their computers are connected to a single sign-on with Office 365. They all have a domain on the Microsoft cloud. Included with this we add Azure, all of their HR software, ERP, and accounting on the cloud. The add-on backup to the environment will be with Microsoft.

We primarily use the solution for disaster recovery.

We are a Microsoft partner and we implement solutions for our customers. We also provide managed services. We work with most of the services on Azure, and this is one of the solutions that we have provided. Azure Backup is a public cloud service, and you can use it to backup on-premises or cloud services. The primary use case is backing up cloud services. However, if you are using it on-premises then the cloud part is much more convenient.

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.