Forum Discussion

Varma_Chiluvuri's avatar
10 years ago

Backups failing with 2027 error code

Some of the backups in our environment are failing with 2027 error code.

Netbackup media server is available

Currently backups are runing using the drives in this media server

Please find the log for the backup failure

12/03/2014 09:05:06 - Info nbjm (pid=23658736) starting backup job (jobid=3044394) for client sapbwsv-nb, policy Ora_RMAN_BWS, schedule Arch_BWS
12/03/2014 09:05:06 - Info nbjm (pid=23658736) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=3044394, request id:{62938BE6-7AF5-11E4-A27D-665E5F7F0000})
12/03/2014 09:05:06 - requesting resource media-server-nb-hcart3-robot-tld-3
12/03/2014 09:05:06 - requesting resource sun107-nb.NBU_CLIENT.MAXJOBS.sapbwsv-nb
12/03/2014 09:05:06 - requesting resource sun107-nb.NBU_POLICY.MAXJOBS.Ora_RMAN_BWS
12/03/2014 09:05:06 - Waiting for scan drive stop STK.T10000A.013, Media server: media-server-nb
12/03/2014 09:07:06 - Info nbjm (pid=23658736) Waiting in NetBackup scheduler work queue on server sun107-nb
12/03/2014 09:07:13 - Error nbjm (pid=23658736) NBU status: 2027, EMM status: Media server is not active
Media server is not active  (2027)

13 Replies

  • Show us output of nbemmcmd -listhosts at the time when error is seen.
    It is possible that there is a network glitch at the time when the error occurs.

    See this TN regarding EMM heartbeat timeout: http://www.symantec.com/business/support/index?page=content&id=TECH70827 
    (There seems to be a problem with Symantec Support site at the moment.)

    My questions of 14 Jan were not answered:

    Multiple interfaces on the media server?

    vmoprcmd output shows drives in use on media-server.

    Job details shows a problem with media-server-nb.

    Curious to see output of 'nbemmcmd -listhosts -verbose'.
    This will show us how 'media-server' is configured in EMM.

     

     

  • output of nbemmcmd -listhosts at present: But how to get the output for that perticular time when the issue occured?

    XYZ-nb
            ClusterName = ""
            MachineName = "XYZ-nb"
            FQName = "XYZ-nb"
            LocalDriveSeed = ""
            MachineDescription = ""
            MachineFlags = 0xf7
            MachineNbuType = media (1)
            MachineState = active for tape and disk jobs (14)
            MasterServerName = "ABC-nb"
            NetBackupVersion = 7.5.0.4 (750400)
            OperatingSystem = solaris (2)
            ScanAbility = 5

  • My question again: 

    Multiple interfaces on the media server?

    vmoprcmd output shows drives in use on media-server.

    Job details shows a problem with media-server-nb.

     

    How are media servers actually configured in NBU? With which name?

     

    But how to get the output for that perticular time when the issue occured?

    Pay someone to monitor backups... 
    Or do it yourself.
    I have often in my level 1 and 2 Support days sat at a customer's site overnight to see what is happening at OS and network level when things go wrong in NBU.

    Please read though the TN that I have posted to see which logs to check for EMM heartbeat errors.