Veritas Status Codes and Messages

9/14/2016
VeritasStatusCodesandMessages
ThisdocumentlistsallthestatuscodesandmessagesprovidedbyNetBackup.
10|20|30|40|50|60|70|80|90|100|110|120|130|140|150|160|170|180|190|200
210|220|230|240|250|260|
123456789
StatusCode:0Top
Message:"therequestedoperationwassuccessfullycompleted"
Explanation:Therewerenoproblemsdetectedwiththerequestedoperation.
RecommendedAction:
None,unlessthiswasadatabasebackupperformedthroughadatabaseextensionproduct(forexample,NetBackupforOracleorNetBackup
forSQLServer).Inthoseinstances,code0meansthebackupscriptthatstartedthebackupranwithouterror.However,youmustcheck
otherstatusasexplainedintherelatedNetBackupmanualtoseeifthedatabasewassuccessfullybackedup.
StatusCode:1Top
Message:"therequestedoperationwaspartiallysuccessful"
Explanation:Aproblemthatmayrequirecorrectiveactionwasdetectedduringtherequestedoperation.
RecommendedAction:
ChecktheAllLogEntriesreportandalsotheprogresslog(ifthereisone).
SomeoftheproblemsthatcanshowupunderStatusCode1are:
Afileordirectorypaththatismorethan1023characterslong.
Couldnotopenafile.
OnaUNIXsystem,NetBackupcouldnotgetthelinknameofafile.
OnaUNIXsystem,NetBackupcouldnotprocessasparsefile.
Readerrorencounteredinafile.
Fileisofanunknowntype.
OnaUNIXsystem,thelstatsystemcallfailsonafilethatiseligibletobebackedup.Thismaybeapermission
problem.
OnUNIX,afilecouldnotbelockedthathasmandatorylockingenabled.
StatusCode:2Top
Message:"noneoftherequestedfileswerebackedup"
Explanation:Abackuporarchivecouldnotbackupanyofthefilesinthefilelist.
RecommendedAction:Verifythatthefilesexistandyouhavereadaccesstothem.
OnUNIXclients,checktoseeifthefilesordirectorieswouldbeexcludedbecauseofanentryin
/usr/openv/netbackup/exclude_list.
OnPCclients,checktheexcludelistpertheinstructionsintheuser'sguidefortheclient.
http://tcc2.technion.ac.il/backup/codes/#Status_Code10
1/43
9/14/2016
OnWindowsNTclients,verifythattheaccountusedtostarttheNetBackupClientservicehasreadaccesstothe
files.
IfyouarebackingupanetworkdriveoraUNC(universalnamingconvention)path,usetheServicesapplicationinthe
WindowsNTControlPaneltoverifythattheNetBackupClientservicedoesnotstartundertheSYSTEMaccount.The
SYSTEMaccountcannotaccessnetworkdrives.
TobackupnetworkdrivesorUNCpaths,changetheNetBackupClientservicestartuptologinasauserthathas
permissiontoaccessnetworkdrives.
StatusCode:3Top
Message:validarchiveimageproduced,butnofilesdeletedduetononfatalproblems
Explanation:Thebackupportionofthearchivecommandreportedproblemssothefileswerenotdeleted.
RecommendedAction:Examinetheprogresslogofthearchiveontheclienttodetermineifyouneedtoretrythearchiveafter
correctingtheproblem.Iftheproblemisnotseriousandthefileswerebackedup,youcanmanuallydeletethefiles.Toverify
whichfileswerebackedup,usetheNetBackupclientuserinterfaceinrestoremodeandbrowsethefilesinthearchive.
Apossiblecauseforfilesnotbeingdeletedisthatyoudonothavethenecessarypermissions.NetBackupcannotdeletefiles
unlessyouareeithertheuserthatownsthefiles,asuperuseronUNIX,oranadministratoronWindowsNT.
StatusCode:4Top
Message:archivefileremovalfailed
Explanation:Thebackupportionofthearchivecompletedwassuccessfulbutthedeletefailed.
RecommendedAction:Verifythatyouhavepermissiontodeletethefilesandthatthereadonlyflagisnotsetforthefiles.On
UNIXclients,verifythatyouhavewritepermissiontothedirectoriesthatcontainthefiles.Sincethebackupwassuccessful,
youcandeletethefilesthatwerebackedup(orhavethesystemadministratordeletethefilesifyoudonothavethenecessary
permissions).
StatusCode:5Top
Message:therestorefailedtorecovertherequestedfiles
Explanation:Therewereerrorsthatcausedtherestoretofail.
RecommendedAction:
1.Examinetheprogresslogontheclientformessagesonwhytherestorefailed.Also,checktheAllLogEntries
reportontheserver.
2.OnWindowsNTandUNIX,checkownershipandpermissionondirectorieswherefileswillberestored.
3.Correctproblemsthatyoufindandretrytherestore.
StatusCode:6Top
Message:thebackupfailedtobackuptherequestedfiles
Explanation:Errorscausedtheuserbackuptofail.
RecommendedAction:
1.Verifythatyouhavereadaccesstothefiles.Checktheprogresslogontheclientformessagesonwhythe
backupfailed.Correctproblemsandretrythebackup.
2.OnWindowsNTclients,verifythattheaccountusedtostarttheNetBackupClientservicehasreadaccesstothe
files.
3.OnMacintoshclients,thiscodecanbeduetomultiplebackupsbeingattemptedsimultaneouslyonthesame
client.Somepossiblesolutionsare:
oAdjustthebackupschedules.
oIftheclientisonlyinoneclass,setthegeneralclassattribute,MaximumJobsperClass,to1.
oSettheNetBackupglobalattribute,MaximumJobsPerClient,to1(notethatthislimitsallclientsinall
classes).
4.ForaUNIXdatabaseextensionclient(forexample,NetBackupforOracle),thiscanmeanaproblemwiththe
scriptthatiscontrollingthebackup.
Checktheprogressreportontheclientforamessagesuchas"Scriptexitedwithstatuscode=number"(thenumber
willvary).Theprogresslogalsousuallynamesthescript.
Checkthescriptforproblems.Also,checkthetroubleshootinglogscreatedbythedatabaseextension.Seethe
NetBackupguidethatcamewiththedatabaseextensionforinformationonthescriptsandtroubleshootinglogs.
StatusCode:7Top
Message:thearchivefailedtobackuptherequestedfiles
Explanation:Errorscausedtheuserarchivetofail.
RecommendedAction:
Verifythatyouhavereadaccesstothefiles.Checktheprogresslogontheclientformessagesonwhythearchivefailed.
Correctproblemsandretrythearchive.
OnWindowsNTclients,verifythattheaccountusedtostarttheNetBackupserviceshasreadaccesstothefiles.
2/43
9/14/2016
StatusCode:8Top
Message:unabletodeterminethestatusofrbak
Explanation:OnDomainOSclients,rbakisusedtodorestores.Ifrbakdoesnotexitwithastatusmessage,NetBackupcannot
determinewhethertherestoreworkedornot.
RecommendedAction:Checkforanewcorefiletoseeifrbakaborted.Checkthepsoutputtoseeifrbakishung.Ifso,killit
andtryagain.Checktheprogresslogforanyunusualmessagesfromrbak.
StatusCode:9
Message:anextensionpackageisneededbutwasnotinstalled
Explanation:ANetBackupextensionproductisrequiredinordertoperformtherequestedoperation.
RecommendedAction:Installtherequiredextensionproduct.
1112131415161819Top
StatusCode:10Top
Message:allocationfailed
Explanation:Allocationofsystemmemoryfailedbecausethereisinsufficientsystemmemoryavailable.Thiscouldbecaused
bythesystembeingoverloadedwithtoomanyprocessesandnotenoughphysicalorvirtualmemory.
RecommendedAction:Freeupmemorybyterminatingunneededprocessesthatconsumememory.Addmoreswapspaceor
physicalmemory.
StatusCode:11Top
Message:systemcallfailed
Explanation:Asystemcallfailed.Thisstatuscodeisusedforagenericsystemcallfailurethatdoesnothaveitsownstatus
code.
RecommendedAction:
1.ChecktheAllLogEntriesandProblemsreportstodeterminewhichsystemcallfailedandotherinformationabout
theerror.
2.Afrequentcauseisthattheserver'sfilesystemisfull.Forexample,ifyouseeamessagesimilartothefollowing
intheProblemsreportorbpdbmactivitylog:
06/27/9501:04:00rombrombdb_FLISTsendfailed:systemcallfailed(11)
06/27/9501:04:01rombrombmediamanagerterminatedbyparentprocess
06/27/9501:05:15rombrombbackupofclientrombexitedwithstatus11(systemcallfailed)
OnUNIXsystems,runadfcommandonthe/usr/openv/netbackup/dbdirectory.
Ifthedfcommanddoesnotrevealtheproblem,checkthebpdbmactivitylogsordoagrepforthemessagesystemcall
failed
in/usr/openv/netbackup/db/error/*
OnWindowsNTsystems,verifythereisroominthediskpartitionwhereNetBackupisinstalled.
3.Verifythatthesystemisnotrunningoutofvirtualmemory.Ifvirtualmemoryistheproblem,shutdownunused
applicationsorincreasetheamountofvirtualmemory.
ToincreasevirtualmemoryonWindowsNT,98,and95:
a.DisplaytheControlPanel.
b.DoubleclickSystem.
c.OnthePerformancetab,setVirtualMemorytoahighervalue.
4.Checkforasemaphoreproblem.Thiserrorcanbecausedbythesystemnothavingenoughsemaphores
allocated.ThisismostcommonlyseenonSolaris2serverswhenanRDBMSisalsorunning.
Thesymptomsoftheproblemvary.Insomecases,errormessagesintheNetBackuplogindicateabackupfailuredue
toanerrorinsemaphoreoperationanothersymptomistheinabilityoftheNetBackupDeviceManagerserviceMedia
Managerdevicedaemon,ltid,toacquireaneededsemaphore(thisistheNetBackupDeviceManagerserviceon
WindowsNT).
Systemrequirementsvarythus,noabsoluterecommendationscanbemade.OnecustomerrunningbothNetBackup
andORACLEontheirSolarisservermadethefollowingchangestotheir/etc/systemfileandthenrebootedthesystem
(bootr)thechangeswerefoundtobeadequate:
setsemsys:seminfo_semmni=300
setsemsys:seminfo_semmns=300
setsemsys:seminfo_semmsl=300
setsemsys:seminfo_semmnu=600
Settheseattributestoavaluegreatenoughtoprovideresourcestoallapplicationsonyoursystem.
5.Checkforasharedmemoryproblem.Thiserrorcanoccurifthesystemcannotallocateenoughsharedmemory.
Thisusuallyoccurswhenyouusemultiplexing,whichincreasesthesharedmemoryrequirements.Asymptomis
anentrysimilartothefollowinginaNetBackuplog(orreport)couldnotallocateenoughsharedmemory
Ifyouseethistypeofmessage,refertothevendordocumentationforyourplatformforinstructionsonincreasingthe
amountofsharedmemoryonyoursystem.
Becausesystemrequirementsvary,wecanmakenoabsoluterecommendations,otherthantousevaluesgreatenough
toprovideresourcestoallapplications.Although,inatleastoneinstance,thefollowingwasfoundtobeadequateona
Sunplatform:
3/43
9/14/2016
setshmsys:shminfo_shmmax=8388608
setshmsys:shminfo_shmmin=1
setshmsys:shminfo_shmmni=100
setshmsys:shminfo_shmseg=10
setsemsys:seminfo_semmnu=600
setsemsys:seminfo_semmns=300
Aftermakingthechangestothe/etc/systemfileontheSunplatformandrebootingwithbootr,theproblemwas
resolved.Notethatintheabove,shminfo_shmminmustbelessthanorequalto100forNetBackupprocessestorun.
6.Examineotheractivitylogsortheprogresslogontheclient.
7.IfabackuponaWindowsNTNetBackupclientfailswithstatuscode11andtheclientisusingOpenTransaction
Manager(OTM)foropenfilemanagement,itispossiblethattheerrorwascausedbytheOTMcachefilebeing
full.Ifthisisthecaseandbpbkaractivitylogsareturnedon,amessagesimilartothefollowingshouldappearat
theendofthebackup:
04/28/9911:27:56AM:[216]:ERROTMError:0xe0001005
04/28/9911:27:59AM:[216]:INFOTMTerminatedisabledforallprocesses
04/28/9911:27:59AM:[216]:FTLBackupoperationaborted!
Ifthiserrorisencountered,youmayneedtoincreaseeithertheinitialOTMcachesizeorthemaximumOTMcache
size,dependingontherequirementsofyourinstallationandyourusageofOTM.
StatusCode:12Top
Message:fileopenfailed
Explanation:Anopenofafilefailed.
RecommendedAction:ChecktheNetBackupProblemsreport.Trytodeterminethefileandwhytheerroroccurred.Apossible
causeisapermissionproblemwiththefile.Fordetailedtroubleshootinginformation,createanactivitylogdirectoryforthe
processthatreturnedthisstatuscode.Then,retrytheoperation,andchecktheresultingactivitylog.
StatusCode:13Top
Message:filereadfailed
Explanation:Areadofafileorsocketfailed.Possiblecausesinclude:
I/Oerrorreadingfromthefilesystem.
Readofanincompleteorcorruptfile.
Socketreadfailing.Asocketreadfailurecanbecausedbyanetworkproblemoraproblemwiththeprocessthat
iswritingtothesocket.
RecommendedAction:
1.ChecktheNetBackupProblemsreportforcluesonwhereandwhytheproblemoccurred.
2.ForaFlashBackupclient,checkthe/var/adm/messageslogforerrorslikethefollowing:
Mar2401:35:58bisonunix:WARNING:sn_alloccache:cache/dev/rdsk/c0t2d0s3fullallsnapsusingthiscacheare
nowunusable
Thisindicatesthatthecachepartitionisnotlargeenough.Ifpossible,increasethesizeofthecachepartition.Or,if
multiplebackupsareusingthesamecache,eitherreducethenumberofconcurrentbackupsbyreschedulingsomeof
themorrescheduletheentirebackuptoatimewhenthefilesystemislessactive.
3.Fordetailedtroubleshootinginformation,createanactivitylogdirectoryfortheprocessthatreturnedthisstatus
code,retrytheoperation,andchecktheresultingactivitylog.
StatusCode:14Top
Message:filewritefailed
Explanation:Awritetoafileorsocketfailed.
RecommendedAction:
ChecktheNetBackupProblemsreportforcluesonwhereandwhytheproblemoccurred.Fordetailedtroubleshooting
information,createanactivitylogdirectoryfortheprocessthatreturnedthisstatuscode,retrytheoperation,andcheckthe
resultingactivitylog.
Thefollowingaresomepossiblecauses:
I/Oerrorwritingtothefilesystem
Writetoasocketfailed.Thiscanbecausedbyanetworkproblemoraproblemwiththeprocessreadingfromthe
socket.
Writingtoafulldiskpartition.
StatusCode:15Top
Message:fileclosefailed
Explanation:Acloseofafileorsocketfailed.
RecommendedAction:ChecktheNetBackupProblemsreportforcluesonwhereandwhytheproblemoccurred.Fordetailed
troubleshootinginformation,createanactivitylogdirectoryfortheprocessthatreturnedthisstatuscode,retrytheoperation,
andchecktheresultingactivitylog.
4/43
9/14/2016
StatusCode:16Top
Message:unimplementedfeature
Explanation:Thespecifiedoperationisunimplemented.ThiserrorshouldnotoccurthroughnormaluseofNetBackup.
RecommendedAction:Saveallerrorinformationandcallcustomersupport.
StatusCode:18Top
Message:pipeclosefailed
Explanation:Closeofapipefailed,whenoneprocesstriestostartachildprocess.
RecommendedAction:ChecktheNetBackupProblemsreportforcluesonwhythefailureoccurred.Fordetailed
troubleshootinginformation,createanactivitylogdirectoryfortheprocessthatreturnedthisstatuscode,retrytheoperation,
andchecktheresultingactivitylog.
StatusCode:19Top
Message:getservbynamefailed
Explanation:Acalltogetservbyname()failed.Thegetservbyname()functionusesthenameoftheservicetofindaservice
entryintheservicesfile(orNISservicesmaponUNIXifitisconfigured).
RecommendedAction:
1.ChecktheNetBackupProblemsreportforcluesonwhythefailureoccurred.
2.OnaUNIXsystem,checkthat/etc/servicesandNISservicesmap(ifapplicable)haveentriesfortheNetBackup
services:bpcd,bpdbm,andbprd.
3.OnaWindowsNTsystem,verifythatthe%SystemRoot%\system32\drivers\etc\servicesfileshowsthecorrect
entriesfortheNetBackupinternetprocesses:bpcd,bpdbm,andbprd.
EnsurethattheNetBackupClientServicePortNumberandNetBackupRequestServicePortNumberontheNetwork
tabintheNetBackupConfigurationdialogboxmatchthesettingsintheservicesfile.Todisplaythisdialogbox,startthe
Backup,Archive,andRestoreinterfaceandclickConfigureontheActionsmenu(alsosee"UsingtheConfigure
NetBackupWindow"onpage57).ThevaluesontheNetworktabarewrittentotheservicesfilewhentheNetBackup
Clientservicestarts.Also,see"VerifyingHostNamesandServicesEntries"onpage31.
4.Checkthelevelofnetworkactivity.Anoverloadednetworkcancausethiserror.
5.Iftheaboveactionsdonotrevealtheproblem,createanactivitylogdirectoryfortheprocessthatreturnedthis
statuscode,retrytheoperation,andchecktheresultingactivitylog.
212223242526272829Top
StatusCode:20Top
Message:invalidcommandparameter
Explanation:Oneormorecommandparameterswerenotvalid.Thiserrorcanoccurwhenamasteranditsslaveserversora
masterserverandaclienthavedifferentlevelsofNetBackupinstalled.Forexample,ifaNetBackupmasterserverhas
NetBackup3.2andtheslaveserverhasNetBackup3.0.Thiserrorcanalsooccurifthewrongparametersareusedwhen
executingacommandline.
RecommendedAction:
1.ChecktheNetBackupProblemsreportforclues.
2.Iftheerroroccurswhenexecutingacommandonthecommandline,verifythattheparametersarevalid.
3.ComparetheNetBackupversionlevelontheservertothatontheclients:
oOnUNIXNetBackupserversandclients,checkthe/usr/openv/netbackup/bin/versionfile.
oOnWindowsNTNetBackupservers,checktheinstall_path\netbackup\version.txtfileortheAbout
NetBackupcommandontheHelpmenu.
oOnMicrosoftWindowsclients,checktheAboutNetBackupcommandontheHelpmenu.
oOnNetWaretargetclients,checktheVersionentryinthebp.inifile.Iftheclientsoftwareisearlierthan3.0,
verifythattheclientisinaStandardtypeclass.
oOnMacintoshclients,checktheversionfileinthebinfolderintheNetBackupfolderinthePreferences
folder.
4.Iftheaboveactionsdonotrevealtheproblem,createanactivitylogdirectoryfortheprocessthatreturnedthis
statuscode,retrytheoperation,andchecktheresultingactivitylog.
StatusCode:21Top
Message:socketopenfailed
Explanation:Asocketopenfailed.
RecommendedAction:
1.ChecktheNetBackupProblemsreportforcluesonwhereandwhythefailureoccurred.Ifyoucannotdetermine
thecausefromtheProblemsreport,createactivitylogdirectoriesfortheprocessesthatreturnedthisstatuscode.
Then,retrytheoperationandchecktheresultingactivitylogs.
2.OnSunSolaris,verifythatalloperatingsystempatchesareinstalled(seetheOperatingNotessectionofthe
NetBackupReleaseNotesUNIX).
3.OnWindowsNT,verifythattherecommendedservicepacksareinstalled.
5/43
9/14/2016
StatusCode:22Top
Message:socketclosefailed
Explanation:Asocketcouldnotbeclosed.
RecommendedAction:
thecausefromtheProblemsreport,createactivitylogdirectoriesfortheprocessesthatcouldhavereturnedthis
statuscode.Then,retrytheoperationandchecktheresultingactivitylogs.
StatusCode:23Top
Message:socketreadfailed
Explanation:Areadoperationfromasocketfailed.
RecommendedAction:
statuscode.Then,retrytheoperationandchecktheresultingactivitylogs.
2.Corruptbinariesareonepossiblecauseforthiserror.Forexample,inoneinstance,thefollowingwasseeninthe
bpschedactivitylog.
get_num_avail_drives:readlinefailed:socketreadfailed(23)
get_stunits:get_num_avail_drivesfailedwithstat23
Loadingafreshbptmfromtheinstallmediaresolvedtheproblem.
StatusCode:24Top
Message:socketwritefailed
Explanation:Awriteoperationtoasocketfailed.
RecommendedAction:
statuscode.Thenretrytheoperationandchecktheresultingactivitylogs.
2.Apossiblecausecouldbeahighnetworkload.Forexample,thishasbeenseeninconjunctionwithCannotwrite
toSTDOUTwhenaWindowsNTsystemthatismonitoringnetworkloadhasdetectedahighloadandsentan
ICMPpackettoothersystemsthatsaystheroutebeingusedbythosesystemswasdisconnected.Thelog
messagesweresimilartothefollowing:
01/31/9614:05:23rublecrabtree.null.comfromclientcrabtree.null.com:ERRCannotwritetoSTDOUT.Errno=242:
Noroutetohost
01/31/9614:05:48rublecrabtree.null.comsuccessfullywrotebackupidcrabtree.null.com_0823125016,copy1,
fragment1,440864Kbytesat628.538Kbytes/sec
01/31/9614:05:51netbackupcrabtree.null.comCLIENTcrabtree.null.comCLASSRemote3SysFullWSCHEDSirius
EXITSTATUS24(socketwritefailed)
StatusCode:25Top
Message:cannotconnectonsocket
Explanation:Aprocesstimedoutwhileconnectingtoanotherprocessforaparticularoperation.Thisproblemcanoccurwhen
aprocesstriestoconnecttotheNetBackuprequestdaemon(bprd)ordatabasemanagerdaemon(bpdbm)andthedaemonis
notrunning(OnWindowsNT,thesedaemonsaretheNetBackupRequestManagerandNetBackupDatabaseManager
services).Itcanalsooccurifthenetworkorserverisheavilyloadedandhasslowresponsetime.
RecommendedAction:
1.OnaUNIXNetBackupmasterserver,verifythatthebprdandbpdbmprocessesarerunning.Iftheseprocesses
arenotrunning,startthem.OnaWindowsNTmasterserver,verifythattheNetBackupRequestManagerand
NetBackupDatabaseManagerservicesarerunning.Iftheseservicesarenotrunning,startthem.
Iftheaboveprocessesarerunning,examinetheAllLogEntriesreportforthetimeofthefailuretodeterminewherethe
failureoccurred.
oIfyoucannotviewthereport,oryougetacannotconnectonsocketerrorwhentryingtoviewit,verify
againthattheNetBackupDatabaseManagerdaemon(orservice)isrunning.Then,createanactivitylog
directoryforbpdbm,retrytheoperation,andchecktheresultingactivitylog.
oIfyoucanviewthereportandhavenotfoundanentryrelatedtothisproblem,createactivitylogdirectories
fortherelatedprocessesthatwererunningwhentheerrorfirstappeared(thisprocesswillfrequentlybe
bpbrm).Then,retrytheoperationandchecktheresultingactivitylogs.
6/43
9/14/2016
2.Verifythattheserverlistspecifiesthecorrectmasterserver.
oOnWindowsNT,98,and95systems,themasterserverisdesignatedasCurrentontheServerstabinthe
NetBackupConfigurationdialogbox.
Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceandclickConfigureontheActions
menu(alsosee"UsingtheConfigureNetBackupWindow"onpage57).
oOnUNIX,andMacintoshsystems,themasterserveristhefirstSERVERentryinthebp.conffile.
oOnNetWaretargetandOS/2clients,themasterservernameisthefirstSERVERentryinthebp.inifile.
Ifyouchangetheserverlistonamasterserver,stopandrestarttheNetBackupdatabasemanagerandrequest
daemons(UNIX)ortheNetBackupDatabaseManagerandNetBackupRequestManagerservices(Windows
NT).
3.Checktheservicesfile.
OnUNIX,verifythatthe/etc/servicesfile(andNISservicesifNISisused)hasentriesfortheNetBackupservices:bpcd,
bpdbm,andbprd.OnWindowsNT,verifythatthe%SystemRoot%\system32\drivers\etc\servicesfilehasthecorrect
entriesforbpcd,bpdbm,andbprd.
Also,verifythattheNetBackupClientServicePortNumberandNetBackupRequestServicePortNumberonthe
NetworktabintheNetBackupConfigurationdialogboxmatchthesettingsintheservicesfile.Todisplaythisdialogbox,
starttheBackup,Archive,andRestoreinterfaceandclickConfigureontheActionsmenu(alsosee"UsingtheConfigure
NetBackupWindow"onpage57).ThevaluesontheNetworktabarewrittentotheservicesfilewhentheNetBackup
Clientservicestarts.Also,see"VerifyingHostNamesandServicesEntries"onpage31.
StatusCode:26Top
Message:client/serverhandshakingfailed
Explanation:Aprocessontheserverencounteredanerrorwhencommunicatingwiththeclient.Thiserrorindicatesthatthe
clientandserverwereabletoinitiatecommunications,butencountereddifficultiesincompletingthem.Thisproblemcanoccur
duringabackuporarestore.
RecommendedAction:DeterminewhichactivityencounteredthehandshakefailurebyexaminingtheAllLogEntriesreportfor
theappropriatetimeperiod.Determinetheclientandserverthathadthehandshakefailure.
Fordetailedtroubleshootinginformation,createanactivitylogdirectoryfortheprocessthatreturnedthisstatuscode,retrythe
operation,andchecktheresultingactivitylog.
StatusCode:27Top
Message:childprocesskilledbysignal
Explanation:Achildoftheprocessreportingthiserrorwaskilled.Thiscanoccurbecausethebackupjobwasterminatedorthe
childprocesswasterminatedbyanothererror.ThisproblemcanalsooccurifaNetBackupprocesswasterminatedthrough
TaskManageroranotherutility.
RecommendedAction:ChecktheNetBackupAllLogEntriesreportforcluesonwhereandwhythefailureoccurred.For
detailedtroubleshootinginformation,createanactivitylogdirectoryfortheprocessthatyoususpectofreturningthisstatus
code.Then,retrytheoperationandchecktheresultingactivitylog.
StatusCode:28Top
Message:failedtryingtoforkaprocess
Explanation:Aforkofachildprocessfailed(onUNIX)oraCreateProcessfailed(onWindowsNT).Thismaybedueto:
Anoverloadedsystem
Insufficientswapspaceorphysicalmemory
Toomanyprocessesrunningonthesystem.
detailedtroubleshootinginformation,createactivitylogdirectoriesfortheprocessesthatyoususpectofreturningthisstatus
code.Then,retrytheoperationandchecktheresultingactivitylogs.
StatusCode:29Top
Message:failedtryingtoexecacommand
Explanation:Acommandcouldnotbeexecuted.Thiscanoccurbecausethepermissionsofthecommanddonotallowittobe
executed,orthereislackofsystemresourcessuchasmemoryandswapspace.
RecommendedAction:
1.ChecktheNetBackupAllLogEntriesreportforcluesonwhereandwhythefailureoccurred.
2.Checkthepermissionsonthecommandtobeexecuted.
313233343536373839Top
7/43
9/14/2016
StatusCode:30Top
Message:couldnotgetpasswdinformation
Explanation:Couldnotgetthepasswdentryforauser.
detailedtroubleshootinginformation,createanactivitylogfortheprocessthatyoususpectofreturningthisstatuscode.Then,
retrytheoperationandchecktheresultingactivitylog.
StatusCode:31Top
Message:couldnotsetuseridforprocess
Explanation:CouldnotsettheuserIDofaprocesstothatoftherequestinguser.NetBackupexecutesclientprocessesasthe
requestinguser.
StatusCode:32Top
Message:couldnotsetgroupidforprocess
Explanation:CouldnotsetthegroupIDofaprocesstotherequestingusergroup.NetBackupexecutesclientprocesseswith
thegroupIDoftherequestinguser.
StatusCode:33Top
Message:failedwhiletryingtosendmail
Explanation:AnEmailnotificationofbackup,archive,orrestoreresultshasfailed.TheEmailcouldnotbesenttothe
administrator'saddressasspecifiedbytheEmailglobalattribute,orinthecaseofaUNIXclient,anEmailaddressspecified
withUSEMAILintheclient'sbp.conffile.
StatusCode:34Top
Message:failedwaitingforchildprocess
Explanation:Thebpschedprocessencounteredafailurewhilewaitingforachildprocesstocomplete.
detailedtroubleshootinginformation,createanactivitylogfortheprocessthatyoususpectofreturningthisstatuscode.Then,
retrytheoperationandchecktheresultingactivitylog.
StatusCode:35Top
Message:cannotmakerequireddirectory
Explanation:Couldnotcreatearequireddirectory.Possiblecausesare:
Aprocessdoesnothavepermissiontocreatethedirectory
Thepathtothedirectoryisnotvalid
AnIOerroroccurs
Therewasnospaceavailableonthedevicecontainingthedirectory
RecommendedAction:
1.ChecktheNetBackupAllLogEntriesreporttodeterminewhichdirectorycouldnotbecreatedandwhyitcould
notbecreated.Inparticular,checkforafulldiskpartition.
2.CheckthepermissionsontheparentdirectoryandverifythatNetBackupservicesarestartedwitha"Logonas"
accountthathaspermissiontocreatethedirectory.
StatusCode:36Top
Message:failedtryingtoallocatememory
Explanation:Allocationofsystemmemoryfailed.Thiserroroccurswhenthereisinsufficientsystemmemoryavailable.This
couldbecausedbythesystembeingoverloadedwithtoomanyprocessesandthereisnotenoughphysicalandvirtual
memory.
8/43
9/14/2016
RecommendedAction:Freeupmemorybyterminatingunneededprocessesthatconsumealotofmemory.Addmoreswap
spaceorphysicalmemory.
StatusCode:37Top
Message:operationrequestedbyaninvalidserver
Explanation:ArequestwasmadetotheNetBackuprequestdaemon(bprd)orNetBackupdatabasemanagerdaemon(bpdbm)
byaninvalidslaveserverorWindowsNTadministrationclient.OnWindowsNT,thesedaemonsaretheNetBackupRequest
ManagerandNetBackupDatabaseManagerservices.
RecommendedAction:
ExaminetheNetBackupAllLogEntriesreportforthetimeofthiserrortodeterminewhichsystemwastryingtoconnecttothe
masterserver.Iftheserverisavalidslaveserver,verifythatthestorageunitfortheslaveserverisdefined.Also,verifythat
theserverorWindowsNTadministrationclienthasaserverlistentryonthemasterserver.
Ifnecessary,updatetheserverlist.OnaUNIXmasterserver,addaSERVER=slave_server_nametothebp.conffile.
slave_server_nameisthehostnameoftheslaveserver.OnaWindowsNTmasterserver,starttheBackup,Archive,and
Restoreinterface.Then,clickConfigureontheActionsmenuandaddtheslaveservertothelistontheServerstabinthe
NetBackupConfigurationdialogbox(also,see"UsingtheConfigureNetBackupWindow"onpage38).
IfaserverorWindowsNTadministrationclienthasmorethanonehostname(forexample,ifithasmultiplenetwork
interfaces),verifythatthemasterserverhasaserverlistentryforeachofthem.
IfyouchangetheserverlistonaUNIXmasterserver,youmuststopandthenrestarttheNetBackupRequestdaemon(bprd)
andNetBackupDatabaseManagerdaemon(bpdbm)forthechangestotakeeffect.IfyouchangetheserverlistonaWindows
NTmasterserver,stopandthenrestarttheNetBackupRequestManagerandNetBackupDatabaseManagerservices.
StatusCode:38Top
Message:couldnotgetgroupinformation
Explanation:CouldnotgetthegroupentrydescribingaUNIXusergroup.
RecommendedAction:ChecktheNetBackupProblemsreportforcluesonwhytheerroroccurred.Fordetailedtroubleshooting
information,createanactivitylogdirectoryfortheprocessthatreturnedthisstatuscode,retrytheoperation,andcheckthe
resultingactivitylog.
StatusCode:39Top
Message:clientnamemismatch
Explanation:ThenamethattheclientusedinarequesttotheNetBackupserverdidnotmatchtheclientnameconfiguredin
theclassontheserver.
RecommendedAction:ChangeeithertheNetBackupclientnamesettingontheclient(seetheapplicableNetBackupusers
guide)ortheoneintheclassconfigurationontheserversothetwomatch.
414243444546474849Top
StatusCode:40Top
Message:networkconnectionbroken
Explanation:Theconnectionbetweentheclientandtheserverwasbroken.Thisstatuscodecanalsoappeariftheconnection
isbrokenbetweenthemasterandslaveserverduringabackup.
RecommendedAction:
1.Trypingingtheclientfromtheserver.Ifthisisnotpossible,checkforlooseconnectionsorothernetwork
problems.
2.Verifythattheserverlistsettingsarecorrectonboththeclientandtheserver.Ifthebackupinvolvesaslave
server,verifythattheseentriesarecorrectonboththemasterandslaveserver.Forexample,ifaslaveserver
doesnothaveaserverlistentryforthemaster,itdoesnotacceptconnectionsfromthemaster.
oOnWindowsNT,98,and95systems,themasterserverisdesignatedasCurrentontheServerstabinthe
NetBackupConfigurationdialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestore
interfaceandclickConfigureontheActionsmenu(alsosee"UsingtheConfigureNetBackupWindow"on
page57).
oOnUNIX,andMacintoshsystems,themasterserveristhefirstSERVERentryinthebp.conffile.
oOnNetWaretargetandOS/2clientsthemasterservernameisthefirstSERVERentryinthebp.inifile.
IfyouchangetheserverlistonaUNIXmasterserver,youmuststopandthenrestarttheNetBackupRequest
daemon(bprd)andNetBackupDatabaseManagerdaemon(bpdbm)forthechangestotakeeffect.OnWindows
NT,stopandrestarttheNetBackupRequestManagerandNetBackupDatabaseManagerservices.
3.Statuscode40canalsobeduetotheoperatordenyingamountrequest.
StatusCode:41Top
Message:networkconnectiontimedout
Explanation:Theserverdidnotreceiveanyinformationfromtheclientfortoolongaperiodoftime.
9/43
9/14/2016
RecommendedAction:
1.OnaUNIXorWindowsNTclients,checkforthefollowingproblemswiththebpbkarclientprocess.
oThebpbkarclientprocessishungonafilethathasmandatorylockingset.Forthiscase,addthefollowing
totheclient'sbp.conffile:
VERBOSE
andasrootontheclientexecute:
touch/usr/openv/netbackup/bpbkar_path_tr
mkdir/usr/openv/netbackup/logs/bpbkar
Thenretrytheoperation.Thenamesofthefilesareloggedintheactivitylogfileinthe
/usr/openv/netbackup/logs/bpbkardirectorybeforebpbkarprocessesthem.Thelastfileinthelogwillbethefile
thatiscausingproblems.
Note:Also,usetheaboveprocedureforother,"unknown"bpbkarhangs.Iftheproblemisduetomandatoryfile
locking,youcanhaveNetBackupskipthelockedfilesbysettingLOCKED_FILE_ACTIONtoSKIPinthe
/usr/openv/netbackup/bp.conffileontheclient.
oThebpbkarclientprocessisnothung,butduetothefilesanddirectoriesitisscanning,ithasnotreplied
totheserverwithinCLIENT_READ_TIMEOUTorCLIENT_CONNECT_TIMEOUT.Thishasbeenseento
occurduringbackupswhendirectorieshavethousandsofunmodifiedfilesithasalsobeenseenwhen
backingupfilesystemsordirectoriesthatresideonopticaldisk,whichisconsiderablyslowerthan
magneticdisk.
Forthiscase,tryaddingormodifyingtheCLIENT_READ_TIMEOUTandCLIENT_CONNECT_TIMEOUTvalues
intheserver's/usr/openv/netbackup/bp.conffile.ThedefaultfortheCLIENT_READ_TIMEOUTand
CLIENT_CONNECT_TIMEOUTis300secondsifunspecified.
Useyoursystem'spscommandandmonitorCPUutilizationtohelpdecidewhichoftheaboveconditionsexist.
Whenyouarethroughinvestigatingtheproblem,deletethe/usr/openv/netbackup/logs/bpbkardirectory,sincethe
logfilescanbecomequitelargeandarenotdeletedautomatically.Alsodelete
/usr/openv/netbackup/bpbkar_path_trsoyoudonotgeneratelargerlogfilesthanneededthenexttimeyou
createdirectory/usr/openv/netbackup/logs/bpbkar.
2.Iftheservercannotconnecttotheclient,createbpcdorbpbkar(UNIXandWindowsNTonly)activitylog
directoriesontheclient,retrytheoperation,andchecktheresultinglogs.Iftheselogsdonotprovideaclue,
createabpbrmactivitylogontheserver,retrytheoperationagain,andchecktheresultingactivitylog.
Ifthebpbrmloghasentriessimilartothefollowing:
bpbrmhookup_timeout:timedoutwaitingduringtheclienthookup
bpbrmExit:clientbackupEXITSTATUS41:networkconnectiontimedout
thentheproblemisintheroutingconfigurationontheserver.VerifythattheclientIPaddressiscorrectinthename
servicethatisbeingused.OnUNIX,ifbothNISandDNSfilesareused,verifythattheymatch.Also,see"Resolving
NetworkCommunicationProblems"onpage21.
3.IfyouareusinganAIXtokenringadapterandtherouteddaemonisrunning,thetimeoutcanoccurbecausethe
tokenringadaptercreatesdynamicroutes,causingtherouteddaemontocrash.
4.ForaFlashBackupclient,thiscanhappenifthefilesystembeingbackedupisverylargeandhasaverylarge
numberoffiles.Itcanalsooccurifalargenumberofconcurrentdatastreamsareactiveatthesametime.The
correctiveactionistoaddCLIENT_READ_TIMEOUTtothe/usr/openv/netbackup/bp.conffileandsetitto
increasethetimeoutinterval.
StatusCode:42Top
Message:networkreadfailed
Explanation:Anattempttoreaddatafromasocketfailed.
RecommendedAction:
1.Verifythatboththeclientandtheserverareoperational.
2.Perform"ResolvingNetworkCommunicationProblems"onpage21.
3.ChecktheProblemsreportforclues.
StatusCode:43Top
Message:unexpectedmessagereceived
Explanation:Theclientandserverhandshakingwasnotcorrect.
RecommendedAction:
1.Verifythatthecorrectversionofsoftwareisrunningontheclientandtheserver.
2.Enabledetailedactivitylogging:
oOntheserver,createabpbrmactivitylogdirectory.
oOnclients,createabpcdactivitylogdirectory(createdautomaticallyonMacintoshclients).
oIncreasetheamountofdebuginformationincludedinthelogsasexplainedintheactivitylogtopicsin
Chapter3,"UsingtheLogsandReports."
3.Retrytheoperationandexaminethelogs.
Note:Ifyouareusingbpstart_notifyscriptsonUNIXorWindowsNTclients,verifythatmessagesarenotbeingwrittento
stdoutorstderr.
StatusCode:44Top
Message:networkwritefailed
10/43
9/14/2016
Explanation:Anattempttowritedatatoasocketfailed.
RecommendedAction:
1.ChecktheProblemsreportforinformationabouttheerror.
2.Verifythattheclientandserversareoperationalandconnectedtothenetwork.
3.Createanactivitylogdirectoryfortheprocessthatreportedtheproblemandtheoperation.Examinetheresulting
activitylogfilefordetailedtroubleshootinginformation.
StatusCode:45Top
Message:requestattemptedonanonreservedport
Explanation:Anattemptwasmadetoaccessaclientfromanonreservedport.
RecommendedAction:Verifythatthelatestsoftwareisinstalledontheclientandserver.
OnUNIXNetBackupserversandclients,checkthe/usr/openv/netbackup/bin/versionfile.
OnWindowsNTNetBackupservers,checktheinstall_path\netbackup\version.txtfileortheAboutNetBackup
commandontheHelpmenu.
OnMicrosoftWindowsclients,checktheAboutNetBackupcommandontheHelpmenu.
OnNetWaretargetclients,checktheVersionentryinthebp.inifile.
IfthisisaNetBackupforNetWareclientandhasaversionofNetBackupearlierthan3.0,verifythattheclientisin
aStandardtypeclass.
OnMacintoshclients,checktheversionfileinthebinfolderintheNetBackupfolderinthePreferencesfolder.
StatusCode:46Top
Message:servernotallowedaccess
Explanation:Theserveristryingtoaccesstheclientbuttheserverisnotlistedontheclientasavalidserver.
RecommendedAction:Iftheserverisavalidserver,additsnametotheclient'sserverlist:
OnWindowsNT,98,and95clients,addtheserverontheServerstabintheNetBackupConfigurationdialogbox.
Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceontheclientandclickConfigureon
theActionsmenu(alsosee"UsingtheConfigureNetBackupWindow"onpage57).
OnUNIX,andMacintoshclients,addaSERVERentryinthebp.conffile.OnNetWaretargetandOS/2clients
addaSERVERentryinthebp.inifile.
Ifyoucontinuetohaveproblems,review"ResolvingNetworkCommunicationProblems"onpage21and"VerifyingHost
NamesandServicesEntries"onpage31.
StatusCode:47Top
Message:hostisunreachable
Explanation:Anattempttoconnecttoanothermachinefailed.
RecommendedAction:
1.Verifythatthenameservice(orservices)beingusedbytheclientisconfiguredtocorrectlyresolvethehost
namesoftheNetBackupserver.
2.Verifythatthenameservice(orservices)beingusedbytheserverisconfiguredtocorrectlyresolvethehost
nameoftheNetBackupclient.
3.Trytopingtheclientfromtheserverandtheserverfromtheclient.
4.Ifyoucontinuetohaveproblems,perform"ResolvingNetworkCommunicationProblems"onpage21.
StatusCode:48Top
Message:clienthostnamecouldnotbefound
Explanation:Thesystemfunctiongethostbyname()failedtofindtheclient'shostname.
RecommendedAction:
1.Verifythattheclientnameiscorrectin:
oTheNetBackupclassconfigurationonthemasterserver.
oTheGeneralandClientstabsintheNetBackupConfigurationdialogboxonMicrosoftWindowsand
NetWarenontargetclients.Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceon
theclientandclickConfigureontheActionsmenu(alsosee"UsingtheConfigureNetBackupWindow"
onpage57).
oThebp.conffileonUNIXandMacintoshclients.
oThebp.inifileonOS/2andNetWaretargetclients.
2.Onclientsandservers,verifythatthenameserviceissetuptocorrectlyresolvetheNetBackupclientnames.On
UNIXclients,verifythattheclient'shostnameisinthe/etc/hostsfileortheYPhostsfileorNISmaps.
StatusCode:49Top
Message:clientdidnotstart
Explanation:Theclientfailedtostartupcorrectly.
RecommendedAction:
1.Verifythatsoftwareisinstalledontheclientanditisthecorrectversion.Ifnecessary,reinstalltheclientsoftware.
11/43
9/14/2016
2.Checkforfullfilesystemsontheclient.
3.Enabledetailedactivityloggingontheclient:
oCreatebpcdandbpbkar(UNIXorWindowsNTonly)activitylogdirectories.
oOnaUNIXclient,addtheVERBOSEoptiontothe/usr/openv/netbackup/bp.conffile.
oOnPCclients,increasethedebugorloglevelasexplainedintheactivitylogtopicsinChapter3,"Using
theLogsandReports."
4.Retrytheoperationandexaminetheresultinglogs.
5.OnUNIXsystems,usetheUNIXsumcommandtocheckforcorruptbinaries.
515253545556575859Top
StatusCode:50Top
Message:clientprocessaborted
Explanation:Theclientbackupaborted.OneinstancewhenthiscodeappearsisifaNetBackupmasterorslaveserverisshut
downorrebootedwhenabackuporrestoreisinprocess.
RecommendedAction:
1.Enabledetailedactivitylogging:
oCreateabpbkaractivitylogdirectory(UNIXorWindowsNTonly).
oCreateabpcdactivitylogdirectory(thislogiscreatedautomaticallyonMacintoshclients.
oOnUNIXclients,addtheVERBOSEoptiontothe/usr/openv/netbackup/bp.conffile.
oOnPCclients,increasethedebugorloglevelasexplainedintheactivitylogtopicsinChapter3,"Using
theLogsandReports."
2.Retrytheoperationandexaminetheresultinglogs.
3.OnUNIXclients,checkforcorefilesinthe/directory.
4.OnUNIXclients,checkthesystemlog(/usr/adm/messagesonSolaris)forsystemproblems.
5.Thisproblemcansometimesbeduetoacorruptbinary.
OnUNIXclients,usetheUNIXsumcommandtocheckthebpcd,bpbkar,andtarbinaries,locatedin
/usr/openv/netbackup/binontheclient.Reinstallthemiftheyarenotthesameasintheclientdirectoryunder
/usr/openv/netbackup/clientontheserver.
OnaWindowsNTclient,checkthebpinetd.exe,bpcd.exe,bpbkar32.exe,andtar32.exeexecutableslocatedinthe
install_path\NetBackup\binfolderontheclient.Reinstalltheclientiftheseexecutablesarenotthesamesizeasonother
WindowsNTclientsorarenotatthesamereleaselevelordonothavethesameNetBackuppatchesappliedasother
WindowsNTclients.
StatusCode:51Top
Message:timedoutwaitingfordatabaseinformation
Explanation:Thedatabaseprocessdidnotrespondwithinfiveminutes.
RecommendedAction:
1.VerifythattheNetBackupDatabaseManagerdaemon(serviceonWindowsNT)isrunning.
2.VerifythatthereisspaceinthefilesystemthatcontainstheNetBackupdatabases.
3.Createbpbrmandbpdbmactivitylogdirectoriesontheserverandretrytheoperation.
4.Lookintheactivitylogfilestofindmoreinformationontheproblem.
StatusCode:52Top
Message:timedoutwaitingformediamanagertomountvolume
Explanation:Therequestedvolumewasnotmountedbeforethetimeoutexpired.Thiserrorcanalsooccurifthevolume
happenstobeacleaningtapebutwasnotspecifiedasacleaningtape.
RecommendedAction:
1.VerifythattherequestedvolumeisavailableandanappropriatedriveisreadyandintheUPstate.
2.Ifthisoccursduringareadoperation(restore,duplicate,verify),thedrivescouldbebusy.Tryincreasingthe
mediamounttimeoutspecifiedbytheNetBackupglobalattributeinordertoallowmoretimeformountingand
positioningthemedia.
3.Verifythatthetapeisnotacleaningtapethatisconfiguredasaregularvolume.
4.WhentherobotiscontrolledbyanAutomatedCartridgeSystem,verifythattheACSLSsystemisup.
5.Ifthisisaninitialinstallation,referto"CommonConfigurationProblems"inchapter2.
6.OnWindowsNT,checktheEventViewerApplicationlogforerrormessagesthatindicatewhythetapemountdid
notcomplete.OnUNIX,checkthesystemlog.
StatusCode:53Top
Message:backuprestoremanagerfailedtoreadthefilelist
Explanation:Thebackupandrestoremanager(bpbrm)couldnotreadthelistoffilestobackuporrestore.
RecommendedAction:Verifythattheserversoftwarehasbeeninstalledcorrectlyonthemasterserverandallslaveservers.If
thatisnottheproblem:
1.Createbpbrmandbpschedactivitylogdirectoriesontheserver.
12/43
9/14/2016
2.OnaUNIXNetBackupserver,addtheVERBOSEoptiontothebp.conffile.OnaWindowsNTNetBackupserver,
settheVerboseoptionontheTroubleshootingtabintheNetBackupConfigurationdialogbox.Todisplaythis
dialogbox,starttheBackup,Archive,andRestoreinterfaceontheserverandclickConfigureontheActions
3.Retrytheoperationandchecktheresultingactivitylogsfordetailedtroubleshootinginformation.
StatusCode:54Top
Message:timedoutconnectingtoclient
Explanation:Theservercouldnotcompletetheconnectiontotheclient.Theacceptsystemcalltimedoutafter60seconds.
RecommendedAction:
1.ForaMacintoshorNetWaretargetclient,verifythattheserverisnottryingtoconnectwhenabackuporrestore
isalreadyinprogressontheclient.TheseclientscanhandleonlyoneNetBackupjobatatime.
OnaMacintosh,youcancheckforactivitybyexaminingtheNetBackupListenfileinthefollowingfolderonthestartup
diskoftheMacintoshclient::SystemFolder:Preferences:NetBackup:logs:inetd:log.mmddyy
2.OnaSequentplatform,verifythatthesystemhasthecorrectlevelofTCP/IP.
4.OnUNIXclients,verifythatthe/usr/openv/netbackup/bin/bpcdbinaryexistsandthatitisthecorrectsize.
StatusCode:55Top
Message:permissiondeniedbyclientduringrcmd
Explanation:TheUNIXclientdoesnothavetheserver'snameinits/.rhostsfile.
RecommendedAction:Addtheservernametothe/.rhostsfileontheUNIXclient.
StatusCode:56Top
Message:client'snetworkisunreachable
Explanation:TheservergotENETUNREACHwhentryingtoconnecttotheclient.
RecommendedAction:Trytopingtheclientfromtheserver.ChecktheIPaddressfortheclient.Ifyoustillhaveproblems,talk
toyournetworkadministrator.
StatusCode:57Top
Message:clientconnectionrefused
Explanation:Theclientrefusedaconnectionontheportnumberforbpcd.Thiscanoccurbecausethereisnoprocesslistening
onthebpcdportortherearemoreconnectionstothebpcdportthanthenetworksubsystemcanhandlewiththelisten()call.
RecommendedAction:
1.ForWindowsNTNetBackupservers:
a.Verifythatthebpcdandbprdportnumbersinthe%SystemRoot%\system32\drivers\etc\servicesfileonthe
servermatchesthesettingontheclient.
b.VerifythattheNetBackupClientServicePortNumberandNetBackupRequestServicePortNumberon
theNetworktabintheNetBackupConfigurationdialogboxmatchthebpcdandbprdsettingsinthe
servicesfile.Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceontheserverand
clickConfigureontheActionsmenu(alsosee"UsingtheConfigureNetBackupWindow"onpage57).
ThevaluesontheNetworktabarewrittentotheservicesfilewhentheNetBackupClientservicestarts.
c.VerifythattheNetBackupClientserviceisrunning.
2.ForUNIXservers,verifythatthebpcdportnumberontheserver(eitherNISservicesmaporin/etc/services)
matchesthenumberintheclient'sservicesfile.
3.ForaMacintoshorNetWaretargetclient,verifythattheserverisnottryingtoconnectwhenabackuporrestore
isalreadyinprogressontheclient.TheseclientscanhandleonlyoneNetBackupjobatatime.
StatusCode:58Top
Message:can'tconnecttoclient
Explanation:Theserverwasunabletoconnecttotheclient.
RecommendedAction:Perform"ResolvingNetworkCommunicationProblems"onpage21.
StatusCode:59Top
Message:accesstotheclientwasnotallowed
Explanation:Themasterorslaveserveristryingtoaccesstheclient,buttheserverisnotrecognizedbytheclientasavalid
server.
RecommendedAction:
1.Iftheserverisavalidserver,verifythatitisintheserverlistontheclient.Ifnecessaryadditasfollows:
oOnWindowsNT,98,and95clients,addtheserverontheServerstabintheNetBackupConfiguration
dialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceontheclientand
13/43
9/14/2016
oOnUNIX,andMacintoshclients,addaSERVERentryinthebp.conffile.
oOnNetWaretargetandOS/2clientsaddaSERVERentryinthebp.inifile.
IfyouchangetheserverlistonaUNIXmasterserver,youmuststopandthenrestarttheNetBackupRequest
daemon(bprd)andNetBackupDatabaseManagerdaemon(bpdbm)forthechangestotakeeffect.OnWindows
NT,stopandrestarttheNetBackupRequestManagerandNetBackupDatabaseManagerservices.
2.OnWindowsNTclients,enablebpinetdactivityloggingasfollows:
a.Createabpinetdactivitylogdirectoryontheclient.
b.IncreasethedebugorloglevelasexplainedintheactivitylogtopicsinChapter3,"UsingtheLogsandReports."
c.Retrythebackupandexaminetheresultinglogstodeterminethecauseofthefailure.
1.OnallbutMacintoshclients,enablebpcdactivityloggingasfollows:
a.Createabpcdactivitylogdirectoryontheclient.
b.OnaUNIXclient,addtheVERBOSEoptiontothe/usr/openv/netbackup/bp.conffile.
c.OnPCclients,increasethedebugorloglevelasexplainedintheactivitylogtopicsinChapter3,"UsingtheLogs
andReports."
d.Retrythebackupandexaminetheresultinglogstodeterminethecauseofthefailure.
2.OnMacintoshclients,checktheinetdandbpcdactivitylogs.Bothlogsarecreatedautomatically.
oChecktheinetdlogtoseeifNetBackupListenisrunning.
oCheckthebpbkarandtarmessagesinthebpcdlogfile.Toincreasetheamountofinformationincludedin
thelogs,settheloglevelparameterinthemac.conffiletoahighervalue.
1.Checkthebpcdactivitylogtodeterminetheserver'speernameandwhatcomparisonsarebeingmade.The
bpcdprocesscomparesNetBackupserverlistentriestothepeernameoftheserverattemptingtheconnection
andrejectstheconnectionifthenamesaredifferent.Ifnecessary,changetheserverlistentryontheclientto
matchthepeername.
2.OnWindowsNTclients,checkthefollowing:
oVerifythatNetBackupforWindowsNTsoftwarewasinstalledunderaWindowsNTadministratoraccount.
IfNetBackupisunderanothertypeofaccount,reinstallitunderanadministratoraccount.Theinstallationwill
completesuccessfullyunderanonadministratoraccountbuttheNetBackupClientserviceisnotaddedto
WindowsNTandtheNetBackupservercannotaccesstheclient.
oVerifythattheWindowsNTTCP/IPservicespecifiesthedomainserverthatresolvesnamesforthesubnet
thatcontainstheNetBackupservers.UNIXandWindowsNTclientsarefrequentlynotonthesame
subnetandusedifferentdomainservers.WhenthisconditionexiststheNetBackupserversandWindows
NTclientsmaybeabletopingoneanother,buttheserverisstillunabletoaccesstheWindowsNTclient.
3.Iftheprecedingstepsdonotresolvethisproblem,see"ResolvingNetworkCommunicationProblems"onpage
21.
616263646566676869Top
StatusCode:60Top
Message:clientcannotreadthemounttable
Explanation:Thebackupprocessontheclientcouldnotreadthelistofmountedfilesystems.
RecommendedAction:
1.Executeadftoseeifthesystemcanreadthemounttable.
2.OnanSCOsystem,code60canoccurbecausethemountpointpathnameexceeds31characters,whichisthe
maximumallowedonanSCOsystem.Thebpbkaractivitylogontheclientwillshowamessagesimilartothe
following:
bpbkarbuild_nfs_list:FTLcannotstatfsnetErrno:42406
Toeliminatetheseerrorsforfuturebackups,createamountpointwithashorternameandsymbolicallylinkthelong
nametotheshortname.
3.Fordetailedtroubleshootinginformation,createabpbkaractivitylogdirectory,retrytheoperation,andexamine
theresultinglog.
StatusCode:61Top
Message:wbakwaskilled
Explanation:ThewbakprocessontheApollowaskilled.
RecommendedAction:Trythebackupagain.
StatusCode:62Top
Message:wbakexitedabnormally
Explanation:ThewbakprocessontheApolloexitedabnormally.
RecommendedAction:Tryrunningwbakbyhandtodeterminethesourceoftheproblem.Directtheoutputofthewbak
commandto/dev/nulltoavoidfillingupyourfilesystemandusethefollowingparameters:
lnhipdtustdoutnwlaandfullorafdate
StatusCode:63Top
14/43
9/14/2016
Message:processwaskilledbyasignal
Explanation:Akillsignalwassenttotheclientprocess.
RecommendedAction:Thisisusuallycausedbysomeoneintentionallyterminatingabackup.
StatusCode:64Top
Message:timedoutwaitingfortheclientbackuptostart
Explanation:Theclientdidnotsendareadymessagetotheserverwithintheallottedtime.
RecommendedAction:
1.1.OnallbutMacintoshclients,enablebpcdactivityloggingasfollows:
a.Createabpcdactivitylogdirectoryontheclient.
b.OnaUNIXclient,addtheVERBOSEoptiontothe/usr/openv/netbackup/bp.conffile.
c.OnPCclients,increasethedebugorloglevelasexplainedintheactivitylogtopicsinChapter3,"Using
theLogsandReports."
2.2.OnMacintoshclients,checktheinetdandbpcdactivitylogs.Bothlogsarecreatedautomatically.
oChecktheinetdlogtoseeifNetBackupListenisrunning.
oCheckthebpbkarandtarmessagesinthebpcdlogfile.Toincreasethelogginglevel,settheloglevel
parameterinthemac.conffiletoahighervalue.
1.OnaUNIXorWindowsNTclient,createthebpbkaractivitylogdirectoryontheclient.
2.OnWindowsNTclients,verifythattheNetBackupClientserviceisrunning.
3.OnaUNIXclient,usethepscommandtocheckforaclientprocessthatisusingtoomuchCPUtime.
4.Retrythebackupandexaminetheactivitylogsforcluesonthecauseofthefailure.
StatusCode:65Top
Message:clienttimedoutwaitingforthecontinuemessagefromthemediamanager.
Explanation:Thetapemanager,bptmreportedthatthemediadidnotloadandpositionwithintheallottedtime.
RecommendedAction:VerifythattherequestedvolumeisavailableandtherequireddeviceisinanUPstate.
Fordetaileddebuginformation:
1.Createabptmactivitylogdirectoryontheserver.
2.OnaUNIXNetBackupserver,addtheVERBOSEoptiontothebp.conffile.OnaWindowsNTNetBackupserver,
settheVerboseoptionontheGeneraltabintheMasterServerPropertiesdialogbox(see"UsingtheConfigure
NetBackupWindow"onpage57).
3.Retrytheoperationandcheckthebptmactivitylogfileforinformationonthedrive,robot,andtapethatiscausing
thetimeout.
4.OnaWindowsNTNetBackupserver(masterorslave),checktheEventViewerApplicationlogforerror
messagesthatindicatewhythetapemountdidnotcomplete.
StatusCode:66Top
Message:clientbackupfailedtoreceivetheCONTINUEBACKUPmessage
Explanation:Theclientbpbkarprocessdidnotreceivethemessagefromtheserverthatindicatesthattheserverisreadyto
continue.
RecommendedAction:
Verifythattheserverdidnotcrash.Ifthatisnottheproblemandyouneedmoreinformation:
1.OnUNIXandWindowsNTclients,enablebpbkaractivitylogging.
a.Createabpbkaractivitylogdirectory.
b.OnaUNIXclient,addtheVERBOSEoptiontothebp.conffile.OnaWindowsNTclient,setVerboseon
theTroubleshootingtabintheNetBackupConfigurationdialogbox.Todisplaythisdialogbox,startthe
Backup,Archive,andRestoreinterfaceontheclientandclickConfigureontheActionsmenu(alsosee
"UsingtheConfigureNetBackupWindow"onpage57).
2.OnotherPCclientsexceptMacintosh,createanactivitylogdirectoryforbpcd(thebpcdlogiscreated
automaticallyonMacintosh).Toincreasetheamountofinformationthatappearsinthelogs,seethelogging
topicsinChapter3,"UsingtheLogsandReports."
3.Onthemasterservercreatebpschedandbpbrmactivitylogdirectories.Ifthereareslaveserversinvolved,create
abpbrmactivitylogdirectoryonthem.
4.Retrytheoperationandchecktheresultingactivitylogs.
StatusCode:67Top
Message:clientbackupfailedtoreadthefilelist
Explanation:Theclientcouldnotreadthelistoffilestobackup.
RecommendedAction:First,verifythattheserverdidnotcrash.Ifthatisnottheproblemandyouneedmoreinformation:
1.Setupactivitylogging:
a.Ontheserver,createabpbrmactivitylogdirectory.
b.OnUNIXandWindowsNTclients,createabpbkaractivitylogdirectory.
c.OnotherPCclientsexceptMacintosh,createanactivitylogdirectoryforbpcd(thebpcdlogiscreated
automaticallyonMacintosh).Toincreasetheamountofinformationthatappearsinthelogs,seethe
loggingtopicsinChapter3,"UsingtheLogsandReports."
15/43
9/14/2016
StatusCode:68Top
Message:clienttimedoutwaitingforthefilelist
Explanation:Theclientdidnotreceivethelistoffilestobackupwithintheallottedtime.Thislistcomesfromtheserver.
RecommendedAction:First,verifythattheserverdidnotcrash.Ifthatisnottheproblemandyouneedmoreinformation:
a.Ontheserver,createabpbrmactivitylogdirectory.
b.OnUNIXandWindowsNTclients,createabpbkaractivitylogdirectory.
c.OnotherPCclientsexceptMacintosh,createanactivitylogdirectoryforbpcd(thebpcdlogiscreated
StatusCode:69Top
Message:invalidfilelistspecification
Explanation:Thefilelistreceivedfromtheserverhadinvalidentries.
RecommendedAction:Checktheclassfilelist.Ifwildcardsareused,verifytherearematchingbracketcharacters([and]).If
thefilelistcontainsUNC(UniversalNamingConvention)names,ensuretheyareproperlyformatted.
7172737475767778Top
StatusCode:70Top
Message:anentryinthefilelistexpandedtotoomanycharacters
Explanation:Thewildcardsusedinoneofthefilelistentriescausedtoomanyfilestobespecified.
RecommendedAction:Changethewildcardsinthefilelisttospecifyfewerfiles.
StatusCode:71Top
Message:noneofthefilesinthefilelistexist
Explanation:Thefilesinthefilelistdidnotmatchanyofthefilesontheclient.Thiserrorcanoccurwhenthereisonlyonefile
inthefilelistandthefilecannotbebackedupduetoanI/Oerror.
RecommendedAction:
1.Verifythatthecorrectfilelistisspecifiedforthisclient.
2.OnWindowsNTclients,verifythattheaccountusedtostarttheNetBackupClientservicehasreadaccesstothe
files.
IfyouarebackingupanetworkdriveoraUNC(universalnamingconvention)path,usetheServicesapplicationinthe
WindowsNTControlPaneltoverifythattheNetBackupClientservicedoesnotstartundertheSYSTEMaccount.The
SYSTEMaccountcannotaccessnetworkdrives.TobackupnetworkdrivesorUNCpaths,changetheNetBackupClient
servicestartuptologinasauserthathaspermissiontoaccessnetworkdrives.
3.ChecktheAllLogEntriesreportforclues.
oOnUNIXandWindowsNTclients,createanactivitylogdirectoryforbpbkar.
oOnotherPCclientsexceptMacintosh,createanactivitylogdirectoryforbpcd(thebpcdlogiscreated
automaticallyonMacintosh).
Toincreasetheamountofinformationthatappearsinthelogs,seetheloggingtopicsinChapter3,"UsingtheLogsand
Reports."
StatusCode:72Top
Message:theclienttypeisincorrectintheconfigurationdatabase
Explanation:Theclasstypeattributeintheclassconfigurationindicatesthattheclientisonetype,buttheinstalledsoftwareis
foranothertype.
RecommendedAction:Verifythattheclasstypeattributefortheclassiscorrect.Also,forUNIX,donotplaceApolloand
standardclientsinthesameclass.
StatusCode:73Top
Message:bpstart_notifyfailed
Explanation:Thebpstart_notifyscriptreturnedanonzeroexitcode.
RecommendedAction:Checkthebpstart_notifyscriptontheclienttoseeifitperformsasdesired.
16/43
9/14/2016
StatusCode:74Top
Message:clienttimedoutwaitingforbpstart_notifytocomplete
Explanation:Thebpstart_notifyscriptontheclienttooktoolong.
RecommendedAction:Trytospeedupthebpstart_notifyscriptorsettheBPSTART_TIMEOUTontheservertoavaluethatis
largerthanthedefault.SetBPSTART_TIMEOUTinthebp.conffileonaUNIXNetBackupserver.OnaWindowsNTNetBackup
server,usetheConfigureNetBackupwindowtosetBackupStartTimeout(see"UsingtheConfigureNetBackupWindow"on
page57).
StatusCode:75Top
Message:clienttimedoutwaitingforbpend_notifytocomplete
Explanation:Thebpend_notifyscriptontheclienttooktoolong.
RecommendedAction:Trytospeedupthebpend_notifyscriptorsetBPEND_TIMEOUTontheservertoavaluethatislarger
thanthedefault.SetBPEND_TIMEOUTinthebp.conffileonaUNIXNetBackupserver.OnaWindowsNTNetBackupserver,
usetheConfigureNetBackupwindowtosetBackupEndTimeout.
StatusCode:76Top
Message:clienttimedoutreadingfile
Explanation:Afifowasspecifiedinthefilelistandnodatawasproducedonthefifowithintheallottedtime.
RecommendedAction:
1.Verifythattheprocessproducesthedataonthenamedfifoisstartedcorrectly.
2.SettheCLIENT_READ_TIMEOUToptionontheservertoavaluethatislargerthanthedefault.The
CLIENT_READ_TIMEOUToptionisinthebp.conffileonaUNIXNetBackupserverandintheregistryona
WindowsNTNetBackupserver.
StatusCode:77Top
Message:executionofthespecifiedsystemcommandreturnedanonzerostatus
Explanation:Animmediatecommandreturnedanonzerostatus.
RecommendedAction:
1.Verifythatthecommandisspecifiedcorrectly.
2.Executethecommandmanuallytoseeifthedesiredresultisproduced.
3.Fordetailedtroubleshootinginformation,setupactivitylogging:
a.OnUNIXandWindowsNTclients,createanactivitylogdirectoryforbpbkar.
b.OnotherPCclientsexceptMacintosh,createanactivitylogdirectoryforbpcd(thebpcdlogiscreated
c.Retrytheoperationandchecktheresultingactivitylog.
StatusCode:78Top
Message:afs/dfscommandfailed
Explanation:IndicatesanAFSvoscommandfailure.
RecommendedAction:
1.ChecktheNetBackupProblemsReportforadditionalinformationonwhythecommandfailed.
2.Thebpbkaractivitylogshowsthecommandthatwasexecuted.Createanactivitylogdirectoryforbpbkar.Retry
theoperationandretrytheresultingactivitylog.
3.Tryexecutingthevoscommandmanuallytoduplicatetheproblem.
8182838485868788Top
StatusCode:80Top
Message:MediaManagerdevicedaemon(ltid)isnotactive
Explanation:IftheserverisUNIX,theTheMediaManagerdevicedaemon,ltid,isnotrunning.IftheserverisWindowsNT,the
NetBackupDeviceManagerserviceisnotrunning.
RecommendedAction:
1.OnWindowsNT,usetheActivityMonitorortheServicesapplicationintheWindowsNTControlPaneltoseeif
theNetBackupDeviceManagerserviceisrunning.Ifitisnotrunning,startit.Toenableverboselogging,place
VERBOSEonalinebyitselfintheinstall_path\Volmgr\vm.conffilebeforestartingtheservice.
2.OnUNIX,usevmpstoseeifltidisrunningandifnecessarystartitinverbosemodewiththefollowingcommand:
/usr/openv/volmgr/bin/ltidv
Or,addaVERBOSEentrytotheMediaManagerconfigurationfile,/usr/openv/volmgr/vm.conf.Createthevm.conffileif
necessary.
3.OnUNIX,checkthesystemlogstoverifythatltidstarts.
17/43
9/14/2016
Note:ltidortheNetBackupDeviceManagerserviceisusedonlyifdevicesareattachedtothesystem.
StatusCode:81Top
Message:MediaManagervolumedaemon(vmd)isnotactive
Explanation:Thetapemanager(bptm)couldnotcommunicatewiththeNetBackupVolumeManagerservice(WindowsNT)or
theMediaManagervolumedaemon(UNIX).Thiscommunicationisrequiredformostoperations.
RecommendedAction:
OnUNIX:
VerifythattheMediaManagerdevicedaemon(ltid)andthevolumedaemon(vmd)arerunning.Startthemifnecessary.
OnWindowsNT:
VerifythatboththeNetBackupDeviceManagerserviceandtheNetBackupVolumeManagerservicearerunning.Startthemif
necessary.
Note:ltidortheNetBackupDeviceManagerserviceisusedonlyifdevicesareattachedtothesystem.
StatusCode:82Top
Message:mediamanagerkilledbysignal
Explanation:Thetapemanager(bptm)ordiskmanager(bpdm)wasterminatedbyanotherprocessorauser.
RecommendedAction:Thisshouldnotoccurinnormaloperation.Ifyouwanttoterminateanactivebackup,usethe
NetBackupActivityMonitor(onWindowsNT)orthejobmonitor(onUNIX).
WhenbackingupaDomainOSclient(forexample,Apollo),thishasbeenseentooccuraftertheserverhasnotreceived
anythingonthesocketforatleast300seconds,thuscausingaclientreadtimeoutandbreakingtheconnection.Thebpbkar
activityloghadanentrysimilartothefollowing:
13:22:49[1347]<16>bpbkar:ERRExtraoutputECONNRESET
Connectionresetbypeer(UNIX/errnostatus)
IncreasingtheCLIENT_READ_TIMEOUTvalue(inthisinstanceto900)hasresolvedthisproblem.
StatusCode:83Top
Message:mediaopenerror
Explanation:Thetapemanager(bptm)ordiskmanager(bpdm)couldnotopenthedeviceorfilethatthebackuporrestore
mustuse.
RecommendedAction:
1.Foradditionalinformation,checkthefollowing:
oNetBackupProblemsreport
oSystemlog(UNIX)
oEventViewerApplicationlog(WindowsNT)
2.Typically,thisstatuscodeindicatesadriveconfigurationproblemthatallowsmorethanoneprocessatatimeto
openthedevice.
OnUNIX,theproblemcouldbedueto:
oTwo(ormore)deviceswereconfiguredthatarereallythesamephysicaldevice(fordifferentdensities
perhaps).Verifythatnoneofthe/devfilesusedforthesedeviceshavethesamemajororminornumbers.
oLinksexistinthefilesystemthatareallowingusersaccesstothedrives.
oThephysicalconfigurationforthedriveswasmodified(xdevadm,tpconfig,orvm.conf)andtheMedia
Managerdevicedaemon,ltid,wasnotrestarted.Verifytheconfigurationandstartltid.
OnWindowsNT,theproblemcouldbethattheMediaManagerdeviceconfigurationwasmodifiedbuttheNetBackup
DeviceManagerservicewasnotrestarted.VerifytheconfigurationandrestarttheNetBackupDeviceManagerservice.
3.Fordetailedtroubleshootinginformation:
a.Createanactivitylogdirectoryforbpdm(ifthedeviceisdisk)orbptm(ifthedeviceistape).
b.OnUNIX,restartltidintheverbosemodebyexecuting:/usr/openv/volmgr/bin/ltidv
Or,addaVERBOSEentrytotheMediaManagerconfigurationfile,/usr/openv/volmgr/vm.conf.Createthe
vm.conffileifnecessary.
c.OnWindowsNT,enableverboseloggingbyaddingVERBOSEonalinebyitselfinthe
install_path\Volmgr\vm.conffile.Then,stopandrestarttheNetBackupDeviceManagerservice.
d.Retrytheoperationandchecktheresultingactivitylogfiles.
StatusCode:84Top
Message:mediawriteerror
Explanation:Thesystem'sdevicedriverreturnedanI/OerrorwhileNetBackupwaswritingtoremovablemediaoradiskfile.
RecommendedAction:
oNetBackupProblemsreporttodeterminethedeviceormediathatcausedtheerror
oSystemanderrorlogsforthesystem(UNIX)
oEventViewerApplicationandSystemlogs(WindowsNT)
2.IfNetBackupwaswritingbackupstoadiskfile,verifythatthediskhasenoughspaceforthebackup.
ForNetBackupdatabasebackuptoadiskpathonaUNIXsystem,youmaybetryingtowriteaimagegreaterthantwo
gigabytes.FilesizesgreaterthantwogigabytesisalimitationonmanyUNIXfilesystems.Tapefilesdonothavethis
18/43
9/14/2016
limit.
3.Ifthemediaistapeoropticaldisk,checkfor:
oAdefectiveordirtydrive,inwhichcase,cleanitorhaveitrepaired(refertothetpcleancommandfor
roboticdrives).
oThewrongmediatype.Verifythatthemediamatchesthedrivetypeyouareusing.Onanopticaldrive,the
plattersmaynotbeformattedcorrectly.
oDefectivemedia.Ifthisisthecase,usethebpmediacommandtosetthevolumetotheFROZENstateso
itisnotusedforfuturebackups.
oIncorrectdriveconfiguration.VerifytheMediaManagerandsystemconfigurationforthedrive.
Forexample,onUNIXthedrivecouldbeconfiguredforfixedmodewhenitmustbevariablemode.Seethe
MediaManagerDeviceConfigurationGuideformoreinformation.
StatusCode:85Top
Message:mediareaderror
Explanation:ThesystemdevicedriverreturnedanI/OerrorwhileNetBackupwasreadingfromtape,opticaldisk,oradiskfile.
RecommendedAction:
NetBackupProblemsreporttodeterminethedeviceormediathatcausedtheerror
Systemanderrorlogsforthesystem(UNIX)
EventViewerApplicationandSystemlogs(WindowsNT)
2.Checkforthefollowing:
Adefectiveordirtydrive.Cleanitorhaveitrepaired(seethetpcleancommandforcleaning).
Incorrectdriveconfiguration.VerifytheMediaManagerandsystemconfigurationforthedrive.
Forexample,onUNIXthedrivecouldbeconfiguredforfixedmodewhenitmustbevariablemode.SeetheMediaManager
DeviceConfigurationGuideformoreinformation.
Defectivemedia.Inthiscase,youmaynotbeabletorecoverallthedataonthemedia.Usethebpmediacommandtosetthe
volumetotheFROZENstatesoitisnotusedforfuturebackups.
Thewrongmediatype.Verifythatthemediamatchesthedrivetypeyouareusing.
StatusCode:86Top
Message:mediapositionerror
Explanation:Thesystem'sdevicedriverreturnedanI/OerrorwhileNetBackupwaspositioningmedia(tapeoropticaldisk).
RecommendedAction:
Incorrectdriveconfiguration.VerifytheMediaManagerandsystemconfigurationforthedrive.
Forexample,onUNIXthedrivecouldbeconfiguredforfixedmodewhenitmustbevariablemode.SeetheMediaManager
DeviceConfigurationGuideformoreinformation.
Defectivemedia.Inthiscase,somedatamaybelost.UsethebpmediacommandtosetthevolumetotheFROZENstateso
Thewrongmediatype.Verifythatthemediamatchesthedrivetypeyouareusing.
StatusCode:87Top
Message:mediacloseerror
Explanation:Thesystem'sdevicedriverreturnedanI/OerrorwhileNetBackupwasclosingatapeoropticaldisk.
RecommendedAction:
Defectivemedia.Inthiscase,somedatamaybelost.UsethebpmediacommandtosetthevolumetotheFROZENstateso
StatusCode:88Top
Message:AuspexSP/Backupfailure
Explanation:NetBackupdetectedaproblemwhenbackingupanAuspexFastBackupclient.
RecommendedAction:ChecktheAllLogEntriesreport.Ifmoredetailsarerequired,createbptmandbpbrmactivitylog
directoriesontheserver.Then,retrytheoperationandchecktheresultinglogfiles.Thiserrorisusuallyduetoaconfiguration
problem.
19/43
9/14/2016
919293949596979899Top
StatusCode:90Top
Message:mediamanagerreceivednodataforbackupimage
Explanation:Thetapemanager(bptm)ordiskmanager(bpdm)receivednodatawhenperformingabackuporarchive.This
canoccurforincrementalbackupswherenodatawasbackedupbecausenofileshavechanged.
RecommendedAction:
EventViewerApplicationlog(WindowsNT)
2.VerifytheMediaManagerandsystemconfigurationforthedrive.
Forexample,onUNIXthedrivemaynotbesetforvariablemodeinacasewherethatmodeisrequiredbyNetBackup.Check
theMediaManagerDeviceConfigurationGuidefordriveconfigurationinformation.
3.VerifythattheMediaManagerconfigurationforthebackupdevicematcheswhatisspecifiedforthestorageunitinthe
NetBackupclass.
4.Verifythatyouareusingthecorrectmediainthedrive.
5.Fordetaileddebuginformation,createabpdmorbptmactivitylogdirectory(whicheverapplies)ontheserver.Iftheclientis
WindowsNT,alsocreateabpbkaractivitylogdirectoryontheclient.Retrytheoperationandchecktheresultingactivitylogs.
Retrytheoperation.Checktheresultingactivitylogfile.
StatusCode:91Top
Message:fatalNBmediadatabaseerror
Explanation:Thetapemanager(bptm)receivedanerrorwhilereadingorupdatingitsmediadatabase.
RecommendedAction:
1.ChecktheAllLogEntriesreportformoreinformation.
2.ChecktheNetBackupMediaListsreporttoseeifthedatabaseisintact.Ifthedatabaseisnotintact,considerreloadingit
fromthelatestNetBackupdatabasebackupvolume.
3.Verifythatthediskpartitiononwhichthedatabaseresideshasenoughspace.
4.Iftheaboveactionsdonotexplaintheproblem,checktheNetBackupProblemsreport.
5.Fordetailedtroubleshootinginformation,createabptmactivitylogdirectoryontheserverandretrytheoperation.Checkthe
resultingactivitylogfile.
6.Contactcustomersupportandsendappropriateproblemandactivitylogsections.
StatusCode:92Top
Message:mediamanagerdetectedimagethatwasnotintarformat
Explanation:Whenperformingarestore,thetapemanager(bptm)ordiskmanager(bpdm)couldnotfindatarheaderatthe
offsetitexpected.
RecommendedAction:
1.Performabpverifyoftheaffectedimagetodetermineifitiswrittencorrectly.
2.ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.
3.VerifytheMediaManagerandsystemconfigurationforthedrive.Forexample,onsomeUNIXsystems,forexample,ifyou
donotconfigurethedriveforvariablemodeblocksizewrites,backupimageswrittentothemediaproducethiserrorwhenan
attemptismadetorestoretheimage.Forexample,youseethefollowingsequenceofevents:
Backupsucceeds
Verifysucceeds
Restorefails
Thebptmactivitylogshowsanerrorsimilarto
00:58:54[2304]<16>write_data:writeof32768bytesindicatedonly29696byteswerewritten,errno=0
Inthiscase,configurethedriveforvariablemodeblocksizesandsuspendmediawrittenonthatdevice.SeetheNetBackup
DeviceConfigurationGuide.
Theimageswrittentothosemediamayberestorable(thisisplatformdependent),butsinglefilerestoresarealmost
guaranteedtofail.Youcanchoosetoexpirethesemediaandregeneratethebackups,oryoucanattempttoduplicatethe
imagesonthesemediatoanotherdeviceandthenexpiretheoriginalcopy.
4.Errorcode92hasbeenencounteredonsomerelabeledandvalueadded8mmtapedriveswherethedrive'smicrocode
incorrectlyprocessesa"forwardspacerecord"SCSIcommand.
5.Iftheproblemisnotoneoftheabove,createanactivitylogdirectoryforeitherbpdmorbptmandretrytheoperation.Check
theresultingactivitylogfile.
StatusCode:93Top
Message:mediamanagerfoundwrongtapeindrive
Explanation:Whenloadingavolumeforabackuporrestore,thetapemanager(bptm)foundavolumeloadedthatdidnothave
theexpectedtapeheader.ThiscanindicatethatvolumesinarobotarenotintheslotsindicatedintheMediaManagervolume
configuration.
20/43
9/14/2016
RecommendedAction:
Ifthevolumeisinarobotandtherobotsupportsbarcodes,performaCompareContentswithVolumeConfiguration(Verify
RobotContentsonUNIX).TheresultingreportshowswhichmediaIDwasfoundandvalidatesitsslotnumberwithwhatisin
theMediaManagervolumeconfiguration.Then,eitherchangethephysicallocationintherobotorchangethevolume
configurationtoshowthecorrectslot.
Ifthevolumewasmountedonanonroboticdrive,verifythatthecorrectvolumewasmountedandassigned.
StatusCode:94Top
Message:cannotpositiontocorrectimage
Explanation:Whensearchingforabackupimagetorestore,thetapemanager(bptm)didnotfindthecorrectbackupIDatthe
expectedpositiononthevolume.Thiscanindicateadrivehardwareproblem.
RecommendedAction:
1.Trytherestoreonanotherdriveifpossible.
NetBackupProblemsreporttodeterminethedeviceorvolumethatcausedtheerror
Systemanderrorlogsforthesystem
3.Fordetailedtroubleshootinginformation,createanactivitylogdirectoryforbptmandretrytheoperation.Checktheresulting
activitylogfiles.
StatusCode:95Top
Message:requestedmediaidnotfoundinNBmediadatabaseand/orMMvolumedatabase
Explanation:AnoperationwasrequestedonamediaIDforwhichNetBackupdoesnothavearecord.Anexampleofthisis
usingbpmediatosuspendorfreezeamediaIDthatdoesnotexist.
RecommendedAction:RunaNetBackupMediaListreporttodeterminethevalidmediaIDs.Then,retrythecommandwitha
validmediaID.
StatusCode:96Top
Message:unabletoallocatenewmediaforbackup,storageunithasnoneavailable
Explanation:Thetapemanager(bptm)couldnotallocateanewvolumeforbackups.Thisindicatesthatthestorageunithasno
morevolumesavailableinthevolumepoolforthisbackup.
RecommendedAction:
ChecktheNetBackupProblemsreporttodeterminethestorageunitthatisoutofmedia.
1.Ifthestorageunitisarobotandthereareemptyslots,addmorevolumes(remembertospecifythecorrectvolumepool).
Iftherearenoemptyslots,movesomemediatononroboticandthenaddnewvolumes.
Ifyouarehavingdifficultykeepingtrackofyouravailablevolumes,trytheavailable_mediascript:
OnUNIX,thisscriptisin:
/usr/openv/netbackup/bin/goodies/available_media
install_path\NetBackup\bin\goodies\available_media.cmd
ThisscriptlistsallvolumesintheMediaManagervolumeconfiguration,andaugmentsthatlistwithinformationonthevolumes
currentlyassignedtoNetBackup.
2.Ifthestorageunitandvolumepoolappeartohavemedia,verifythefollowing:
VolumeisnotFROZENorSUSPENDED.
CheckforthisconditionbyusingtheNetBackupMediaListreport.Ifthevolumeisfrozenorsuspended,usethebpmedia
commandtounfreezeorunsuspendit(ifthatisdesired).
Volumehasnotexpiredorexceededitsmaximumnumberofmounts.
VolumeDatabaseHostnameforthedeviceiscorrect.
IfyouchangetheVolumeDatabaseHostname,stopandrestarttheMediaManagerdevicedaemon,ltid,(iftheserveris
UNIX)ortheNetBackupDeviceManagerservice(iftheserverisaWindowsNTsystem).
ThecorrecthostisspecifiedforthestorageunitintheNetBackupconfiguration.
Thehostconnectionshouldbetheserver(masterorslave)thathasdrivesconnectedtoit.
TheMediaManagervolumeconfigurationhasmediainthecorrectvolumepoolandunassignedoractivemediaisavailable
attherequiredretentionlevel.
UsetheNetBackupMediaListreporttoshowtheretentionlevels,volumepools,andstatus(activeandsoon)forallvolumes.
UsetheNetBackupMediaSummaryreporttocheckforactivevolumesatthecorrectretentionlevels.
3.Insomeconfigurations,theNetBackupbptmprocessisrejectedwhenrequestingmediafromthevmdprocess(NetBackup
VolumeManagerserviceonWindowsNT)becausethatprocesscannotdeterminethenameofthehostthatismakingthe
request.
Thiscanbeduetoincorrectnetworkconfigurationinvolving:
Multiplenetworkinterfaces
/etc/resolv.confonthoseUNIXsystemsthatuseit
RunningDNSandnothavingreverseaddressingconfigured
4.Createbptmandvmdactivitylogdirectoriesandretrytheoperation.
5.Examinethebptmactivitylogtoverifythatbptmisconnectingtothecorrectsystem.Ifanerrorislogged,examinethevmd
log.
OnUNIX,thevmdlogis:
/usr/openv/volmgr/debug/daemon/log.xxxxxx
21/43
9/14/2016
OnWindowsNT,thevmdlogis:
install_path\Volmgr\debug\daemon\xxxxxx.log.
6.Ifthisisanewstorageunit,andthisisthefirstattempttouseit,stopandrestartNetBackuponthemasterserver.
Note:Thebptmactivitylogs(inverbosemode)usuallyshowtheNetBackupmediaselectionprocess.
StatusCode:97Top
Message:requestedmediaidisinuse,cannotprocessrequest
Explanation:AnoperationwasrequestedonamediaIDthatisinuse.Anexampleofthisisattemptingtosuspendorfreezea
volumewhileitisbeingusedforabackuporrestore.
RecommendedAction:Retrythecommandwhenthevolumeisnotinuse.UsetheDeviceMonitortodetermineifthevolumeis
inuse(onUNIXyoucanalsousexdevadm).
StatusCode:98Top
Message:errorrequestingmedia(tpreq)
Explanation:Thetapemanagerandopticalmanager(bptm)receivedanerrorwhenrequestingamediamountfromthe
NetBackupDeviceManagerserviceonWindowsNTortheMediaManagerdevicedaemon(ltid)onUNIX.
RecommendedAction:ChecktheNetBackupProblemsreporttodeterminethereasonforthefailure.Themostcommoncause
isthattheNetBackupDeviceManagerserviceonWindowsNTortheMediaManagerdevicedaemon(ltid)onUNIXisnot
running.Startitifnecessary.
StatusCode:99Top
Message:NDMPbackupfailure
Explanation:NoneofthepathsinyourNDMPclassfilelistwerebackedupsuccessfully.
RecommendedAction:ChecktheNetBackupAllLogEntriesreportformoreinformation.Apossiblecauseforthiserroristhat
noneofthebackuppathsexistontheNDMPhost.
101102105106Top
StatusCode:100Top
Message:systemerroroccurredwhileprocessingusercommand
Explanation:Asystemcallfailedinbparchive,bpbackup,bplist,orbprestore.
RecommendedAction:
1.Enableactivityloggingforbparchive,bpbackup,bplist,orbprestore(asappropriate)bycreatingactivitylogdirectoriesfor
them.
OnUNIX,ifanonrootuserishavingproblems,verifythatthedirectorycreatedhasmode666.Lookforandcorrectany
reportederrors.
2.Retrytheoperationandchecktheresultinglogs.
Ifthelogsdonotrevealtheproblem,usethecommandlineversionofthecommandandcorrectanyproblemsthatare
reportedonstderr.
StatusCode:101Top
Message:failedopeningmailpipe
Explanation:Theprocessthatattemptstosendmailcouldnotopenthepipetotheserver.
RecommendedAction:Verifythatmailisconfiguredontheclient.Fordetailedtroubleshootinginformation,createabpcd
activitylogdirectoryandretrytheoperation.Checktheresultingbpcdactivitylog.
StatusCode:102Top
Message:failedclosingmailpipe
Explanation:Theprocessthatsendsmailcouldnotclosethepipetotheserver.
RecommendedAction:Verifythatmailisconfiguredontheclient.Fordetailedtroubleshootinginformation,createabpcd
activitylogdirectoryandretrytheoperation.Checktheresultingbpcdactivitylog.
StatusCode:105Top
Message:filepathnameexceedsthemaximumlengthallowed
Explanation:Thepathnamebuiltbyusingthecurrentworkingdirectoryexceedsthemaximumpathlengthallowedbythe
system.
RecommendedAction:Shortenthecurrentworkingdirectorypathlength.
22/43
9/14/2016
StatusCode:106Top
Message:invalidfilepathnamefound,cannotprocessrequest
Explanation:Oneofthefilepathstobebackeduporarchivedisnotvalid.
RecommendedAction:Verifythatfullpathnamesareused(theystartwith/onUNIX),andtheyarelessthanthemaximum
pathlengthforthesystem.Also,verifythatthefilesexistandthepermissionsallowNetBackuptoaccessthem.
111112Top
StatusCode:110Top
Message:/usr/openv/netbackup/bp.confnotfound
Explanation:OnWindowsNT,NetBackupcouldnotreadtheregistryentriesthatwerecreatedduringinstallation.OnUNIX,
/usr/openv/netbackup/bp.conffiledoesnotexist.
RecommendedAction:ReinstallNetBackupsoftwareontheclientorcreatethe/usr/openv/netbackup/bp.conffilewithatleast
thefollowinglines:
SERVER=server_name
CLIENT_NAME=client_name
StatusCode:111Top
Message:SERVERwasnotspecifiedin/usr/openv/netbackup/bp.conf
Explanation:OnUNIX,theSERVER=server_namelineismissinginthebp.conffile.OnWindowsNT,theserverlistcontains
noentries.RecommendedAction:
OnaUNIXclient,addthefollowinglinetothetopofthe/usr/openv/netbackup/bp.conffile:
SERVER=server_name
OnaMicrosoftWindowsornontargetNetWareclient,addtheservernameontheServerstabintheNetBackupConfiguration
dialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceontheclientandclickConfigureonthe
Actionsmenu(alsosee"UsingtheConfigureNetBackupWindow"onpage57).
OnanOS/2orNetWaretargetclient,addtheservernametothebp.inifile.
OnaMacintoshclient,addtheSERVER=server_namelinetothebp.conffileintheNetBackupfolderinthePreferences
folder.
StatusCode:112Top
Message:nofilesspecifiedinthefilelist
Explanation:Arestorewasrequestedwithnofilesinthefilelist.
RecommendedAction:Specifyatleastonefiletoberestored.
121122123124125126127Top
StatusCode:120Top
Message:cannotfindconfigurationdatabaserecordforrequestedNBdatabasebackup
Explanation:TheprogramthatbacksuptheNetBackupinternaldatabases(calledcatalogsonWindowsNT)couldnotfindthe
attributesthatindicatewhichmediaIDstouseorpathstobackup.Thiserrorshouldnotoccurundernormalcircumstances.
RecommendedAction:
2.Fordetailedtroubleshootinginformation,createadminandbpdbmactivitylogdirectoriesandretrytheoperation.Checkthe
resultingactivitylogs.
3.Contactcustomersupportandsendappropriateproblemandactivitylogsectionsdetailingtheerror.
StatusCode:121Top
Message:nomediaisdefinedfortherequestedNBdatabasebackup
Explanation:NetBackupattemptedtobackupitsinternaldatabases(calledcatalogsonWindowsNT)andtherewerenomedia
IDsdefinedinthedatabasebackupconfiguration(calledcatalogbackuponWindowsNT).
RecommendedAction:AddthemediaIDstotheNetBackupdatabasebackupconfiguration.VerifythatthemediaIDsarein
theNetBackupvolumepool.
StatusCode:122Top
Message:specifieddevicepathdoesnotexist
Explanation:TheNetBackupinternaldatabases(calledcatalogsonWindowsNT)werebackedupbyusingthebpbackupdb
commandlineandspecifyingarawdevicefilethatdoesnotexist.
RecommendedAction:Retrythecommandusingavaliddevicefilename.
23/43
9/14/2016
StatusCode:123Top
Message:specifieddiskpathisnotadirectory
Explanation:NetBackupattemptedtobackupitsinternaldatabases(calledcatalogsonWindowsNT)andthebackup
attributesweresettodumptoadisk.However,thediskfilepathalreadyexistsandisnotadirectory.
RecommendedAction:Specifyadifferentdiskpathforthedatabasebackupordeletethefilethatalreadyexists.
StatusCode:124Top
Message:NBdatabasebackupfailed,apathwasnotfoundorisinaccessible
Explanation:Oneormoreofthepathsspecifiedinthedatabasebackupconfigurationcouldnotbebackedup(thedatabases
arecalledcatalogsonWindowsNT).
RecommendedAction:
1.ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.Somepossiblecausesare:
Thepathdoesnotexist.
OnaUNIXsystem,thereisasymboliclinkinoneofthepaths.
2.Afterdeterminingwhichpathcouldnotbeaccessed,correctthepathnamesinthedatabasebackupconfiguration.
StatusCode:125Top
Message:anotherNBdatabasebackupisalreadyinprogress
Explanation:OnlyoneNetBackupdatabasebackupmaybeactiveatanygiventime.
RecommendedAction:None.
StatusCode:126Top
Message:NBdatabasebackupheaderistoolarge,toomanypathsspecified
Explanation:ToomanypathswerespecifiedintheNetBackupdatabasebackupconfigurationtofitinafixedsizemedia
header.Thiserrorshouldnotoccurundernormalcircumstances.
RecommendedAction:Deletesomeofthepathsfromthedatabasebackupconfiguration.
StatusCode:127Top
Message:specifiedmediaorpathdoesnothaveavalidNBdatabasebackupheader
Explanation:ThebprecovercommandwasissuedandthemediaIDspecifieddoesnothavevaliddatabasebackupdata.
RecommendedAction:ValidatethatthecorrectmediaIDisbeingused.
131133135Top
StatusCode:130Top
Message:systemerroroccurred
Explanation:Anerroroccurredthatpreventstheproductfromoperatinginaconsistentfashion.Thiserrorisusuallyrelatedtoa
systemcall.
RecommendedAction:
2.Checkthesystemlogforreportedproblems.
3.Fordetailedtroubleshootinginformation,createbpdbm,bpsched,bptm,andbprdactivitylogdirectoriesonthe
masterserverandretrytheoperation.Checktheresultingactivitylogs.
StatusCode:131Top
Message:clientisnotvalidatedtousetheserver
Explanation:Theclientname,asdeterminedfromtheconnectiontotheserver,didnotmatchanyclientnameinthe
NetBackupconfigurationandtherewasnoaltnamesconfigurationforthisclientonthemasterserver.Aclientandserverthat
havemultiplenetworkconnectionscanencounterthisproblemifthenamebywhichtheclientisconfiguredisnottheoneby
whichitsroutingtablesdirectconnectionstotheserver.
RecommendedAction:
1.ExaminetheNetBackupProblemsreport.
2.Createanactivitylogdirectoryforbprdandretrytheoperation.Checktheresultingactivitylogtodeterminetheconnection
andclientnames.
Dependingontherequesttype(restore,backup,andsoon.),youmayneedorwantto:
Changetheclient'sconfiguredname.
Modifytheroutingtablesontheclient.
Onthemasterserver,setupanaltnamesdirectoryandfileforthisclient(seetheNetBackupSystemAdministrator'sGuide
UNIX).
or
24/43
9/14/2016
OnaUNIXmasterserver,createasoftlinkintheNetBackupimagedatabase.
3.Review"VerifyingHostNamesandServicesEntries"onpage31.
StatusCode:133Top
Message:invalidrequest
Explanation:Oneoftwoexplanationsexist.
Arequestwasmadethatisunrecognized.ThisusuallyresultsfromdifferentversionsofNetBackupsoftwarebeingused
together.
Ifaclientreceivesthiserrorinresponsetoalistorrestorerequest,itmeansthattheDISALLOW_CLIENT_LIST_RESTORE
orDISALLOW_CLIENT_RESTOREoptionexistsinthebp.conffileonaUNIXNetBackupserverorregistryonaWindowsNT
NetBackupserver.TheseoptionsdenylistandrestorerequestsfromallNetBackupclients.
RecommendedAction:
1.Ifyoususpectthatthesoftwareversionsaretheproblem,verifythatallNetBackupsoftwareisatthesameversionlevel.
OnWindowsNTNetBackupservers,checktheinstall_path\netbackup\version.txtfileortheAboutNetBackupcommandon
theHelpmenu.
OnNetWaretargetclients,checktheVersionentryinthebp.inifile.Iftheclientsoftwareisearlierthan3.0,verifythatthe
clientisinaStandardtypeclass.
2.Iftheserverisdenyinglistandrestorerequests,removetheDISALLOW_CLIENT_LIST_RESTOREand
DISALLOW_CLIENT_RESTOREoptionsfromthebp.conffileonaUNIXNetBackupserverorregistryonaWindowsNT
NetBackupserver.Then,stopandrestarttheNetBackuprequestdaemon(UNIX)orNetBackupRequestManagerservice
(WindowsNT).
3.Fordetailedtroubleshootinginformation,createbpdbm,bprd,andadminactivitylogdirectories.Then,retrytheoperation
andchecktheresultingactivitylogs.
StatusCode:135Top
Message:clientisnotvalidatedtoperformtherequestedoperation
Explanation:Thisisusuallycausedbyarequesttorestorefilestoaclientotherthantheonethatmadetherequestandthe
requestdidnotcomefromtherootuser(administratoronWindowsNT)onaNetBackupserver.
RecommendedAction:Retrytheoperationasarootuser(administratoronWindowsNT)onthemasterserver.Alsoseestatus
code131.
141142143144145146147148Top
StatusCode:140Top
Message:useridwasnotsuperuser
Explanation:Theprocesswasstartedbyauserorprocessthatdidnothaverootprivileges(onUNIX)oradministrator
privileges(onWindowsNT).
RecommendedAction:Ifdesired,givetheuserorprocessadministratorprivileges(onWindowsNT)orrootprivileges(on
UNIX)andretrytheoperation.
StatusCode:141Top
Message:filepathspecifiedisnotabsolute
Explanation:Thefilespecificationmustbeanabsolutepath.
RecommendedAction:Correctthefilespecificationandretrythecommand.
StatusCode:142Top
Message:filedoesnotexist
Explanation:Thiscodeisreservedforfutureuse.
StatusCode:143Top
Message:invalidcommandprotocol
Explanation:AnillformedrequestwasmadetotheNetBackuprequestdaemon(UNIX)orRequestManagerservice(Windows
NT).Thiscanbeduetomismatchedversionsoftheproduct,corruptednetworkcommunication,ortoanonNetBackup
processsendingdataacrosstheportforthedaemonorservice.
RecommendedAction:ExaminetheNetBackuperrorlogstodeterminethesystemthatwasthesourceofthedataandonthat
systemdeterminetheprocessthatinitiatedtherequest.IfitwasaNetBackupprocess,verifythattheprocessorcommandis
25/43
9/14/2016
compatiblewiththeversionofsoftwareontheserver.
StatusCode:144Top
Message:invalidcommandusage
Explanation:ThisstatuscodeisduetoaNetBackupprocessbeingstartedwithimproperoptionsoranincompatibilityinthe
product.
RecommendedAction:EithercorrectthecommandorverifythatallNetBackupbinariesareatthesameversionlevel.
StatusCode:145Top
Message:daemonisalreadyrunning
Explanation:Thereisanothercopyoftheprocessexecuting.
RecommendedAction:Terminatethecurrentcopyoftheprocessandthenrestarttheprocess.
StatusCode:146Top
Message:cannotgetaboundsocket
Explanation:Thedaemon(serviceonWindowsNT)couldnotbindtoitssocket.AsystemcallfailedwhenthedaemonUNIX)
orservice(WindowsNT)attemptedtobindtoitsconfiguredportnumber.Thisisusuallycausedbyanotherprocesshaving
acquiredtheportbeforethedaemonorservicestarted.
RecommendedAction:
1.ExaminetheNetBackupProblemsandAllLogEntriesreports.
2.Createbprdandbpdbmactivitylogdirectoriesandretrytheoperation.
Checktheresultinglogstoseethesystemerrormessageresultingfromtheattempt.
Ifanotherprocesshastheport,useothersystemcommandstodeterminetheprocess.Basedonthisresearch,eitherchange
theportnumberinyourservicesfileormaporterminatetheprocessthathasacquiredtheport.
OnUNIX,anotherpossiblecauseforthiserroristerminatingbprdorbpdbmwiththekillcommand.Therecommendedwayto
stopbprdiswiththeterminateoptionsin,xbpadm.Tostopbpdbm,usethe/usr/openv/netbackup/bin/bpdbmterminate
command.Usingthekillcommandtostoptheseprocessescanleavethemunabletobindtotheirassignedportsthenexttime
theyarestarted.
Toidentifyabprdorbpdbmproblem,lookforlinessimilartothefollowingintheactivitylogfortherespectiveprocess:
<16>getsockbound:bind()failed,Addressalreadyinuse(114)
<32>listen_loop:cannotgetboundsocket.errno=114
<4>terminate:terminationbegun...errorcode=146
Similarentriescanappearinthereports.
3.Iftheproblempersistslongerthantenminutes,itispossiblethatitwillbenecessarytoreboottheserver.
StatusCode:147Top
Message:requiredorspecifiedcopywasnotfound
Explanation:Therequestedcopynumberofabackuporarchiveimagecannotbefound.
RecommendedAction:Correcttherequesttospecifyacopynumberthatdoesexist.
StatusCode:148Top
Message:daemonforkfailed
Explanation:ANetBackupservicecouldnotcreateachildprocessduetoanerrorreceivedfromthesystem.Thisisprobably
anintermittenterrorbasedontheavailabilityofresourcesonthesystem.
RecommendedAction:
1.Restarttheserviceatalatertimeandinvestigatesystemproblemsthatlimitthenumberofprocesses.
2.ChecktheEventViewerApplicationandSystemlogs(WindowsNT).
151152153154158159Top
StatusCode:150Top
Message:terminationrequestedbyadministrator
Explanation:Theprocessisterminating(orhasterminated)asadirectresultofarequestfromanauthorizeduserorprocess.
StatusCode:151Top
Message:BackupExecoperationfailed
26/43
9/14/2016
Explanation:TheGlobalDataManagerconsolehasreportedthataBackupExecjob(backup,archive,orrestore)didnot
completenormally.
RecommendedAction:ConsulttheBackupExecjobhistoryontheBackupExecserverfordetails.
StatusCode:152Top
Message:requiredvaluenotset
Explanation:Anincompleterequestwasmadetothebpdbmprocess(NetBackupDatabaseManagerserviceonWindowsNT).
Thisusuallyoccursbecausedifferentversionsofsoftwarearebeingusedtogether.
RecommendedAction:
1.Verifythatallsoftwareisatthesameversionlevel.
2.Fordetailedtroubleshootinginformation,createbpdbmandadminactivitylogdirectoriesandretrytheoperation.Checkthe
StatusCode:153Top
Message:serverisnotthemasterserver
Explanation:Thisstatuscodeisreservedforfutureuse.
StatusCode:154Top
Message:storageunitcharacteristicsmismatchedtorequest
Explanation:Abackupwasattemptedandthestorageunitselectedforusehadcharacteristicsthatwerenotcompatiblewith
thebackuptype.
RecommendedAction:Verifythatthecharacteristicsofthestorageunitinvolvedareappropriateforthebackupattempted:
ForanNDMPclasstype,verifythatastorageunitoftypeNDMPisdefinedandtheNDMPhostvaluematchesthehostname
oftheclient.Forexample,iftheNDMPclassspecifiestoasterastheclient,theconfigurationforthestorageunitmustspecify
toasterastheNDMPhost.
ForaclasstypeotherthanNDMP,verifythattheclassspecifiesaMediaManagerorDisktypestorageunit.
StatusCode:158Top
Message:failedaccessingdaemonlockfile
Explanation:Theprocesscouldnotlockitslockfilebecauseanerrorwasreceivedfromasystemcall.Thislockfile
synchronizesprocessactivities(forexample,preventingmorethanonedaemonfromexecutingatatime).
RecommendedAction:
1.ExaminetheNetBackuperrorlogtodeterminewhythesystemcallfailedandcorrecttheproblem.Itcouldbeapermission
problem.
2.Iftheerrorlogdoesnotshowtheerror,createanactivitylogdirectoryforbprd,bpdbm,orbpsched(dependingonwhich
processencounteredtheerror)andretrytheoperation.Examinetheresultingactivitylog.
StatusCode:159Top
Message:licensedusehasbeenexceeded
Explanation:Thisstatuscodeisreservedforfutureuse.
164165166167168169Top
StatusCode:160Top
Message:authenticationfailed
Explanation:Aproblemwasencounteredwhentwosystemswereattemptingtoauthenticateoneanother.
RecommendedAction:SeetheNetBackupSystemadministrator'sGuideUNIXformoreinformationonthefilesand
commandsmentionedhere.
1.Ensurethattheauthenticationlibrariesexist:
WindowsNT,98,95:
install_path\NetBackup\lib\libvopie.dll
install_path\NetBackup\lib\libnoauth.dll
UNIX(exceptHPUX):
/usr/openv/lib/libvopie.so
/usr/openv/lib/libnoauth.so
UNIX(HPUXonly):
/usr/openv/lib/libvopie.sl
/usr/openv/lib/libnoauth.sl
Macintosh:
27/43
9/14/2016
:SystemFolder:Extensions:libvopie.dll
:SystemFolder:Extensions:libnoauth.dll
2.Checkthemethods_allow.txtfilesonthesystemsthatarehavingproblemstoensurethatauthenticationisenabled.Thefiles
areinthefollowinglocations:
WindowsNT,98,95:
install_path\NetBackup\var\auth
UNIX:
/usr/openv/var/auth
Macintosh:
:SystemFolder:Preferences:NetBackup:var:auth
3.Onthesystemsthatarehavingtheauthenticationproblem,removetheremotehostthatisnotbeingauthenticatedfromthe
methods_allow.txtfile.
Forexample,ifhostaandhostbarehavingtheproblem,removehostafromthefileonhostbandviceversa.
Retrytheoperation.
Iftheproblemstillexists,itindicatesconnectionproblemsnotrelatedtoauthentication.
Ifconnectionsarenowsuccessful,proceedtothenextstep.
4.Executebpauthsyncvopieonthemasterservertoresynchronizethekeyfilesonthesystems.
OnWindowsNT:
install_path\NetBackup\bin\admincmd\bpauthsyncvopieservers
clients
OnUNIX:
/usr/openv/netbackup/bin/admincmd/bpauthsyncvopieservers
clients
5.Addbackthenamesremovedinstep3andretrytheoperation.
6.CreateactivitylogdirectoriesfortheprocessesinvolvedinauthenticationbetweenNetBackupsystems.Theseinclude:
Ontheserver,createactivitylogdirectoriesforbprd,bpdbm,bpcd.
Ontheclient,createactivitylogdirectoriesforbpbackup,bprestore,
bpbkar(WindowsNTonly).
Retrytheoperationandcheckthelogs.
StatusCode:164Top
Message:unabletomountmediabecauseitisinaDOWNdriveormisplaced
Explanation:ArestorewasattemptedandthevolumerequiredfortherestorewasinaDOWNdriveinarobot.Or,theslotthat
shouldcontainthevolumeisempty.
RecommendedAction:
IfvolumeisinaDOWNdrive,removeitandplaceitinitsdesignatedslot.Then,retrytherestore.
Ifthevolumeisinthewrongslot,usearobotinventoryoptiontoreconcilethecontentsoftherobotwiththeMediaManager
volumeconfiguration.
StatusCode:165Top
Message:NBimagedatabasecontainsnoimagefragmentsforrequestedbackupid/copynumber
Explanation:ArestorewasattemptedandNetBackuphasnorecordoffragmentsassociatedwiththebackupIDthathasthe
files.
RecommendedAction:ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.Fordetailed
troubleshootinginformation,createanactivitylogdirectoryforeitherbpdmorbptm(whicheverapplies)andretrytheoperation.
Checktheresultingactivitylog.
StatusCode:166Top
Message:backupsarenotallowedtospanmedia
Explanation:Anendofmedia(EOM)wasencounteredwhilethebackupimagewasbeingwritten.Thebackupwasterminated
becausetheNetBackupDISALLOW_BACKUPS_SPANNING_MEDIAoptionwaspresentinbp.confonUNIXortheregistryon
WindowsNT.Thebackupwillberetriedautomaticallywithadifferentvolumeifthisisallowedbythebackuptriesattributein
theNetBackupglobalattributeconfiguration.
StatusCode:167Top
Message:cannotfindrequestedvolumepoolinMediaManagervolumedatabase
Explanation:Abackuptoanonroboticdrivewasattemptedandthetapemanager(bptm)couldnotfindoraddthespecified
volumepool.
RecommendedAction:VerifytheMediaManagervolumeconfiguration.ChecktheNetBackupProblemsreportformore
informationabouttheerror.Fordetailedtroubleshootinginformation,createabptmactivitylogdirectoryandretrythe
operation.Checktheresultingactivitylog.
StatusCode:168Top
28/43
9/14/2016
Message:cannotoverwritemedia,dataonitisprotected
Explanation:Adatabasebackupwasattemptedtoavolumethatcouldnotbeoverwrittenbecauseitcontainsdatathat
NetBackup,bydefault,doesnotoverwrite(tar,cpio,ANSI,andsoon).
RecommendedAction:ReplacethevolumewithanewoneorsettheNetBackupALLOW_MEDIA_OVERWRITEoptiontothe
appropriatevalue.
StatusCode:169Top
Message:mediaidiseitherexpiredorwillexceedmaximummounts
Explanation:Abackupordatabasebackupwasattemptedandthevolumeselectedforusehasreacheditsmaximumnumber
ofmountsasspecifiedintheMediaManagervolumeconfiguration.Foraregularbackup,thevolumeisautomaticallysettothe
SUSPENDEDstateandnotusedforfurtherbackups.ForaNetBackupdatabasebackup,theoperationterminatesabnormally.
RecommendedAction:Ifthevolumewassuspended,waituntilitexpiresandthenreplaceit.ForNetBackupdatabase
backups,replacethemedia.
171172173174175176177178179Top
StatusCode:171Top
Message:mediaidmustbe6orlesscharacters
Explanation:Anoperation,suchasusingbpmediatosuspendorfreezeamediaIDwasattemptedandthemediaIDspecified
waslongerthansixalphanumericcharacters.
RecommendedAction:RetrythecommandwithavalidmediaID.
StatusCode:172Top
Message:cannotreadmediaheader,maynotbeNetBackupmediaoriscorrupted
Explanation:Whenloadingavolumeforabackuporrestore,thetapemanager(bptm),didnotfindtheexpectedtapeheader.
ThiscanmeanthatavolumeinaroboticdeviceisnotintheslotnumbershownintheMediaManagervolumeconfigurationor
thatareaderror(I/Oerror)occurred.
RecommendedAction:
1.Ifthevolumeisinarobotthatsupportsbarcodes,verifytherobotcontentsbyusingaMediaManagerrobotinventoryoption.
2.Ifthevolumewasmountedonanonroboticdrive,verifythatthecorrectvolumewasmountedandassigned.
3.ChecktheNetBackupProblemsreport.Ifafatalreaderroroccurred,attempttheoperationagainusinganotherdrive,if
possible.
StatusCode:173Top
Message:cannotreadbackupheader,mediamaybecorrupted
Explanation:Whensearchingforabackupimagetorestore,thetapemanager(bptm)couldnotfindthecorrectbackupIDat
thepositiononthemediawhereNetBackupexpectedittobe.Thiscanindicateadrivehardwareproblem.
RecommendedAction:
1.ChecktheNetBackupProblemsreportforcluesastowhatcausedtheerror.
2.Trytherestoreonanotherdriveifpossible.
activitylog.
StatusCode:174Top
Message:mediamanagersystemerroroccurred
Explanation:Anabnormalconditionoccurredcausingatapemanager(bptm)ordiskmanager(bpdm)failure.Thisshouldnot
occurundernormalcircumstances.
Note:IfthisoccursonaSequentplatformandyouareattemptingtobackupmorethanfourgigabytesofdata,saveallyour
logsandcallVERITAStechnicalsupport.Forotherplatformsperformtherecommendedactionsdescribedbelow.
RecommendedAction:
1.ChecktheNetBackupProblemsreporttoseeifitshowsthecauseoftheproblem.IfyouseeaProblemsreportmessage
similarto"attemptingtowrite32767bytes,notamultipleof1024"savealllogsandcallVERITAScustomersupport.
2.OnUNIX,ifthisoccursduringarestore,itmaybethatthetapedriveisincorrectlyconfiguredtowriteinfixedlengthmode
whenitshouldwriteinvariablelengthmode.
Verifyyourdrive'sconfiguration,comparingittowhatisrecommendedintheMediaManagerDeviceConfigurationGuide(also
seeStep7ofthisprocedure).
Ifyourconfigurationincorrectlyspecifiesfixedlengthmode,changetheconfigurationtospecifyvariablelengthmodeand
suspendmediathatwerewrittenonthatdevice.Theimageswrittentothosemediamayberestorable(thisisplatform
dependent),butsinglefilerestoresarealmostguaranteedtofail.
3.Ifyouseetheproblemwithonlyoneclient,verifythattheclientbinariesarecorrect,especiallythoseforbpcd.
4.Canyoureadorwriteanyotherimagesonthismedia?
Ifso,thecheckthefollowingreportsforclues:
ImagesonMediareport
29/43
9/14/2016
MediaContentsreport
5.Verifythefollowing:
ThemediabyusingtheNetBackupimageverifyoption.
Thatyouareusingthecorrectmediatypeforthedevice.
6.Checkthesystemorconsolelogforerrors(onUNIX)ortheEventViewerApplicationlog(onWindowsNT).
7.Fordetaileddebuginformation,createanactivitylogdirectoryforeitherbptmorbpdm(whicheverapplies)andretrythe
Ifthebptmactivitylogshowsanerrorsimilarto
00:58:54[2304]<16>write_data:writeof32768bytesindicatedonly29696byteswerewritten,errno=0
itmaybethatthetapedriveisconfiguredtowriteinfixedlengthmoderatherthanvariablelengthmode,andtheimagebeing
writtenencounteredtheendofmedia.
TakethecorrectiveactionsuggestedinStep2.
StatusCode:175Top
Message:notallrequestedfileswererestored
Explanation:Whenrestoringfilesfromanimage,thebptmorbpdmprocessdetectedafatalerrorconditionandterminatedthe
restorebeforeitcompleted.Thisshouldnotoccurundernormalcircumstances.
RecommendedAction:
1.ChecktheNetBackupProblemsreportandtheprogresslogontheclientforadditionalinformationabouttheerror
2.Fordetailedtroubleshootinginformation,createanactivitylogdirectoryforeitherbptmorbpdm(whicheverapplies)andretry
theoperation.Checktheresultingactivitylog.
StatusCode:176Top
Message:cannotperformspecifiedmediaimportoperation
Explanation:Thetapemanager(bptm)detectedanerrorconditionwhenattemptingtoimportaspecificbackupimage.
Possiblereasonsforthisare:
MediaIDisalreadyactiveintheNetBackupmediadatabaseonthisserver
MediaIDisnotintheMediaManagervolumeconfiguration
Fataltapemanager(bptm)erroroccurred
TotalimagewasnotobtainedfromPhase1ofimport
RecommendedAction:
1.ChecktheNetBackupProblemsreporttofindtheexactcauseofthefailure.
2.Trythefollowing:
IfthemediaIDisalreadyactive,duplicateallimagesontheoriginalmediaIDtoanothervolume.Then,manuallyexpirethe
originalmediaandredotheimport.
IfthemediaIDisnotpresentintheMediaManagervolumeconfiguration,addit.
Ifafatalbptmerroroccurred,verifythattheMediaManagervolumedaemon(vmd)isactiveonUNIXortheNetBackup
VolumeManagerserviceisactiveonWindowsNT.
Iftheentireimageisnotpresent,performimportphase1onthemediaIDsthathavetheremainderoftheimage.
StatusCode:177Top
Message:couldnotdeassignmediaduetoMediaManagererror
Explanation:Thetapemanager(bptm)couldnotsuccessfullydeassignamediaID.
RecommendedAction:
1.ChecktheNetBackupProblemsreportforthecauseoftheproblem.
2.VerifythattheMediaManagervolumedaemon(vmd)isactiveonUNIXortheNetBackupVolumeManagerserviceisactive
onWindowsNT.
activitylog.
StatusCode:178Top
Message:mediaidisnotinNetBackupvolumepool
Explanation:NetBackupattemptedabackupofitsdatabasesandthemediaIDspecifiedforthedatabasebackupwasnotin
theNetBackupvolumepool.VolumesfordatabasebackupsmustbeintheNetBackupvolumepool.
RecommendedAction:ChecktheMediaManagervolumeconfigurationtoverifythatthemediaIDsarepresentandinthe
NetBackupvolumepool.
StatusCode:179Top
Message:densityisincorrectforthemediaid
Explanation:Anoperationsuchas"listcontents"wasattemptedonaninvalidmediaID,suchasacleaningtape.Another
possibilityisthatamediaIDintheNetBackupdatabasebackupconfigurationdoesnotmatchthemediatypeenteredinthe
MediaManagervolumeconfiguration.
RecommendedAction:CheckthevolumeconfigurationandtheNetBackupdatabasebackupconfigurationandcorrectany
problemsfound.
30/43
9/14/2016
181182183184185186189Top
StatusCode:180Top
Message:tarwassuccessful
Explanation:tarreturnedasuccessfulexitstatus.
StatusCode:181Top
Message:tarreceivedaninvalidargument
Explanation:Oneoftheparameterspassedtotarwasnotvalid.RecommendedAction:
OnaUNIXclient:
Ensurethatthetarcommandin/usr/openv/netbackup/binistheoneprovidedbyNetBackup.Ifyouareindoubt,reinstallit.
Check/usr/openv/netbackup/bin/versionontheclienttoverifythattheclientisrunningthecorrectlevelsoftware.Ifthe
softwareisnotatthecorrectlevel,updatethesoftwareperthedirectionsintheNetBackupreleasenotes.
OnaWindowsNTclient,createataractivitylogdirectory,retrytheoperation,andcheckthelog.
OnaMacintoshclient,checktheversionfilethatisinthebinfolderintheNetBackupfolderinthePreferencesfolder.Ifthe
softwareisnotatthecorrectlevel,installthecorrectsoftwareasexplainedintheinstallationguide.
StatusCode:182Top
Message:tarreceivedaninvalidfilename
Explanation:tarcannotwritetothefilethatisspecifiedwiththefparameter.
RecommendedAction:
1.Createabpcdactivitylogdirectoryontheclient(onaMacintoshNetBackupcreatesthelogautomatically).
2.OnaWindowsNTclient,createataractivitylogdirectory.
3.Increasethelogginglevelontheclient:
OnaUNIXclient,addtheVERBOSEoptiontothe/usr/openv/netbackup/bp.conffile.
OnPCclients,increasethedebugorloglevelasexplainedintheactivitylogtopicsinChapter3,"UsingtheLogsand
Reports."
4.Reruntheoperation,checktheresultingactivitylogsfortheparameterspassedtotarandcallcustomersupport.
StatusCode:183Top
Message:tarreceivedaninvalidarchive
Explanation:Thedatapassedtotarwascorrupt.
RecommendedAction:
IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/taractivitylogdirectoryontheclientandrerunthe
operation.
a.Checkthetaractivitylogfileforerrormessagesthatexplaintheproblem.
b.Reboottheclienttoseeifthisclearstheproblem.
c.Whenyouarethroughinvestigatingtheproblem,deletethe/usr/openv/netbackup/logs/tardirectoryontheclient.
IftheproblemiswithaMicrosoftWindows,NetWare,orMacintoshclient:
a.Createabpcdactivitylogdirectoryontheclient(onaMacintoshNetBackupcreatesthelogautomatically).
b.OnaWindowsNTclient,createataractivitylogdirectory.
c.IncreasethedebugorloglevelasexplainedintheactivitylogtopicsinChapter3,"UsingtheLogsandReports."
d.Reruntheoperationandchecktheresultingactivitylogs.
e.Reboottheclienttoseeifitclearstheproblem.
StatusCode:184Top
Message:tarhadanunexpectederror
Explanation:Asystemerroroccurredintar.
RecommendedAction:
IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/taractivitylogdirectoryontheclientandrerunthe
operation.Createa/usr/openv/netbackup/logs/tardirectoryontheclientandreruntheoperation.
a.Checkthetaractivitylogfileforerrormessagesthatexplaintheproblem.
b.Reboottheclienttoseeifthisclearstheproblem.
c.Whenyouarethroughinvestigatingtheproblem,deletethe/usr/openv/netbackup/logs/tardirectoryontheclient.
IftheproblemiswithaMicrosoftWindows,NetWare,orMacintoshclient:
a.Createabpcdactivitylogdirectoryontheclient(onaMacintoshNetBackupcreatesthelogautomatically).
c.OnaWindowsNTclient,createataractivitylogdirectory.
d.Retrytheoperationandchecktheresultingactivitylogs.
e.Reboottheclienttoseeifitclearstheproblem.
31/43
9/14/2016
StatusCode:185Top
Message:tardidnotfindallthefilestoberestored
Explanation:Therewerefilesinthetarfilelistthatwerenotintheimage.
RecommendedAction:
IftheproblemiswithaUNIXclient:
a.Enablebpcdactivityloggingbycreatingthe/usr/openv/netbackup/logs/bpcddirectoryontheclient.
b.Reruntheoperation,checktheresultingbpcdlogfilefortheparameterspassedtotar,andcallcustomersupport.
IftheproblemiswithaMicrosoftWindows,NetWare,orMacintoshclient:a.Createabpcdactivitylogdirectoryontheclient
(onaMacintoshNetBackupcreatesthelogautomatically).
c.OnaWindowsNTclient,createataractivitylogdirectory.
d.Retrytheoperation.
e.Checktheresultingactivitylogsfortheparameterspassedtotarandcallcustomersupport.
StatusCode:186Top
Message:tarreceivednodata
Explanation:Themediamanagerdidnotsenddatatotar.
RecommendedAction:
1.Retrytheoperationandchecktheprogresslogontheclientforerrormessagesthatrevealtheproblem.
2.Verifythatthetapeisavailableandreadable.
3.VerifythatthatthedriveisinanUPstate.UsetheDeviceMonitor(onUNIXxdevadmcanalsobeused)
4.Fordetailedtroubleshootinginformation:
a.Createabptmactivitylogontheserver.
b.OnaWindowsNTclient,createataractivitylog.
c.Retrytheoperationandchecktheresultingactivitylogs.
StatusCode:189Top
Message:theserverisnotallowedtowritetotheclient'sfilesystems
Explanation:Theclientisnotallowingwritesfromtheserver.
RecommendedAction:
Performthefollowingtoperformrestoresorinstallsoftwarefromtheserver.
OnaUNIXclient,deleteDISALLOW_SERVER_FILE_WRITESfromthe/usr/openv/netbackup/bp.conffile.
OnaMicrosoftWindowsorNetWarenontargetclient,selectAllowServerDirectedRestoresontheGeneraltabinthe
NetBackupConfigurationdialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceontheclient
andclickConfigureontheActionsmenu(alsosee"UsingtheConfigureNetBackupWindow"onpage57).
OnaMacintoshclient,deleteDISALLOW_SERVER_FILE_WRITESfromthebp.conffileintheNetBackupfolderinthe
Preferencesfolder.
OnaNetWaretargetclient,setALLOW_SERVER_WRITEtoyesinthebp.inifile.
191194195196197198199Top
StatusCode:190
Message:foundnoimagesormediamatchingtheselectioncriteria
Explanation:Averify,duplicate,orimportwasattemptedandnoimagesmatchingthesearchcriteriawerefoundinthe
NetBackupdatabase.
RecommendedAction:Changethesearchcriteriaandretry.
StatusCode:191Top
Message:noimagesweresuccessfullyprocessed
Explanation:Averify,duplicate,orimportwasattemptedandfailedforallselectedimages.
RecommendedAction:ChecktheNetBackupProblemsreportforthecauseoftheerror.Toobtaindetailedtroubleshooting
information,createanadminactivitylogdirectoryandretrytheoperation.Checktheresultingactivitylog.
StatusCode:194Top
Message:themaximumnumberofjobsperclientissetto0
Explanation:TheNetBackupMaximumJobsperClientglobalattributeiscurrentlysetto0.Settingthevalueto0disables
backupsandarchives.
RecommendedAction:Toenablebackupsandarchives,changetheglobalattributevaluetothedesirednonzerosetting.
StatusCode:195Top
32/43
9/14/2016
Message:clientbackupwasnotattempted
Explanation:AbackupjobwasintheNetBackupscheduler'sworklistbutwasnotattempted.
RecommendedAction:
1.Retrythebackupeitherimmediatelywithamanualbackuporallowthenormalschedulerretries.
2.Foradditionalinformation,checktheAllLogEntriesreport.Fordetailedtroubleshootinginformation,createabpsched
activitylogdirectoryonthemasterserver.Afterthenextbackupattempt,checktheactivitylog.Someactionstoperformare:
Verifythatthevmdandltiddaemons(UNIX)ortheNetBackupVolumeManagerandNetBackupDeviceManagerservices
(WindowsNT)arerunning.
Lookforaprobleminanearlierbackupthatmadethemediaorstorageunitunavailable.
StatusCode:196Top
Message:clientbackupwasnotattemptedbecausebackupwindowclosed
Explanation:Abackuporarchiveoperationthatwasqueuedbythebackupschedulerwasnotattemptedbecausethebackup
windowwasnolongeropen.
RecommendedAction:
Ifpossible,changethescheduletoextendthebackupwindowforthisclassandschedulecombinationsoitdoesnotoccur
again.
Ifthebackupmustberun,usetheManualBackupcommandontheClassmenuintheBackupPolicyManagementwindow
toperformthebackup.Manualbackupsignorethebackupwindow.
Ifthebackupmustberun,usetheNetBackupadministrationinterfacecommandformanualbackupstoperformthebackup.
Manualbackupsignorethebackupwindow.
StatusCode:197Top
Message:thespecifiedscheduledoesnotexistinthespecifiedclass
Explanation:Auserbackuporarchiverequesthasspecifiedtheexactclassandscheduletousewhenperformingabackup.
Theclassexistsbutdoesnotcontaintheschedule.
OnMicrosoftWindowsandNetWarenontargetclients,youcanspecifyaclassorscheduleontheBackupstabin
theNetBackupConfigurationdialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestore
interfaceontheclientandclickConfigureontheActionsmenu(alsosee"UsingtheConfigureNetBackup
Window"onpage57).
OnUNIXandMacintoshclients,youcanspecifyaclassorschedulebyusingthebp.confoptions,
BPBACKUP_CLASSorBPBACKUP_SCHED.OnNetWaretargetclients,youcanspecifyaclassorschedulein
thebp.inifile.
RecommendedAction:
1.Checktheclientprogresslog(ifavailable)todeterminetheclassandschedulethatwerespecified.
2.Checktheconfigurationonthemasterservertodetermineifthescheduleisvalidfortheclass.Ifthescheduleis
notvalid,eitheraddthescheduletotheclassconfigurationorspecifyavalidscheduleontheclient.
StatusCode:198Top
Message:noactiveclassescontainschedulesoftherequestedtypeforthisclient
Explanation:Auserbackuporarchivehasbeenrequested,andthisclientisnotinaclassthathasauserbackuporarchive
schedule.
RecommendedAction:
Determineiftheclientisinanyclassthathasascheduleoftheappropriatetype(eitheruserbackuporarchive).
Iftheclientisinsuchaclass,checkthegeneralclassattributestoverifythattheclassissettoactive.
Iftheclientisnotinsuchaclass,eitheraddascheduleoftheappropriatetypetoanexistingclassthathasthisclientor
createanewclassthathasthisclientandascheduleoftheappropriatetype.
StatusCode:199Top
Message:operationnotallowedduringthistimeperiod
Explanation:Auserbackuporarchivehasbeenrequestedandthisclientisnotinaclassthathasauserbackuporarchive
schedulewithanopenbackupwindow.Thiserrorimpliesthatthereisanappropriateclassandschedulecombinationforthis
client.
RecommendedAction:Determinetheclassestowhichthisclientbelongsthatalsohaveascheduleoftheappropriatetype
(eitheruserbackuporarchive).
Ifpossible,retrytheoperationwhenthebackupwindowisopen.
Ifthebackupwindowisnotopenduringappropriatetimeperiods,adjustabackupwindowforascheduleinone
oftheclasses.
201202203204205206207208209Top
33/43
9/14/2016
StatusCode:200Top
Message:schedulerfoundnobackupsduetorun
Explanation:Whencheckingtheclassandscheduleconfiguration,theNetBackupschedulerprocess(bpsched)didnotfind
anyclientstobackup.Thiscouldbedueto:
Nobackuptimewindowsareopen(appliesonlytofullandincrementalschedules).
Classesaresettoinactive.
Theclientswererecentlybackedupandarenotdueforanotherbackup(basedonFrequencysettingfortheschedules).
Classesdonothaveanyclients.
RecommendedAction:Usually,thismessagecanbeconsideredinformationalanddoesnotindicateaproblem.However,if
yoususpectaproblem:
1.ExaminetheNetBackupAllLogEntriesreporttoseeifthereareanymessagesinadditiontooneindicatingthatthe
schedulerfoundnothingtodo.
2.Examinetheclassconfigurationforallclassesorthespecificclassinquestionanddetermineifanyofthereasons
mentionedintheExplanationsectionaboveapply.
3.Toobtaindetailedtroubleshootinginformation,createabpschedactivitylogdirectoryonthemasterserverandretrythe
StatusCode:201Top
Message:handshakingfailedwithserverbackuprestoremanager
Explanation:Aprocessonthemasterserverencounteredanerrorwhencommunicatingwiththemediaserver(eitherthe
masteroraslaveserver).Thiserrormeansthatthemasterandmediaserverprocesseswereabletoinitiatecommunication,
butencountereddifficultiesincompletingthem.Thisproblemcanoccurduringabackup,restore,ormedialistinasingleor
multipleserverconfiguration.
RecommendedAction:
1.DeterminetheactivitythatencounteredthehandshakefailurebyexaminingtheNetBackupAllLogEntriesreportforthe
appropriatetimeperiod.Ifthereareslaveservers,determineif:
Thehandshakefailurewasencounteredbetweenthemasterandaslaveserver.
or
Onlythemasterserverwasinvolved.
2.Ifnecessary,createthefollowingactivitylogdirectoriesforthefollowing:
bpcdontheNetBackupmediaserver(eithermasterorslave).
Iftheerrorwasencounteredduringabackupoperation,bpschedonthemasterserver.
Iftheerrorwasencounteredduringarestoreoperation,bprdonthemasterserver.
Iftheerrorwasencounteredduringamedialistoperation,adminintheNetBackuplogs/admindirectoryonthemasterserver.
3.Retrytheoperationandexaminetheresultingactivitylogsforinformationonwhytheerroroccurred.
StatusCode:202Top
Message:timedoutconnectingtoserverbackuprestoremanager
Explanation:Aprocessonthemasterservertimedoutwhiletryingtoinitiatecommunicationswiththemediaserver(eitherthe
masteroraslaveserver).Thisproblemcanoccurduringabackuporrestoreineitherasingleormultipleserverconfiguration.
RecommendedAction:DeterminewhichactivityencounteredtheconnectiontimeoutfailurebyexaminingtheAllLogEntries
reportfortheappropriatetimeperiod.Ifthereareslaveservers,determineifthetimeoutoccurredbetweenthemasteranda
slaveorifonlythemasterwasinvolved.
1.Verifythattheschedulespecifiesthecorrectstorageunit.
2.Executethepingcommandfromonehosttoanotherbyusingthefollowingcombinations:
Fromthemasterserver,pingthemasterandallslaveserversbyusingthehostnamesfoundinthestorageunitconfiguration.
Fromeachoftheslaveservers,pingthemasterserverbyusingthehostnamespecifiedintheNetBackupserverlist.Ona
UNIXserver,thisisthefirstSERVERentryinthebp.conffile.OnaWindowsNTserver,themasterisdesignatedasthe
CurrentserverontheServerstabintheNetBackupConfigurationdialogbox.Todisplaythisdialogbox,starttheBackup,
Archive,andRestoreinterfaceontheserverandclickConfigureontheActionsmenu(alsosee"UsingtheConfigure
NetBackupWindow"onpage57).
3.Verifythatthemasterservercancommunicatewithbpcdonthehostthathasthestorageunit.
Aftereachbackup,theschedulerchecksthestorageunittoseehowmanydrivesareavailable(incasethebackupcauseda
drivetobeautomaticallydowned).Ifbpschedcannotcommunicatewithbpcd,itsetsthenumberofavailabledrivesinthat
storageunitto0andfurtherbackupstothatstorageunitfail.
Theavailabledrivesremainat0untiltheschedulerisinitializedagain.Therefore,evenifbpcdseemstobeoperatingcorrectly
now,checkthebpschedandbpcdactivitylogs(seebelow)forrecordsofanearlierfailure.
4.See"TestingSlaveServerandClients"onpage18and"ResolvingNetworkCommunicationProblems"onpage21.
5.Ifnecessary,createactivitylogdirectoriesforthefollowingprocessesandretrytheoperation.Then,checktheresulting
activitylogsonthemasterserver:
Iftheerroroccurredduringabackupoperation,checkthebpschedactivitylogs.Also,checkthebpcdactivitylogs.
Iftheerroroccurredduringarestoreoperation,checkthebprdactivitylogs.
StatusCode:203Top
Message:serverbackuprestoremanager'snetworkisunreachable
34/43
9/14/2016
Explanation:Aprocessonthemasterservercouldnotconnecttoaparticularhostonthenetworkwhentryingtoinitiate
communicationwiththemediaserverforaparticularoperation.Thisproblemcanoccurduringabackuporrestoreineithera
singleormultipleserverconfiguration.
RecommendedAction:DeterminewhichactivityencounteredthenetworkunreachablefailurebyexaminingtheAllLogEntries
reportfortheappropriatetimeframe.IfthereismorethanoneNetBackupserver(thatis,oneormoreslaveservers)determine
ifthenetworkunreachablefailurewasencounteredbetweenthemasterandaslaveserverorifonlythemasterserverwas
involved.Executethepingcommandfromonehosttoanotherbyusingthefollowingcombinations:
1.Fromthemasterserver,pingthemasterandallslaveserversbyusingthehostnamesinthestorageunitconfiguration.
2.Fromeachoftheslaveservers,pingthemasterserverhostbyusingthehostnamespecifiedintheNetBackupserverlist.
OnaUNIXserver,thisisthefirstSERVERentryinthebp.conffile.OnaWindowsNTserver,themasterisdesignatedasthe
CurrentserverontheServerstabintheNetBackupConfigurationdialogbox.Todisplaythisdialogbox,starttheBackup,
Archive,andRestoreinterfaceandclickConfigureontheActionsmenu(alsosee"UsingtheConfigureNetBackupWindow"
onpage57).
3.See"TestingSlaveServerandClients"onpage18and"ResolvingNetworkCommunicationProblems"onpage21.
4.Ifnecessary,createactivitylogdirectoriesforthefollowingprocessesandretrytheoperation.Then,checktheresulting
activitylogsonthemasterserver:
Iftheerroroccurredduringabackup,checkthebpschedactivitylogs.
Iftheerroroccurredduringarestore,checkthebprdactivitylogs.
StatusCode:204Top
Message:connectionrefusedbyserverbackuprestoremanager
Explanation:Themediaserverrefusedaconnectionontheportnumberforbpcd.Thiserrorcanbeencounteredduringa
backuporrestore.
RecommendedAction:Executethepingcommandfromonehosttoanotherbyusingthefollowingcombinations:Note:Also,
see"ResolvingNetworkCommunicationProblems"onpage21.
1.Fromthemasterserver,pingthemasterandallslaveserversbyusingthehostnamesinthestorageunit
configuration.
2.Fromeachoftheslaveservers,pingthemasterserverbyusingthenamespecifiedintheNetBackupserverlist.
OnaUNIXserver,thisisthefirstSERVERentryinthebp.conffile.OnaWindowsNTserver,themasteris
designatedastheCurrentserverontheServerstabintheNetBackupConfigurationdialogbox.Todisplaythis
dialogbox,starttheBackup,Archive,andRestoreinterfaceontheserverandclickConfigureontheActions
3.OnUNIXservers,verifythatthebpcdentriesin/etc/servicesorNISonalltheserversareidentical.Verifythatthe
mediaserverislisteningonthecorrectportforconnectionstobpcdbyrunningoneofthefollowingcommands
(dependingonplatformandoperatingsystem):
netstata|grepbpcd
netstata|grep13782(orthevaluespecifiedduringtheinstall)
rpcinfop|grep13782(orthevaluespecifiedduringtheinstall)
OnUNIXservers,youmayhavetochangetheservicenumberforbpcdin/etc/servicesandtheNISservicesmap
andsendSIGHUPsignalstotheinetdprocessesontheclients.
/bin/psef|grepinetd
killHUPthe_inetd_pid
or
/bin/psaux|grepinetd
killHUPthe_inetd_pid
Note:OnaHewlettPackardUNIXplatform,useinetdctosendaSIGHUPtoinetd.
4.OnWindowsNTservers:
a.Verifythatthebpcdentriesarecorrectin:
%SystemRoot%\system32\drivers\etc\services
b.VerifythattheNetBackupClientServicePortNumberandNetBackupRequestServicePortNumberon
theNetworktabintheNetBackupConfigurationdialogboxmatchthesettingsintheservicesfile.To
displaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceandclickConfigureontheActions
menu(alsosee"UsingtheConfigureNetBackupWindow"onpage57).ThevaluesontheNetworktab
arewrittentotheservicesfilewhentheNetBackupClientservicestarts.
c.StopandrestarttheNetBackupservices.
5.See"TestingSlaveServerandClients"onpage18and"ResolvingNetworkCommunicationProblems"onpage
21.
6.Ifnecessary,createactivitylogdirectoriesforthefollowingprocessesandretrytheoperation.Then,checkthe
resultingactivitylogsonthemasterserver:
oIftheerroroccurredduringabackupoperation,checkthebpschedactivitylogs.
oIftheerroroccurredduringarestoreoperation,checkthebprdactivitylogs.
StatusCode:205Top
Message:cannotconnecttoserverbackuprestoremanager
Explanation:Aprocessonthemasterservercouldnotconnecttoaprocessonahostonthenetworkwhiletryingtoinitiate
communicationwiththeserverthathasthestorageunitforaparticularoperation.Thisproblemcanoccurduringabackupor
35/43
9/14/2016
restoreineitherasingleormultipleserverconfiguration.Thiscanalsooccurwhentheschedulerprocess(bpsched)isbuilding
itslistofavailablestorageunitstouseduringbackups.
RecommendedAction:Executethepingcommandfromonehosttoanotherbyusingthefollowingcombinations:
Note:Also,see"ResolvingNetworkCommunicationProblems"onpage21.
1.Fromthemasterserver,pingthemasterandallslaveserversbyusingthehostnamesinthestorageunit
configuration.
2.Fromeachoftheslaveservers,pingthemasterserverbyusingthenamespecifiedintheNetBackupserverlist.
OnaUNIXserver,thisisthefirstSERVERentryinthebp.conffile.OnaWindowsNTserver,themasteris
designatedastheCurrentserverontheServerstabintheNetBackupConfigurationdialogbox.Todisplaythis
dialogbox,starttheBackup,Archive,andRestoreinterfaceandclickConfigureontheActionsmenu(alsosee
3.OnaUNIXserver,verifythatthebpcdentryin/etc/servicesorNISonalltheserversareidentical.Verifythatthe
mediaserverislisteningonthecorrectportforconnectionstobpcdbyrunningoneofthefollowingcommands
(dependingonplatformandoperatingsystem):
netstata|grepbpcd
netstata|grep13782(orthevaluespecifiedduringtheinstall)
rpcinfop|grep13782(orthevaluespecifiedduringtheinstall)
4.OnWindowsNTservers:
a.Verifythatthebpcdentriesarecorrectintheservicesfile:
%SystemRoot%\system32\drivers\etc\services
b.VerifythattheNetBackupClientServicePortNumberandNetBackup
RequestServicePortNumberontheNetworktabintheNetBackupConfigurationdialogboxmatchthe
settingsintheservicesfile.Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceand
ThevaluesontheNetworktabarewrittentotheservicesfilewhentheNetBackupClientservicestarts.
c.StopandrestarttheNetBackupservices.
5.See"TestingSlaveServerandClients"onpage18and"ResolvingNetworkCommunicationProblems"onpage
21.
6.Createabpcdactivitylogdirectoryontheserverthathasthestorageunitandretrytheoperation.Then,checkfor
additionalinformationintheresultingactivitylog.
StatusCode:206Top
Message:accesstoserverbackuprestoremanagerdenied
Explanation:Themasterserveristryingtostartaprocessonanotherserver(oritself)andthemasterserverdoesnotappear
intheNetbackupserverlistonthatserver.OnaUNIXserver,themasteristhefirstSERVERentryinthebp.conffile.Ona
WindowsNTserver,themasterisdesignatedastheCurrentserverontheServerstabintheNetBackupConfigurationdialog
box.
Todisplaythisdialogbox,starttheBackup,Archive,andRestoreinterfaceandclickConfigureontheActionsmenu(alsosee
RecommendedAction:
1.Verifythatthemasterserverappearsasaserverinitsownserverlistaswellasbeinglistedonallslaves.
Ifyouchangetheserverlistonamasterserver,stopandrestarttheNetBackupdatabasemanagerandrequest
daemons(UNIX)ortheNetBackupDatabaseManagerandNetBackupRequestManagerservices(Windows
NT).
2.Ifnecessary,createactivitylogdirectoriesforthefollowingprocessesandretrytheoperation.Then,checkthe
resultingactivitylogsonthemasterserver:
oIftheerroroccurredduringabackupoperation,checkthebpschedactivitylogs.
oIftheerroroccurredduringarestoreoperation,checkthebprdactivitylogs.
StatusCode:207Top
Message:errorobtainingdateoflastbackupforclient
Explanation:Anerroroccurredwhenthebackupscheduler(bpsched)triedtoobtainthedateofthelastbackupforaparticular
client,class,andschedulecombination.
RecommendedAction:
1.VerifythattheNetBackupdatabasemanager(bpdbm)process(NetBackupDatabaseManagerserviceon
WindowsNT)isrunning.
2.ExaminetheAllLogEntriesreportfortheappropriatetimeframetogathermoreinformationaboutthefailure.
3.Fordetailedtroubleshootinginformation,createactivitylogdirectoriesforbpschedandbpdbmonthemaster
serverandretrytheoperation.Then,checktheresultingactivitylogs.
StatusCode:208Top
Message:failedreadinguserdirectedfilelist
Explanation:Anerroroccurredwhenthebackupscheduler(bpsched)attemptedtoreadthelistoffilesrequestedforauser
backuporarchive.Thiserrorindicateseitheraclientservercommunicationproblem,orasystemproblemonthemasterserver
wheretheNetBackupschedulerprocess(bpsched)isrunning.
36/43
9/14/2016
RecommendedAction:Fordetailedtroubleshootinginformation,createactivitylogdirectoriesforbpschedandbprdonthe
masterserverandretrytheoperation.Then,checktheresultingactivitylogs.
StatusCode:209Top
Message:errorcreatingorgettingmessagequeue
Explanation:Anerroroccurredwhenthebackupscheduler(bpsched)attemptedtocreateaninternalmessagequeueconstruct
forinterprocesscommunication.Thiserrorindicatesaproblemonthemasterserverandismostlikelyduetoalackofsystem
resourcesforSystemVinterprocesscommunication.
RecommendedAction:Createabpschedactivitylogdirectoryonthemasterserverandretrytheoperation.Then,determine
thetypeofsystemfailurebyexaminingtheerrormessageinthebpschedactivitylog.
OnUNIXservers,alsogathertheoutputoftheipcsacommandtoseewhatsystemresourcesarecurrentlyinuse.
211212213214215216217218219Top
StatusCode:210Top
Message:errorreceivinginformationonmessagequeue
Explanation:Anerroroccurredwhenoneofthebackupscheduler(bpsched)processesattemptedtoreceiveamessagefrom
anotherbpschedprocessonaninternalmessagequeueconstruct.Thiserrorindicatesaproblemonthemasterserverandis
likelyduetoproblemswithoralackofsystemresourcesforSystemVinterprocesscommunication.
thetypeofsystemfailurebyexaminingtheerrormessageinthebpschedactivitylogonthemasterserver.OnUNIXservers,
alsogathertheoutputoftheipcsacommandtoseewhatsystemresourcesarecurrentlyinuse.
StatusCode:211Top
Message:schedulerchildkilledbysignal
Explanation:Abackupscheduler(bpsched)childprocess,whichinteractswiththebackuprestoremanager(bpbrm)onthe
mediaserver,wasterminated.Thiscanoccurbecauseofsystemadministratoraction.
RecommendedAction:Createanactivitylogdirectoryforbpschedonthemasterserverandretrytheoperation.Then,to
determinethecauseofthechildtermination,examinethemessagesinthebpschedactivitylog.
StatusCode:212Top
Message:errorsendinginformationonmessagequeue
Explanation:Thebackupscheduler(bpsched)encounteredanerrorwhenattemptingtoattachtoanalreadyexistinginternal
messagequeueconstructforinterprocesscommunication.Thiserrorindicatesaproblemonthemasterserverandislikelydue
toalackofsystemresourcesforSystemVinterprocesscommunication.
thetypeofsystemfailurebyexaminingtheerrormessageinthebpschedactivitylog.OnaUNIXserver,also,gatherthe
outputoftheipcsacommandtoseewhatsystemresourcesarecurrentlyinuse.
StatusCode:213Top
Message:nostorageunitsavailableforuse
Explanation:TheNetBackupschedulerprocess(bpsched)didnotfindanyofitsstorageunitsavailableforuse.Eitherall
storageunitsareunavailableorallstorageunitsareconfiguredfor"ondemandonly"andtheclassandscheduledoesnot
requireaspecificstorageunit.
RecommendedAction:
1.ExaminetheBackupStatusandAllLogEntriesreportfortheappropriatetimeperiodtodeterminetheclassor
schedulethatreceivedtheerror.
2.Verifythatthestorageunit'sdrivesarenotdownorwaitingformediafromapreviousoperationthatdidnot
complete.
3.Examinethestorageunitconfigurationtoverifythatallthestorageunitsdonothavetheir"ConcurrentJobs"
attributesetto0.
4.VerifythattherobotnumberandhostnameinthestorageunitconfigurationmatchestheMediaManagerdevice
configuration.
5.Determineifallstorageunitsaresetto"OnDemandOnly"foraclassandschedulecombinationthatdoesnot
requireaspecificstorageunit.Ifthisisthecase,eitherspecifyastorageunitfortheclassandschedule
combinationorturnoff"OnDemandOnly"forastorageunit.
6.IfthestorageunitisonaUNIXNetBackupslaveserver,itcouldindicateproblemwithbpcd.Check/etc/inetd.conf
ontheslaveservertoverifythatthebpcdentryisok.IfthestorageunitisonaWindowsNTNetBackupslave
server,verifythattheNetBackupClientservicehasbeenstartedontheWindowsNTNetBackupslaveserver.
7.Fordetailedtroubleshootinginformation,createabpschedactivitylogdirectoryonthemasterserverandretrythe
operation.Then,checktheresultingactivitylog.
37/43
9/14/2016
StatusCode:214Top
Message:regularbpschedisalreadyrunning
Explanation:TheNetBackupscheduler(bpsched)performsperiodiccheckingoftheclassandscheduleconfigurationto
determineiftherearenewbackupsdue.Error214indicatesthatwhenanewinstanceofNetBackupstarts,itfindsthata
schedulerprocessisalreadycheckingtheclassandscheduleconfiguration.
RecommendedAction:Usually,noactionisrequiredforthiscondition.However,NEVERkillbpschedbeforedoingsome
checking.Forexample,bpschedcouldbecallingbpdbm(NetBackupDatabaseManagerserviceonWindowsNT)tocleanup
andcompressthedatabases.Todeterminewhattherunningbpschediscurrentlydoing,examinethebpschedactivitylogon
themasterserver.Ifnecessary,enablebpschedactivityloggingbycreatingabpschedactivitylogdirectoryonthemaster
serverandretryingtheoperation.Tocheckforbackupsdothefollowing:
OnaUNIXmasterserver:
1.Checkforactiveorqueuedbackupsbyusingthejobmonitor.
2.Checkforactivebpprocesseswithbpps.Thisrevealsiftherearebpbrmorbptmprocessesrunninganda
backupisactive.
3.Ifthereisnoreasonforbpschedtoberunning,thenusekillHUPtoterminateit.
OnaWindowsNTNetBackupmasterserver:
StatusCode:215Top
Message:failedreadingglobalconfigdatabaseinformation
Explanation:DuringtheperiodiccheckingoftheNetBackupconfiguration,theNetBackupschedulerprocess(bpsched)was
unabletoreadtheglobalconfigurationparameters.
RecommendedAction:
1.OnaUNIXmasterserver,verifythattheNetBackupdatabasemanager(bpdbm)processisrunning.Ona
WindowsNTmasterserver,verifythattheNetBackupDatabaseManagerserviceisrunning.
2.AttempttoviewtheglobalconfigurationsettingsbyusingthetheNetBackupadministrationinterface.
StatusCode:216Top
Message:failedreadingretentiondatabaseinformation
Explanation:DuringitsperiodiccheckingoftheNetBackupconfiguration,theNetBackupschedulerprocess(bpsched)could
notreadthelistofretentionlevelsandvalues.
RecommendedAction:
1.OnaUNIXmasterserver,verifythattheNetBackupdatabasemanager(bpdbm)processisrunning.Ona
WindowsNTmasterserver,verifythattheNetBackupDatabaseManagerserviceisrunning.
StatusCode:217Top
Message:failedreadingstorageunitdatabaseinformation
Explanation:DuringitsperiodiccheckingoftheNetBackupconfiguration,theNetBackupschedulerprocess(bpsched)could
notreadthestorageunitconfiguration.
RecommendedAction:
1.OnaUNIXserver,verifythattheNetBackupdatabasemanager(bpdbm)processisrunning.OnaWindowsNT
server,verifythattheNetBackupDatabaseManagerserviceisrunning.
2.AttempttoviewthestorageunitconfigurationbyusingtheNetBackupadministrationinterface.
3.Fordetailedtroubleshootinginformation,createactivitylogsforbpschedandbpdbmonthemasterserverand
retrytheoperation.Then,checktheresultingactivitylogs.Ensurethatthecorrectmasterserverisbeing
specifiedfortheconnection.
StatusCode:218Top
Message:failedreadingclassdatabaseinformation
Explanation:DuringtheperiodiccheckingoftheNetBackupconfiguration,theNetBackupschedulerprocess(bpsched)could
notreadtheclass(backuppolicy)configuration.
RecommendedAction:
1.OnaUNIXserver,verifythattheNetBackupdatabasemanager(bpdbm)processisrunning.OnaWindowsNT
server,verifythattheNetBackupDatabaseManagerserviceisrunning.
2.AttempttoviewtheclassconfigurationbyusingtheNetBackupadministrationinterface.
serverandretrytheoperation.Then,checktheresultingactivitylogs.Ensurethatthecorrectmasterserveris
beingspecifiedfortheconnection.
StatusCode:219Top
38/43
9/14/2016
Message:therequiredstorageunitisunavailable
Explanation:Theclassorscheduleforthebackuprequiresaspecificstorageunit,whichiscurrentlyunavailable.Thiserror
alsooccursforotherattemptstousethestorageunitwithinthecurrentbackupsession.
RecommendedAction:ExaminetheBackupStatusandAllLogEntriesreportfortheappropriatetimeperiodtodeterminethe
classorschedulethatreceivedtheerror.Then,examinethespecificclassandscheduleconfigurationtodeterminethe
requiredstorageunit.
1.Verifythattheschedulespecifiesthecorrectstorageunitandthestorageunitexists.
2.VerifythattheMediaManagerdevicedaemon(ltid)isrunning(iftheserverisUNIX)ortheNetBackupDevice
Managerserviceisrunning(iftheserverisaWindowsNTsystem).UsebppsonUNIXandtheActivityMonitoron
WindowsNT.
3.VerifythattheNumberofDrivesattributeforthestorageunitisnotsetto0.
4.Ifthestorageunitisatapeoropticaldisk,verifythatatleastoneofthedrivesisintheUPstate.UsetheDevice
Monitor(onUNIXxdevadmcanalsobeused).
5.VerifythattherobotnumberandhostinthestorageunitconfigurationmatcheswhatisspecifiedintheMedia
Managerdeviceconfiguration.
6.Verifythatthemasterservercancommunicatewiththebpcdprocessontheserverthathasthestorageunit.
a.Verifythatbpcdislisteningontheportforconnections.
OnaUNIXserver,executing
netstata|grepbpcd
shouldreturnsomethingsimilartothefollowing:
*.bpcd*.*0000LISTEN
Dothisontheserverwherethestorageunitisconnected.
OnaWindowsNTNetBackupserver,executing
netstata
printsoutseverallinesofoutput.Ifbpcdislistening,oneofthoselinesissimilartothefollowing:
TCPmyhost:bpcd0.0.0.0:0LISTENING
Dothisontheserverwherethestorageunitisconnected.
b.Ifbpcdseemstobeoperatingcorrectly,createbpschedandbpcdactivitylogdirectoriesandretrythe
operation.Checktheresultingactivitylogsforrecordsofanearlierfailure.
Aftereachbackup,theschedulerchecksthestorageunittoseehowmanydrivesareavailable(incase
thebackupcausedadrivetobeautomaticallydowned).Ifbpschedcannotcommunicatewithbpcd,itsets
thenumberofavailabledrivesinthatstorageunitto0andfurtherbackupstothatstorageunitduringthis
backupsessionwillfail.Thenumberofavailabledrivesremainsat0untiltheschedulerisinitializedagain.
7.c.Ifthecauseoftheproblemisnotobvious,performsomeofthestepsin"ResolvingNetworkCommunication
Problems"onpage21.
221222223224225226227228229Top
StatusCode:220Top
Message:databasesystemerror
Explanation:Thebpdbmprocess(NetBackupDatabaseManagerserviceonWindowsNT)couldnotcreateadirectorypathfor
itsconfigurationdatabasesduetothefailureofasystemcall.Thisisusuallyduetoapermissionproblemoran"outofspace"
condition.
RecommendedAction:Createanactivitylogdirectoryforbpdbmandretrytheoperation.Checktheresultingactivitylogfor
information.
StatusCode:221Top
Message:continue
Explanation:ThisstatuscodeisusedincoordinatingcommunicationbetweenvariousNetBackupprocessesandnormallydoes
notoccur.Ifthelogsshowthatitisassociatedwithasubsequenterror,itusuallyindicatesacommunicationproblem.Inthis
case,concentrateyourtroubleshootingeffortsonthesubsequenterror.
RecommendedAction:Determinethecauseofthestatuscodethatfollowsthisone.
StatusCode:222Top
Message:done
Explanation:ThisstatuscodeisusedincoordinatingcommunicationbetweenvariousNetBackupprocessesandisnormally
notseen.Iftheerrorlogsshowthatitisassociatedwithasubsequenterror,itusuallyindicatesacommunicationproblem.In
thiscase,concentrateyourtroubleshootingeffortsonthesubsequenterror.
RecommendedAction:Determinethecauseofthestatuscodethatfollowsthisone.
StatusCode:223Top
Message:aninvalidentrywasencountered
Explanation:Arequesttothebpdbmprocess(NetBackupDatabaseManagerserviceonWindowsNT)hadinvalidorconflicting
information.Thisisusuallyaresultofusingsoftwarefromdifferentversionstogether,butcanalsobecausedbyincorrect
39/43
9/14/2016
parametersonacommand.
RecommendedAction:VerifythatallNetBackupsoftwareisatthesameversionlevelandthecommandparametersare
specifiedcorrectly.Ifneitheroftheseistheproblem,obtaindetailedtroubleshootinginformationbycreatingabpdbmactivity
logdirectoryandretryingtheoperation.Checktheresultingactivitylog.
StatusCode:224Top
Message:therewasaconflictingspecification
Explanation:Arequesttothebpdbmprocess(NetBackupDatabaseManagerserviceonWindowsNT)hadconflicting
information.Thisisusuallyaresultofusingsoftwarefromdifferentversionlevelstogether.
RecommendedAction:VerifythatallNetBackupsoftwareisatthesameversionlevel.Ifthatisnottheproblem,obtaindetailed
troubleshootinginformationbycreatingbpdbmandadminactivitylogdirectoriesandretryingtheoperation.Checktheresulting
activitylogs.
StatusCode:225Top
Message:textexceededallowedlength
Explanation:Arequestcontainingtextthatexceedsabuffersizewasmadetothebpdbmprocess(NetBackupDatabase
ManagerserviceonWindowsNT).Thisisusuallyaresultofusingsoftwarefromdifferentversionlevelstogether.
RecommendedAction:VerifythatallNetBackupsoftwareisatthesameversionlevel.Ifthatisnottheproblem,createactivity
logdirectoriesforbpdbmandadmin.Then,retrytheoperationandexaminetheresultingactivitylogs.
StatusCode:226Top
Message:theentityalreadyexists
Explanation:Theconfigurationalreadyhasanentitywiththesamenameordefinition.Forexample,youseethisstatusifyou
trytoaddanewclasswhenanexistingclasshasthesamenameordefinition(attributes,clients,andsoon).
RecommendedAction:Correctyourrequestandreexecutethecommand.
StatusCode:227Top
Message:noentitywasfound
Explanation:Theitemrequestedwasnotinthedatabase.Forexample,theentitycouldbeafileorclassinformation.
RecommendedAction:Acommoncauseforthisproblemisaquerythathasnomatchingimages.Specifydifferentparameters
oroptionsfortheoperationandtryitagain.
StatusCode:228Top
Message:unabletoprocessrequest
Explanation:Aninconsistencyexistsinthedatabaseorarequestwasmadethatwouldbeimpropertosatisfy.
RecommendedAction:
1.Ifthisinvolvesaslaveserver,verifythatitsserverlistspecifiesthecorrectmasterserver.OnaUNIXserver,the
masterserveristhefirstSERVERentryinthebp.conffile.OnaWindowsNTserver,themasterisdesignatedas
theCurrentserverontheServerstabintheNetBackupConfigurationdialogbox.Todisplaythisdialogbox,start
theBackup,Archive,andRestoreinterfaceandclickConfigureontheActionsmenu(alsosee"Usingthe
ConfigureNetBackupWindow"onpage57).
2.Fordetailedtroubleshootinginformation,createabpdbmactivitylogdirectoryandretrytheoperation.Then,
checktheresultingactivitylog.
StatusCode:229Top
Message:eventsoutofsequenceimageinconsistency
Explanation:Arequestwasmadewhich,ifsatisfied,wouldcausetheimagedatabasetobecomeinconsistent.
RecommendedAction:Obtaindetailedtroubleshootinginformationbycreatinganactivitylogdirectoryforbpdbm.Then,retry
theoperation,savetheresultingactivitylog,andcallcustomersupport.
231232233234235236237238239Top
StatusCode:230Top
Message:thespecifiedclassdoesnotexistintheconfigurationdatabase
Explanation:Thespecifiedclassnamedoesnotexist.
RecommendedAction:Correctyourparametersoroptionsandretrytheoperation.
40/43
9/14/2016
StatusCode:231Top
Message:schedulewindowsoverlap
Explanation:Thestartanddurationtimesspecifiedforonedayofthescheduleoverlapwithanotherdayoftheschedule.
RecommendedAction:Correctthescheduletoeliminatetheoverlappingbackupwindows.
StatusCode:232Top
Message:aprotocolerrorhasoccurred
Explanation:Thisisanintermediatestatuscodethatusuallyprecedesanotherstatuscode.Itindicatesthateitherthebpdbm
process(NetBackupDatabaseManagerserviceonWindowsNT)ortheprocesscommunicatingwithithasreceived
unexpectedinformation.
RecommendedAction:Createanactivitylogdirectoryforbpdbm.Then,retrytheoperation,savetheactivitylog,andcall
customersupport.
StatusCode:233Top
Message:prematureeofencountered
Explanation:Thisisanintermediatestatuscodethatusuallyprecedesanotherstatuscodeandisassociatedwithaproblemin
networkcommunication.
RecommendedAction:Duringarestore,thismeansthattar(ontheclient)receivedastreamofdatathatwasnotwhatit
expected.Ifthisisanewconfiguration,verifythatthetapedriveisconfiguredforvariablemode(seetheMediaManager
DeviceConfigurationGuide).
Ifthecommunicationfailureisnotduetoaninterruptonaclientsystem,saveallerrorinformationandcallcustomersupport.
StatusCode:234Top
Message:communicationinterrupted
Explanation:Thisisanintermediatestatuscodethatusuallyprecedesanotherstatuscodeandisassociatedwithaproblemin
networkcommunication.Aprocess,eitherserverorclient,receivedaninterruptsignal.
StatusCode:235Top
Message:inadequatebufferspace
Explanation:Thiscodeusuallyindicatesamismatchbetweenserverandclientsoftwareversions.
RecommendedAction:
1.VerifythatallNetBackupsoftwareisatthesameversionlevel.UpdateearlierversionsofNetBackupsoftware.
OnWindowsNTNetBackupservers,checktheinstall_path\NetBackup\version.txtfileortheAboutNetBackup
commandontheHelpmenu.
OnNetWaretargetclients,checktheVersionentryinthebp.inifile.Iftheclientsoftwareisearlierthan3.0,verify
thattheclientisinaStandardtypeclass.
2.Iftheproblempersists,saveallerrorinformationandcallcustomersupport.
StatusCode:236Top
Message:thespecifiedclientdoesnotexistinanactiveclasswithintheconfigurationdatabase
Explanation:Aclientnamewasnotspecifiedorthespecifiedclientdoesnotexist.
RecommendedAction:Activatetherequiredclass,correcttheclientname,oraddtheclienttoaclassthatmeetsyourneeds.
Aftermakingthecorrection,retrytheoperation.
StatusCode:237Top
Message:thespecifiedscheduledoesnotexistinanactiveclassintheconfigurationdatabase
Explanation:ThespecifiedscheduledoesnotexistintheNetBackupconfiguration.
RecommendedAction:Activatetherequiredclass,correcttheschedulename,orcreateascheduleinaclassthatmeetsyour
needs.Aftermakingthecorrection,retrytheoperation.
StatusCode:238Top
Message:thedatabasecontainsconflictingorerroneousentries
Explanation:Thedatabasehasaninconsistentorcorruptedentry.
RecommendedAction:Obtaindetailedtroubleshootinginformationforbpdbm(NetBackupDatabaseManagerserviceon
WindowsNT)bycreatinganactivitylogdirectoryforit.Then,retrytheoperation,saveresultingactivitylog,andcallcustomer
41/43
9/14/2016
support.
StatusCode:239Top
Message:thespecifiedclientdoesnotexistinthespecifiedclass
Explanation:Thespecifiedclientisnotamemberofthespecifiedclass.
RecommendedAction:Correcttheclientnamespecification,specifyadifferentclass,oraddtherequiredclientnametothe
class.Aftermakingthecorrection,retrytheoperation.
241242243244245246247248249Top
StatusCode:240Top
Message:noschedulesofthecorrecttypeexistinthisclass
Explanation:Theappropriateschedulewasnotfoundinthespecifiedclass.Forexample,auserbackupspecifiedaclass
namebutnouserbackupscheduleexistsinthatclass.
RecommendedAction:Specifyadifferentclassorcreateascheduleoftheneededtypeintheclass.Aftermakingthe
correction,retrytheoperation.
StatusCode:241Top
Message:thespecifiedscheduleisthewrongtypeforthisrequest
Explanation:Theschedulethatwasspecifiedforanimmediatemanualbackupisnotforafullnoranincrementalbackup.It
mustbeoneofthese.
RecommendedAction:Specifyonlyfullorincrementalschedulesformanualbackups.Ifonedoesnotexistintheclass,create
one.
StatusCode:242Top
Message:operationwouldcauseanillegalduplication
Explanation:Processingtherequestwouldcauseaduplicatedatabaseentry.Thisisusuallyduetoamistakeinspecifying
mediaIDsforNetBackupdatabasebackups.
RecommendedAction:Checktheerrorreportstodeterminethespecificduplicationthatwouldoccur.Correctthesettingsfor
theoperationandretryit.
StatusCode:243Top
Message:theclientisnotintheconfiguration
Explanation:Thespecifiedclientnamewasnotinthedatabase.
RecommendedAction:Eithercorrecttheclientnameoraddtheclienttothedesiredclass.
StatusCode:244Top
Message:mainbpschedisalreadyrunning
Explanation:Abpschedprocesstriedtobecomethemainbackupschedulerbutanotherprocessiscurrentlyinthismode.
StatusCode:245Top
Message:thespecifiedclassisnotofthecorrectclienttype
Explanation:Auserbackupspecifiedaclassthatisnotthetyperequiredfortheclient.
RecommendedAction:Retrytheoperationbyspecifyingaclassthatisthecorrecttypefortheclient.Ifsuchaclassdoesnot
exist,createone.
StatusCode:246Top
Message:noactiveclassesintheconfigurationdatabaseareofthecorrectclienttype
Explanation:Auserbackuprequestwasnotsatisfiedbecausenoactiveclasseswerethetyperequiredfortheclient.
RecommendedAction:Createoractivateanappropriateclasssotheuserbackuprequestcanbesatisfied.
StatusCode:247Top
42/43
9/14/2016
Message:thespecifiedclassisnotactive
Explanation:Backupsforthespecifiedclassaredisabledbecausetheclassisinactive.
RecommendedAction:Activatetheclassandretrytheoperation.
StatusCode:248Top
Message:therearenoactiveclassesintheconfigurationdatabase
Explanation:Noactiveclasswasfoundthatwouldsatisfytherequest.
RecommendedAction:Activatetheappropriateclassandretrytheoperation.
StatusCode:249Top
Message:thefilelistisincomplete
Explanation:Theservertimedoutwhilewaitingfortheclienttofinishsendingthefilelist,orasequencingproblemoccurred.
RecommendedAction:Obtainadditionalinformationbyfirstcreatingactivitylogsandthenattemptingtorecreatetheerror.The
activitylogstocreateareasfollows:
Ontheserver,bptm,bpbrm,andbpdbm.
OnUNIXandWindowsNTclients,bpbkar.
Onotherclients,bpcd.
Toincreasetheamountofinformationincludedinthelogs.See"ActivityLogsonPCClients"onpage67.
251254Top
StatusCode:250Top
Message:theimagewasnotcreatedwithTIRinformation
Explanation:Thisisaninternalerrorandshouldnotbeseenbycustomers.RecommendedAction:Obtaindetailed
troubleshootinginformationbycreatingactivitylogsforbptmandbpdbmontheserver.Then,retrytheoperationandcheckthe
StatusCode:251Top
Message:thetirinformationiszerolength
Explanation:Foratrueimagebackup,theclientsentnofileinformationtothemasterserver.NetBackupdiscoveredthis
conditionwhenitattemptedtowritetheTIRinformationtomedia.
RecommendedAction:
1.Checkthefilelistfortheclassandtheexcludeandincludelistsontheclienttoverifythattheclienthasfilesthatareeligible
forbackup.Forexample,thisstatuscodecanappeariftheexcludelistontheclientexcludesallfiles.
2.Toobtaindetailedtroubleshootinginformation,createactivitylogsforbptmandbpdbmontheserver.Then,retrythe
operationandchecktheresultingactivitylogs.
StatusCode:254Top
Message:servernamenotfoundinthebp.conffile
Explanation:ThiserrorshouldnotoccurthroughnormaluseofNetBackup.
43/43

Veritas Status Codes and Messages

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Veritas Status Codes and Messages

Diunggah oleh

Hak Cipta:

Format Tersedia

9/14/2016

Anda mungkin juga menyukai