Forum Discussion

j083418's avatar
j083418
Level 5
14 years ago
Solved

NetBackup Enterprise Media Manager Service.....

NetBackup Enterprise Media Manager  service had an issue this morning on the Netbackup 6.5.4 Cluster. It was running but when starting up the GUI there were lots of error messages stating that it was unavailable. I can't see anything in the MS Windows event logs that points to any issues. Is there somewhere else I could look (a netbackup log maybe) to see if any issues occurred over night?

7.1.x and Earlier
Agents
Backing Up
Backup and Recovery
Basics
Best Practice
Configuring
Documentation
Error messages
Features
  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    14 years ago

    vxlogview -a -p NB -o 111

     

    Stop and start emm, then run that command and check the last few entries.

     

    Also, stop and start the database manager service, then run nbdb_ping to see if the db is available.

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    14 years ago

    vxlogview -a -p NB -o 111

     

    Stop and start emm, then run that command and check the last few entries.

     

    Also, stop and start the database manager service, then run nbdb_ping to see if the db is available.

  • j083418's avatar
    j083418
    Level 5
    14 years ago

    17/05/2011 04:17:55.861 [Warning] V-111-1058 [DA_Thread_Pool::IsDiskFull] File system for Q:\\NetBackupDB\data has 0.219637 percent available and requires 1.000000 percent.
    17/05/2011 04:17:55.861 [Critical] V-111-1056 [DA_Thread_Pool::CheckNBDBDiskFull] Not enough disk space on file system.  Shutting down NetBackup database (NBDB).
    17/05/2011 04:18:01.119 [Error] V-111-1049 EMMServer generic error = Failed to get database connection, retval = < 4005006 >

     

    Looks like it ran out of space of the Q:\ drive

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    14 years ago

    Great, you found the issue. Have a look at Q:\\NetBackupDB\data\NBDB.log, it sometimes grows way to big if a catalog backup wasn't run. You can truncate it with nbdb_backup.

     

    Or you might just be running out of space due to other logs, or images growth.