Unitrends has been validated for use with Wasabi. For additional info on how Wasabi works with Unitrends, visit this Unitrends Backup and Recovery with Wasabi combines industryleading BCDR with ultra-low-cost cloud storage. Follow the steps outlined below to configure Wasabi as a cloud storage target for your Unitrends backups.
Unitrends Backup performs an initial server-side copy and then deletes the original backup object as part of its object-naming convention. You may notice an increase in the amount of deleted storage shown on your account as a result. To maximize the amount of time your backups are available and to minimize the amount of deleted storage being used, we recommend setting the Retention Period in Unitrends Backup to a minimum of 30 days if you are a Reserved Capacity Storage (RCS) customer, or 90 days if you pay as you go, for backups going to Wasabi. See the Minimum Storage Duration Policy for details.
The data restoration process is handled by your specific backup software application. As many variables can affect your unique environment, Wasabi strongly recommends that you seek guidance from your backup software’s technical support team if you encounter difficulties or have application-specific inquiries.
Requirements
Unitrends software is installed and licensed. This solution was most recently tested with version 10.8.7.
Access to Unitrends Console.
Access to Wasabi Console.
Active Wasabi account with a bucket created for Unitrends backup. Do not configure Object Lock or Versioning on your bucket because Unitrends does not currently support these features. Refer to Working With Buckets and Objects for details on creating a Wasabi bucket.
Adding Wasabi as a Backup Copy Target
Log in to the Unitrends console.
Navigate to Configure select Backup Copy Targets.
Expand the Add target dropdown menu and select Cloud from the list of options.
In the Add Cloud Backup Copy Target window, provide a name for the target.
Under the Storage Details section, choose Wasabi as the Cloud Storage target, enter the following details, and then click Save.
Storage Path - Wasabi bucket name
Wasabi Region - Service URL of the Wasabi region your bucket is located in. Note: This config example uses Wasabi’s us-east-1 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL as described in Service URLs for Wasabi’s Storage Regions.
Access Key ID
Secret Access Key
Under Options, select the checkbox next to Enable storage threshold. Set the Threshold to be an appropriate value for your organization. This will set the maximum amount of Wasabi storage your backups will consume. In this example, 100 TB (100,000 GB) was configured.
IMPORTANT: This storage threshold must be set if you wish to limit the amount of Wasabi storage Unitrends backups will utilize. Otherwise, Unitrends will believe your Wasabi bucket has infinite space. From Unitrends documentation:
The recently added Wasabi account will show up as an Online target.
Adding Assets to be Backed Up by Unitrends
Navigate to Configure, then Protected Assets, then Add.
Click Virtual Host.
Configure the following and click Save.
Hypervisor—Choose the hypervisor type that has VMs needing to be backed up
Hypervisor IP address, hostname, or FQDN that is resolvable and reachable by the Unitrends server
Hypervisor Username
Hypervisor Password
.png)
The virtual host is now listed under the Protected Assets.
Scheduling Job Methods
Choose ONE of the following methods. For details, see Unitrends Backup Administration and Procedures for information on creating backup and backup copy jobs and on scheduling jobs.
Create an SLA policy. This is a quick and easy way to back up locally and to Wasabi. It also helps you meet your organization’s RPO goals. However, it is not as flexible as creating separate backup and backup copy jobs. See the Create SLA Policy section below for configuration details.
Create separate backup and backup copy jobs. This is slightly more complex but offers more scheduling options and greater granular control. See the Creating a Backup Job and Creating a Backup Copy Job sections below for the configuration details.
Creating SLA Policy
Navigate to Jobs, then SLA Policies, and click Create Policy.
In the Create SLA Policy window, provide a name (SLA Policy was used in this example). In the Select Items tab, choose the appropriate option from the dropdown menu (VMware was used in our example) under Inventory, then select the desired VM(s). Click Next.
In the Define Policy Options tab, under the Backup Frequency section, select the RPO that determines how often backups will run.
Click Show Backup Window and choose the window that applies to your backup strategy.
Under the Backup Copies section, select Copy backups daily to the Cold Backup Copy Target and set the Cold Backup Copy Retention Days to the appropriate value for your organization.
Click Save.
NOTE: The “Cold Backup Copy Retention Days” setting works in conjunction with the storage threshold configured above under Adding Wasabi as a Backup Copy Target to delete older backups in Wasabi.
Run a test backup by going to Jobs, then Job Manager, selecting the automatically created SLA backup job.Click Run.
Navigate to Active Jobs. After the job is complete, its status will show Success.
.png)
Run a test backup copy job to Wasabi, navigating to Jobs, then Job Manager. Select the automatically created SLA backup copy job, and click Run.
Navigate to Active Jobs. After the job is complete, its status should show Success.
Proceed to the Verifying That Data is in the Wasabi Bucket section below.
Creating a Backup Job
Refer to the information about Backup jobs in the Administrator Guide for Recovery Series and Unitrends Backup.
Navigate to Jobs, then Active Jobs. Click Create job and choose Backup.
In the Create Backup Job window, provide a job name. In the Select Items tab, choose VMware or the appropriate hypervisor type from the Inventory dropdown menu, then select the desired VM(s). Click Next.
In the Define Job Settings tab, under the Job Detail section, choose Create a Schedule and select the backup type (Full and Incremental were selected in our testing). Set the job schedule. Under Options, select the backup target (Internal was used below). Click Save. Note that the backup copy job to Wasabi will be configured later.
Click OK on the Success screen.
Run a test backup by going to Jobs, Job Manager, selecting the previously created backup job, and clicking Run.
Choose Active Jobs. After the job is complete, its status will show a status of Success.
.png)
Proceed to the Creating a Backup Copy Job section below.
Creating a Backup Copy Job
Refer to information about Backup Copy Jobs in Administrator Guide for Recovery Series and Unitrends Backup.
Navigate to Jobs, then Active Job. Click Backup Copy.
In the Create Backup Copy Job window, enter a name, such as Copy Job to Wasabi. In the Select Items tab, choose the VM(s) that have been previously backed up and click Next.
Configure the following, then click Save.
Backup Copy Type then Backup Copy (Cold)
Backup Copy Target then Wasabi
Backups to Copy, then All backup modes
Retention Period, then set to the appropriate value for your organization.
If the storage threshold is reached, then delete older backup data to free space
NOTE: The “Retention Period” and “If Storage Threshold Is Reached” settings work in conjunction with the storage threshold configured above under Add Wasabi as a Backup Copy Target to delete older backups in Wasabi.
Select when to run this job, then create a Schedule
Configure desired schedule
Range Type then Last Backups
.png)
Navigate to Jobs, then Job Manager. Select the Backup Copy Job going to Wasabi, and click Run.
.png)
Go to the Recent Jobs tab. When the backup copy job is finished, ensure the status shows Success.
Verifying That Data is in the Wasabi Bucket
Log in to the Wasabi Console and confirm the data is stored in your Wasabi bucket.
