Scribd
Upload
12K views2 pages

Code 78

This document provides solutions to errors "Could not list cache: EMM server failed to process the request (78)" or "ERROR UNDEFINED: EMM server failed to process the request" that occur after upgrading to Veritas NetBackup 6.x. The errors are caused by the nbpushdata command not being run after upgrade, which moves data from the 5.x database to the new 6.x EMM database. Running the nbpushdata command with the -add_flag option can resolve the issue by setting a flag to indicate the data migration has occurred.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
12K views2 pages

Code 78

This document provides solutions to errors "Could not list cache: EMM server failed to process the request (78)" or "ERROR UNDEFINED: EMM server failed to process the request" that occur after upgrading to Veritas NetBackup 6.x. The errors are caused by the nbpushdata command not being run after upgrade, which moves data from the 5.x database to the new 6.x EMM database. Running the nbpushdata command with the -add_flag option can resolve the issue by setting a flag to indicate the data migration has occurred.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Problem

NetBackup status code 78: afs/dfs command failed

Solution
Message: afs/dfs command failed Explanation: Indicates an AFS vos command failure. Recommended action: 1 Check the NetBackup Problems Report for additional information on why the command failed. 2 The bpbkar debug log shows the command that was run. Create a debug log directory for bpbkar. Retry the operation and retry the resulting debug log. 3 Try running the vos command manually to duplicate the problem.

Problem
STATUS CODE 78: After upgrading to Veritas NetBackup (tm) 6.x , the error message "Could not list cache: EMM server failed to process the request (78)" or "ERROR UNDEFINED: EMM server failed to process the request" is returned when scanning hosts for drives in the device configuration wizard.

Error
EMM server failed to process the request (78)

Solution
Overview After upgrading to NetBackup 6.x, the error message "Could not list cache: EMM server failed to process the request (78)" or "ERROR UNDEFINED: EMM server failed to process the request" is returned when scanning hosts for drives in the device configuration wizard. Troubleshooting This is seen in environments where the nbpushdata command was never run upon the initial upgrade to NetBackup 6.x. This is a crucial step in upgrading NetBackup.

After installing the NetBackup server software, as a part of an upgrade installation, nbpushdata must be run as directed in the installation guide. This command moves data from 5.x database files (a subset of the NetBackup catalog) into the newly created 6.x Enterprise Media Manager (EMM) database. This final step in the upgrade process is critical to ensure that the NetBackup environment is functional. More information on nbpushdata is available in the NetBackup Installation Guide, referenced below, in the Related Documents section.

Emm Server Log Files (Usually the Master Server) vxlogs for nbemm (originator id 111)
4/6/2006 16:06:09.640 [Diagnostic] NB 51216 nbemm 111 PID:980 TID:472 [No context] 1 V-111-1049 [MachineConfigImpl::helperQueryNbpushdataConfig] EMMServer generic error = nbpushdata must be run to complete the upgrade 4/6/2006 16:06:09.640 [Diagnostic] NB 51216 nbemm 111 PID:980 TID:472 [No context] 1 V-111-1049 [MediaImpl::createMediaEx] EMMServer generic error = cannot add media until nbpushdata has been run

Resolution If nbpushdata was not run upon initial install of 6.x and the effects of not doing so are known, the following command can be run to set a flag indicating that nbpushdata has been run, allowing use of the existing NetBackup EMM database to continue: UNIX/Linux: From the <install_path>/openv/netbackup/bin/ directory, type the following exactly as it appears: nbpushdata -add_flag NBPUSHDATA_G_GLOBDB_HOST dummyhostname:dummyhostname Windows: From the <install_path>\NetBackup\bin directory, type the following exactly as it appears: nbpushdata -add_flag NBPUSHDATA_G_GLOBDB_HOST dummyhostname:dummyhostname

You might also like