{"id":6195,"date":"2017-03-27T17:30:20","date_gmt":"2017-03-27T07:30:20","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=6195"},"modified":"2018-12-11T09:58:07","modified_gmt":"2018-12-10T23:58:07","slug":"data-protection-licensing","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2017\/03\/27\/data-protection-licensing\/","title":{"rendered":"Data protection licensing"},"content":{"rendered":"<p>I&#8217;d like to take a little while to talk to you about licensing.&nbsp;I know it&#8217;s&nbsp;not normally&nbsp;considered an&nbsp;<em>exciting<\/em> subject (usually at best people think of it as a <em>necessary-evil<\/em>&nbsp;subject), but I&nbsp;think it&#8217;s common to see&nbsp;businesses not take full advantage of the potential data protection licensing available to them from Dell EMC. Put it this way: I think&nbsp;if you take the time to read this post about licensing, you&#8217;ll come away&nbsp;with some thoughts on how you might be able to expand&nbsp;a backup system to a full data protection system just thanks to some very handy licensing options&nbsp;available.<\/p>\n<p>When I first started using NetWorker,&nbsp;the only licensing model was what I&#8217;d refer to as&nbsp;<em>feature based<\/em> licensing. If you wanted to do X, you&nbsp;bought a license that specifically enabled NetWorker to do X. The sorts of licenses you would use included:<\/p>\n<ul>\n<li>NetWorker Base Enabler \u2013 To enable the actual base&nbsp;server itself<\/li>\n<li>OS enablers \u2013 Called &#8220;ClientPack&#8221; enablers, these would let you backup operating systems other than the operating system of the NetWorker server itself (ClientPack for Windows, ClientPack for Unix, ClientPack for Linux, etc).<\/li>\n<li>Client Count enablers \u2013&nbsp;Increasing the number of&nbsp;clients you can backup<\/li>\n<li>Module enablers \u2013 Allowing you to say, backup Oracle, or SQL, or Exchange, etc.<\/li>\n<li>Autochanger enablers \u2013 Allowing you to connect autochangers of a particular slot count (long term NetWorker users will remember short-slotting too&#8230;)<\/li>\n<\/ul>\n<p>That&#8217;s a small&nbsp;excerpt of the types of licences you might have deployed. Over time, some licenses got simplified or even removed \u2013&nbsp;the requirement for ClientPack enablers for instance were dropped quite some time ago, and the database licenses were simplified by being condensed into licenses for Microsoft databases (NMM) and licenses for databases and applications (NMDA).<\/p>\n<p>Feature based licensing is, well, confusing.&nbsp;I&#8217;d go so far as to suggest it&#8217;s anachronistic. As a long-term NetWorker user, I occasionally get asked&nbsp;what a feature based licensing set might look like, or what might be required to achieve X, and even for me, having dealt with feature based licenses for&nbsp;20 years, it&#8217;s not fun.<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/2017\/03\/27\/data-protection-licensing\/decision-making-crisis\/\" rel=\"attachment wp-att-6196\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-6196\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/bigStock-Confused.jpg\" alt=\"bigStock Confusion\" width=\"867\" height=\"900\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/bigStock-Confused.jpg 867w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/bigStock-Confused-289x300.jpg 289w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/bigStock-Confused-768x797.jpg 768w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/bigStock-Confused-24x24.jpg 24w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/bigStock-Confused-36x36.jpg 36w\" sizes=\"auto, (max-width: 867px) 100vw, 867px\" \/><\/a><\/p>\n<p>The problem \u2013 and it&#8217;s actually a serious one \u2013 with feature based licensing is you&nbsp;typically remain locked, for whatever your minimum budget cycle&nbsp;is, into what your backup functionality is.&nbsp;Every new&nbsp;database, set of clients, backup device or special requirement has to be planned well&nbsp;in advance to make sure you have the&nbsp;licenses you need. How often is that really the case?&nbsp;I&#8217;m into my 21st year of working with backup and I still regularly hear stories of new&nbsp;systems or projects coming&nbsp;on-line without full consideration of the data protection requirements.<\/p>\n<p>In this modern age of datacentre infrastructure where the absolute requirement is&nbsp;<em>agility<\/em>, using feature-based licensing is like trying to run on a treadmill that&#8217;s submerged waist-deep in golden syrup.<\/p>\n<p>There was, actually, one other type of NetWorker licensing back then \u2013 in the &#8216;old days&#8217;, I guess I can say: an Enterprise&nbsp;license. That enabled everything in one go, but required yearly audits to ascertain usage and appropriate maintenance costs, etc. It enabled convenient use but from a price perspective it only suited upper-echelon businesses.<\/p>\n<p>Over time to assist with providing licensing agility, NetWorker got a second&nbsp;license type \u2013&nbsp;<em>capacity<\/em> licensing. This&nbsp;borrowed the &#8220;unlimited features&#8221; aspect of enterprise-based licensing,&nbsp;and worked on the basis of what&nbsp;we refer to as FETB \u2013 Front End TB.&nbsp;The simple summary of FETB is &#8220;if you did a full backup of everything you&#8217;re protecting, how big would it be?&#8221; (In fact, various white-space components are typically stripped out \u2013 a 100 GB virtual machine for instance that&#8217;s thickly provisioned but only using 25GB would effectively be considered to contribute just 25 GB to the capacity.)<\/p>\n<p>The beauty of the capacity license scheme is that it doesn&#8217;t matter&nbsp;<em>how many copies<\/em> you generate of your&nbsp;data. (An imaginary BETB (&#8220;Back End TB&#8221;) license would be unpleasant in the extreme \u2013 limiting you to the total stored&nbsp;capacity of your backups.) So that FETB license applies regardless of whether you just keep all your backups for 30 days, or whether you keep all your backups for 7 years. (If you keep all your backups for 7 years, <a href=\"https:\/\/nsrd.info\/blog\/2017\/03\/22\/what-queen-can-teach-us-about-long-term-retention\/\" target=\"_blank\">read this<\/a>.)<\/p>\n<p>A FETB lets you&nbsp;adjust your backup functionality as the business changes around you. Someone deploys Oracle but you&#8217;ve only had to backup SQL Server before? Easy, just install&nbsp;NMDA and start backing Oracle up. The business makes the strategic decision to switch from Hyper-V to VMware? No problem \u2013 there&#8217;s nothing to change from a licensing perspective.<\/p>\n<p>But, as I say <a href=\"https:\/\/www.amazon.com\/Data-Protection-Ensuring-Availability\/dp\/1482244152\" target=\"_blank\">in my book<\/a>, backup and recovery, as a standalone topic is dead.&nbsp;That&#8217;s why Dell EMC has licensing around&nbsp;<em>Data Protection Suite<\/em>. In fact, there&#8217;s a few different options to suit different tiers of organisations. If you&#8217;ve not heard of Data Protection Suite licensing,&nbsp;you&#8217;ve quite possibly been missing out on a wealth of opportunities for&nbsp;your organisation.<\/p>\n<p>Let&#8217;s start with the first variant that was introduced,&nbsp;<em>Data Protection Suite for Backup<\/em>. (In fact, it was&nbsp;originally just Data Protection Suite.)&nbsp;DPS for Backup has been expanded as other products have been released, and now includes:<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/2017\/03\/27\/data-protection-licensing\/dps-for-backup\/\" rel=\"attachment wp-att-6201\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-6201\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Backup.jpg\" alt=\"DPS for Backup\" width=\"494\" height=\"481\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Backup.jpg 494w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Backup-300x292.jpg 300w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Backup-24x24.jpg 24w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Backup-36x36.jpg 36w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Backup-48x48.jpg 48w\" sizes=\"auto, (max-width: 494px) 100vw, 494px\" \/><\/a><\/p>\n<p>Think about that \u2013 from a single wrapper&nbsp;license (DPS for Backup), you get access to <strong>6 products<\/strong>. Remember before when&nbsp;I said the advantage of NetWorker capacity licensing over&nbsp;&#8216;feature&#8217; licensing was the ability&nbsp;to adapt to changes in the business requirements for backup? This sort of license expands on that ability even more so. You might start today using NetWorker to protect your environment, but in a year&#8217;s time your business&nbsp;needs to setup some remote offices that are best served by Avamar. With DPS for Backup, you don&#8217;t need to go and buy Avamar licenses, you just deploy Avamar. Equally,&nbsp;the strategic decision might be made to give DBAs full control over&nbsp;<em>their<\/em> backup processes, so it makes sense to give them access to shared protection&nbsp;storage via Data Domain Boost for Enterprise&nbsp;Applications (DDBEA), instead of needing&nbsp;to be configured for manual backups in NetWorker. The business&nbsp;could decide to start pushing some&nbsp;long term backups from NetWorker out to Cloud object storage \u2013 that&#8217;s easy, just deploy a CloudBoost virtual machine&nbsp;<em>because you can<\/em>. You&nbsp;can mix and match your licenses as you need. Just as importantly, you can deploy Data Protection Advisor at the business layer to provide centralised reporting and monitoring across the entire gamut, and&nbsp;you can take advantage of <a href=\"https:\/\/www.youtube.com\/watch?v=C8YVoq92Ee0\" target=\"_blank\">Data Protection Search<\/a> to easily find&nbsp;content regardless&nbsp;of whether it was&nbsp;NetWorker or Avamar that protected it.<\/p>\n<p>Data Protection Suite for Backup is licensed \u2013 like the NetWorker Capacity model \u2013 via FETB. So if you license for say, 500 TB, you can slice and dice that however you&nbsp;need between NetWorker, Avamar and DDBEA, and get CloudBoost, DPA and DP-Search rolled in. Suddenly your&nbsp;backup solution is a much broader data protection solution,&nbsp;just thanks to a license model!<\/p>\n<p>If you&#8217;re not&nbsp;an existing&nbsp;NetWorker or Avamar site, but you&#8217;re looking for some&nbsp;increased efficiencies in your application backups\/backup storage, or a reduction in the capacity licensing for another product, you might instead be interested in&nbsp;DPS for Applications:<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/2017\/03\/27\/data-protection-licensing\/dps-for-applications\/\" rel=\"attachment wp-att-6203\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-6203\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Applications.jpg\" alt=\"DPS for Applications\" width=\"496\" height=\"396\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Applications.jpg 496w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Applications-300x240.jpg 300w\" sizes=\"auto, (max-width: 496px) 100vw, 496px\" \/><\/a><\/p>\n<p>Like DPS for Backup, DPS for Applications is a FETB capacity license. You get to deploy Boost for Enterprise Apps and\/or ProtectPoint to suit your requirements, you get Data Protection Advisor to report on your protection status, and you also get the option to&nbsp;deploy Enterprise Copy Data Management (eCDM). That lets you set policies on&nbsp;application&nbsp;protection \u2013 e.g., &#8220;There must always be 15 copies of this&nbsp;database&#8221;. The&nbsp;application administration team can remain in charge of backups, but to assuage business requirements, policies can be established to ensure systems are still adequately protected. And ProtectPoint:&nbsp;whoa, we&#8217;re talking serious speed there. Imagine backing up a 10TB or 50TB database, not&nbsp;20% faster, but 20 <em>times<\/em> faster. That&#8217;s&nbsp;ProtectPoint \u2013 Storage Integrated Data&nbsp;Protection.<\/p>\n<p>Let&#8217;s say you&#8217;re an ultra-virtualised business. There&#8217;s&nbsp;few, if any, physical systems left, and you don&#8217;t&nbsp;want to think of your data protection licensing in terms of FETB, which might be quite variable \u2013 instead, you want to look at a socket based licensing count. If that&#8217;s the case, you probably want to look at Data&nbsp;Protection Suite for Virtual Machines:<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/2017\/03\/27\/data-protection-licensing\/dps-for-virtual-machines\/\" rel=\"attachment wp-att-6204\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-6204\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Virtual-Machines.jpg\" alt=\"DPS for Virtual Machines\" width=\"494\" height=\"396\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Virtual-Machines.jpg 494w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Virtual-Machines-300x240.jpg 300w\" sizes=\"auto, (max-width: 494px) 100vw, 494px\" \/><\/a><\/p>\n<p>DPS for Virtual Machines is&nbsp;targeted for the small to medium end of town&nbsp;to meet their data protection requirements in a richly functional way.&nbsp;On a per socket (<em>not<\/em> per-core)&nbsp;license model, you get to protect&nbsp;your virtual infrastructure (and, if you need to, a few physical servers) with Avamar, using image based and agent-based backups in whatever mix is required. You also get <a href=\"https:\/\/www.youtube.com\/watch?v=nNKsmc5f0XE\" target=\"_blank\">RecoverPoint for Virtual Machines<\/a>. RecoverPoint gives you DVR-like&nbsp;Continuous Data&nbsp;Protection that&#8217;s completely storage independent, since it operates at the&nbsp;hypervisor layer.&nbsp;Via an advanced journalling&nbsp;system, you get to deliver very tight SLAs back to the business with RTOs and RPOs in the seconds or minutes, something that&#8217;s almost impossible with just standard backup. (You can literally choose to roll back virtual machines on an IO-by-IO basis. Or spin up testing\/DR copies using the same criteria.)&nbsp;You also get DPA and DP-Search, too.<\/p>\n<p>There&#8217;s a Data&nbsp;Protection Suite for archive bundle as well if your requirements are purely archiving based. I&#8217;m going to skip that for the moment so I can talk about the final licensing bundle that gives you unparalleled flexibility for establishing a full data protection&nbsp;strategy for your&nbsp;business; that&#8217;s Data&nbsp;Protection Suite for Enterprise:<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/2017\/03\/27\/data-protection-licensing\/dps-for-enterprise\/\" rel=\"attachment wp-att-6205\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-6205\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Enterprise.jpg\" alt=\"DPS for Enterprise\" width=\"494\" height=\"821\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Enterprise.jpg 494w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/03\/DPS-for-Enterprise-181x300.jpg 181w\" sizes=\"auto, (max-width: 494px) 100vw, 494px\" \/><\/a><\/p>\n<p>Data Protection Suite for Enterprise returns to&nbsp;the FETB model but it gives you ultimate flexibility. On top of it all you again get Data Protection Advisor and Data Protection Search, but then you get a raft of&nbsp;data protection and archive functionality, all again in a single&nbsp;bundled consumption model:&nbsp;NetWorker, Avamar, DDBEA, CloudBoost,&nbsp;RecoverPoint for Virtual Machines, ProtectPoint, AppSync, eCDM, and all the&nbsp;flavours of SourceOne. In terms of flexibility, you couldn&#8217;t ask for more.<\/p>\n<p>It&#8217;s easy when we work in backup to think only in terms of the&nbsp;main backup&nbsp;product we&#8217;re using, but there&#8217;s two things that have become&nbsp;urgently apparent:<\/p>\n<ul>\n<li><strong>It&#8217;s not longer&nbsp;just about backup<\/strong> \u2013 To stay relevant, and to deliver value and results back to the business, we need to be thinking about&nbsp;<em>data protection strategies<\/em> rather than&nbsp;<em>backup and recovery<\/em> strategies. (If you want proof of that change from my perspective, think of my first book title vs the second \u2013 the first was &#8220;Enterprise Systems&nbsp;Backup and Recovery&#8221;, the second, &#8220;Data Protection&#8221;.)<\/li>\n<li><strong>We need to be more agile than &#8220;next budget cycle&#8221;<\/strong> \u2013 Saying you can&#8217;t do anything to protect a&nbsp;newly emerged or altering workload until you get budget&nbsp;<em>next year<\/em> to do it is just a recipe for disaster. We&nbsp;need, as data&nbsp;protection professionals, to be able to pick the appropriate tool for each workload and get it operational&nbsp;<em>now<\/em>, not next month or next year.<\/li>\n<\/ul>\n<p>Licensing: it may on the outset appear to be a boring topic, but I think it&#8217;s actually pretty damn exciting in what a flexible licensing policy like&nbsp;the Data Protection Suite allows you to offer back to your business. I hope you do too, now.<\/p>\n<hr>\n<p>Hey, you&#8217;ve made it this far, thanks! <a href=\"https:\/\/www.amazon.com\/Data-Protection-Ensuring-Availability\/dp\/1482244152\" target=\"_blank\">I&#8217;d love it if you bought my book, too<\/a>! (In Kindle format as well as&nbsp;paperback.)<\/p>\n<hr>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;d like to take a little while to talk to you about licensing.&nbsp;I know it&#8217;s&nbsp;not normally&nbsp;considered an&nbsp;exciting subject (usually at&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":true,"_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":[14],"tags":[134,1230,1351,1354,1355,342,1332,1236,1249,1277,1352,1353,913],"class_list":["post-6195","post","type-post","status-publish","format-standard","hentry","category-licensing","tag-avamar","tag-cloudboost","tag-data-protection-suite","tag-ddbea","tag-dp-search","tag-dpa","tag-ecdm","tag-licensing","tag-networker","tag-protectpoint","tag-recoverpoint","tag-recoverpoint-for-virtual-machines","tag-sourceone"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pKpIN-1BV","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/6195","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=6195"}],"version-history":[{"count":14,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/6195\/revisions"}],"predecessor-version":[{"id":7393,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/6195\/revisions\/7393"}],"wp:attachment":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/media?parent=6195"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/categories?post=6195"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/tags?post=6195"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}