Wasabi is a member of Veeam's cloud partner ecosystem and we have worked with Veeam on several different methods for interfacing your Veeam environment with Wasabi (as summarized below). More info on how Veeam works with Wasabi can be found here.
- Option 1: Native S3 interface: Veeam has introduced a native S3 interface for Veeam's Backup & Replication product as part of Release 9.5 update 4. As of January 22nd 2019, this release is Generally Available. This native S3 interface will allow Veeam customers to use S3-compatible storage such as Wasabi as a Cloud Tier in Veeam. Veeam customers should contact their Veeam account team for details on this.
- Option 2: VTL (virtual tape library) Gateway approach: This approach involves using a third-party product that interfaces with Veeam over a VTL interface and Wasabi over an S3 interface. Examples of a third-party product that support this capability is StarWind VTL. This capability works with any Veeam version that supports VTL.
(We've also added an FAQ Appendix following these steps)
Option 1: The Native Veeam Interface:
Note that you need a minimum software release of Veeam 9.5 update 4 (Veeam application requires base licensing of "Enterprise or Enterprise Plus" in order to leverage the Scale out Repository feature which is required for Wasabi Integration. Contact your Veeam sales representative to learn more about Veeam licensing. Read more about Veeam licensing)
VIDEO - Watch a video of how to integrate Veeam 9.5u4 with Wasabi here
1. Once the Veeam application is fully installed – Launch “Veeam Backup & Replication Console” and click “Connect” (with appropriate login credentials)
2. This step provides information on how to add Wasabi as a Backup repository; once logged in click on “Backup Infrastructure”
3. Once in “Backup infrastructure” – Click on “Backup Repositories”
4. Then a new repository, click on “Add Repository”
5. Choose “Object Storage”
6. Then click on “S3 Compatible”
7. Application will direct you for Wasabi’s S3 account details:
8. Provide a name, ex: Wasabi Technologies and click “Next”
9. On the “Account” page – provide the following details:
a. Service Point ex: https://s3.wasabisys.com
b. Region ex: us-east-1
c. “Add” next to “credentials” – that will open a window where you can enter Access & Secret Keys. Follow instructions on creating Access & Secret keys
Note that this config example discusses the use of Wasabi's us-east-1 storage region. To use other Wasabi storage regions, please use the appropriate Wasabi service URL as described in this article
10. Once you enter details mentioned above, click “OK” & “Next” on the “Account” page
11. Veeam application will use the data points shared in the previous step to establish connection with Wasabi’s storage – it will then retrieve information from your S3 Bucket layout – Choose the right destination for your data to be backed-up
12. Click “Next” and proceed to “Summary” page.
13. Click “Finish"
14. Navigate to “Scale-out Repositories”
15. Right click on “Scale-out Repositories” and “Add Scale-out Backup Repository…”
16. Issue a “Name” for the Scale-out Repo
17. Click “Next”, in “Performance Tier” page – click “Add” and choose previously created “Backup repositories” and click “OK”
Note: A Scale Out Backup Repository creates a 1:1 relationship with your primary storage & cloud storage, In the Performance Tier configuration all un-allocated primary storage (aka Backup repo) destinations configured will be available to be scaled out to object storage. Include a primary storage and then extend that primary storage to Wasabi as part of the "Capacity Tier" Configuration.
18. After choosing the “backup repositories” via Extents page, Click “Next” in the “Performance Tier” page
19. Choose “Data locality” and click “Next”
20. Check the “Move older backup files to object storage (reduces the long-term retention costs” option & Under “object storage” choose “Wasabi Technologies” For test purposes we set the value for “Move backup files older than” to 0 days – this can be set to a value of your choice based on your deployment and compliance model. Setting the value to 0 will trigger the backups that Veeam has deemed "Closed" to be uploaded to Wasabi. This assessment is done every 4 hours by the Veeam application. Click “Apply”
21. To create a backup job, follow the steps below.
22. Click on “Home” and then click “Backup” right click and choose “VMware vSphere” as shown below:
23. Provide a name for the backup job and click “Next”
24. Once you click “Next” you will be routed to “Virtual Machines” page – Click “Add” and choose all the VMware vSphere servers which are going to be backed up as show below
25. Once you add the servers that requires to be backed up, click “Next” and choose the Scale out backup repository previously created “SOBR01”and click “Next”
The value set for “Restore points to keep on disk” can be adjusted down or up based on the implementation model desired. During Wasabi & Veeam testing the value was dropped to “7”
26. You will be routed to “Guest Processing” page – no changes are required
27. Next page allows you to configure any schedules around your backup job – default value is OK and click “Apply”
28. Once you click “Apply”, summary of your Backup job will be displayed, ensure to click on “Run the job when I click Finish” and click “Finish”
29. Once you click “Finish” – Veeam performs something called as “Active Full backup” – that’s a full backup – backup file from this event will be stored local in the drive configured.
30. The series of backup functions is required in this order.
- Active Full Backup (Right click on Backup Job and choose Active Full)
- Active Full Backup (Right click on Backup Job and choose Active Full)
31. Once you complete the backup functions in the order mentioned above, navigate to “Backup Infrastructure” and hold "control + right click" on”SOBRO1” and choose “Run Tiering Job Now” manually.
Note: Veeam automatically runs the SOBR offload every 4 hours
Once you click on “Run tiering job now” feature – that initiates S3-based backup to Wasabi. Once the action completes, you will be able to locate your backup on Wasabi via the Wasabi Management Console. Sample screen shot below:
Appendix A: Frequently Asked Questions about Veeam implementation with Wasabi Cloud Object Storage
1. How do I onboard Wasabi Cloud storage to your existing or new Veeam infrastructure?
Answer: Veeam application and supported reference architecture requires a customer to retain & manage local storage; the local storage will be your primary storage, all backups are first written to your local/primary storage network - this allows for the backup strategy to have the ability to recover from a disaster situation even if there is a loss of internet connectivity or loss of access to cloud networks. Veeam requires you to retain the most recent backups in local storage. You may then configure the system to backups to Wasabi.
2. How do I create local/primary storage on Veeam Backup & Replication software?
Answer: Following steps below walk you thru adding local backup repository required by Veeam application
A. Click on Backup Repository & “Add Backup Repository”
B. Select "Direct attached Storage" > choose the type of server
C. Provide a name to the local repository (Primary Store) and click “Next”
D. Click “Populate” to list all available drives available to be the backup repository and click “Next”
E. Choose a destination on your local machine (C:\Backups) and click “Next”
F. Choose default values on the “Mount Server” configuration page and click “next” and move to review page.
G. Click “Apply”
3. Why does the Folder structure on the Console look different from my primary store?
Answer: Veeam uses a proprietary method to upload the backups to S3-compatible storage by breaking down the backups into 1MB chunks and each of these 1MB chucks equates to an s3 PUT API call. Prior to uploading the backup to an S3 storage service - Veeam indexes the backup and retains information in your primary storage with pointers on how the data needs to be re-constructed in case recovery from a cloud storage system becomes necessary.
4. How do I duplicate primary storage to Wasabi?
Answer: Veeam recommends that you retain primary storage local to Veeam network and not host the primary storage via cloud. However, you could create a duplicate site for your primary backups and that duplicate site can be located on Wasabi. You many then use a SEPARATE application to copy the backups to that location. There are several pointers to assess before you explore the option:
- Veeam application will always create your backups
- A 3rd party application such as cloudberry (or any S3 compatible client/explorer) will allow you to create a DUPLICATION of your backup that was created by Veeam in a bucket that you create on the Wasabi system.
- VERY IMPORTANT - Veeam application DOES NOT know of the 3rd party application or what its doing to the backup files
- Its very important to coordinate your efforts with both Veeam and 3rd party applications and handle your backup repo's with proper care by experienced Veeam & storage professionals
- If cloudberry application is being considered - please use cloudberry's ultimate edition- as it supports moving over 1TB of data.
- An operational Veeam setup
- Install Cloudberry or other backup software which supports S3 compatible interface (not just AWS S3 compatible)
- Create a backup schedule via the 3rd party application to move/copy your backup to Wasabi storage
- Create your backup via Veeam application
- Note that if you set the "Restore points to store on local disk" to 1 - the Veeam application will keep just one copy on disk
- Use the target you specify for your local Veeam repositories, as the directory being copied over to wasabi or using file explorer type products which allows you mount a cloud instance as an expansion drive (example - W: or X:)
- Please note that Veeam DOES NOT know off the actions 3rd party applications are talking to the backups created by Veeam.
- Above process would create Wasabi as a duplication site for your primary storage
5. While adding Wasabi as a S3-compatible storage, Veeam application is not loading my bucket created on Wasabi?
Answer: We have heard of, but not replicated situations when a previously created bucket is not showing up in the Veeam application. As a workaround, please select the "New Folder" option at the bottom, name this new Folder and click enter. This newly created Folder can be used for Backup which you can locate on the console by going inside the selected Bucket -> Veeam -> Archive -> your New Folder. If you require the backups to be written to your previously created buckets & Veeam application is unable to load the bucket structure - please contact Wasabi support at firstname.lastname@example.org
6. Do I get billed for every Active & incremental backup?
Answer: Wasabi's storage services only get utilized as secondary storage - primary storage is still Veeam. The Full (Active Full) backup and Incremental Backups stay within Veeam infrastructure - Wasabi storage gets utilized only after a manual or automatic "prune to Cloud tier" operation on your Scale out backup repository. Every Full or incremental backup action wouldn't increase or decrease your costs on Wasabi storage. However Prune'ing to the cloud tier will affect your storage utilization on Wasabi
7. Can I backup to multiple cloud destinations?
Answer: Yes. you can configure Veeam to have a additional destination for any job to create a duplicate copy of your cloud storage. You can create additional copies of your backup with either of these two approaches:
- Create a second local backup infrastructure in your Veeam ecosystem and then to point that to a second Wasabi bucket
- Use a 3rd party application such as cloudberry and schedule a backup job on your 3rd party application to push the backup to second Wasabi location
8. How long does Veeam keep backups on Wasabi?
Answer: Please contact Veeam for accurate information about retention policy. Also review the following Veeam Help Center Article
9. How many types of backup does Veeam create?
Answer: Please review the following Veeam Help Center Article for more information.