Organizations are modernizing their data centers so that they can provision IT services faster, strengthen security and control, and lower operating costs. While building modern data centers, organizations invest in server virtualization, modern storage applications, and cloud-based services. However, businesses are facing new demands from end users, including access to data and applications at all times and systems with no downtime or data loss. In addition, they are facing exponential data growth annually.

This whitepaper is intended for a technical audience that understands how Veeam® Backup & Replication™ works. Additional knowledge about Cisco® UCS® and Cisco Unified Fabric is useful but not required.

Veeam Backup & Replication provides an architecture where different components can be scaled out simply by adding additional components. To maximize backup and restore performance for the entire system, the Veeam Proxy and Repository roles need to be balanced. Doing so allows Veeam to provide availability for the data, ensuring the lowest recovery time and point objectives (RTPO™). A performance-optimized architecture is key to reach that goal. This whitepaper will rely on the following simplified model of a modern data center.

Oracle databases are among the most important applications in many environments. Relational databases are used for custom applications developed internally by a company, or as a database backend for commercial applications deployments. In both scenarios, data registered in Oracle databases require a proper design for their availability needs. This involves specific virtualization capabilities like HA, and proper data protection. Availability for BCA is not something that can be applied afterwards as an add-on, but instead a critical component that should be planned for and designed into the overall plan.

In this technical whitepaper, Shawn Lieu and Michael Cade will guide you through three scenarios where Veeam Backup & Replication and NetApp technologies can be leveraged to achieve maximum application and data availability. One of the best ways to protect data and provide availability is to follow the “3-2-1 rule”— keep three copies of your data, stored on two different sets of media, with at least one copy stored off site. Implementing this level of availability can be somewhat challenging and requires planning ahead.

Oracle databases are among the most important applications in many environments. Relational databases are used for custom applications developed internally by a company, or as a database backend for commercial applications deployments. In both scenarios, data registered in Oracle databases require a proper design for their availability needs. This involves specific virtualization capabilities like HA, and proper data protection. Availability for BCA is not something that can be applied afterwards as an add-on, but instead a critical component that should be planned for and designed into the overall plan.

Organizations are modernizing their data centers so that they can provision IT services faster, strengthen security and control, and lower operating costs. While building modern data centers, organizations invest in server virtualization, modern storage applications, and cloud-based services. However, businesses are facing new demands from end users, including access to data and applications at all times and systems with no downtime or data loss. In addition, they are facing exponential data growth annually.

Globalization has become the norm. The exploding use of mobile devices and the Internet now requires most businesses’ websites to be constantly available. Additionally, employees need 24×7 access to corporate resources. These types of requirements drive the need for increased levels of availability and recoverability for your business services. Downtime can be extremely costly. A 2014 Gartner study called “The Cost of Downtime” revealed that the average cost of downtime for businesses was $5,600 per minute, which roughly equates to $300,000 per hour. That particular study was an average across all businesses. For many organizations, it can be much more. For instance, according to a Forbes article, a 30-minute outage for Amazon in 2013 cost the company an estimated $3 million in lost revenue.

Globalization has become the norm. The exploding use of mobile devices and the Internet now requires most businesses’ websites to be constantly available. Additionally, employees need 24×7 access to corporate resources. These types of requirements drive the need for increased levels of availability and recoverability for your business services. Downtime can be extremely costly. A 2014 Gartner study called “The Cost of Downtime” revealed that the average cost of downtime for businesses was $5,600 per minute, which roughly equates to $300,000 per hour. That particular study was an average across all businesses. For many organizations, it can be much more. For instance, according to a Forbes article, a 30-minute outage for Amazon in 2013 cost the company an estimated $3 million in lost revenue.

In this technical whitepaper, Shawn Lieu and Michael Cade will guide you through three scenarios where Veeam Backup & Replication and NetApp technologies can be leveraged to achieve maximum application and data availability. One of the best ways to protect data and provide availability is to follow the “3-2-1 rule”— keep three copies of your data, stored on two different sets of media, with at least one copy stored off site. Implementing this level of availability can be somewhat challenging and requires planning ahead.

Oracle databases are among the most important applications in many environments. Relational databases are used for custom applications developed internally by a company, or as a database backend for commercial applications deployments. In both scenarios, data registered in Oracle databases require a proper design for their availability needs. This involves specific virtualization capabilities like HA, and proper data protection. Availability for BCA is not something that can be applied afterwards as an add-on, but instead a critical component that should be planned for and designed into the overall plan.