HYCU With Wasabi
    • 26 Sep 2024
    • 4 Minutes to read
    • PDF

    HYCU With Wasabi

    • PDF

    Article summary

    How do I use HYCU with Wasabi?

    Wasabi has been validated for use with HYCU, which is a leading multi-cloud backup as a service provider. To setup Wasabi with your HYCU application, follow the instructions below.

    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.

    Reference Architecture

    Prerequisites

    • HYCU version 4.9.0 or above
    • An active Wasabi account

    Configuring HYCU

    1. Launch the HYCU Backup Controller application.

    2. To add a source for the protection environment, click on the Settings gear wheel and select Sources.

    3. In the Sources window, click + New in the Hypervisor tab.

      Note: In this example, the source is a vCenter Server.

    4. In the New Hypervisor window, provide the required details. Click Next and Save in the Summary window.

    5. Click Targets. Click + Add.

    6.  Select "AWS S3" and click Continue.  
    7. Provide a Name for the target and click Next.

    8. Provide the following and click Save:

      — Service Endpoint - example: https://s3.us-east-2.wasabisys.com (enter the service URL for the region your bucket is in - see notes highlighted below).
      — Bucket Name - see Working With Buckets and Objects for details on creating a bucket.
      — Access Key
      — Secret Key

      This configuration example discusses the use of Wasabi's us-east-2 storage region. To use another Wasabi storage region, use the appropriate Wasabi service URL.
      The HYCU application REQUIRES the service endpoint to be prepended with transport definition (https).

      9. The Targets tab will now display the newly added Wasabi cloud storage.10. We need to assign the Wasabi target to a policy. Navigate to Policies on the left side pane. Select the desired policy and click Edit.
      11. In the Edit Policy window, set the Backup options as needed and assign Wasabi as the Target. Click Save.For detailed information on the configuration elements, refer to the section "Setting up an AWS S3/Compatible target" in the HYCU user guide.
      12. Assign the policy to the virtual machines that must be protected. To do so, navigate to Virtual Machines on the left side pane. Select the required VMs and click Set Policy.13. In the Set Policy window, select the desired policy (Gold in our example) and click Assign.

    The protected virtual machines will now be backed up to Wasabi per the configured settings in the policy. 

    Enabling Immutable Backups

    You can use Wasabi’s Object Lock feature with HYCU v4.9.0 and above to make your backups immutable. To protect the backups from ransomware events, this implementation utilizes the Object Lock capabilities offered by Wasabi, which means the retention mode setting and the required retention period will be set on Wasabi and extended by HYCU to match the retention period set in HYCU.  For example, if you set bucket-level object retention in Wasabi to be 30 days and the retention period in HYCU to be two months, HYCU will extend the Wasabi retention period to be two months.

    HYCU supports Compliance and Governance retention modes of Object Lock

    It is highly recommended to use Compliance mode to ensure that the data cannot be modified or deleted by a user (even the administrator) until the retention policy has passed.
    To use Wasabi’s Object Lock feature, the HYCU version must be at least 4.9.0. 

    To make your HYCU backups immutable with Wasabi, follow the instructions below.

    1. Log in to the Wasabi Console and create an Object Lock-enabled bucket.  Enabling Object Lock on the bucket must be performed at the time of bucket creation.  
    2. Select your bucket and click on the gear icon in the top right hand corner.

    3. Click on the Object Locking tab.

    4. Enable Bucket-level Object Retention. Select Enable Compliance Mode. Set the retention period (in our example, the retention period is 30 days) and click Apply.
      The bucket Retention Time configured in this step must be less than the HYCU retention period that is configured in step 11 below.

    5. Once you apply the settings, you will be presented with a confirmation box, type "CONFIRM" and click CONFIRM to apply the settings. 

    6. Login to the HYCU console.  Click Targets. Click + Add.

    7.  Select "AWS S3" and click Continue
    8. Provide a Name for the target and click Next.

    9. Provide the following and click Save:

      — Service Endpoint - example: https://s3.us-east-2.wasabisys.com (enter the service URL for the region your bucket is in - see notes highlighted below).
      — Bucket Name
      — Access Key
      — Secret Key

      This configuration example discusses the use of Wasabi's us-east-2 storage region. To use another Wasabi storage region, use the appropriate Wasabi service URL.
      The HYCU application REQUIRES the service endpoint to be prepended with the transport definition (https).


    10. The Targets tab will now display the newly added Wasabi cloud storage with a lock icon as Object Lock & Bucket-Level Object Retention Time are configured for the bucket.


      We need to assign the Wasabi target to a policy.


    11. Navigate to Policies on the left side pane.  Select the desired policy and click Edit. Scroll down and expand the Targets drop-down menu. Select the Wasabi WORM target configured in Step 9 above as the Target and configure the Retention period.
      The HYCU Retention period must be greater than the Wasabi bucket Retention Time set above in step 4. 
      Click Save.

    12. The next step is assigning the policy to the virtual machines that must be protected. Navigate to Virtual Machines on the left side pane. Select the required VMs and click Policies (Steps 12 and 13 in the Configuring HYCU section above) and select the policy configured in Step 11 in this section above.

    All the backups written to the backup target will now be immutable.