If you’re using a modern NetWorker environment, the chances are that you’ll periodically notice entries such as the following in the daemon.log \/ daemon.raw files on the backup server:<\/p>\n
39078 02\/02\/2009 09:45:13 PM\u00a0 0 0 2 1152952640 5095 0 nox nsrexecd SYSTEM error: There is already a machine using the name: “faero”. Either choose a different name for your machine, or delete the “NSR peer information” entry for “faero” on host: “nox” <\/em><\/p>\n While this may look confronting, it’s actually a trivially easy error to fix that requires just a minute or so of your time with nsradmin. First, note the client that the error is about<\/em>, and the client that the error is being recorded from<\/em>. In this case, the error is about the client faero<\/em>, while the error is being registered against the host nox<\/em>.<\/p>\n To fix, run up nsradmin against the client<\/em> service on nox<\/em>:<\/p>\n (alternatively, you can use: nsradmin -p 390113 -s nox)<\/p>\n At the nsradmin> prompt, enter the command:<\/p>\n And answer yes when prompted to confirm. For example, the session might resemble the following:<\/p>\n There, you’ve done it. Note that you should<\/em> be periodically scanning your daemon raw\/log files for errors and trying to eliminate them. The goal should be that any error or warning reported in the file is something that you do<\/em> need to worry about\/investigate, rather than having a lot of “false positives” floating around in the system.<\/p>\n [Update, 2009-05-12]<\/strong><\/p>\n I thought I’d mention that one of the most common times I see these warnings occur is after I’ve uninstalled\/reinstalled NetWorker on a client, as opposed to having upgraded. Since on some clients it’s more or less necessary to uninstall\/reinstall rather than upgrade, that helps to understand why the information is lost periodically. My surmise is that on a new install, the NetWorker client processes generate a new ‘certificate’ or ‘identity’. As this new information conflicts with existing information the backup server has on the client, that’s what triggers the error.<\/p>\n It could be that other factors can cause this, but it seems that this is at least a primary cause.<\/p>\n","protected":false},"excerpt":{"rendered":" If you’re using a modern NetWorker environment, the chances are that you’ll periodically notice entries such as the following in…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[6,16,20],"tags":[54,650,653,659],"class_list":["post-172","post","type-post","status-publish","format-standard","hentry","category-basics","category-networker","category-scripting","tag-54","tag-nsr-peer-information","tag-nsradmin","tag-nsrexec"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t# nsradmin -p nsrexec -s nox<\/pre>\n
delete type: NSR peer information; name: faero<\/pre>\n
nsradmin> delete type: NSR peer information; name: faero\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 type: NSR peer information;\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 administrator: root, \"user=root,host=nox\";\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 name: faero;\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 peer hostname: faero;\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Change certificate: ;\n\u00a0\u00a0\u00a0 certificate file to load: ;\nDelete? y\ndeleted resource id 17.0.83.117.0.0.0.0.210.37.85.73.0.0.0.0.10.0.0.1(1)<\/pre>\n