Related Links

    Integrate VAST Data with IDrive® e2

    VAST Data is a technology company founded in 2016 that delivers a high-performance, all-flash data platform optimized for AI workloads and large-scale unstructured data. The platform unifies file and object services using protocols such as S3, NFS, and SMB, supporting GPU-driven analytics across on-premises and hybrid environments. Integrating VAST Data with IDrive® e2 provides a capable, scalable cloud object storage solution that integrates smoothly to extend capacity and support cost-efficient object storage at scale.

    Prerequisites:

    Before you begin, ensure the following:

    1. An active IDrive® e2 account. Sign up here if you do not have one.
    2. A bucket in IDrive® e2. Learn how to create a bucket
    3. Valid Access Key ID and Secret Access Key. Learn how to create an access key.
    4. VAST Data v3.4.0 and later.

    The following steps can help you configure and integrate VAST Data with IDrive® e2

    Configure VAST Data for S3
    1. Log in to your VAST Data cluster management interface (VAST Data Web UI).
      Vast Data Guide - Log in to VAST Data web UI screen
    2. Navigate to Data Protection > S3 Replication Peers.
      Vast Data Guide - Select S3 replication peers screen
    3. In the top-right-hand corner, click + Create S3 Replication Peer.
      Vast Data Guide - Create S3 replication peer screen
    4. In the Add S3 Replication Peer window, select Custom S3 as the Peer Type and provide the following details. Click Create.
      1. Peer name - provide an appropriate name for the replication peer
      2. Bucket name - name of the bucket
      3. HTTP protocol - https
      4. Custom Bucket URL - S3 endpoint URL of the bucket
      5. Secret Key - Enter the secret key
      6. Access Key - Enter the access key
      7. Proxies - Type in the proxies through which replication traffic is routed, if any
      8. Click Create.
        9. Vast Data Guide - Enter details and create screen
    5. The replication peer is created and is displayed on the S3 Replication Peers page. When the cluster can successfully connect to the target, its status will display as Active.
      Vast Data Guide - Active replication peer status screen
    Create a protection policy
    1. Navigate to Protection Policies and click + Create Protection Policy.
      Vast Data Guide - Create protection policy screen
    2. In the Add Protection Policy window, provide a Policy name and select the S3 replication peer created in Step 4 from the Peer dropdown menu.
      Vast Data Guide - Add protection policy details screen
    3. Provide an appropriate Snapshot Prefix and configure the desired replication schedule, and click Create.
      Vast Data Guide - Snapshot prefix and create screen
    Create a Protected Path
    1. In this example, we will be using an existing path in the Element store to create a protected path. To view your existing paths, navigate to Element Store > Views.
      Vast Data Guide - Navigate to Element Store views screen
    2. All the existing paths are listed under Views. We will use the path: /idrivee2-export-test to create a protected path.
      Vast Data Guide - Existing paths listed under views screen
    3. Navigate to Data Protection > Protected Paths. Click + Create Protected Path.
      Vast Data Guide - Create protected path screen
    4. In the Add Protected Path window, provide the following details and click Create.
      1. Path name - enter a name for the protected path.
      2. Choose a policy - select the policy created in Steps 6 - 8 (IDrive® e2 Test in our example)
      3. Path - enter the path from the Element store
        Vast Data Guide - Add protected path screen
    5. The newly created path is listed under Protected Paths. It goes through Initializing, Initial Sync, and finally into the Active state.
      Vast Data Guide - Data protection screen
      Vast Data Guide - Protected paths list screen
      Vast Data Guide - Protected paths active screen

      6. When a protected path is active, it performs an initial data sync to the replication peer or the S3 replication peer (if applicable) immediately after it is created. The initial sync creates the first restore point. Therefore, the restore point created on the start date configured in the Protection Policy is, in fact, the second restore point.