08-07-2012 12:16 PM
"There are no entries in the drive database. The NetBackup Device Manager service only needs to run when devices are configured. The service will now exit.ce only needs to run when devices are configured. The service will now exit."
C:\Program Files\Veritas\NetBackup\bin\Admincmd>bpminlicense -list_keys -verbose 1236-456M-789R-012Z-345R-678U-9014-3327-G111-N 1116-111M-111R-111Z-O111-111U-11L 4-JS27-GT8R-N file version = 0x05000000 time added = 0x502163fa 08/07/12 11:52:42 hostname = hsphxmfp01-2.hs.azdhs.gov product ID = 6 NetBackup Enterprise Server serial number = 73583 key version = 0x05000000 count = 0 server platform = 0 Any platform client platform = 0 Any platform server tier = 10 NetBackup Enterprise Server client tier = 0 No tier license type = 1 Permanent Site ID = 2006 Unknown site: 2006 Feature ID = 89 Unknown feature ID: 89 + Feature ID = 84 SAN Client + Feature ID = 83 PureDisk MS Exchange Agent Feature ID = 81 Enterprise Vault Agent + Feature ID = 80 PureDisk MS SQL Server Agent + Feature ID = 79 Flexible Disk Option + Feature ID = 78 OpenStorage Disk Option + Feature ID = 76 Virtual Tape Option + Feature ID = 75 Bare Metal Restore + Feature ID = 74 Encryption + Feature ID = 73 Open File Backup + Feature ID = 71 Remote Client Support + Feature ID = 70 Robotic Library Sharing Support + Feature ID = 69 Remote Media Server Support + Feature ID = 68 Microsoft RSM Robotic Libraries + Feature ID = 67 ADIC DAS/SDLC Robotic Libraries + Feature ID = 66 IBM ATL Robotic Libraries + Feature ID = 65 Fujitsu LMF Robotic Libraries + Feature ID = 64 StorageTek ACS Robotic Libraries + Feature ID = 62 Snapshot Client + Feature ID = 61 MS SharePoint Agent + Feature ID = 58 Inline Tape Copy + Feature ID = 54 Vault + Feature ID = 49 Library Based Tape Drives + Feature ID = 46 DataStore + Feature ID = 43 Encryption (Legacy DES 56-bit) + Feature ID = 42 Encryption (Legacy DES 40-bit) + Feature ID = 40 SAP extension + Feature ID = 38 Sybase extension + Feature ID = 37 Informix extension + Feature ID = 36 Oracle extension + Feature ID = 35 Lotus Notes extension + Feature ID = 34 DB2 extension + Feature ID = 33 MS SQL Server extension + Feature ID = 32 MS Exchange extension + Feature ID = 30 Shared Storage Option + Feature ID = 27 NDMP + Feature ID = 22 Additional clients + Feature ID = 20 Base NetBackup + 111P-111Y-111P-111C-111P-111O-222P-22CN-222Y-J 222P-222Y-333P-333C-333P-333O-444P-555N-333Y-J file version = 0x05000000 time added = 0x50132b03 07/27/12 16:57:55 hostname = hsphxmfp01-2.hs.azdhs.gov product ID = 6 NetBackup Enterprise Server serial number = 657267 key version = 0x05000000 count = 0 server platform = 0 Any platform client platform = 0 Any platform server tier = 10 NetBackup Enterprise Server client tier = 0 No tier license type = 1 Permanent Site ID = 2006 Unknown site: 2006 Feature ID = 84 SAN Client + Feature ID = 81 Enterprise Vault Agent + Feature ID = 75 Bare Metal Restore + Feature ID = 74 Encryption + Feature ID = 73 Open File Backup + Feature ID = 70 Robotic Library Sharing Support + Feature ID = 69 Remote Media Server Support + Feature ID = 68 Microsoft RSM Robotic Libraries + Feature ID = 67 ADIC DAS/SDLC Robotic Libraries + Feature ID = 66 IBM ATL Robotic Libraries + Feature ID = 65 Fujitsu LMF Robotic Libraries Feature ID = 64 StorageTek ACS Robotic Libraries + Feature ID = 62 Snapshot Client + Feature ID = 58 Inline Tape Copy + Feature ID = 49 Library Based Tape Drives + Feature ID = 46 DataStore + Feature ID = 43 Encryption (Legacy DES 56-bit) + Feature ID = 42 Encryption (Legacy DES 40-bit) + Feature ID = 22 Additional clients + Feature ID = 20 Base NetBackup + C:\Program Files\Veritas\NetBackup\bin\Admincmd>
Solved! Go to Solution.
08-07-2012 10:43 PM
Seems like a comms issue with mfp01-2.
Fist of all - you have two separate media server entries for this server - one with shortname and another with FQDN (instead of one entry with emm alias for alternate name).
Checking with the host "mfp01-2"...
Checking with the host "mfp01-2.hs.azdhs.gov"...
When you previously decommissioned this media server, which name did you use - FQDN or shortname?
You should have one entry only - not both (like with other workin media servers).
Also, returned emtries failed for FQDN and shortname returned FQDN for EMM server where other media servers returned shortname.
I have learned that consistency works best - either shortname or FQDN - not a mix.
I have also seen that media servers that cannot be contacted cause all sorts of issues with resource broker on the master server - like jobs queing for long times and long delays between identifying resources and assigning them.
So, my suggestion is to first of all get rid of FQDN for media server to avoid attempts to communicate with it:
<unknown> UNKNOWN RELEASE (-2)mfp01-2.hs.azdhs.gov <unknown>
*Failed to get the configuration for the host "mfp01-2.hs.azdhs.gov". client hostname could not be found(48)
nbemmcmd -updatehost -machinename <media-server> -machinestateop set_tape_active -machinetype media -masterserver <master>
08-07-2012 12:28 PM
I have honestly never seen capacity-based license causing issues....
Have you entered the same license key on master and all media servers?
Please post output of these command on master (this will confirm comms with media server):
nbemmcmd -listhosts -verbose
nbemmcmd -getemmserver
08-07-2012 01:51 PM
I'm not certain it's a licensing issue or not, but that's what all the errors seem to point to. The same license key is installed on master and media servers, except the mfp01-1, which seems to be working, although I haven't restarted services on it. mfp01-2 is the one in question. Mexmb01 also had the same issue, though I can't reproduce it now because services were set up to start as the netbackup user, which our admin seems to have lost the password (but I digress). Our deduplication server dd01 does not have the problem, and I've attempted to install the same keys (our older licenses, licensed for a count of 8 Windows) on the mfp01-2.
08-07-2012 10:43 PM
Seems like a comms issue with mfp01-2.
Fist of all - you have two separate media server entries for this server - one with shortname and another with FQDN (instead of one entry with emm alias for alternate name).
Checking with the host "mfp01-2"...
Checking with the host "mfp01-2.hs.azdhs.gov"...
When you previously decommissioned this media server, which name did you use - FQDN or shortname?
You should have one entry only - not both (like with other workin media servers).
Also, returned emtries failed for FQDN and shortname returned FQDN for EMM server where other media servers returned shortname.
I have learned that consistency works best - either shortname or FQDN - not a mix.
I have also seen that media servers that cannot be contacted cause all sorts of issues with resource broker on the master server - like jobs queing for long times and long delays between identifying resources and assigning them.
So, my suggestion is to first of all get rid of FQDN for media server to avoid attempts to communicate with it:
<unknown> UNKNOWN RELEASE (-2)mfp01-2.hs.azdhs.gov <unknown>
*Failed to get the configuration for the host "mfp01-2.hs.azdhs.gov". client hostname could not be found(48)
nbemmcmd -updatehost -machinename <media-server> -machinestateop set_tape_active -machinetype media -masterserver <master>
08-07-2012 11:19 PM
I will try to get rid of the FQDN. I don't know where they came from (other admin, maybe?). I stay pretty consistent in using hostname only.
08-08-2012 01:07 AM
I see that quite often in bigger environments with more than one admin.
Normally creates major confusion within NBU...
08-08-2012 04:53 AM
that media server (FQDN) shows "not reachable by master".
If you do a bptestbpcd against that media server, guess it would either hang or return an error.
I agree with Marianne that hostname resolution needs to be sorted out first. The license could be impacted as it's tied to hostname, try to see if you get error when doing a:
/usr/openv/netbackup/bin/admincmd/get_license_key
It will give you error if the hostname you currently use for that media server is incorrect (FQDN instead of shortname or vice versa)
08-08-2012 10:08 PM
After removing the media server from the EMM db, it looks ok, and I can activate it manually for tape and disk, but after I try to re-add the robot and drives via the Admin console, the FQDN shows back up.
08-27-2012 03:53 AM
1. Try to inspect your admin-logs on master server to check when this record was created.
2. If your master can't resolve mfp01-2.hs.azdhs.gov and if mfp01-2.hs.azdhs.gov and mfp01-2 are the same try to add record into /etc/hosts at master-server.
3. Try to run on the problem media-server:
bpclntcmd -self
4. Try to run on the master server:
# nbemmcmd -machinealias -getaliases -machinename mfp01-2.hs.azdhs.gov -machinetype media
# nbemmcmd -machinealias -getaliases -machinename mfp01-2 -machinetype media