My company uses BDRSuite to back up our workflows from machines to the cloud. We also use it to back up files and folders. Currently, we have S3 and Google Cloud blob storage. I'm going straight to the cloud backup repository and bypassing the local repository. It's been backing up very fast to the cloud. It's pretty optimized.

I use it to back up the virtual machines running on VMware ESXi. I also use it for backing up Windows Server. I don't use it for Microsoft 365. I have a daily backup, and I also have a monthly backup to capture all the data and changes.

I started with version 3.0, and now, it's version 5.3.

I've actively been using the Vembu product for backups. It is being used to back up the Hyper-V environment that I have. If the hypervisor has hardware problems, e.g., all the storage dies, you can run up a new Hyper-V server, then restore the VMs onto it. It doesn't take that long. So, you are up and running within several hours of restoring it. Also, you can restore individual files. Therefore, it's a full VM-based image backup as well as a file level backup, if you want to restore the files that way. There is also an option to restore AD users, computers, and contacts, in addition to Exchange databases at the brick level.

I'm mainly working with home-based customers. I don't have any business clients yet.

It's on-premise, not cloud-based at the moment. I'm planning to possibly have replication to an external site since my Internet link is much better now. That will be done in the future. I'll probably replicate to a private cloud somewhere.

We use it for backups of our shared files server.

I use BDRSuite for my customers. I do backups for them. One of the reasons we chose BDRSuite is because it's a hybrid solution. We perform backups using a local server at the customer site, and we also have an off-site server. This way, we have a backup copy stored outside the customer's site. In case the customer site burns down or faces any disaster, we can still restore the data. That's one of the primary reasons we chose Vembu BDRSuite.

Additionally, it's quite economically viable, and not that expensive. It provides the flexibility to use our own cloud instead of relying solely on the Vembu Cloud. Vembu Cloud is, of course, an option, so we don't have to store anything ourselves. But I prefer having my backup center where I store copies of my customer's backups. So, those are the two main reasons - it's economical and it offers the right backup solution.

I'm using the backup from Vembu for my home lab where I have ESXi. I'm backing up VMware servers. That's all I use it for.  I have Oracle Databases running in these VM machines and I do testing, patches, upgrades, etc. I want to be able to back them up and, if need be, restore them so that I don't have to rebuild them.

I'm running it in a Windows Server in a VM machine. I have ESXi 6.7 running on a Dell PowerEdge R720 and I have a Windows 10 VM running in that. And in that I have the Vembu BDR running as my backup server.

We use BDRSuite for our databases and server backups.

It sits on a hypervisor and backs up two virtual machines. 

We use it for providing backups and recovery. We have a file server with a little over seven terabytes of data. The content changes quite a bit and we needed an easy tool to work with that would give us the ability to restore in a variety of ways: at the individual file level, folder level, and whole volume level, if necessary. This tool does that for us.

We're in telecom and wireless. We do installations and maintenance of towers and equipment for microwave and cellular. We do that mostly in the United States, occasionally in other places in the world. We'll have 400 people out in the field providing data to us that we have to put in a repository, that's the file server, that shows work prior to us initiating our work assignment from our customer, during the process, and at completion. That way, the customer doesn't have to go to remote places to verify. Sometimes, we can address an intermittent problem and say it's fixed and, of course, it comes back the next day because it really wasn't fixed. So, it's hard for our customer to know when something is done.

So we take a lot of images of our work, associated with projects, and those are uploaded by the field people every day. We provide the backup necessary to our customer. We'll receive ten or 20 gigabytes of images daily, which go into the repository. They have to be tracked and recorded, put into the reports associated with the projects and the status of those projects, and then provided to our customers.

That's what we do on a daily basis. We're a 24/7 shop, so what we do has to minimize downtime, so that the tools are available to the people, especially if they're in the field. They'll VPN in and provide reports and images necessary to show the work has been performed.

We are a managed service provider (MSP). We have also started to sell it recently. We have been using this solution at our company, and after testing the product for close to six months, we realized this is a good option moving forward.

BDRSuite is used for workstation backup to the cloud.

We use BDRSuite to back up our customers' VMs. We are a service provider, and each of our customers has different requirements. We host VMs based on the customer's environment. If the customer doesn't want a VM backup, we'll use the Citrix ADM. They will back up their own applications, and we'll send a new VM to them in the event of a disaster. 

The solution is used for:

1. Backing up important data and applications to the cloud. BDRSuite allows businesses to back up critical data and applications to the cloud, which can help protect against data loss in the event of a disaster, such as a cyberattack, hardware failure, or natural disaster.
2. Disaster recovery and business continuity. BDRSuite provides businesses with disaster recovery and business continuity services, which can help them quickly restore their data and applications in the event of a disaster.
3. Remote monitoring and management. BDRSuite allows IT administrators to remotely monitor and manage backup and disaster recovery operations, which can help streamline the backup process and reduce the risk of errors.

We use Vembu to back up and replicate virtual machines. We run virtual machines using VMware ESXi, and we back up and replicate our virtual machines.

We offer the solution to our customers, primarily SMBs, for backup and disaster recovery. Deployment models include both cloud and on-prem. 

We use the solution for the backup and recovery of our VMware data.

Currently, we use Vembu for weekly backups of our virtual infrastructure and monthly backups for separate, confidential data.

We use it only with VMware.

Vembu has been a great solution for my smaller clients who don’t need a lot of storage. The entry price is excellent for small businesses who want to use cloud backups.

I have 8 clients currently using Vembu Cloud BDR.

We are using it for the backup of our VMs and restoration activity. We are deploying some new technologies for which we would be able to use the features of Vembu.

We have, in-house, around 70 end-users and around 30 branches. Currently, We are using Vembu to do the daily backup of our in-house end points. 

As data is increasing day by day, taking and managing backup is a hard job. As IT personnel, we were looking for a solution where we could do auto backups for all our machines and restore them at any point in time as required. 

Vembu came to us and solved our problems in the backup space. In the next phase, we are looking to deploy it for our remote branch users. It's a great solution.

We're deploying it to support the backup of some on-premise VMware vSphere workloads.

We use it to backup VMware virtual machines, so I'm backing up my VMware environment. My product is for Windows Server Backup.

We are a small business. We don't use the enterprise version of the solution.

We use it purely for Hyper-V backup. It's used to protect our entire server estate.

We use it for backup and replication. 

Our primary use case is for VM backups.

We were using an older version and just upgraded two weeks ago.

We use it for backing up physical Windows Servers and one hypervisor server. The main draw for us was the ability to back up hypervisors, Hyper-V, specifically.

I have approximately 50 clients for whom I provide backup services using Vembu software.

I don't have a virtual environment.

Our daily scheduled backups are only with Vembu. We are using the disk based solution only.

We are a business school.

Mainly, we use it for our backup recovery. If you have relevant data, we need to make backups similar to the data to ensure that we can export it in the case of any emergency or disaster. The main use case is disaster recovery for relevant data to be able to survive after any disaster.

I have two deployments. One of them is Hyper-V deployment with backup for Hyper-V virtual machines. The other one with backup for the Vembu virtual infrastructure version. Both of them are on-premises. There is nothing on the cloud.

We are using the Enterprise version for backup. With the license that we have now, I'm using the NetworkBackup application. This includes having email backup with MS Exchange Server, which is very helpful because we can restore by mailbox or mail. We don't have to restore the entire server.

We also have FAS, Windows Subsystem for Linux, and MySQL databases. It is very easy to use with them.

I have some virtual machines. I use an VMware ESXi server to back them up.

We use it to back up ESXi clients, so mainly Linux based or Unix based servers on our ESXi host.

We use the solution to back up our virtual environments (VMware). It has been good for our organization so far.

I use it as a backup solution for our VMware system.

The primary use for this solution is to replace the old-fashioned backup solution that we had that was based at the application level. I was doing backups of an SQL database or mailboxes from Exchange, but we needed a more modern solution where we could back up the entire virtual machine.

We manage 100s of backups at any given time. This includes virtual machines, both VMware and Hyper-V, physical machines running Windows, and file-level backups.

We have backups that are 100% cloud-based as well as ones that retain both a local backup and a cloud backup copy. The data replicated to the cloud must be contained within a data center that is owned/managed by our organization.

Our recovery processes primarily include being able to restore directly to an ESXi host/vCenter appliance. This must be able to be completed in the shortest amount of time possible.

Backup and replication.

We back up all our customers' files. We back up only files, and maybe some databases. However, primarily, we are backing up files on our own server.

We are currently using the updated version of this product.

We're doing onsite local backups as well as offsite DR of our VM infrastructure.

We use it primarily for backups and restoration of data, for disaster recovery purposes. We back up our file servers as well as our access control servers. We use it for standard, physical Windows 2016 servers, at this stage.

The key things we use in this solution thus far are only the backup portion, the recovery, and the reports. We will try to make use of it more extensively, but for now it's working for us.

It's on-prem at this stage, but we would love at a later stage to go to the cloud.

We have a multi-tenant environment with multi-cloud, but we are only using this for our local data center backups. This is a small setup with around 50 to 60 VMs.

We do cloud hosting for our customers, and we do reselling when they want to do VMware on their premises.

Our whole environment is virtualized except for a couple of servers which are still physical. So I primarily use this for backing up my physical servers. I do an image backup as well as a file-level backup.

We were looking for a backup for Red Hat Virtualization. We don't need any advanced features from a backup solution yet. We don't have VMware or Hyper-V, we only have Red Hat Virtualization.

We are a service provider and we have many customers but we are only using this solution for one of our customers. They have a small environment with four servers.

We back up servers and workstations.

The primary use case is for backup.

I am using the latest version.

The primary intended target for it was VMware backup and utilizing it in a VMware environment. It is a production, Active Directory, file server type of environment.

I am using the current version.

Primary use is for vSphere or VMware.

Backing up virtual machines, we use it for Windows Hyper-V platform in one data center, but we've also got future plans for a VMware Hypervisor platform in another data center. So thinking ahead, we chose Vembu.

The primary use case is to be able to back up data outside of on-premise with the ability to restore as fast as possible. We also use Vembu NetworkBackup to selectively back up files on the file share along with our virtual machines. It gives us more control over what we can backup and restore, especially in the files.

We use it for backing up virtual machines.

We use it to back up a test lab type of environment. It's a virtual environment where we use Hyper-V.

Backup virtual machines on VMware.

We use it for backup copies of key virtual servers in our company.

We use it for replication to our disaster recovery sites for the storage we have on-prem. We needed our critical infrastructure and our critical applications backed up. We needed to have something we can restore from when we have an issue.

Our environment is hybrid. We have some of our servers on-prem, some on Azure, and some on AWS.

We use it for backing up VMs.

We use it for our file server and database backups.

It is a backup and disaster recovery solution for small businesses. I use it primarily for Vista machines.