Backup Job in Veeam v11 With Wasabi

How do I use a Backup Job in Veeam v11 with Wasabi?

Wasabi is a member of Veeam's cloud partner ecosystem. We have worked with Veeam closely to offer both a seamless implementation and a smooth transition to cloud storage. For more information on how Veeam works with Wasabi, refer to Veeam with Wasabi Solution Overview.

Native S3 interface: The Veeam v11 release has continued its native support of the S3 interface for Veeam's Backup and Replication product. This native S3 interface enables Veeam customers to use S3-compatible storage (such as Wasabi) as a Capacity Tier.  Veeam customers should contact their Veeam account team for specific details.

Using Wasabi Object Storage with Veeam necessitates the creation of a Scale-Out Backup Repository (SOBR). The SOBR requires a Local Performance Tier Backup Repository in order to be created.

If you already have an existing Local Performance Tier Backup Repository and it meets the criteria given in the Veeam Limitations for Scale-Out Backup Repositories Guide, you can use your existing backup repositories.

If this is not the case, you should setup your SOBR with a Local Performance Tier repository based on your chosen type of Performance Tier (Local Storage, DeDeuplication Device, NAS, and so on). There are many ways to achieve this. The Veeam Support team is the best point of contact in order to configure your SOBR appropriately.

Follow the steps below to create a Local Performance Tier using your Veeam local drives. This is an optional step.

Creating Local Performance Tier Repository (Optional)

This section provides steps to create a Local Performance Tier Repository to store your initial backups. Veeam will always take backups to a Performance Tier before it copies/moves them to Wasabi Hot Cloud Storage (also known as Capacity Tier/Object Storage).

1. Log into your Veeam 11 instance.

   

2. Navigate to Backup Infrastructure. Select Backup Repositories.

   

3. Right-click Backup Repositories. Click “Add Backup Repository…”.

   

4. Click Direct Attached Storage.

   This could also be "Network attached storage" or a "Deduplicating storage appliance", depending on your specific environment. Contact Veeam Support for more information about integrating NAS or other de-duplication appliances.

   

5. Click Microsoft Windows.

   

6. Enter a Name and Description. Click Next.

   

7. Click Populate. Select your desired local storage drive.

   In this case, we have a local OS drive C:\ and a storage drive called Z:\. We will be using Z:\ for the Local Storage Repository.

   

8. Input the path to the folder in which to use, or use the default of Backups. Click Next.

   

9. In the Veeam Backup and Replication pop-up, click Yes to use the recommended ReFS volume formatted with 64K cluster size.

   Depending on the formatting of the drive that you chose in Step 7, this window may or may not appear.

   

10. Leave the default settings for Mount Server. Click Next.

    

11. On the Review page, click Apply.

    

12. On the Apply page, click Next.

    

13. On the Summary page, click Finish.

    

14. In the Veeam Backup and Replication pop-up, click No to decline changing the configuration backup location to the new repository.

    A backup repository containing a Configuration Backup Job (the backup of Veeam's configuration and settings), cannot be a part of an SOBR. Therefore, you do not want to use the newly created local repository as the target for the Configuration Backup Job.

    

    You will now see your newly created Local Performance Tier Repository in the Backup Repositories list.

    

Creating a Wasabi Capacity Tier Repository

This section lists the steps to create the configuration for the actual Wasabi Hot Cloud Storage Repository. It is the only place you will be interacting with Wasabi in the configuration process. You will need to have already created a Wasabi Bucket and need both your Access Key and Secret Key for your Wasabi account.

1. Right-click Backup Repositories. Click “Add Backup repository…".

   

2. Click Object Storage.

   

3. Click S3 Compatible.

   

4. Enter a Name and Description.

   

5. Enter the following information:

   • Service Point: s3.us-east-2.wasabisys.com

   • Region: us-east-2

   • Credentials: Your Access key and Secret Key

   This configuration example discusses the use of Wasabi's us-east-2 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL as described in Wasabi Service URLs.

   

6. Click Add... Input your Wasabi Access key and Secret key credentials. Click OK.

   

7. Click Next.

   

8. Select an existing bucket and click Browse to create a new folder. Click New Folder in the desired bucket.

   

9. Click Apply.

   To leverage Veeam with Immutable Object Storage, refer to the Veeam Object Lock Integration guide, as you will have created a bucket with Object Lock support.

   

10. Review the Summary. Click Finish.

    

    You will now see your newly created Wasabi Hot Cloud Storage Repository in the Backup Repository list.

    

Creating a Scale-out Backup Repository

This section lists the steps to create a Scale-Out Backup Repository (SOBR). In Veeam terms, this is a combination of a Performance Tier Repository and a
Capacity Tier Repository. They work in conjunction as follows: First, the backups are created directly to the Performance Tier Repository. Once the backups are created, they are copied or moved over to your Capacity Tier Repository depending on your settings. You must always have as much storage space available in your Performance Tier Repository, as required by your backups.

1. Right-click Scale-Out Repository. Click "Add scale-out backup repository...".

   

2. Provide a Name and Description. Click Next.

   

3. In the Performance Tier section, click Add. Click the checkbox next to the previously created Performance Tier Local Storage Repository. Click Next.

   In this instance, we previously created "My Local Wasabi Repo", so we checked the box next to that.

   CAUTION: You will not be able to continue if you select "Default Backup Repository", this is the default repository where Veeam keeps its local configuration backups. This is why we needed to create a new Local Repository to use for Wasabi.

   

4. Choose the default values for Placement Policy. Click Next.

   

5. On the Capacity Tier configuration page, check Extend scale-out backup repository capacity with object storage. From the drop-down menu, select the Wasabi Hot Cloud Storage Repository that was previously created as a Capacity Tier Repository.

6. Optionally, select one or both of the following options, depending on business needs.

   • Copy backups to object storage as they are created. Checking this box this will immediately copy any backups made into Wasabi Hot Cloud Storage.

   • Move backups to object storage as they age out of the operational restore window, change the days to fit your needs. Checking this box will move backups off local storage after the active backup chain has been sealed, and the backup files are older than X days.

     Selecting this option by itself will not immediately move files into Wasabi. The backup chain must be sealed first by creating an "Active Full Backup", or a "Synthetic Full Backup", then waiting for the operational window to pass. Finally, run the "SOBR Offload Job".

   • Encrypt data uploaded to object storage. By Checking this, Veeam will apply its own third party-encryption before sending objects to Wasabi.

7. Click Apply when you are done making configuration choices.

   

8. Review the Summary page. Click Finish.

   

   You will now see your newly created Scale-out Backup Repository.

   

Creating a Backup Job

This section lists the steps to create a new Backup Job that leverages the newly created SOBR to first run backups locally, then copy these backups to Wasabi based upon the selected settings in the SOBR configuration.

1. Click the Home tab, then Backup Job. Click Virtual Machine.

   

2. Enter a Name for your backup job and a Description. Click Next.

   

3. Click Add to select the VM and select the Virtual machine to be backed up. Click Next.

   

4. Select the scale out backup repository that was created previously (Wasabi Hot Cloud Storage SOBR). Click Next.

5. Optionally, configure Backup Storage Settings.

   • Keep certain full backups longer for archival purposes. Checking this will allow you to configure GFS(Grandfather/Father/Son) backups, which are kept in addition to your backups kept by the retention policy. For more information, refer to Veeam GFS Docs.

   • Configure secondary destinations for this job. Checking this will allow you to assign this backup to be backed up by different type of job called a "Backup Copy Job". A "Backup Copy Job", is a separate job that makes copies of an existing "Backup Job" when it runs. In order to check this box, you will need to have an existing "Backup Copy Job" already created. For more information, refer to Veeam Backup Copy Docs.

   The Retention Policy here determines the number of days, or restore points, for which your backup jobs will be retained after its successful job.

   

6. Leave the default values for Guest Processing. Click Next.

7. Optionally, configure Guest Processing Options.

   To read about the Veeam Specific Guest Procession Options, refer to the Veeam Guest Processing Docs.

   

8. Leave the default values for Schedule. Click Apply.

9. Optionally, configure Scheduling settings.

   To read about the Veeam Specific Scheduling Options, review Veeam Job Scheduling Docs.

   

10. On the Summary page, check Run the job when I click Finish to initiate the backup job. Click Finish.

    

11. Check your Wasabi storage account for the new folder structure created by Veeam. Notice that no backups are stored at this point.

    

12. Return to the Veeam application. Notice that the backup executes.

    

    Once the backup job completes, an offload activity kicks off. This activity moves the backup instantly to Wasabi storage.

    These jobs can be reviewed in the Home -> Last 24 Hours -> Success Page.

    

13. Check your Wasabi storage bucket to confirm that the backup has been stored.