{"id":5195,"date":"2014-06-30T15:12:57","date_gmt":"2014-06-30T05:12:57","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=5195"},"modified":"2014-06-30T15:12:57","modified_gmt":"2014-06-30T05:12:57","slug":"whats-new-in-8-2","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2014\/06\/30\/whats-new-in-8-2\/","title":{"rendered":"What&#8217;s new in 8.2?"},"content":{"rendered":"<p>NetWorker 8.2\u00a0entered Directed Availability (DA) status a couple of weeks ago. Between finishing up one job and looking for a new one,\u00a0I&#8217;d been a bit too busy to blog about 8.2 until now, so here goes&#8230;<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/06\/whats-new-in-8.2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5196\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/06\/whats-new-in-8.2.png\" alt=\"what's new in 8.2\" width=\"642\" height=\"243\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/06\/whats-new-in-8.2.png 642w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/06\/whats-new-in-8.2-300x113.png 300w\" sizes=\"auto, (max-width: 642px) 100vw, 642px\" \/><\/a><\/p>\n<p>First and foremost, NetWorker 8.2 brings some\u00a0additional functionality to\u00a0VBA. VBA was introduced as the new backup process in NetWorker\u00a08.1. Closely integrating\u00a0Avamar backup technologies, VBA leverages a special, embedded\u00a0virtual Avamar node to achieve high performance backup and recovery. Not only can policies be\u00a0defined in NMC for VBA can be assigned by a\u00a0VMware administrator in the vSphere Web Client,\u00a0\u00a0&#8230; so too can\u00a0image level backup and recovery operations be executed there. Of course, regularly scheduled backups are still controlled by NetWorker.<\/p>\n<p>That was the lay of\u00a0the land in 8.1 \u2013 8.2 reintroduces some of\u00a0the much-loved VADP\u00a0functionality, allowing for a graphical visualisation map of the virtual environment from within NMC.<\/p>\n<p>Continuing that Avamar\/VMware integration, NetWorker 8.2 also gets something that Avamar 7 administrators have had for a while \u2013\u00a0<em>instant-on<\/em> recoveries when backups are performed to Data Domain.\u00a0There&#8217;s also an emergency restore option to pull a VM back to an ESX host even if vCenter is unavailable, and greater granularity of virtual machine backups \u2013 individual VMDK files can be backed up and restored if necessary. For those environments where VMware administrators\u00a0aren&#8217;t meant to be starting\u00a0backups outside of\u00a0the policy schedules, there&#8217;s also the option now to turn off\u00a0<em>VBA Adhoc Backups<\/em> in NMC.<\/p>\n<p>Moving on from VMware, there&#8217;s some fantastic snapshot functionality in NetWorker 8.2. This is\u00a0something I&#8217;ve not yet had a\u00a0chance to play around with, but by all accounts, it&#8217;s off to a promising start and will continue to get deeper integration with NetWorker over time. Currently, NetWorker supports integrating with snapshot technologies\u00a0from Isilon, VNX, VNX2, VNX2e and NetApp, though the level of integration depends on what is available from each array. This new functionality is called\u00a0<em>NSM for NAS<\/em> (NetWorker Snapshot Management).<\/p>\n<p>The NSM integration allows NAS hosts to be integrated\u00a0as clients within NetWorker for policy management, whilst still working\u00a0from\u00a0the traditional &#8220;black box&#8221; scenario of NAS\u00a0systems not getting custom agents\u00a0installed. There&#8217;s a long list of\u00a0functionality, including:<\/p>\n<ul>\n<li>Snapshot discovery:\n<ul>\n<li>Finding snapshots\u00a0taken on the NAS outside of NetWorker&#8217;s control (either before integration, or by other processes)<\/li>\n<li>Facilitate roll-over and recovery from those snapshots (deleting isn&#8217;t available)<\/li>\n<li>Available as a scheduled task or via manual execution<\/li>\n<\/ul>\n<\/li>\n<li>Snapshot operations:\n<ul>\n<li>Create\u00a0snapshots<\/li>\n<li>Replication snapshots<\/li>\n<li>Move snapshots out to other storage (Boost, tape etc) using NDMP protocols<\/li>\n<li>Lifecycle\u00a0management of snapshots and replicas via retention policies<\/li>\n<li>Recover from snapshots<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Data Domain Boost integration gets a &#8230;\u00a0well, boost, with support for Data Domain&#8217;s\u00a0<em>secure multi-tenancy.<\/em>\u00a0This support scaling\u00a0for large systems designed for service providers, with up to 512\u00a0Boost devices supported per secure storage unit on the Data Domain. While previously there was a requirement for a single Data Domain Boost user account across all\u00a0Data Domain devices, this now allows for better tightening of access.<\/p>\n<p>One of my gripes with BBB (Block Based Backup) in NetWorker 8.1 has been addressed in 8.2 \u2013\u00a0if you&#8217;re stuck using ADV_FILE devices rather\u00a0than Data Domain, you can now perform\u00a0BBB even if the storage node being written to is\u00a0<em>not<\/em> Windows. Another time-saving option that was introduced in 8.1, Parallel Save Stream (PSS), has been extended to support Windows systems, and has also been updated to support Synthetic and Virtual Synthetic Fulls.\u00a0in 8.1 it had only supported Unix\/Linux, and only in traditional backup models.<\/p>\n<p>Continuing the trend towards storage nodes\u00a0being seen as a fluid rather than locked resource mapping, there&#8217;s now an\u00a0<em>autoselect storage node<\/em>\u00a0option, which if\u00a0enabled allows NetWorker to\u00a0select the storage node itself during backup and recovery operations. If this is enabled, it will override any storage node preferences assigned to individual clients, and NetWorker looks for local storage nodes wherever possible.<\/p>\n<p>There&#8217;s a few things that have left\u00a0NetWorker in 8.2, which are understandable: Support for\u00a0Windows XP, Windows 2003 and the Change Journal Manager. If you still\u00a0to\u00a0protect Windows XP or Windows Server 2003,\u00a0be sure to keep your installers for 8.1. and lower client software around.<\/p>\n<p>There&#8217;s some documentation updates in\u00a0NetWorker\u00a08.2 as well:<\/p>\n<ul>\n<li><strong>Server Disaster Recovery and Availability Best Practices<\/strong> \u2013 This describes the disaster recovery process for the NetWorker server, including best practices for ensuring you&#8217;re\u00a0<em>prepared<\/em> for a disaster recovery situation.<\/li>\n<li><strong>Snapshot Management for NAS Devices Integration<\/strong> \u2013 This documents the aforementioned\u00a0<em>NSM for NAS<\/em>\u00a0new feature of NetWorker.<\/li>\n<li><strong>Upgrading to NetWorker 8.2 from a Previous Release<\/strong> \u2013 This covers off in fairly comprehensive detail how you can upgrade your NetWorker environment to 8.2.<\/li>\n<\/ul>\n<p>In years gone by I&#8217;ve\u00a0found that documentation updates have been a lagging component of NetWorker, but that&#8217;s\u00a0long since disappeared.\u00a0With each new version of NetWorker now we&#8217;re\u00a0seeing\u00a0either\u00a0entirely new documents, or substantially enhanced documentation (or both). This speaks volumes of the commitment EMC has to NetWorker.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>NetWorker 8.2\u00a0entered Directed Availability (DA) status a couple of weeks ago. Between finishing up one job and looking for a&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":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[356,16],"tags":[1178,1050,1053],"class_list":["post-5195","post","type-post","status-publish","format-standard","hentry","category-emc","category-networker","tag-8-2","tag-update","tag-upgrade"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pKpIN-1lN","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/5195","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=5195"}],"version-history":[{"count":2,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/5195\/revisions"}],"predecessor-version":[{"id":5198,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/5195\/revisions\/5198"}],"wp:attachment":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/media?parent=5195"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/categories?post=5195"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/tags?post=5195"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}