Master Server Installation
This document is for entertainment purposes only. Use at your own risk. This site is in no way affiliated with Symantec or NetBackup.
- Chapter 23 of the Symantec NetBackup™ Administrator's Guide, Volume I - About the NetBackup relational database (NBDB) installation starting on page 876 and Post-installation tasks starting on page 919.
- Symantec NetBackup™ Installation Guide
- NetBackup 7.6 Late Breaking News
- Check the Hardware Comparability list for compatible hardware
- Check the OS Compatibility list for compatible OS's to install on.
- The easiest and most cost-effective OS in my experience is Redhat or Suse Linux.
- OS Performance Tuning
- Identify the OpsCenter Server
- Copy Server install software to server.
- Create logging directories on alternate/local disk, separate from db/catalog file system.
- Logs can be on local disk, but should still have decent performance.
[root@nbumaster dir]# mkdir openv [root@nbumaster dir]# mkdir openv/logs [root@nbumaster dir]# mkdir openv/nbu-logs [root@nbumaster dir]# ls -al openv/ total 16 drwxr-xr-x 4 root root 4096 Apr 14 16:16 . drwxr-xr-x 5 root root 4096 Apr 14 16:16 .. drwxr-xr-x 2 root root 4096 Apr 14 16:16 logs drwxr-xr-x 2 root root 4096 Apr 14 16:16 nbu-logs
- Mount NBU Catalog filesystem on /usr/openv (or link /usr/openv to filesystem)
- It's best to have the NetBackup Catalog installed on high performance SAN disk.
- It's also helpful for Disaster Recovery (DR) purposes to have this SAN disk replicated to a DR site.
See also: Example NetBackup 220.127.116.11 Install Log
The install binaries for Linux come in a compressed "tar" ball. simply use the "tar" command to extract it:
tar zxvf NetBackup_18.104.22.168_LinuxR_x86_64.tar.gz
This will create a sub-directory named "NetBackup_22.214.171.124_LinuxR_x86_64".
Then run the install
Follow the on-screen instructions. Most of the time the defaults are ok, but it's good to make sure you know what to expect beforehand, and to have a clear understanding of how the backup environment is architected.
You will be asked for the following during the install:
- Verification that you wish to install the NetBackup Server Software (which needs to be a "y" to continue).
- If you want to "Participate in the NetBackup Product Improvement Program".
- probably a "n" unless it's a test environment that has access to the internet
- If "you want to install NetBackup and Media Manager files" (which needs to be a "y" to continue).
- A NetBackup Server or Enterprise Server license key(s)
- The primary network interface to be used as the NetBackup server name of the target machine
- and if it is to be the master server (which is a "y" unless you are trying to install it on a Media Server).
- Optionally the DNS names of any media servers' primary network interfaces to be used for backups.
- The "Enterprise Media Manager server" primary network interface DNS name (most often, but not always, the same as the Master Server's primary backup network interface name).
- If upgrading, it helps to know in advance the number of clients and policies that are currently configured, for verification purposes.
Post Installation Task
Not all of these will be needed in all environments, but these are the most common things that need to be done to to enable you to start using and further configure newly install NetBackup server software:
- Update the "/usr/openv/java/auth.conf" if you plan to use the Java Admin Console with a non-root account.
- Configure NetBackup EMMDB Aliases for any secondary or alternate network interfaces on the master server.
- Move the "logs" directories to a different filesystem, and then create links from the old path to the new path.
- NOTE: It's best to do this with NetBackup shutdown.
- The reasons for this include:
- We don't want to use expensive SAN disk for logs
- We want to replicate the catalog to a DR site, but not the logs with their high update rate.
- We don't want to risk crashing our database because the filesystem filled up.
- We have plenty of high-speed internal raid disks on the server that will go to wast otherwise.
- Edit the "/usr/openv/netbackup/bp.conf" file to make sure the correct Server(s) and Client Name is listed.
- You can also add additional entries for your media servers while your at it as well.
- You can also add a windows "server" (i.e. the OpsCenter server) to be used as a GUI Admin Console server.
- Re-start NetBackup to insure all new settings take affect.
- Additional Configurations for the backup enviorment
Back to NetBackup