Picking up where we left off, let’s dig deeper into the remainder of the Veeam presentation from Cloud Field Day 5. I’m going to provide a summary for the last three videos recorded live by the good people at PrimeImage Media.
- Veeam Cloud Tier by Anthony Spiteri
- Veeam Availability for AWS by David Hill
- Veeam Cloud and Service Providers by Anthony Spiteri
Our next presenter from Veeam was Anthony Spiteri (Global Technologist, Product Strategy) and his discussion focused on the Veeam Cloud Tier.
The first portion of the presentation was an overview that included a breakdown of each of the Cloud Tier terminologies and they include:
- Object Storage Repository – as we’ve come to know, Veeam is focused on keeping it simple for the customer which includes the ability to offload backup data directly to cloud-based object storage such as Amazon S3, Azure Blob, and IBM Cloud.
- Capacity Tier – consists of one or more scale-out backup repositories.
- SOBR (Scale-Out Backup Repository) – consists of the Performance and Capacity Tier extents.
The Veeam Cloud Tier was created to extend object storage integration (Amazon S3, Azure Blob storage, IBM cloud object storage, S3-compatible service providers or on-premises storage offerings) to include unlimited capacity with no additional charges for cloud storage or subscription charges. Veeam Cloud Tier is also hardware agnostic so there is no dependency on any specific type of hardware. With Veeam, you receive Backup and Replication with the functionality listed above depending on the license type.
The purpose of Veeam Cloud Tier is to shift data from expensive local storage to less expensive cloud based storage solutions. The data is shifted in tiers (chunks as Anthony put it) and is not intended to act as an archiving solution.
The key takeaways for Veeam includes no subscription fees (Keep It Simple for the customers), offloaded backup files remain on the Performance Tiers by dehydrating the data. This essentially creates a shell that is local but reduces cloud charges, provides the ability to rebuild objects if data is lost but still provides full functionality (instant recovery, entire computer and disk-level restore, and file-level and item-level restore) because the data is being tiered and NOT archived.
Starting from the top left, the metadata is moved from the (SOBR) Scale-Out Backup Repository (Performance Tier) to the top right (OSR) Object Storage Repository (Capacity Tier) , then the remaining chunks of data are shifted to the OSR leaving behind the shell (dehydrated VBK) that only includes the local metadata in the center image.
There are two methods to offload the data:
- Operational Restore Window – create a landing zone (aka operational restore window) that is defined in the SOBR configuration. It can be set to however many days you deem fit including zero days but it’s recommended to have some local data for faster restores and instant recovery.
- Sealed Backed Chain – Backup data is collected from extents, then the data is moved based on conditions, the data is then offloaded by the Veeam agent to a Capacity Tier and the jobs can be run in two methods (PowerShell or the UI) every 4 hours by default.
By default, Veeam has 4 different block sizes (before compression):
- Local Target (16 TB + backup files): 4096 KB data blocks
- Local Target: 1024 KB data blocks
- LAN Target: 512 KB data blocks
- WAN Target: 256 KB data blocks
Intelligent Block Recovery (IBR) can reduce Egress charges and if you’re interested calculating Capacity Tier Sizing, Timothy Dewin has provided the following calculator for your convenience. To learn more about Anthony’s live demo, please click here.
David Hill was up next and his presentation was focused on the The Veeam Availability for AWS.
Veeam Availability for AWS is a combination of two Veeam products (N2WS Backup & Recovery and Veeam Backup & Replication Instance management).
N2WS Backup & Recovery is deployed in AWS, which is used to manage all the instances and then Veeam uses the external repository feature in Veeam Backup & Replication Instance management to manage the AWS backups.
AWS capabilities are readily available but cost is a consideration. This is where Veeam comes in because it provides additional capabilities which includes protecting production workloads including archiving to S3, VPC (Virtual Private Cloud) backups, and file recovery to name a few.
Disaster recovery native for AWS provides security for cross account disaster recovery which includes protection against malicious attacks. Backups include Amazon Dynamo DB, Oracle and MySQL database services that can be backed up and restored in AWS.
For more information about the N2WS interface and its features, I would recommend following David’s live demo.
To close out the Veeam session, Anthony Spiteri capped it off with his Veeam for Cloud and Service Providers presentation.
The purpose of this discussion was to focus on the differentiators as it applies to Veeam technologies and the VCSP program. I would recommend watching the video presentation to follow along which includes a detailed description how Veeam has evolved over the years including its technology and features, particularly over the past 4 years.
As you can see from the images above, Veeam has a foot print across the various services which includes IaaS, BaaS, RaaS, DRaaS, TaaS, and SaaS.
If you’d like to connect with any of the Veeam presentators, their contact info is found below.
For more information about Veeam, Tech Field Day and how to become a TFD – please click on the links below:
Please take a moment to subscribe to the YouTube channel which also includes watching the various videos that were posted throughout the day. Kudos to PrimeImage Media for recording the live sessions.
Thanks again to our sponsor Veeam for hosting a wonderful event and I can’t thank Ken Nalbone, Stephen Foskett, Ben T. Gage and the wonderful people at Tech Field Day and Gestalt enough for allowing me to join them.