• EN

Topics started by olivier.rossi

12 Topics

olivier.rossi
olivier.rossiVeeam MVP
posted in Veeam Backup and Replication

Single production data center to an offsite datacenter with ObjectFirst repositories 1,000 VMs

Updated 12.1The environment described in this architecture is one main datacenter containing 1,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of used storage space. All backups will be targeted to a primary backup repository and copied to a secondary offsite location. Proxies are installed on a physical server and use the network transport (NBD) method. The backup target will be ObjectFirst Ootbi set for Immutability and accessed via Gateway servers.

2
leduardoserrano
18 days ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

SOBR - Switching Capacity Tier Vendor

IntroductionVeeam Capacity Tier allows the addition of an object storage-based extent to a Veeam Scale-Out Backup Repository (SOBR). This object storage could be on-premises or could be hosted by a cloud provider. Regardless of your chosen platform, Capacity Tier provides a cost-effective way to tier backup data from on-prem 'Performance' extents to Object for longer-term storage.We encourage you to read and understand the Product documentation on Capacity Tier at https://helpcenter.veeam.comThere are a number of reasons why switching Capacity Tier vendor might make sense to you. Perhaps there was a change in your corporate strategic alliances, or perhaps a simple cost analysis has revealed that deeper savings could be found elsewhere.Switching object vendor comes with a few challenges:You need to keep your old Capacity tier around until its retention expires and you want to be able to restore from it as well. You don't have "spare" performance tier storage available and thus creating

6
Ralf
1 month ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

Object Storage: Secure access to ObjectFirst-based repositories

IntroductionRansomware attacks are top of mind for all IT professionals and backups are the last line of defense.The single most important best practice is to make sure you can recover from your backups by: Implementing immutability Encrypting your backups Verify recoverability Have a recovery plan Harden and limit access to your backup infrastructure, especially the repositories.  Ample security guidance can be found in Veeam's user guides and best practices.Curated by Veeam Solutions Architect and Systems Engineers, Veeam has also published a library of Technical Security Blueprints to address joint Vendors configurations. In this post, I would like to focus on Hardening and Limit Access to ObjectFirst repositories. For those unfamiliar with ObjectFirst, it is a Veeam dedicated S3-Compatible Object Storage appliance that implements Out Of The Box Immutability (Ootbi) and leverages Veeam Smart Object Storage API.My colleague, SteveF, has blogged about the SOS API and ObjectFir

7
Geoff Burke
4 months ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

Object Storage: Backup directly to AWS S3 - step by step recipe

IntroductionV12 is launching (register here) on Valentine's day and one of the most anticipated feature is the ability to backup directly to object. As my Valentine's gift to you, I wanted to highlight what's required to get your first V12 backup Direct to AWS S3 going. What do we need?An S3 bucket, an IAM user with the proper policy and a VPC for the helper appliance. A quick note about the V12 direct to object "helper" applianceIn the context of direct backups to AWS S3, the helper Appliance is a temporary EC2 instance that Veeam leverages to perform backup file health-checks.The benefit is to avoid having to "pull-down" any of the backup data on-premises to perform that maintenance operation. You configure the helper appliance settings at the Mount Server step of declaring your Object Repository.Giving the proper permissions in your policy, Veeam gives you the option to auto-create the required VPC, Subnet, Security Group and Route table.I personally would rather set all of this up-

8
olivier.rossi
5 months ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

SOBR: Veeam Capacity Tier – Calculations and Considerations (in v11)

IntroductionSOBR is a logical construct allowing a backup administrator to group storage extents together to form a multi-tier storage "pool" to ease the management of backups.The Performance Tier holds the "operational restore window" parts of the backups on-premises, typically on block or file-based storage, while both the Capacity and Archive Tiers allow expansions to Object Storage.The Capacity tier offers two types of offload operations:Copy Move (after x days).Note: You can combine both offload operations.When offloading backups to the Capacity Tier, the “.VBK” or “.VIB” shell is cracked open. Veeam backup Meta-Data and Data bits become Objects stored onto the Capacity Tier via PUT operations.Note: It is safe to assume that 99% of all objects created are backup Data bits, the rest is backup Meta-Data.With most public cloud providers, API operations are not free.If you are considering an "on-premises" Object Storage solution, be mindful of vendor-specific limitations in their abil

10
Scott
7 months ago
olivier.rossi
olivier.rossiVeeam MVP
posted in YARA and Script Library

Is this share already protected?

IntroductionOver the past few months, I have had customers report over-consumption of VUL, when leveraging Veeam NAS backups.Veeam NAS backup is licensed by the amount of protected source data. The protected data amount is rounded down to the nearest 500GB and consumes one VUL per 500GB (see the user guide for details).The important licensing caveat is that if, for instance, a same share is protected by two different backup jobs, even though it is the same source data, its protected amount doubles (in this particular instance).It easy to see how your VUL consumption can very quickly get out of control. The purpose of that short post is to share a very small script that helps identify if a given share has been backed up multiple times.Note: The script only analyzes the defined shares path and cannot detect any “share alias” set on the NAS device. ScriptThe script lists all NAS backup jobs and combs through its protected shares, sort the data and generates an HTML and CSV report. See the

4
dloseke
9 months ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

How to use the Data Domain repository mtree replica at the DR site?

Scenario:Very recently a customer asked me if Veeam could leverage Data Domain mtree replica for DR purposes.Of course, the answer is YES! While this idea is not new, I thought it would be a good reminder of Veeam’s backup import capabilities. Steps:You must use Data Domain repository on the source site. It most likely will be declared as a DDboost share. The mtree should be replicated to the DR site. Note that the mtree replica will be Read Only! The mtree replica needs to be exposed as a share over your protocol of choice (CIFS, DDboost), so it can be defined in the DR VBR server. In this example, I chose DDboost.Note again that this DDboost share is Read Only! The last step is to declare that DR DDboost share and import backups You should now be able to access these backups from the “Disk (Imported)” section. Remember that you will have to manually rescan that repository in order to refresh new “mtree replicated” restore points.

5
Y
9 months ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

Object Storage: Secure your buckets

IntroductionWith backup direct to object being one of the most anticipated features in v12 AND with the ever-increasing number of cyber-threats, it is paramount to secure access to our buckets.In this series of posts, I will explore v12's direct to object capabilities and offer some suggestions to batten down the hatches.Note: For this post, I will use Wasabi and Minio as my Object Stores of choice. While some slight variations are expected, keep in mind that the same concepts should apply to any S3 compatible target. Restrict bucket access with a simple User IAM policyYou can find the Amazon S3 Object Storage Permissions in the User Guide for VMware vSphere and kb3151 highlights the required steps.Let's review what that looks like in Wasabi's console. For this example, I will configure a simple S3 bucket without immutability. Step 1: Create the policy as described in kb3151This policy grants access to the <<orossisecurebucket01>> bucket to the identity it is associated wit

5
BertrandFR
1 year ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

Object Storage: Handy AWS cli cheat sheet

IntroductionOne of the most notable upcoming Veeam Backup and Replication v12 capability is Direct to “Object Storage” backups.I thought it might come in handy to share a small AWS cli cheat sheet with the community. Initial AWS cli configurationThe first step is to run aws configureAll you need to provide are access key and secret key. You specify the --endpoint-url directly in the commands.Next, make sure you are using v4 signature aws configure set default.s3.signature_version s3v4 Creating a simple bucketaws s3api create-bucket --bucket <yourbucketname> --endpoint-url=<yourendpointurl> --no-verify-sslNote: You don’t necessarily need the --no-verify-ssl option except if like me you are lazy with certificates in your lab. Creating a bucket with object lockCheck out this great post from my colleague Steve Firmes where he discusses “How to avoid an Immutability Migraine”.The command is pretty straight forward:aws s3api create-bucket --bucket <yourbucketname> --object-

2
JMeixner
1 year ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

How to backup Wasabi Cloud NAS with Veeam

Wasabi recently released their Wasabi Cloud NAS offering and you may wonder, like some of the SEs I work with, if Veeam can protect its shares.The answer is: YES, of course!If that is all you need to know then you can stop reading, else keep scrolling down. IntroductionWasabi Cloud NAS is presented as the “Bottomless NAS file storage”.It installs as a service on a windows server and offers a nice and simple UI allowing you to configure your replication and offload policies.Based on these policies, the service will only keep small stub files on local disk. It is 100% transparent to the end user, extremely simple to use and with zero egress/ingress fees from Wasabi, makes for an attractive/interesting NAS solution.How can we protect it? That is what you are about to find out.In this post we will explore some basic backup and restore operations, list some caveats around offline extended file attribute, discuss what happens when you leverage Wasabi Cloud NAS’s file versioning and Complianc

16
JasonBailey
1 year ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

SOBR: Veeam Archive Tier – Calculations and Considerations (in v11)

IntroductionIn a previous post, I covered the SOBR Capacity tier Calculations and Considerations. Today, I will be exploring the Archive tier and discuss how to estimate Archive storage requirements, expected API calls and Proxy Appliance uptime. Before we jump into more details, remember that the Archive tier only works with “Amazon S3 Glacier”, “Amazon S3 Glacier Deep Archive” and “Microsoft Azure Archive Storage” in Veeam v11. In the SOBR configuration, under Archive Tier, you define after how many days (1) you want to free up space from your more expensive capacity tier by offloading to the typically** less expensive Archive Tier.**Keep in mind that the Archive tier is meant to store data for a long time (i.e. more than 1 year, up to 7 or more years). It is not meant for active day-to-day restore operations.You will find that storing data in the Archive Tier for less than 1 year won’t make much economic sense (at least at the time of this write-up!). It is also very important to re

0
olivier.rossi
1 year ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Blogs and Podcasts

Object Storage: Impact of Job Storage Optimization Settings (in v11)

IntroductionObject storage vendors all have configuration considerations that must be accounted for as part of the process of designing Veeam backup repositories. Some of these considerations can be limiting, while others simply help dictate architecture decisions. In this post, I discuss on-premises vendor considerations, and how Veeam job settings can make an impact.To accommodate for vendor specific on-premises Object Storage Device limitations, it is sometimes necessary to adjust Veeam’s storage optimization settings. Every on-premises Object Storage vendor may express these limitations differently, but it usually boils down to the ability to handle large amounts of object metadata (and therefore number of objects) per bucket and/or device.In our experience, using larger storage optimization settings (job block size) with on-premises Object Storage devices typically works best. The bigger the storage optimization settings, the bigger the average object size which means less objects

8
Iams3le
1 year ago

Badge winners

Show all badges
Terms & Conditions