How Do I Add a Veritas NetBackup Media Server?

Hi Friends,

I'm creating a new NetBackup environment and I installed the Primary (Master) server and I noticed a question.  Would you like to add Media servers?  Well no, I haven't installed my Primary yet...  Right?

So after I installed my Primary, I began installing the NetBackup software on my Media servers.  You tell NetBackup it's NOT a Primary, you give the installer the name of the Primary and away you go!

After everything installed, I noticed my new Media servers showed up in the Hosts tab in the Web GUI, but when I tried to add one of my new Media servers as a Storage server, they weren't showing up...  Hmmmm.....

To you NetBackup veterans, you're going to laugh at me, but for the life of me I couldn't figure out how to let the Primary server know this new server was a Media server.

From what I can see, there are a couple ways to do this.  I'm sure there's lots of other ways, so let me know in the comments!  :-)

1. Edit the bp.conf located in /usr/openv/netbackup

2. Add the machine in the Java GUI using jnbSA in /usr/openv/netbackup/bin

=========

Let's tackle number one first.  On the Primary server go to /usr/openv/netbackup and edit the bp.conf file.

Here's what mine looks like:

SERVER = the_name_of_your_primary_server

CLIENT_NAME = the_name_of_your_primary_server

CONNECT_OPTIONS = localhost 1 0 2

EMMSERVER = the_name_of_your_primary_server

VXDBMS_NB_DATA = /usr/openv/db/data

OPS_CENTER_SERVER_NAME = the_name_of_your_primary_server (unless your Ops Center isn't the primary)

MEDIA_SERVER = the_name_of_your_new_media_server

SERVICE_USER = the_user_you_selected

WEBSVC_GROUP = nbwebgrp

WEBSVC_USER = nbwebsvc

TELEMETRY_UPLOAD = YES

The MEDIA_SERVER entry should not exist and this will need to be added.

After you add this line I've seen sometimes having to restart netbackup on the Primary, sometimes on the Media, but for me it eventually popped up as an asset and I could use as a Storage Server.

========

The second way involves opening up the Java GUI (jnbSA) under /usr/openv/netbackup/bin.  When the GUI opens, click on Host Properties > Master Servers.

On the right hand side, right click on your Primary/Master server and select Properties.

Then click on Servers on the left hand side and select Media Servers on the right hand side.  From here, you can add your Media servers, which will add the server(s) to your bp.conf file.

Check your bp.conf file again and make sure the Media server was added.

As I said earlier, I've seen recommendations to restart NetBackup on your Primary server, but for me the newly added Media server popped up as a Storage server in the Web GUI.

And that should be it!  You should be able to use your new Media server(s).

Until Next Time,

Neil

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

Veritas in The Cloud (AWS, Azure, Google Cloud Platform)

Hi Friends,

I'm studying and reading like crazy to learn about Veritas NetBackup goodness because it's been awhile since I've used it.  This is NOT the NetBackup that I used so many years ago, it's got so many cool new features!

You'll probably say, "We already know about this Neil!", but I was so jazzed when I saw some of the new features I wanted to share what I've seen so far.

Just like when I was a System Administrator, you can run NetBackup on prem, but say you want to put your backup infrastructure in the cloud.  I was thinking, you've got to deploy some servers, install the software, make sure everything is configured correctly, yada, yada yada.

The cloud brings great new rewards, but it can be challenging and intimidating if you're not familiar with it.

But wait, what's this?  Veritas NetBackup images right in the cloud stores!  How cool is that?!

Remember I'm still learning, so bear with me here.  :-)

Want to deploy in AWS:

How about Azure:

And last but not least Google Cloud Platform:

Isn't that cool?!  Okay, *I* think it's cool.  :-)

More when I'm more educated!

Neil

Hello World - Part III

Hi Friends,

I've started a new position at Veritas!  I'm super excited to start sharing all the cool things Veritas has in store for you.  I'm going to be focusing on cloud, so feel free to send in requests!

In the mean time, here are some pretty pictures of clouds.  :-)

Until Next Time,

Brain