Networker Rap Error Unable To Extract Resource Info For Client

Management Converged Platforms Data Protection Infrastructure Management Platform Solutions Security Storage Dell Products for Work Network Servers Education Partners Programs Highlighted Communities Support » Connect » Developers » Partners » Downloads » 日本語コミュニティ EMC Community Dell Community A AppSync Application Xtender Atmos Avamar C Captiva Celerra Centera CLARiiON Cloud Tiering Appliance Connectrix D Data Domain Data Protection Advisor Disk Library DiskXtender Documentum E ECS eRoom G Greenplum H Host Systems I InfoArchive Isilon ISIS Document Imaging L Leap N NetWorker P PowerPath Prosphere R RecoverPoint Replication RSA S ScaleIO Secure Remote Smarts SourceOne & EmailXtender EMC Storage Analytics Symmetrix U Unity V ViPR Controller Product Communities > NetWorker > Documents Currently Being Moderated Troubleshooting 'RAP error, Unable to extract resource info for client (client_name)' errors created by Prajith on Aug 8, 2013 10:04 AM, last modified by Prajith on Aug 8, 2013 10:04 AM Version 1 Product:NetWorkerDescription:Error: 'RAP error, Unable to extract resource info for client (client_name)' Error: 'save: Cannot open save session with (client_name)' Error: 'save: error, no matching devices; check storage nodes, devices or pools' Message appears after deleting a 2nd instance of an existing client resource Scheduled backups for the remaining client instances fail with errors After updating a client resource on a NetWorker server with many clients the scheduled saves fail with error Error: 'RPC error unable to retrieve client resources' Error:'system error: client (shortname) is not properly configured' Error:'No client can be found on the server' Error:'RPC error, Authentication error, cannot retrieve client resources' savefs -p fails with error rpc error unable to receive cannot retrieve client resources Error: 'RPC error, unable to receive' Backup of cluster not workingDomain name changed Client was deleted Resolution:Verify the following, but keep in mind that in most cases the reason for this error is a change or failure in the name resolution service or a misconfiguration in NetWorker: Verify that all known aliases for the NetWorker client ar

FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central Forums Forum Index » EMC NetWorker » RAP error: Unable to extract resource info for client myclie The time now is Fri Oct 21, 2016 1:43 am View previous topic | View next topic Page 1 of 1 RAP error: Unable to extract resource info for client myclie Author Message Clark, Patricia Guest RAP error: Unable to extract resource info for client myclie RAP error: Unable to https://community.emc.com/docs/DOC-26571 extract resource info for client myclient I have searched the archives since this error message is not documented and found a three (3) references which mention this error: 1. Stop/restart the client networker process(es) 2. Delete the client alias entries 3. Stop/restart the server networker process(es) Having tried all three in the above order and not having any functional results until the server networker http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/emc-networker-19/rap-error-unable-to-extract-resource-info-for-client-myclie-41351/ was restarted, I would like to know what the error message means. Hit and miss attempts to correct errors does not lead to understanding. The configuration for both client and server is: Solaris 9 fully patched - SUN V440 Networker 7.1.2 Quantum M2500 jukebox w/ 2 - LTO-2 drives Does anyone have an idea on what causes the above error or better yet, what it means? Patti Clark Unix System Administrator Office of Scientific and Technical Information Note: To sign off this list, send a "signoff networker" command via email should be sent to stan < at > temple.edu Mon Oct 18, 2004 10:16 am Mark Dokter Guest RAP error: Unable to extract resource info for client myclie We have the same issue's here. Looked with arp -a while running a backup. The ip-adress-mac-adress translation is completly corrupt. Backup requist were send to the wrong systems. Rebooted the backup server and every thing was ok again. It only happens on cluster clients (both unix and windows) when a failover had occured but not allways. We will have an ohter failover again and will do some more investigation. It looks

FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn http://www.tek-tips.com/viewthread.cfm?qid=1074263 Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on http://nsrd.moab.be/nwcr/jbverify.html members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML networker rap Markdown MediaWiki reStructuredText code below into your site. Legato back-up solutions Forum at Tek-Tips HomeForumsServer RackBack-up SystemsLegato back-up solutions Forum RAP error thread480-1074263 Forum Search FAQs Links MVPs RAP error RAP error ptitechatt (TechnicalUser) (OP) 9 Jun 05 11:45 I've a problem to save a linux client by a windows serverI've all my licence oki so it s not a licence pb!I've this error message:RAP error: Unable to extract networker rap error resource info for client Cannot open save session with I ve seen the same error in the forum bur it was for a Filer NetApp and there were no solution acceptable ... so if you have some ideas...I'm using networker 7.2 on the server and on the clientthanks RE: RAP error 605 (Instructor) 9 Jun 05 14:27 It looks like the server can not read the client's info from the resource files. Can you recreate it? RE: RAP error NWNinja (IS/IT--Management) 10 Jun 05 02:52 Do like this, it will most likely solve the problem, i have seen it many times. It is probably casued by cached data that is no longer valid.Do this on the client:1) Stop NetWorker2) Delete everything (files and folders) in ../nsr/tmp3) Start NetWorker4) Try the backup againYou will *problably* just need to do this on the client, butif it still doesn´t work, do the same thing on the backup server. If it still doesn´t work, you will need to delete the client and re-add it in NetWorker Admin.Hope it helps!Cheers! Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. Cancel Red Flag SubmittedThank yo

name ]... [ -l ] [ -M ] [ -n ] [ -N ] [ -P port ] [ -q ] [ -Q ] [ -r no. of retries ] [ -R ] [ -S slot ] [ -s server ] [ -t ] [ -U ] [ -v ]... [ -Z ] DESCRIPTION jbverify verifies the devices defined in the NetWorker database, making sure that each one of them is configured properly by checking them for accessibility and usability. To do this, jbverify makes use of Net- Worker processes and requires that the NetWorker server (nsrd) be run- ning on the server machine, and the NetWorker client (nsrexecd) be run- ning on the client machines. By default, jbverify checks all devices in the NetWorker database, but can be instructed to check only jukeboxes, only stand-alone drives or only local devices using the -j, -d and -l options respectively. Indi- vidual jukeboxes and drives can also be checked for by using the -J and -D options. Devices belonging to specific hosts can be checked using the -H option. For jukeboxes, jbverify ensures proper configuration by loading a tape into each drive and unloading them, without performing any write opera- tions on the tape. The only exception to this is if the -t option is used, explained below. A slot to be used for the test can be specified by using the -S option. If no slot is specified, jbverify goes through all the slots defined as available to NetWorker and loads the first one available. Apart from checking for accessibility and usability, jbverify can run a series of tests on tapes loaded into the drives being tested by calling on NetWorker's tapeexer program (see tapeexercise (1m)), when used with the -t option. Running tapeexercise involves writing to the tape to determine the tape drive's usability, so when -t is specified, any volume which has a Net- Worker label on it is immediately rejected as unusable and the next slot is tried. If there are no non-NetWorker tapes in any of the slots, jbverify exits without doing any tests. jbverify can be run on any storage node, and can be used to test any device on that storage node provided the device has been configured in NetWorker. When run on the NetWorker s