hit counter script

Veeam S3 Immutable

Veeam S3 Immutable – Today’s topic will be about Cloud Native workloads within Azure & AWS and how to best adhere to Veeam’s 3-2-1-1-0 best practices and how concepts can differ from traditional on-premises data protection. Remember the 3-2-1-1-0 best practice is a minimum desired standard and going above and beyond these minimums will help your data availability and recoverability goals.

The public cloud has presented a major transformational opportunity for organizations, the pay-as-you-go model allows organizations to deploy quickly and without the overhead of infrastructure management. But these platforms are still part of a shared-responsibility model, with a key risk you retain, the protection of your data.

Veeam S3 Immutable

Veeam S3 Immutable

Let’s start with the easiest one. Three copies of your data, including your production data. Public cloud services like Azure will inform you that they keep three synchronous copies of your data as a minimum via their “Locally Redundant Storage” offering, or by using “Zone-Redundant Storage” to synchronize three copies of your data across three Availability Zones to keep within the primary region. It should not be recognized as more than a single copy of data, due to the synchronized state. Any damage or deletion of data will affect all copies simultaneously.

Beat Ransomware With Double Play Immutability From Veeam

Instead, use the original Veeam Backup offering for the public cloud of your choice to create backups of your data, this will enable you to create copies of data that are independent of the state of the production data. We will soon touch on what types of backups we can use to meet these criteria.

The purpose of copying your data to multiple media types is to prevent a problem from occurring that affects all of your recoverability scenarios. For example, if you stored all your data in AWS S3 buckets, but you lost access to your AWS tenant, you lost access to all copies of your data.

So how can we escape our Azure/AWS storage offerings? The best way is to use a Veeam Backup & Replication server, either on-premises or within another data center isolated from your public cloud. Deploy the Veeam Backup for Microsoft Azure / Veeam Backup for AWS plugin and create a backup copy task. This will allow you to take copies from the cloud to your own environment, and by extension your own storage media of choice.

This one is simpler, if your data is backed up within a specific public cloud region, make sure at least one of your backups is not within the same region. If you use Azure’s Northern Europe as your primary production and primary backup region, a regional failure will affect both copies of data. To counter this, you can copy to another public cloud region such as Western Europe or outside the public cloud to your own infrastructure using the guidelines discussed in the previous point above.

Kasten K10 By Veeam With Suse Rancher

Depending on your public cloud vendor, you may already have an option available. AWS supports immutability on S3 storage, while Microsoft does not yet have a publicly available immutable storage option. Fear not, because these are not the only options. Using the Veeam Backup & Replication plugin, it is still possible to run backup copy jobs to the following immutable locations:

There are multiple considerations when deciding which option best suits your business, my default recommendation is for Veeam Cloud Connect due to the true isolation it provides, as you and your team have no management capabilities over a service provider’s infrastructure, eliminating the insider threat, no one can steal a tape or USB drive or gain physical access to destroy it. While the availability of all backup copies via the Internet allows for much faster recovery as opposed to tape or USB on average. Why do I recommend Veeam Cloud Connect over an S3 provider? Typically, the IT administrator who established the account with the S3 storage provider has much more control over the data. But by using Veeam Cloud Connect instead, we can ensure a level of independence of the copy of data.

If this was normally an on-premises deployment, I would recommend configuring SureBackup/SureReplica, but unfortunately these technologies do not currently exist within the public cloud space. However, it is still possible to restore copies of VMs within the public cloud and use functionality such as Instant VM Recovery to manually test backups of the public cloud within your own infrastructure, or use the restore to AWS/Azure mechanisms to starting it from a whole. different public cloud.

Veeam S3 Immutable

The lack of SureBackup does not mean that this process has to be done manually, it is entirely possible via the Veeam PowerShell module to create your own custom testing of your backups automatically via scripting. It’s worth reading what you can do with Veeam and PowerShell (a lot).

Achieving 3 2 1 1 0 Protection For Cloud Native Workloads

Hopefully, through this post, you’ve compared your current data protection and found ways to make it more robust.

Be sure when designing a data protection strategy to consider not only the technical obstacles that may necessitate data recovery, but also environmental and commercial ones. If a billing issue with a public cloud vendor can shut down your environment and leave your backups inaccessible, you’ve allowed your data to be held to ransom from the vendor.

Likewise, if you choose to have off-site copies, the greater distance between them will help further protect against environmental issues. If you used both AWS and Azure in London, a disaster in this city could cause an incident affecting both copies of data, but using London and Berlin would dramatically reduce the chances of a simultaneous disaster.

Michael Paul – #VeeamLegend | #VeeamVanguard | Veeam Certified Architect | VMware vExpert | https://micoolpaul.com | Twitter: @MicoolPaul

How Stonefly And Veeam Offer The Best Ransomware Protection

Sorry, we’re still checking this file’s contents to make sure it’s safe to download. Please try again in a few minutes.Architecture Cloud Operations & Migrations for Games Marketplace News Partner Network Smart Business Big Data Business Productivity Cloud Enterprise Strategy Cloud Financial Management Compute Contact Center Containers Database Desktop & Application Streaming Developer Tools DevOps Front-End Web & Mobile

HPC Industries Integration and Automation Internet of Things Machine Learning Media Messaging and Targeting Microsoft Workloads on Networking and Content Delivery Open Source Public Sector Quantum Computing Robotics SAP Security Startups Storage Training and Certification

Many customers use Veeam Backup & Replication to protect their on-premises infrastructure and want to reduce the amount of physical backup infrastructure they need to purchase and maintain. They also want to ensure that their backups are in highly durable, cost-effective storage. Storage services such as Amazon S3, Storage Gateway and Snowball Edge integrate seamlessly with Veeam Backup & Replication to meet these needs.

Veeam S3 Immutable

Veeam Backup & Replication enables customers to automatically tier backups to Amazon S3 to help reduce their reliance and costs associated with more expensive on-premises backup storage. Initially released in version 9.5 Update 4 in January 2019, Veeam Backup & Replication has been used by customers such as Best Friends Animal Society (case study) to improve their DR strategy while providing cost savings. In February 2020, Veeam released Veeam Backup & Replication Version 10, which added additional functionality to capacity level. Capacity tier is an additional tier of storage that can be attached to a scale-out backup repository.

Disaster Recovery With Veeam

In this blog post, we review the options and best practices available to Veeam customers looking to integrate with storage services, based on knowledge learned both in the lab and in the field. In addition, we discuss strategies to help you leverage Veeam Backup & Replication to restore your workloads on-premises as Amazon EC2 instances for disaster recovery (DR) purposes. By the end of this post, you should have a better understanding of how the integration between Veeam Backup & Replication with Storage services works. You’ll also have information to decide which approach will work best for your organization’s use case, including any caveats to note when implementing these integrations.

Scale Out Backup Repository (SOBR): A SOBR is a logical entity consisting of one or more backup repositories configured as tiers. A SOBR is used as a single target for backup and copy jobs. Customers must configure a SOBR that includes a performance level that provides fast access to data with locally hosted backup repositories as direct-attach block storage, NAS storage, or a deduplication appliance. The SOBR also allows customers to define a capacity level useful for long-term storage, where Amazon S3 is used as the object storage repository.

Veeam customers can also use Snowball Edge as an object storage repository to seed large initial backups to Amazon S3. Snowball Edge is a small, rugged and secure portable storage and edge computing device used for data collection, processing and migration. Snowball Edge appliances are purpose-built to move multiple terabytes of data offline to overcome the challenge of limited bandwidth. Snowball Edge encrypts all data at rest with 256-bit encryption with customer-supplied keys using the Key Management Service (KMS). This can be useful for customers with large volumes of on-premise backups that may

Veeam immutable backup azure, s3 immutable, immutable storage veeam, veeam azure immutable, wasabi immutable veeam, veeam immutable backup aws, veeam cloud connect immutable, veeam 11 immutable backups, veeam immutable backup s3, veeam immutable linux repository, azure immutable storage veeam, veeam immutable backup

Leave a Reply

Your email address will not be published. Required fields are marked *