I would rate the easiness of the initial setup as an eight out of ten. Setting up Azure Backup was pretty straightforward, especially if you follow the steps in the right order. It might seem a bit complex at first, but with experience, subsequent setups become easier. Planning is key to optimizing its effectiveness.

Deploying Azure Backup typically takes around half an hour to an hour to set up one VM, involving creating a recovery services vault, defining a backup policy, and configuring storage options. For a more comprehensive setup including proper recovery planning, it might take a few hours. The key steps involve creating a resource group, and a recovery services vault, selecting a storage type, and defining backup policies. I deployed the solution myself.

I don't know if the product's setup phase is easy or difficult since I am not involved in the setup process. I am only responsible for the team that carries out the steps related to the product's setup phase in our organization.

The initial setup of Azure Backup is easy.

The solution can be deployed in ten to fifteen minutes.

The number of people required for the deployment depends upon the number of virtual machines that must be onboarded in the backup. Ideally, a person or two can easily manage the backup solution of an enterprise-level customer.

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.

Azure Backup is pretty simple to deploy if your applications are hosted on Azure. And the more cloud-native services you use, the easier it is to deploy. The closer you are to Azure's native environment, the easier it gets. It's almost seamless. It's just about checking a few boxes, and it's done. The complexities come in when you are in a hybrid environment.

The time taken to deploy the solution depends upon your backup policy. At most, deploying would not take more than a few minutes. Configuring the backup policies will take time, but actual deployment takes minutes.

Azure Backup is simpler to maintain compared to an on-prem backup. It's a managed service from Azure. With a backup solution, the important thing is to check your daily, weekly, and monthly schedule and the integrity of backups. That's the most time-consuming part, but all that gets highly automated in Azure.

The setup for insight cloud backup is easy. However, site recovery from on-premise to the cloud can be tough because we have to set a lot of parameters.

The initial syncing process is tough in case of site recovery. However, it performs better once your system is synced. It is difficult in specific situations, like if you stop syncing, if storage is full, or if your on-premises server storage is full. The initial setup is difficult for site recovery and backup. It becomes easy once the initial backup is completed.

The installation was easy. We took two to three months to deploy the solution. We had to plan since we had a lot of servers.

The initial setup was straightforward. It is a cloud solution. We download the agent and scan for the VMs on-premise. Then, we connect the on-premise server with Azure. Later, we do the network and storage configuration.

The initial setup required some assistance. The deployment depends on the company's size and environment. 

The first stage of our deployment is accessing the client's information, such as environment size, the reason for use, and what deployment model we are interested in.

I rate the initial setup of Veeam Backup & Replication a seven out of ten.

The initial setup was straightforward. The product is deployed on the cloud.

It's easy to deploy.

We have a deployment team. There is usually very few people dealing with the implementation. You might have eight to ten guys doing the migration and other things. Recently, we did a project where there were close to 1,000 servers that have to be moved to the public cloud and we implemented Azure Backup for all of them. It didn't take much of our time since the management and the interface are very easy and you don't have much to do over there. 

It's a slow process. You're not moving all of them at one shot. We'll do 15 to 20 servers in a batch, which we are doing based on the applications. One application, we are going to move at a given time. If there are 15 to 20 servers within one particular application, it takes hardly a few hours to go and do everything. However, if there are many, many applications, it will take time.

The initial setup of this solution is straightforward, 

The initial setup is fairly standard and not too complex. Deployment generally takes a few days depending on the size. Anything to do with data retention takes more time as we have to define the backup schedules and retention and those kinds of things. Validating the backups is quick and efficient but determining which data we need to keep and for how long, takes time. Those are all issues related to the customer.

Deployment steps are basically about carrying out an inventory of the workloads. You want to guard the types of protection you're applying specifically to databases versus different systems and services, and then how that ties into full recoverability. That would take a week maximum in the worst case and we do that internally. 

We usually have two systems engineers involved in maintenance. Different projects require different capacities.

I'd rate its setup a ten out of ten in terms of ease because you don't need to read anything to configure it. It's super easy like filling out a form.

The initial setup is relatively straightforward. You just need to follow the instructions provided, which are usually quite clear. Whether you're selecting Hyper-V or a barebone machine, the instructions are generally easy to understand. The only potential challenge I've encountered is with download links when you need to install an agent. When it comes to the backup processes themselves, I haven't faced any significant issues. All of my students have been able to follow the instructions, which speaks to the product's usability and reliability.

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. 

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. 

The initial setup has medium complexity. I rate the process a five or six out of ten.

The initial setup was easy.

You need someone with experience to complete the initial setup. If you bring in an engineer or a computer science person who doesn't have experience in Microsoft then he cannot do it. They might be able to install the Windows Operating Systems and Active Directory but they won't be able to connect to the VM online on the cloud. They need some experience. If someone trains them, they can get it in one day or maybe two.

In my experience, each installation with us can take 18 days if the client requests an on-premises deployment. If they need just a server to create a backup, we will create a virtual machine online, which will take one or two days.

It will take time for an on-premises installation because we will install the server locally. This includes the operating system, the links, and connecting them to the server and then to the cloud. It will work online or offline. This will take 15 to 18 days.

Again, to backup online, for the server and Active Directory, it will be one day to complete.

The initial setup was not as straightforward as I expected. I was facing certain challenges and I was deeply in contact with the Azure team from Microsoft technical support. It took quite some time for them to resolve my issues. My case was escalated to level three support and to reach that level, it took 10 to 14 working days.

It takes very serious research or good troubleshooting skills to eliminate some of the complex problems that can occur.

In total, it took us about a month to deploy.

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

The initial setup was straightforward. It was something that was easy for us.

It was completed within a few minutes. It can depend on the environment, but usually, it is fast.

The number of staff required for maintenance depends on the automation. We require more staff now, but we are working on the automation. Generally, it is relatively low. For the most part, it works by itself.

The tool is very easy to deploy and configure. A person who understands networks can deploy and configure the product very easily. If a person has a clear concept of networks, they can work on any cloud solution. I rate the ease of setup a nine out of ten. We have many clients.

We have replicated our clients’ resources from on-premise to cloud and from cloud to cloud. The time taken for deployment varies for every client. If a company has 100 VMs, the tool can be deployed in two days. We can configure the tool with Azure CLI.

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.

The initial setup is done by our cloud solution provider. While I'm not aware of the details. my understanding is that the deployment was quick and did not take long.

The initial setup was straightforward. Deployment time depends on the size of the data.

The initial setup was easy. I did it myself. It is not very complicated at all. This is another one of its valuable features, that it is easy to set up. Microsoft has guidelines, documentation, instructions, procedures, and tutorials available.

Because it's a Microsoft product, admin guidelines and instructions are available. It's not that complicated. You can have any infrastructure on the cloud or on-premise. If you want to install a server you will need to install maybe a virtual machine. But if you don't need to install it, you can install only an agent on the computers. That's it.

The deployment took around two days. I have experience with other backup solutions so I understand the concept. It's like a car. You have a car, you know how to drive a car. But this is Rolls Royce or a Porsche or whatever, but it is the same concept. You can still own the car and you can go. It is the same. So for us, it doesn't take that much time to understand the concept of backup and then implement it. 

The deployment required two people, myself and a colleague. 

It requires three people for maintenance.

The initial setup of Azure Backup took a couple of hours to complete. It was quick and straightforward.

The initial setup was easy. I rate it nine out of ten. The solution was deployed in a few days.

Once you know how to do it, the initial setup is pretty easy and pretty straightforward. Even later on, as you transfer the responsibility to the customer, they can do it on their own.

The initial setup of this solution is straightforward. 

Setting up Azure Backup is straightforward and the total deployment time was about a month. 

The initial setup is straightforward, but you have to think about the recovery strategy.  Implementing the two is quite easy, but you also have to think about the backup and the overall recovery strategy and what kind of recovery strategy you will use to backup and restore. I know it's easy for the most common use cases.

There is no installation, it's all in the cloud. You're just building into it.

The initial setup was easy. To install it, you just choose an agent, and that agent is automatically deployed.

I was not involved in the initial setup. I can't speak to the complexity or straightforwardness of the implementation.

I'm not sure how long deployment takes.

We have an in-house team that handles maintenance.

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. 

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.

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.

The initial setup is easy.

The deployment is not complicated and easy to do.

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.

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

Installation is straightforward.

The initial setup was very easy. I deployed it myself and I believe we had it up and running in one day.

The initial setup complexity depends on the environment. On-prem can be complex to set up but the cloud is simple.

The time it takes to deploy depends. It can take anywhere from half a day or a few days, depending on the complexity.