Oprd Error 96
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success
Ipc Error: Daemon May Not Be Running
Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership error connecting to oprd status(39) Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano
Error Connecting To Media Manager Network Protocol Error 39
日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Getting error "error connecting to oprd on server xxx ,oprd returned abnormal status 96" when running nbrbutil the device configuration wizard Article:000008823 Publish: Article URL:http://www.veritas.com/docs/000008823 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print nbrbutil command Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Getting error "error connecting to oprd on server xxx ,oprd returned abnormal status 96" when running the device configuration wizard.Also unable to expand the devices tab ,getting error "error connecting to oprd,network protocol error 39" Error Message Error connecting to oprd on server xxx ,oprd returned abnormal status 96 Error connecting to oprd,network protocol error 39 Cause Stale entries for deleted devices in the NetBackup EMM database.Or if a media server is not correctly decommissioned. Solution Step 1:Windows only:From command prompt run set devmgr_show_nonpresent_devices=1Open the device manager click 'view' >show hidden devices > tape drives >check for ghost drives which are no longer connected to the server,if any remove them (repeat this for each media server)Step 2:Stop NetBackup services Windows
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : https://www.veritas.com/support/en_US/article.000008823 Backup and Recovery : NetBackup : oprd returned abnormal status (96) VOX : Backup and Recovery : NetBackup : oprd returned abnormal status (96) Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page oprd returned abnormal status https://vox.veritas.com/t5/NetBackup/oprd-returned-abnormal-status-96/td-p/444613 (96) Nitesh_Bhat Level 2 12-15-2011 01:27 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, I am not able to get media manager daemons after bouncing Netbackup Daemons. And i got this error #./vmoprcmd -d oprd returned abnormal status (96) IPC Error: Daemon may not be running Logs of daemon & reqlib & ltid as below:- Ltid:- 01:21:23.746 [23332] <4> CheckShutdownWhileInit: Pid=1, Data.Pid=25157, Type=100, Param1=0, Param2=-5056, LongParam=-23490544 01:21:24.281 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-01 is ACTIVE 01:21:24.281 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-02 is ACTIVE 01:21:24.281 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-03 is ACTIVE 01:21:24.281 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-06 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-07 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-08 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-10 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-12 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Dr
cd /usr/openv/volmgr/debug ls mkdir reqlib bpps -x kill -9 557180 bpps -a kill -9 380994 netbackup start bpps -a nbrburil -dump nbrbutil -dump ' bpdbjobs -summary nbrbutil http://margaux99.blogspot.com/2011/09/general-error-oprd-returned-abnormal.html -resetMediaserver nbrbutil -resetMediaServer nbu_master nbrbutil -dump nbrbutil -resetAll df -Pk bpps -a bpps -a vmoprcmd vmoprcmd -d vmoprcmd -devmon hs robtest bpps -a netbackup stop bpps -a kill -9 205226 netbackup start vmoprcmd -devmon hs nbrbutil -dump bpps -a robtest vmoprcmd -d vmoprcmd -devmon hs vmoprcmd -devmon hs Posted by James Kim at 4:10 PM Reactions: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: netbackup error connecting No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) AIX Blog James Kim|Create Your Badge AIX James KimCreate Your Badge Facebook Badge James KimCreate Your Badge Total Pageviews Follow by Email Popular Posts 0042-006 niminit: (init to master) rcmd A remote host refused an attempted connect operation. Problem: nim -o define -t MachineType -a Attribute=Value ... MachineName nim_master: A error connecting to remote host refused an attempted connect oper... VIO Server/Client 구성 방법 VIO 서버 구성 방법 . 00. 사전준비 . a. 기종은 IBM Power5 이상 되어야함 . b. Physical HDD 1 개 이상 c. Physical Ethernet ... How to remove ipv6 in AIX 1. Remove from device. lsattr -El lo0 chdev -l lo0 -a netaddr6=''" ifconfig -a ifconfig lo0 inet6 ::1/0 delete ifconfig... 3D32B80D topsvcs NIM thread blocked topsvcs NIM thread blocked --------------------------------------------------------------------------- LABEL: TS_NIM_ERRO... ACT01513 : HMC Can't open the console ACT01513 : HMC Can't open the console Solution : window start => all program => Java => configure java => security => e... aix parameters ioo aio_minserver 3 # ioo -p -d aio_minservers ioo aio_maxserver 130 # ioo -p -o aio_maxservers=1... NFS rpc.lockd fails Error IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION CB4A951F 0118163912 I S SRC SOFTWARE PROGRAM ERROR slawmsa1:roo... How to kill the CLOSE_WAIT sections on AIX How to kill the CLOSE_WAIT sections on AIX root@server #netstat -a | grep CLOSE tcp4 104 0 server.49196 server.43787 CLOSE_WAIT tcp4 104... AIX Error - Delayed_INTS Problem: LABEL: DELAYED_INTS IDENTIFIER: A2205861 Date/Time: Thu Jul 12 10:56:40 GMT-04:00 2012 Sequence Nu... Simple template. Powered by Blogger.