Forum Discussion

Level 5

13 years ago

NetBackup 7.1 Media (Device) Manager Won't stay started

We recently switched to capacity-based licensing and now our Windows media servers won't start as media servers. The first symptom of this was that we were having trouble with one of our media servers, so we decommissioned it and re-installed it (following documented instructions from NetBackup 7.1 Administrator's Guide). I then tried adding the devices through the Admin Console (from the master) wizard, and got the error that it couldn't start the "media manager device daemon", after I've verified that it's able to see the robot and tape drives. The client is a Windows Server 2003R2 running NBU 7.1 and the Master is a Solaris 10 running NBU 7.1.0.2.

Following the troubleshooting guides and this thread, I found that I get the following in the Event Viewer after trying to start the Device Manager manually:

"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."

I've tried to open up a support with Symantec, but when we switched to capacity-based licensing, they mucked something up and now my email is no longer attached to my customer number, and, therefore, licensing. I have an open case with licensing support to get it fixed, but in the meantime, I really need to get this fixed.

Someone (Marianne, mph999?), please help!

As you can see below, Shared Storage Option is enabled, as well as Remote Client Support. (Note that I've obscured the license key.)

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>

7.1.x and Earlier

Backup and Recovery

NetBackup

SAN Shared Storage Option

Marianne
13 years ago
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.

MEDIA 7.1 mfp01-1 wayback

MEDIA 7.1 mfp01-2 wayback.hs.azdhs.gov

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)

Try 'nbemmcmd -deletehost .....'
Hopefully this will work without issues. If there are EMM device or media or image entries, command will fail.

Next, get all emmserver entries consistent with:

nbemmcmd -setemmserver

After all server names have been cleaned up, try to activate mfp01-2 for disk and tape:

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

Marianne
Level 6
13 years ago
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
AlanTLR
Level 5
13 years ago
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.

/usr/openv/netbackup/bin/admincmd # nbemmcmd -listhosts -verbose

NBEMMCMD, Version:7.1.0.2

The following hosts were found:

mfp01-2.hs.azdhs.gov

ClusterName = ""

MachineName = "mfp01-2.hs.azdhs.gov"

FQName = "mfp01-2.hs.azdhs.gov"

LocalDriveSeed = ""

MachineDescription = ""

MachineFlags = 0xb7

MachineNbuType = media (1)

MachineState = not reachable by master (4)

MasterServerName = "wayback"

NetBackupVersion = 7.1.0.0 (710000)

OperatingSystem = windows (11)

ScanAbility = 5

mfp01-2

ClusterName = ""

MachineName = "mfp01-2"

FQName = "mfp01-2"

LocalDriveSeed = ""

MachineDescription = ""

MachineFlags = 0

MachineNbuType = media (1)

MachineState = active for disk jobs (12)

MasterServerName = "wayback"

NetBackupVersion = 7.1.0.0 (710000)

OperatingSystem = windows (11)

ScanAbility = 5

hsprod14

ClusterName = ""

MachineName = "prod14"

FQName = "prod14"

LocalDriveSeed = ""

MachineDescription = ""

MachineFlags = 0xf5

MachineNbuType = media (1)

MachineState = active for tape and disk jobs (14)

MasterServerName = "wayback"

NetBackupVersion = 7.1.0.0 (710000)

OperatingSystem = solaris (2)

ScanAbility = 5

mdd01

ClusterName = ""

MachineName = "mdd01"

FQName = "mdd01"

LocalDriveSeed = ""

MachineDescription = ""

MachineFlags = 0x15

MachineNbuType = media (1)

MachineState = active for tape and disk jobs (14)

MasterServerName = "wayback"

NetBackupVersion = 7.1.0.2 (710200)

OperatingSystem = windows (11)

ScanAbility = 5

mexmb01

ClusterName = ""

MachineName = "mexmb01"

FQName = "mexmb01"

LocalDriveSeed = ""

MachineDescription = ""

MachineFlags = 0xa1

MachineNbuType = media (1)

MachineState = not active for tape or disk jobs (8)

MasterServerName = "wayback"

NetBackupVersion = 7.1.0.0 (710000)

OperatingSystem = windows (11)

ScanAbility = 5

mfp01-1

ClusterName = ""

MachineName = "mfp01-1"

FQName = "mfp01-1"

LocalDriveSeed = ""

MachineDescription = ""

MachineFlags = 0xb1

MachineNbuType = media (1)

MachineState = active for tape and disk jobs (14)

MasterServerName = "wayback"

NetBackupVersion = 7.1.0.0 (710000)

OperatingSystem = windows (11)

ScanAbility = 5

fearless

ClusterName = ""

MachineName = "fearless"

FQName = "fearless.hs.state.az.us"

LocalDriveSeed = ""

MachineDescription = ""

MachineFlags = 0xf5

MachineNbuType = media (1)

MachineState = active for tape and disk jobs (14)

MasterServerName = "wayback"

NetBackupVersion = 6.5.5.0 (655000)

OperatingSystem = solaris (2)

ScanAbility = 5

wayback

ClusterName = ""

MachineName = "wayback"

FQName = "wayback.hs.state.az.us"

GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"

LocalDriveSeed = ""

MachineDescription = ""

MachineFlags = 0xf7

MachineNbuType = master (3)

MachineState = active for tape and disk jobs (14)

NetBackupVersion = 7.1.0.2 (710200)

OperatingSystem = solaris (2)

ScanAbility = 5

mdd01

MachineName = "mdd01"

FQName = "mdd01"

MachineDescription = "PureDisk"

MachineFlags = 0x2

MachineNbuType = ndmp (2) (storage_server)

vsf03

MachineName = "vsf03"

FQName = "vsf03"

MachineDescription = ""

MachineNbuType = client (8)

hsdev2p

MachineName = "hsdev2p"

FQName = "hsdev2p.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = client (8)

vsf01

MachineName = "vsf01"

FQName = "vsf01"

MachineDescription = ""

MachineNbuType = client (8)

esx08.hs.azdhs.gov

MachineName = "esx08.hs.azdhs.gov"

FQName = "esx08.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

esx07.hs.azdhs.gov

MachineName = "esx07.hs.azdhs.gov"

FQName = "esx07.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

esx06.hs.azdhs.gov

MachineName = "esx06.hs.azdhs.gov"

FQName = "esx06.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

esx05.hs.azdhs.gov

MachineName = "esx05.hs.azdhs.gov"

FQName = "esx05.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

esc05.hs.azdhs.gov

MachineName = "esc05.hs.azdhs.gov"

FQName = "esc05.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

mvc02.hs.azdhs.gov

MachineName = "mvc02.hs.azdhs.gov"

FQName = "mvc02.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

mvc01.hs.azdhs.gov

MachineName = "mvc01.hs.azdhs.gov"

FQName = "mvc01.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

esx04.hs.azdhs.gov

MachineName = "esx04.hs.azdhs.gov"

FQName = "esx04.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

esx03.hs.azdhs.gov

MachineName = "esx03.hs.azdhs.gov"

FQName = "esx03.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

esx02.hs.azdhs.gov

MachineName = "esx02.hs.azdhs.gov"

FQName = "esx02.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

esx01.hs.azdhs.gov

MachineName = "esx01.hs.azdhs.gov"

FQName = "esx01.hs.azdhs.gov"

MachineDescription = ""

MachineNbuType = virtual_machine (10)

bullwinklep

MachineName = "bullwinklep"

FQName = "bullwinklep"

MachineDescription = ""

MachineNbuType = app_cluster (7)

NetBackupVersion = 0.0.0.0 (0)

Active Node Name = ""

waybackp

MachineName = "waybackp"

FQName = "waybackp"

MachineDescription = ""

MachineNbuType = app_cluster (7)

NetBackupVersion = 7.1.0.2 (710200)

Active Node Name = "wayback"

mfp01

MachineName = "mfp01"

FQName = "mfp01"

MachineDescription = ""

MachineNbuType = app_cluster (7)

NetBackupVersion = 7.1.0.0 (710000)

Active Node Name = "mfp01-1"

wayback

MachineName = "wayback"

FQName = "wayback.hs.state.az.us"

MachineDescription = ""

MachineNbuType = server (6)

Command completed successfully.

root@wayback 13:42:36

/usr/openv/netbackup/bin/admincmd # nbemmcmd -getemmserver

NBEMMCMD, Version:7.1.0.2

These hosts were found in this domain: fearless, mdd01, mexmb01, mfp01-1, mfp01-2, mfp01-2.hs.azdhs.gov, hsprod14, wayback

Checking with the host "fearless"...

Checking with the host "mdd01"...

Checking with the host "mexmb01"...

Checking with the host "mfp01-1"...

Checking with the host "mfp01-2"...

Checking with the host "mfp01-2.hs.azdhs.gov"...

Checking with the host "hsprod14"...

Checking with the host "wayback"...

Server Type Host Version Host Name EMM Server

MEDIA 6.5 fearless wayback

MEDIA 7.1 mdd01 wayback

MEDIA 7.1 mexmb01 wayback

MEDIA 7.1 mfp01-1 wayback

MEDIA 7.1 mfp01-2 wayback.hs.azdhs.gov

<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)

MEDIA 7.1 hsprod14 wayback

MASTER 7.1 wayback wayback

One or more hosts had mismatched EMM Servers.

There were problems getting information on one or more hosts.

The consistency check either failed or was incomplete.

Command did not complete successfully.
Marianne
Level 6
13 years ago
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.

MEDIA 7.1 mfp01-1 wayback

MEDIA 7.1 mfp01-2 wayback.hs.azdhs.gov

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)

Try 'nbemmcmd -deletehost .....'
Hopefully this will work without issues. If there are EMM device or media or image entries, command will fail.

Next, get all emmserver entries consistent with:

nbemmcmd -setemmserver

After all server names have been cleaned up, try to activate mfp01-2 for disk and tape:

nbemmcmd -updatehost -machinename <media-server> -machinestateop set_tape_active -machinetype media -masterserver <master>
AlanTLR
Level 5
13 years ago
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.
Marianne
Level 6
13 years ago
I see that quite often in bigger environments with more than one admin.

Normally creates major confusion within NBU...
watsons
Level 6
13 years ago
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)
AlanTLR
Level 5
13 years ago
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.

root@wayback 22:01:14

/usr/openv/netbackup/bin/admincmd # !521

nbemmcmd -deletehost -machinename mfp01-2.hs.azdhs.gov -machinetype media

NBEMMCMD, Version:7.1.0.2

Command completed successfully.

root@wayback 22:01:26

/usr/openv/netbackup/bin/admincmd # !530

nbemmcmd -getemmserver

NBEMMCMD, Version:7.1.0.2

These hosts were found in this domain: fearless, mdd01, mexmb01, mfp01-1, mfp01-2, hsprod14, wayback

Checking with the host "fearless"...

Checking with the host "mdd01"...

Checking with the host "mexmb01"...

Checking with the host "mfp01-1"...

Checking with the host "mfp01-2"...

Checking with the host "hsprod14"...

Checking with the host "wayback"...

Server Type Host Version Host Name EMM Server

MEDIA 6.5 fearless wayback

MEDIA 7.1 mdd01 wayback

MEDIA 7.1 mexmb01 wayback

MEDIA 7.1 mfp01-1 wayback

MEDIA 7.1 mfp01-2 wayback

MEDIA 7.1 hsprod14 wayback

MASTER 7.1 wayback wayback

Command completed successfully.

root@wayback 22:01:45

/usr/openv/netbackup/bin/admincmd # !529

nbemmcmd -updatehost -machinename mfp01-2 -machinestateop set_tape_active -machinetype media -masterserver wayback

NBEMMCMD, Version:7.1.0.2

Command completed successfully.

/usr/openv/netbackup/bin/admincmd # !530

nbemmcmd -getemmserver

NBEMMCMD, Version:7.1.0.2

These hosts were found in this domain: fearless, mdd01, mexmb01, mfp01-1, mfp01-2, hsprod14, wayback

Checking with the host "fearless"...

Checking with the host "mdd01"...

Checking with the host "mexmb01"...

Checking with the host "mfp01-1"...

Checking with the host "mfp01-2"...

Checking with the host "hsprod14"...

Checking with the host "wayback"...

Server Type Host Version Host Name EMM Server

MEDIA 6.5 fearless wayback

MEDIA 7.1 mdd01 wayback

MEDIA 7.1 mexmb01 wayback

MEDIA 7.1 mfp01-1 wayback

MEDIA 7.1 mfp01-2 wayback

MEDIA 7.1 hsprod14 wayback

MASTER 7.1 wayback wayback

Command completed successfully.

root@wayback 22:02:56

/usr/openv/netbackup/bin/admincmd # !530

nbemmcmd -getemmserver

NBEMMCMD, Version:7.1.0.2

These hosts were found in this domain: fearless, mdd01, mexmb01, mfp01-1, mfp01-2, mfp01-2.hs.azdhs.gov, hsprod14, wayback

Checking with the host "fearless"...

Checking with the host "mdd01"...

Checking with the host "mexmb01"...

Checking with the host "mfp01-1"...

Checking with the host "mfp01-2"...

Checking with the host "mfp01-2.hs.azdhs.gov"...

Checking with the host "hsprod14"...

Checking with the host "wayback"...

Server Type Host Version Host Name EMM Server

MEDIA 6.5 fearless wayback

MEDIA 7.1 mdd01 wayback

MEDIA 7.1 mexmb01 wayback

MEDIA 7.1 mfp01-1 wayback

MEDIA 7.1 mfp01-2 wayback

<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)

MEDIA 7.1 hsprod14 wayback

MASTER 7.1 wayback wayback

One or more hosts had mismatched EMM Servers.

There were problems getting information on one or more hosts.

The consistency check either failed or was incomplete.

Command did not complete successfully.

root@wayback 22:04:44

/usr/openv/netbackup/bin/admincmd #
Mike_Gavrilov
Level 6
13 years ago
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

Forum Discussion

NetBackup 7.1 Media (Device) Manager Won't stay started

Related Content

How to view managed devices within NetBackup WebUI and Administration Console

Netbackup volume manager\request daemon\device manager services are not coming up

Netbackup web management console Tomcat

Re: ayuda por favor; Error: V-79-57344-33043 Backup Exec

Netbackup Web Management Console

Recent Discussions

Same Media server, new storage

NBU security questions

NBInstallAnswer file CLIENT silent install

AIR replication – restart of the replication job, deduplication

Best ways to revocer a virtual domain controller