In this video, we’re going to look at how to create a Veeam Scale-out Backup Repository and leverage the new Cloud Tier feature (or Capacity Tier as you’ll see it named in the interface).

First, we will need to create a repository to use as the Performance Tier. So, we will click on Backup Repositories and then either click Add Repository from the ribbon or right-click. Click Add Backup Repository. We’ll click Direct attached storage. Since I have a local volume to use, we’ll click Microsoft Windows.

Now, we’ll name our repository and give it a description. Click Next. Since the volume is on this server, we’ll click Populate to select it. We’ll select the F drive and click Next. We’ll leave the repository defaults for this video, so we’ll click Next. We’re not using ReFS or fast cloning for this video, so we’ll click Yes. We’ll leave the mount server defaults for this video, so we’ll click Next. Now, we’ll click Apply, and Veeam will create our repository. Click Finish.

Now that we have our local repository, we need to create a repository to use as the Cloud/Capacity Tier. So, we’ll create a new repository. We’ll click Object storage. We’ll click S3 Compatible since we’re using S3 Compatible storage. We’ll name our repository and give it a description. Click Next.

Now we need to enter our service port URL. So, we’ll enter the service port for our S3 compatible storage. Then, we’ll select the credentials which I’ve already supplied to Veeam. Click Next.

We can select the bucket we wish to store our data. Since it’s defaulted to the correct one, I won’t change it. We’ll then specify the folder to store our data. Click Browse. Then, we’ll expand the bucket. If the folder exists, you can select it. We’ll click New Folder and name a new folder. Now that it’s created, we’ll click OK. If we wanted to limit the storage consumption, we could do that here. Since we don’t, we’ll click Next. Our settings are now saved, so we’ll click Finish. Veeam has now created our object storage repository.

Now, we want to put these two repositories together in a Scale-out Backup Repository. In order to do this, you will need at least a Veeam Enterprise license as the Standard license doesn’t support Scale-out Backup Repositories.

So, we will right-click on Scale-out Repositories and click Add Scale-out Backup Repository.

Now, we’ll name our scale-out repository and give it a description. Click Next. Click Add. For the Performance Tier, formerly named an Extent in the interface, we’ll select the local repository we created earlier. Click Advanced to change unique settings for this scale-out repository. For this video, we’ll disable per-VM backup files. Click OK. Now, click Next. Default placement policy is fine for this video, so we’ll click Next.

With Veeam Update 4, we can now extend our scale-out repository to object storage, called Capacity Tier. So, we’ll check the box. If other object storage repositories were created and free, we could select it in the drop down. If we want to define when uploading to the object storage repo is allowed, we can set a window. Click Window. Then, we could define the permitted times. We’ll click Cancel for this video.

Here we have the option to move backups as they age. This option has 2 settings to define when data is moved. The first is if data is older than certain days. The second overrides the first based on free space.

Click Override. Here we can check the box and then set the used threshold that will dictate when data is moved. For this video, we will set the override to 80% capacity. Click OK. Now, we want to set the first setting to 0 days. This will move data as soon as possible as it ages. If we wanted to enable encryption, we could do that here. For this video, we’ll leave encryption disabled. Click Apply.

Now we can click Finish. That’s all there is to it. You have now successfully created a Veeam Scale-out Backup Repository that leverages the new Cloud Tier feature.