IMPORTANT – Please read the latest defense digest about the Veeam Backup & Replication encrypted credentials disclosure

214.363.1900
Request a Quote
What is Veeam Backup

What is Veeam Backup

by | Apr 23, 2016 | Backup

Veeam Backup and Replication

Backup and recovery solutions are vital to your organization, but backup solutions that used to work effectively may no longer do the trick in today’s ever-changing computing landscape, especially if your firm relies heavily on virtualization. Veeam backup offers backup and disaster recovery solutions that make an ideal fit in the virtual environment.

Backup Solutions That No Longer Work

Tape backup has been a longstanding solution.  Tape restores take far longer to complete when compared to a restore from disk – or the even faster alternative – using the backup as the primary. That’s not even possible with tape.

Tape solutions mean that finding the data always means finding the right tape. That’s time-consuming and risky. Plus, with tape there is the risk of obsolesce of the media when the tape software or drive gets upgraded. Finally, tape solutions simply cannot provide the guaranteed availability that every modern business requires.

Enter Veeam for the Virtual World

Veeam works in the virtual environment by backing up virtual machine images instead of files, storing the images in a secure, central location. If disaster were to strike, the VM images could be rebooted nearly instantly, rapidly restoring the machines with a recovery time and point objectives of fewer than 15 minutes for all data and applications.

How Veeam Works

Veeam’s software runs through what is called a hypervisor, which is a layer of software that allows for multiple VMs to be run on a single, physical machine. Veeam’s first task is to take full backup of each virtual machine. It then subsequently uses caching and duplication elimination processes to only store new information in the VM images.

Veeam Benefits and Options

The Veeam Availability Suite provides five main capabilities. They are:

  • Rapid recovery: Choose exactly what you want to recover and how you want to recover it.
  • Avoidance of data loss: Near-continuous data protection coupled with streamlined recovery methods
  • Verified recoverability:  Veeam stands by its ability to recover every application, file or virtual machine, with no exceptions.
  • High visibility: Receive alerts and enjoy continuous monitoring to become aware of issues before they can affect operations.

The Veeam Availability Suite combines two products into a single solution: Veeam Backup & Replication for restoring and replicating information and Veeam ONE for monitoring and reporting. A smaller version of the Veeam Availability Suite, known as Veeam Backup Essentials, is available for smaller businesses that may not need the suite’s full capabilities.

Headquartered in Switzerland with main offices in Ohio, France and Australia, Veeam was founded in 2006. It has since become the go-to backup and recovery solution for more than 183,000 customers across the globe.

 

Veeam V11 Updates

 

 

Takeaway:

Whether you are a small business or enterprise data center, Veeam Backup offers a cost-effective solution for backup and recovery in virtual environments. Veeam Backup enables you to protect virtual environments, physical servers and their workloads, and even physical workloads.

Find More DRaaS and Backup Related Topics

 

 

Webinar: The Importance of a Business Impact Analysis

Webinar: The Importance of a Business Impact Analysis

The following is a lightly edited transcript of our September 2022 webinar on the importance of Business Impact Analysis. The speakers are: Kelly Culwell, Senior Manager, Service Transition, Dataprise Steven New, Director of Operations, Dataprise Tom Shay, vCIO,...

Why RPO and RTO are so important to effective disaster recovery

Why RPO and RTO are so important to effective disaster recovery

Business continuity is at the forefront of most IT departments. Between human error and hardware failure, no environment is completely free of risk. And with 236.1 million ransomware attacks worldwide during the first half of 2022, odds are that your organization will...

Disaster Recovery as a Service
Learn More

Reseller Request
How to build a disaster recovery site – part 3

How to build a disaster recovery site – part 3

by | Aug 10, 2012 | Archived, Disaster Recovery

Whether you are outsourcing your Disaster Recovery program or keeping it in house, the steps required to implement it are critical. In this series, we’ve drafted an outline of how to build a remote Disaster Recovery site for your IT. In our previous articles, Choosing a Disaster Recovery Site Location and What Does It Take To Build a Remote Disaster recovery Site for Your IT? we detailed steps 1 through 5: dr-plan-for-gdv1-631x300
  1. Determine the business requirements for RTO and RPO
  2. Determining the right location
  3. Acquire and / or build the right platform at the Disaster Recovery location
  4. Virtualization of the primary and backup environments and production systems
  5. Moving the data
In this final installment, we’re taking a look at the last three steps: 6. Synchronizing the data 7. Creating the failover environment 8. Testing the program Synchronizing the Data The only way to synchronize the data is to implement software or hardware to manage the process. The software application or hardware platform you choose to install will sit in your primary server environment and it will keep an eye on all your data, continually monitoring it for changes. When it sees a change, it knows to send the change to the Disaster Recovery site. This activity typically occurs on what’s referred to as a “block level.” Block storage is normally abstracted by a file system or database management system for use by applications and end users.  A block of data is what your disk system writes. Think of it like this: Your operating system has a database that houses all your data. If you hit “file à open” in Microsoft Word, you then choose the file you want, and you’re telling your operating system to open the file. The computer translates this activity to a disk location where your information is stored internally, then the operating system and file system move the read head to that location and it starts reading the data – and voila, it pulls up the file on your screen. (more…)
Building a Disaster Recovery Site – part 2

Building a Disaster Recovery Site – part 2

by | Aug 2, 2012 | Archived, Disaster Recovery

What does it take to build a remote Disaster Recovery site for your IT? (Part 2 of 3)

Whether you are outsourcing your Disaster Recovery program or keeping it in house, the steps required to implement it are critical. In this series, we’ve drafted an outline of how to build a remote Disaster Recovery site for your IT. In our previous article we detailed steps 1 and 2:

  1. Determine the business requirements for RTO and RPO
  2. Determining the right location

And in this article we’ll look at steps 3 – 5:

building-fire-image-540x300

3. Acquire and / or build the right platform at the Disaster Recovery location

4. Virtualization of the primary and backup environments and production systems

5.Moving the data

Building the right platform:

After establishing your RTO (restore time objective) and RPO (restore point objective) requirements, you’ll have to have a way to make restores happen. If you’re capturing transactions, for example, you have to have a method to record those transactions in multiple places so that you will be able to bring them to the disaster recovery site. And, naturally they need to be delivered to the disaster recovery site in a timely enough basis to achieve your RTO and RPO.

You will need:

  • tools that can replicate databases
  • high speed communications between the sites that are reliable and can keep the replication in place and keep it current
  • redundant storage
  • redundant processing power
  • a way to switch between primary and backup quickly and easily without things going terribly wrong
  • the manpower to build out infrastructure nearly twice in separate locations and to keep the two sites synchronized
  • the mechanisms in place to see that if the primary is offline, switch to the secondary, and when disaster is over, switch back to primary. (more…)