Posted on by Luis Freixas

Object First OOTBI: Final Steps to Get Ready

Before setting up the S3 bucket, we covered the first boot and initial configuration of the OOTBI cluster.

Now for the fun part: configuring the S3 bucket, adding it to VBR, and sharing my first impressions—all with screenshots, as always!

Open the OOTBI GUI using the cluster IP configured in the earlier steps, then sign in with the objectfirst username and the password you set during installation.
A great initial dashboard, with clear and essential information.
Let’s create our S3 key so we can create the bucket.
Here it is. Save the Key ID and password somewhere safe.
The key has been created and is listed.
We’re now in the S3 Buckets section of the side navigation menu.
Create a bucket with a name and enable versioning for immutability.
The bucket is now created.

Next, add the OOTBI S3 repository to VBR: go to Infrastructure > Backup Repositories > Add Repository.
Object Storage
S3 Compatible
S3 Compatible
These steps should look familiar: enter a name,
the access IP address, region, and credentials. Here we’ll add the S3 key we created earlier.
Accept the certificate.
Great! The bucket is listed. Select it.
VBR asks you to create a directory inside the bucket. I used the same name for consistency.
IMPORTANT: The second checkbox enables immutability. Select it and set the immutability period. In my lab I used one day, but the right value depends on your retention policy. Remember that an immutable backup cannot be deleted until it expires, so size your repository carefully.

Here’s a summary of what we added.
Done! The repository is now listed in VBR.

Now that the repository has been added to VBR, let’s run a simple test with a VM, a job, and one day of immutability.

Test job
Starting with VBR 12, you can send backups directly to S3 repositories. Select the repository and use a short retention policy for this test.
Summary: three days of retention, one day of immutability, and one virtual machine.
The full backup has been created.
Here’s the full backup stored on our OOTBI.
Let’s try to delete the backup. Remember, it has one day of immutability, so we should not be able to delete it.
That’s the expected error: “Failed to delete, immutable.”
The backup is still available, so immutability has protected our restore point from deletion.

I hope you found this deployment and test walkthrough useful.

Next, I’ll test larger machines, Instant Recovery, SORB repositories for Performance and Capacity Tier, and more—one step at a time…

Regards.