Veritas CloudPoint Install - Tips and More Tips!

Hi Friends,

I've been busy working away and installing software so I can show you all the coolness Veritas has to offer.  I've been recently tackling Veritas CloudPoint (CP).  This is a SUPER cool piece of software the integrates with your existing NetBackup infrastructure.  Basically the CP server lets you talk to your cloud provider(s) so you can backup stuff in the cloud or to the cloud, depending on how you'd like to architect your environment.  LOTS more to come on this.

Here's a few new cool CloudPoint features that were introduced in NetBackup 9.1:

• Cloud autoscaling dynamically resizes cloud resources, ensuring your protection needs are met while optimizing storage costs and resources.

• Cloud intelligent policies lets you back up snapshots to anywhere using the same protection policies on-premises and in the cloud.

• Native Kubernetes support provides integrated, scalable, container-agnostic protection for all major Kubernetes deployments across all architecture layers.

• Cloud immutable storage with support for immutable Object Lock storage on AWS S3 ensures backup data integrity and prevents your data from being compromised.

What would Neil's blog be without a friendly tip on something I messed up on and don't want you to have to suffer as well?

CP runs within a Docker container, so if you've never worked with Docker, you might want to have a look at some of their docs to get you familiar with the technology.

I was following the instructions in the CloudPoint Administrator's Guide and it was time to deploy the CP image after I installed Docker.

After you download the CP software, it's time to load up your CP software into Docker:

# sudo docker load -i Veritas_CloudPoint_2.x.x_IE.img.gz

Okay, that was easy enough.

Next it's time to install the software:

# sudo docker run -it --rm -v /<full_path_to_volume_name>:/<full_path_to_volume_name> -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:<version> install

Wow, there's a lot there!

Okay, here's where I messed up:

/<full_path_to_volume_name>:/<full_path_to_volume_name>

Sooooo what is the full path to the volume name?  Well, according to the document:

<full_path_to_volume_name>

Represents the path to the CloudPoint data volume, which typically is /cloudpoint.

Stupid me, I decided to put something else, cause why be like everyone else?

When I ran the process everything was going cool until it hit:

"Creating self signed keys and certs for nginx".

And then it froze....  After MANY uninstalls and re-installs I decided to go talk to my good friend Google.  And wouldn't you know it.

SOLUTION!

Yep, there was an article describing EXACTLY what I saw and how to fix the problem.

Problem

When attempting to install CloudPoint to a directory other than /cloudpoint, the installation hangs at "Creating self signed keys and certs for nginx".

Error Message

N/A

Cause

Currently we only support installing CloudPoint at /cloudpoint location.

Solution

If the cloudpoint mount point is not /cloudpoint, then unmount the current mount point and re-mount it as /cloudpoint.

Then re-attempt the installation:

# docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:<version> install

So make sure when you install your CP server, don't be like Neil and choose whatever for your install directory.  Choose /cloudpoint:/cloudpoint.  You'll save yourself hours of swearing, headaches, and pain in general.  :-)

Until Next Time!

Neil