{"id":2319,"date":"2010-06-23T07:38:05","date_gmt":"2010-06-22T21:38:05","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=2319"},"modified":"2018-12-11T18:39:02","modified_gmt":"2018-12-11T08:39:02","slug":"divorcing-nmc-from-networker","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2010\/06\/23\/divorcing-nmc-from-networker\/","title":{"rendered":"Divorcing NMC from NetWorker"},"content":{"rendered":"<p>The classic NetWorker install will see:<\/p>\n<ul>\n<li>A bunch of clients<\/li>\n<li>Optional storage nodes and\/or dedicated storage nodes<\/li>\n<li>The NetWorker server<\/li>\n<li>The NetWorker Management Console server running on the NetWorker server<\/li>\n<\/ul>\n<p>Architecturally, there&#8217;s no reason why you <em>have<\/em> to have the NetWorker Management Console server running on the backup server itself. Both logically and architecturally, there are good reasons why you would choose to keep these separate. Let&#8217;s start by using a diagram to show how the alternate architecture looks:<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2010\/06\/split-console.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2320\" title=\"Divorcing NetWorker Management Console Server from Backup Server\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2010\/06\/split-console.jpg\" alt=\"Divorcing NetWorker Management Console Server from Backup Server\" width=\"614\" height=\"706\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2010\/06\/split-console.jpg 614w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2010\/06\/split-console-260x300.jpg 260w\" sizes=\"auto, (max-width: 614px) 100vw, 614px\" \/><\/a><\/p>\n<p>So, what are the advantages of this sort of layout? There&#8217;s three distinct advantages:<\/p>\n<ul>\n<li><strong>Feature access<\/strong> \u2013 in my experience the vast majority of backup administrators are conservative in their approach to the technology in use. This means that there&#8217;s a slow-ramping process for adoption of new backup server software. While some users will hop on the bandwagon straight away, others will wait for a while. The momentum eventually builds up, but it takes a while to get there. In the meantime though, we periodically encounter situations where the features in the latest version of NMC <em>are<\/em> highly desirable. For instance, the unified monitoring provided in the version of NMC that comes with NetWorker 7.6 should appeal to just about every NetWorker administrator out there. If the NMC server and the NetWorker server are one and the same machine, it makes rolling out a new version of NMC while keeping the old version of NetWorker practically impossible. On the other hand, if the NMC server and the NetWorker server aren&#8217;t the same machine, it&#8217;s trivial to upgrade a single client to the latest version of NetWorker and NMC.<\/li>\n<li><strong>Performance<\/strong> \u2013 in small environments, the footprint of the NMC server creates negligible additional load on the backup server. As the number of clients and simultaneously active savesets ramps up though, the load of the NMC server \u2013 particularly with multiple accessing consoles \u2013 the impact of running the NetWorker Management Console server on the backup server <em>can<\/em> be observed. By keeping these hosts separate, the problem does not happen.<\/li>\n<li><strong>Protection<\/strong> \u2013 the NMC server has become considerably more stable over its lifetime, but like all software, there are no guarantees that it is crash proof. If the NMC server isn&#8217;t running on the same host as the backup server, then it gives you the advantage of being able to reboot the NMC server should there be an issue with monitoring, without impacting the actual backup server itself. In actual fact, keeping systems separate that don&#8217;t <em>need<\/em> to be together gives you better options for fault handling, upgrades and scheduled maintenance.<\/li>\n<\/ul>\n<p>Assuming you want to run the NMC server as a separate host to the NetWorker server, it&#8217;s really quite easy:<\/p>\n<ul>\n<li>Using either nsradmin or the existing NMC install on the backup server, modify NetWorker&#8217;s Administrator user group to include administrators from the NMC server.<\/li>\n<li>Install the NMC server and NetWorker client software on the intended host. (If on Unix, I always recommend also installing the NetWorker man pages. You never know when you&#8217;ll need them.) Be sure to allow NetWorker to setup the NMC backup instance if you want your database backed up and aren&#8217;t sure how to configure this manually.<\/li>\n<li>Shutdown NMC on your backup server and configure it to not automatically start up. If necessary you can start it later to retrieve historical reports &#8211; otherwise you can leave it there installed, but not running, to avoid confusion.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The classic NetWorker install will see: A bunch of clients Optional storage nodes and\/or dedicated storage nodes The NetWorker server&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_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}},"categories":[3,16],"tags":[],"class_list":["post-2319","post","type-post","status-publish","format-standard","hentry","category-architecture","category-networker"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pKpIN-Bp","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/2319","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/comments?post=2319"}],"version-history":[{"count":1,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/2319\/revisions"}],"predecessor-version":[{"id":7552,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/2319\/revisions\/7552"}],"wp:attachment":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/media?parent=2319"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/categories?post=2319"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/tags?post=2319"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}