Add new tape library

[RickyB]

I have a master server version 7.0.1 running on a Solaris 10 box with a direct connected SL48 tape library attached that performs all of our local backups.  I would like to attach a C4 library to one of the Solaris clients in another building to do my NetApp filer backups.  The C4 library is attached to the client and I can see the library and the drives from the OS.  What process do I need to perform to allow this server to do the filer backups.  If there is a library attached to it, does it need to have a media server installed on it?  Do I need to install the master on it as well?  Where do I define the robot and drives?  From the original master server?  Do I need to create anything from the new server side console?  I've read I need to update the bp.confs on both sides.  With what?  Please, if any one has any direction for me, I'd appreciate it.

thanks,

rick  

[Marianne]

We can go into detail once you have checked an confirmed all of the following:

Current license key on the master:
You need Enterprise Server license. If you have only NetBackup Server license, you will not be able to add a media server.

If Enterprise Server, you will need to remove Client software on the NBU client and install Server software. For that you will need another Enterprise Server license. You will also need library based tape drive license and NDMP license if you want to use the NDMP option for backups.

Another option is to attach the library directly to the Filer and use instructions in the documentation to add devices on the Filer and in NBU to avoid network traffic. You will need NDMP license and library based tape drive license.

Do you have sufficient license keys to proceed?

[RickyB]

Hi Marianne,

Thanks for the reply.  When I do a "List Registered License Keys" from get_license_key, here is what I get:

License Key:     XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX

Date Added:      Nov 05, 2009 at 15:37:14

Host:                alabama

Product:           Netbackup Enterprise Server

Client count:     See license certificate.

Expires:           No Expiration Date

Feature:           Library Based Tape Drives (Active)

License Key:     YYYY-YYYY-YYYY-YYYY-YYYY-YYYY-YYYY-YY

Date Added:      Nov 05, 2009 at 15:37:14

Host:                alabama

Product:           Netbackup Enterprise Server

Client count:     See license certificate.

Expires:           No Expiration Date

Feature:           NDMP (Active) 

License Key:     ZZZZ-ZZZZ-ZZZZ-ZZZZ-ZZZZ-ZZZZ-ZZZZ-ZZ

Date Added:      Nov 05, 2009 at 15:37:14

Host:                alabama

Product:           Netbackup Enterprise Server

Client count:     See license certificate.

Expires:           No Expiration Date

Feature:           Open File Backup (Active)

Feature:           Remote Client Support (Active)

Feature:           Robotic Library Sharing Support (Active)

Feature:           Remote Media Server Support (Active)

Feature:           Microsoft RSM Robotic Libraries (Active)

Feature:           ADIC DAS/SDLC Robotic Libraries (Active)

Feature:           IBM ATL Robotic Libraries (Active)

Feature:           Fujitsu LMF Robotic Libraries (Active)

Feature:           StorageTek ACS Robotic Libraries (Active)

Feature:           Open File Backup - deprecated (Active)

Feature:           Intelligent Disaster Recovery (Active)

Feature:           Base Netbackup (Active)

I should be able to use any of these on another server right?

thanks,

rick

[RickyB]

Marianne,

We originally direct connected to the filer, but always seemed to have issues controlling the library from the NetApp device.  We could more easily troubleshoot with the library connected to a Solaris box.

thanks,

rick

[Marianne]

Good, you have Enterprise server license for the master, tape drive and NDMP license keys. Your license key certificate will confirm quantities.

You need another Enterprise server license key to install new media server.

You will need to add a SERVER entry for the new Media server in Master's bp.conf.

The current bp.conf will have entries like:

SERVER = <master>
CLIENT_NAME = <master>
EMMSERVER = <master>

You need to add a SERVER entry for the media server below the 1st SERVER entry for the master:

SERVER = <master>
SERVER = <media-server>
CLIENT_NAME = <master>
EMMSERVER = <master>

Restart NBU on master.

Remove NBU client software - see p. 96 of Installation Guide for UNIX and Linux  http://www.symantec.com/docs/TECH127083    for this topic: 'Removing UNIX NetBackup client software'

To install media server, use steps listed in same Install Guide.  See p. 47 onwards for section called 'To install NetBackup media server software'.

The media server's bp.conf will be updated with its own and master server entries during installation.

Install 7.0.1 patch.

Verify comms between master and media with commands such as 'nbemmcmd -listhosts -verbose'.

Ensure NBU can see devices on media server with /usr/openv/volmgr/bin/sgscan

Use Device Config Wizard on the master to add devices for the media server and add Storage Unit.

[RickyB]

Hi Marianne,

Just got back to this after Symantec worked on an issue for the last couple months...  I followed your steps above and was successful up to the "Install 7.0.1 patch." step.  I was unable to install the patch and got the following error:

ERROR: Cannot find required pack NB_CLT_7.0.1.

Exiting NB_update.install

I have the client patch, but I thought we removed the UNIX Netbackup client software earlier.  Did the process to install the media server re-install the client software?  So, should I install the NB_CLT_7.0.1 patch? 

I was able to verify the coms with 'nbemmcmd -listhosts -verbose'

Saw the devices on the media server with /usr/openv/volmgr/bin/sgscan command.

Tried to use the Device Config Wizard on the master to add devices for the media server and add Storage Unit, but the wizard came back with:

"Miscellaneous failure"

and was unable to go past the first screen of the Config Wizard...

thanks,

rick

[Mark_Solutions]

Hi

You need to extract the NB_CLT_7.0.1 into the same directory as the Server one

You only then install the server one but it detects and installs the client one during the process

When the first screen comes up it should say it has found the server and client patch available - just select the server one, it will do the rest for you

Hope this helps

#edit#

Make sure yuou have checked out this tech note in relation to the patches:

http://www.symantec.com/docs/TECH154080

[RickyB]

Hi Mark,

Thanks so much for the help.  I've done the process that you state numerous times before but never for a media server install.  Marianne recommends uninstalling the client software before installing the media server software.  If I install the NB_CLT_7.0.1, I'm installing to something that Marianne suggested should not be installed.  It doesn't make sense based on Marianne's suggestion, but I will apply the client patch, nonetheless.  Maybe that will help me with the Device config wizard on the server side.  Thanks again, Mark. , , , ka;sldkfjal;sdkfjakl;

rick

[Marianne]

Server software includes Client software. The installation guide that I mentioned above says the following on p. 39:
How the installation script works
When you install NetBackup server software, client software is also installed.
 

Subsequent patches needs the Client and Server patch.

All of this is documented in the download URL's, e.g:

NB_7.1.0.1.solaris.tar provides fixes  NetBackup 7.1 master and media servers on Solaris SPARC.
http://www.symantec.com/docs/TECH158811

NB_7.1.0.1.solaris_x86.tar provides fixes for NetBackup 7.1 master and media servers on Solaris x86_64.
http://www.symantec.com/docs/TECH158810

=================
PACK DEPENDENCIES
=================

     -- NB_CLT_7.1.0.1.tar must be installed before this
        Maintenance Release is installed.

[Mark_Solutions]

Im afraid as far as i know there is no option when installing the server component but to have the client available to be installed at the same time buy the server installation

Keep us updated

[RickyB]

I've successfully installed the NB_CLT_7.0.1, NB_7.0.1.solaris and NB_JAV_7.0.1 patches.  I went back to the master server and executed:

nbemmcmd -addhost -machinename nc -machinetype media -masterserver alabama -operatingsystem solaris -netbackupversion 7.0.1

When I tried to "Configure Storage Devices" on the master server, I get a "Miscellaneous failure" dialog box and I have no choice but to cancel the wizard.

Any suggestions would be greatly appreciated.

rick

[Marianne]

Please post output of the following on the master:

nbemmcmd -listhosts -verbose

and

bptestbpcd -host <new-media-server> -debug -verbose

[RickyB]

# nbemmcmd -listhosts -verbose

NBEMMCMD, Version:7.0.1
The following hosts were found:
alabama
        MachineName = "alabama"
        FQName = "alabama"
        MachineDescription = ""
        MachineNbuType = server (6)
sdd
        MachineName = "sdd"
        FQName = "sdd"
        MachineDescription = ""
        MachineFlags = 0x1
        MachineNbuType = ndmp (2) (snapvault)
filer3
        MachineName = "filer3"
        FQName = "filer3.rnetusers"
        MachineDescription = ""
        MachineFlags = 0x1
        MachineNbuType = ndmp (2) (snapvault)
filer3old
        MachineName = "filer3old"
        FQName = "filer3old.rnetusers"
        MachineDescription = ""
        MachineFlags = 0
        MachineNbuType = ndmp (2)
alabama
        ClusterName = ""
        MachineName = "alabama"
        FQName = "alabama"
        GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0xe6
        MachineNbuType = master (3)
        MachineState = active for tape and disk jobs (14)
        NetBackupVersion = 7.0.1.0 (701000)
        OperatingSystem = solaris (2)
        ScanAbility = 5
nc
        ClusterName = ""
        MachineName = "nc"
        FQName = "nc.rnetusers"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0
        MachineNbuType = media (1)
        MachineState = active for disk jobs (12)
        MasterServerName = "alabama"
        NetBackupVersion = 7.0.1.0 (701000)
        OperatingSystem = solaris (2)
        ScanAbility = 5
Command completed successfully.

bptestbpcd -host nc -debug -verbose >bptestbpcd.out 2>bptestbpcd.err

Output to bptestbpcd.out

1 1 1
138.109.250.180:54682 -> 138.109.248.35:1556
138.109.250.180:54683 -> 138.109.248.35:1556
PEER_NAME = alabama
HOST_NAME = nc
CLIENT_NAME = nc
VERSION = 0x07010000
PLATFORM = solaris10
PATCH_VERSION = 7.0.1.0
SERVER_PATCH_VERSION = 7.0.1.0
MASTER_SERVER = alabama
EMM_SERVER = alabama
 

Output to bptestbpcd.err

13:03:43.246 [16631] <2> bptestbpcd: VERBOSE = 0
13:03:43.266 [16631] <2> vnet_pbxConnect: pbxConnectEx Succeeded
13:03:43.266 [16631] <2> logconnections: BPCD CONNECT FROM 138.109.250.180.54682
 TO 138.109.248.35.1556 fd = 4
13:03:43.276 [16631] <2> vnet_pbxConnect: pbxConnectEx Succeeded
13:03:43.282 [16631] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1716: 0:
via PBX: VNETD CONNECT FROM 138.109.250.180.54683 TO 138.109.248.35.1556 fd = 5
13:03:43.282 [16631] <2> vnet_vnetd_connect_forward_socket_begin: ../../libvlibs
/vnet_vnetd.c.540: 0: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a
13:03:43.347 [16631] <2> vnet_vnetd_connect_forward_socket_begin: ../../libvlibs
/vnet_vnetd.c.557: 0: ipc_string: /tmp/vnet-07628321639424382924000000001-.faG5o
13:03:43.412 [16631] <2> local_bpcr_connect: expected reserved port, got 1556
13:03:43.545 [16631] <2> bpcr_get_peername_rqst: Server peername length = 7
13:03:43.608 [16631] <2> bpcr_get_hostname_rqst: Server hostname length = 2
13:03:43.675 [16631] <2> bpcr_get_clientname_rqst: Server client name length = 2
13:03:43.738 [16631] <2> bpcr_get_version_rqst: bpcd version: 07010000
13:03:43.805 [16631] <2> bpcr_get_platform_rqst: Server client platform length =
 9
13:03:43.868 [16631] <2> bpcr_get_version_rqst: bpcd version: 07010000
13:03:43.938 [16631] <2> bpcr_patch_version_rqst: theRest == > <
13:03:43.939 [16631] <2> bpcr_get_version_rqst: bpcd version: 07010000
13:03:44.014 [16631] <2> bpcr_patch_version_rqst: theRest == > <
13:03:44.015 [16631] <2> bpcr_get_version_rqst: bpcd version: 07010000
<2>bptestbpcd: EXIT status = 0
13:03:44.085 [16631] <2> bptestbpcd: EXIT status = 0
 
 

[Marianne]

MachineState = active for disk jobs (12)

Which license keys did you add on this new server?

Did you add Library based tape drive ans SSO license?

Confirn with get_license_key on the media server. (command in /usr/openv/netbackup/bin/admincmd)

If license keys are fine, run this on the master server:

nbemmcmd -updatehost -machinename <media-server> -machinestateop set_tape_active -machinetype media -masterserver <master>

[RickyB]

Hi Marianne,

I added "Base NetBackup", "NDMP" and "Library Based Tape Drives".  I've never heard of the SSO license, so "no" to that one.

Performed a "get_license_key on new media server and it looked good.  It had all three features listed above but without the "SSO" license you listed.

Performed the

nbemmcmd -updatehost -machinename <media-server> -machinestateop set_tape_active -machinetype media -masterserver <master>

and it output:

NBEMMCMD, Version:7.0.1

Command completed successfully.

Attemped the Device Configuration Wizard and got the same result.  "Miscellaneous failure".

Thanks for all your help, Marianne.  What do you think?

rick

[Marianne]

Apologies - I forgot that you have added a dedicated library to the new media server - this thread has started so long ago ... SSO is only needed if the same tape drives are shared between media servers.

Apologies if this a silly question, but did you replace <media-server> with nc and <master> with alabama?

Please run 'nbemmcmd -listhosts -verbose' again and see if media server is now listed as 'active for tape and disk jobs'

This output looks like licensing issues:

        MachineFlags = 0
       .....
        MachineState = active for disk jobs (12)

[Marianne · Accepted solution]

http://www.symantec.com/docs/TECH166601

The bottom half of this TN might shed some light on the reason for your problem:

Cause

On the master server, we can see that MachineFlags for the media server has not been updated by running:

nbemmcmd -listhost -verbose shows:

xxxxxx.xxxxxx.net
       ClusterName = ""
       MachineName = "xxxxxx.xxxxxx.net"
       FQName = "xxxxxx.xxxxxx.net"
       LocalDriveSeed = ""
       MachineDescription = ""
       MachineFlags = 0
       MachineNbuType = media (1)
       MachineState = active for disk jobs (12)
       MasterServerName = "xxxxxx"
       NetBackupVersion = 7.0.1.0 (701000)
       OperatingSystem = windows (11)
       ScanAbility = 5 

Media server has multiple NICs and not communicating to master server on intended NIC

Solution

- PBX log shows that the communication to the master is from different interface, not the interface that is intended to use on the media server.

-------------
2,50936,103,103,1684749,1312512278247,660,2104,0:,61:PBX_Client_Proxy::parse_line,line = ack=1  From 172.16.16.80,0:,0,(0|)
2,50936,103,103,1684750,1312512278247,660,2104,0:,72:PBX_Client_Proxy::parse_line,line = extension=nbrmms  From 172.16.16.80,0:,0,(0|)
-------------

- If interface is not being used, disable un-used interface
- Run bpclntcmd -clear_host_cache on both master and media servers
- Stop and Restart Netbackup services on media server
- MachineFlags should not show 0 now and backup should work.
 

Check output of 'ifconfig -a' on media server.

[RickyB]

Marianne,

yes, it started eons ago....sry, and yes, i replaced media-server with nc and master-server with alabama. :) 

After running nbemmcmd -listhosts -verbose again, the media server is now listed as:

ClusterName = " "

MachineName = "nc"

FQName = "nc.rnetusers"

LocalDriveSeed = " "

MachineDescription = " "

MachineFlags = 0

MachineNbuType = media (1)

MachineState = active for tape and disk jobs (14)

MasterServerName = "alabama"

NetBackupVersion = 7.0.1.0 (701000)

OperatingSystem = solaris (2)

ScanAbility = 5

Sorry for the double spacing.  Does that output look better?

[Marianne]

MachineState = active for tape and disk jobs (14) is what we need to see, but MachineFlags = 0 does not seem right... I don't have exact codes of what 'flags' should be, but I know it has to do with license keys reported by the media server and that it should NOT be 0...

Please check PBX logs on the master for the last 30 minutes and see if you can find the media server IP address :

vxlogview -p 50936 -o 103 -t 00:30:00

[RickyB]

Hi Marianne!

Wow, u are incredible.  I downed, unplumbed and removed (not physically) the second interface on the media server, rebooted the server, cleared the cache, shutdown netbackup, restarted and redid the nbemmcmd command on the master server and the value for MachineFlags was, drumroll please!

MachineFlags = 0xe6

I restarted the Device Configuration Wizard and voila, it scanned my media server and found the devices (two drives and a changer).  I haven't attempted a backup yet, but I'm feeling pretty good about it!

Marianne, thank you SO much for all your help.  You've been incredible.  I will let you know how the backup goes!

thanks,

rick