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. More info on how Veeam works with Wasabi can be found in our Veeam with Wasabi Solution Overview.
Note: The data restoration process is handled by your specific backup software application. As there are many potential variables that will affect your unique environment, it is strongly recommended that you seek the guidance of your backup software's technical support team in the event that you encounter difficulty, or have application-specific inquiries.
Native S3 interface: The Veeam v11 release has continued its native support of the S3 interface for Veeam's Backup & Replication product. This native S3 interface allows 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.
Note:
- The steps outlined below require the Veeam v11 release. For other release versions, please check our Main Veeam KB Article.
- The Veeam application requires base licensing of "Enterprise" or "Enterprise Plus" in order to leverage the Scale-Out Backup Repository feature. The SOBR is required for Wasabi Integration. Contact your Veeam sales representative to learn more about Veeam licensing. You can read more about Veeam Licensing on the Veeam Product Features Comparison page.
Table of Contents
1. Create Local Performance Tier Repository
2. Create Wasabi Hot Cloud Storage as a Capacity Tier Repository
3. Create a Scale-out Backup Repository
Using Wasabi Object Storage with Veeam necessitates the creation of a Scale-Out Backup Repository (SOBR). The SOBR, in turn, 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, etc…). There are many ways to achieve this. The Veeam Support team is the best point of contact in order to configure your SOBR appropriately.
Following along in this guide, we will create a Local Performance Tier using your Veeam local drives. This is an optional step.
Caution: Some configuration choices below are used as examples of a typical local data storage environment. Your specific environment may differ from the example. If you are unsure of any configuration changes, it is recommended that you reach out to Veeam support directly.
Create Local Performance Tier Repo (Optional)
This section lists the steps that will allow you to create a Local Performance Tier Repository in order 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 in to your Veeam 11 instance.
2. Navigate to "Backup Infrastructure", then to "Backup Repositories".
3. Right Click "Backup Repositories", then click "Add Backup Repository".
4. Click "Direct Attached Storage".
Note: This could also be "Network attached storage" or a "Deduplicating storage appliance", depending upon your specific environment. Please contact Veeam Support for more information about integrating NAS or other de-dupe appliances.
5. Click "Microsoft Windows".
6. Input a name and description, then click "Next"
7. Click "Populate", and then choose your desired local storage drive.
Note: 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 you want to use, or use the default of "Backups", then click "Next".
9. If you receive a question about recommending using ReFS formatted with 64K cluster size, click "Yes" to proceed anyway.
Note: This may or may not appear, depending on the formatting of the drive you had chosen in step 7.
10. Leave default settings for Mount Server, then click "Next"
11. On the "Review" page, click "Apply".
12. On the "Apply" page, click "Next".
13. On the "Summary" page, click "Finish".
14. Click "No", to decline changing the "configuration backup location" to the new repository.
Note: 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".
15. You will now see your newly created Local Performance Tier Repo in the Backup Repositories List.
Create Wasabi Capacity Tier Repo
This section lists the steps that will allow you 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 you will need both your Access Key and Secret Key for your Wasabi account.
16. Right click on "Backup Repositories", then click "Add Backup repository".
17. Click "Object Storage".
18. Click "S3 Compatible".
19. Input a name and description.
20. Input the following information:
- Service Point: s3.us-east-2.wasabisys.com
- Region: us-east-2
- Credentials (Your Access key and Secret Key)
Note: This configuration example discusses the use of Wasabi's us-east-2 storage region. To use other Wasabi storage regions, please use the appropriate Wasabi service URL as described in our Wasabi Service URLs article.
21. Click "Add...", and then input your Wasabi Access key and Secret key credentials. Then, click "OK".
22. Click "Next".
23. Choose an existing bucket, and create a new folder by clicking on "Browse", and then clicking "New Folder" in the desired bucket.
24. Click "Apply".
Note: If you want to leverage Veeam with Immutable Object Storage, please refer to the Veeam Object Lock Integration guide, as you will have created a bucket with Object Lock support.
25. Review Summary and click "Finish".
26. You will now see your newly created Wasabi Hot Cloud Storage Repository in the Backup Repository List
Create Scale-out Backup Repository
This section lists the steps that allow you to create what is referred to as 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. Then, 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.
27. Create a Scale-Out Repository, Right-click on "Scale-Out Repository", then click "Add scale-out backup repository...".
28. Provide a name and description, then click "Next".
29. In the "Performance Tier" section, click "Add", check the box next to the previously created Performance Tier Local Storage Repo, then 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.
30. Choose default values for "Placement Policy", then click "Next".
31. On the "Capacity Tier" configuration page
- Check "Extend scale-out backup repository capacity with object storage", then, from the drop-down menu, choose the "Wasabi Hot Cloud Storage Repo" that was previously created as a Capacity Tier Repo.
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
Note: 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, and finally, having the "SOBR Offload Job" run.
- Encrypt data uploaded to object storage
- By Checking this, Veeam will apply its own 3rd party encryption before sending objects to Wasabi.
Click "Apply" when you are done making configuration choices.
32. Review "Summary" page, then click "Finish".
33. You will now see your newly created Scale-out Backup Repository.
Create Backup Job
This section lists the steps that allow you to create a new "Backup Job" which 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.
34. Click on "Home", then "Backup Job", and then click "Virtual Machine".
35. Input a name for your backup job, and a description, then click "Next".
36. Choose the VM by clicking on "Add", select the Virtual machine that needs to be backed up, and then click "Next".
37. Choose the scale out backup repository that was created previously: "Wasabi Hot Cloud Storage SOBR", then click "Next".
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, please see the 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, please see the Veeam Backup Copy Docs.
Note: The Retention Policy here determines the number of days, or restore points, for which your backup jobs will be retained after its successful job.
38. Leave default values for "Guest Processing", then click "Next".
Optionally configure Guest Processing Options
Note: To read about the Veeam Specific Guest Procession Options please see the Veeam Guest Processing Docs.
39. Leave default values for "Schedule", then click "Apply".
Optionally configure Scheduling settings
Note: To read about the Veeam Specific Scheduling Options please see the Veeam Job Scheduling Docs.
40. On the "Summary" page, check "Run the job when I click Finish" to initiate the backup job, then click "Finish".
41. Check your Wasabi storage account for the new folder structure created by Veeam and notice no backups are stored at this point.
42. Go back to the Veeam application, and notice that the backup executes.
43. Once the backup job completes, an offload activity kicks off. This activity moves the backup instantly to Wasabi storage.
Note: These jobs can be reviewed in the Home->Last 24 Hours->Success Page.
44. Check your Wasabi storage bucket, in order to confirm that the backup has been stored.
