{"id":5433,"date":"2015-02-02T18:33:35","date_gmt":"2015-02-02T08:33:35","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=5433"},"modified":"2018-12-11T13:02:54","modified_gmt":"2018-12-11T03:02:54","slug":"shared-data-domain-access","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2015\/02\/02\/shared-data-domain-access\/","title":{"rendered":"Shared Data Domain Access"},"content":{"rendered":"

If you’ve come from a tape library environment, you’re well aware the only way to share a tape library between multiple NetWorker datazones<\/em> \u2013 i.e., multiple NetWorker servers \u2013 is to use library partitioning. Thus, a 1000 slot library might be presented as 1 x 800 slot library and 1 x 200 slot library to the independent servers.<\/p>\n

But what happens when you’re using Data Domain? That’s considerably more flexible.<\/p>\n

\"Data<\/a><\/p>\n

If we look at basic Virtual Tape Libraries (VTLs), the answer is obvious: create as many VTLs as you need and present each one to a different NetWorker server. VTLs though, like their physical counterparts, suffer limitations that can make them impractical to use. You remain hampered by the number of drives provisioned in the library, and (far more importantly with VTL), you still can’t simultaneously write to a virtual tape and<\/em> read from it. Looking down to specific technologies, VTLs are also severely limited in a NetWorker environment now when you compare them against Boost functionality. You can’t for instance use a Data Domain VTL for instant access<\/a> or for granular Exchange recoveries. (Check out this post for more details of VTL vs Boost<\/a>.)<\/p>\n

You don’t have to use VTL to share a Data Domain between two or more NetWorker servers. Once you’ve configured Boost on a Data Domain, you can simply add the Data Domain to each NetWorker server you want to use it with, and a new Mtree will be automatically created for each NetWorker server as you create the first device on each.<\/p>\n

For instance, this Data Domain system has 3 NetWorker servers communicating with and using it:<\/p>\n

sysadmin@squeezebox# ddboost storage-unit show<\/strong>\nName      Pre-Comp (GiB)   Status\n-------   --------------   ------\ncentaur             74.5   RW    \ncyclops            181.8   RW    \nmedusa               6.6   RW    \n-------   --------------   ------\n D    : Deleted \n Q    : Quota Defined\n RO   : Read Only\n RW   : Read Write<\/pre>\n
One obvious advantage of using the same Data Domain system for multiple NetWorker servers is the deduplication still happens globally across all Mtrees. Thus, if you’ve got a production NetWorker environment and a test NetWorker environment, you can share a Data Domain between them and achieve a high deduplication rate, assuming your test environment is populated with copies of systems from your production environment.<\/p>\n
(With the new multi-tenancy support in DDOS 5.5 and higher, you’ve got the additional advantage of using potentially multiple Boost accounts, thereby segregating access between the NetWorker servers. While a NetWorker server won’t have access to an Mtree for another NetWorker server, a shared Boost user will<\/em>. Independent Boost users won’t.)<\/p>\n
There are of course a couple of caveats to this approach. Including the need to either use multi-tenancy on the Data Domain or<\/em> make sure you trust everyone who is simultaneously using it, you’ll need to consider the following:<\/p>\n
    \n
  • Performance<\/strong>:\n
      \n
    • You’ll want to make sure the systems are mutually compatible for performance requirements. Two large-scale production NetWorker environments might for instance have a greater risk of causing performance challenges than say, one large scale production environment and small to medium size lab environment.<\/li>\n<\/ul>\n<\/li>\n
    • Stream count<\/strong>:\n
        \n
      • Almost a subset of performance, but it warrants calling out independently \u2013 regardless of whether you’ve got one NetWorker server or fifty NetWorker servers using a Data Domain system, you still have to face the recommended hard high limits on stream counts from the Data Domain administration guides for any unit you’re using. With that in mind, you’ll likely want to use NetWorker’s pool<\/em> based parallelism settings to ensure there are hard limits established to the number of simultaneous savesets NetWorker can write.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
        Sharing a Data Domain between multiple NetWorker servers won’t be a solution for every environment, but if you’re limited for budget it’s something to keep in mind.<\/p>\n","protected":false},"excerpt":{"rendered":"
        If you’ve come from a tape library environment, you’re well aware the only way to share a tape library between multiple…<\/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":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[3,1181,16],"tags":[275,1208],"class_list":["post-5433","post","type-post","status-publish","format-standard","hentry","category-architecture","category-data-domain-2","category-networker","tag-data-domain","tag-sharing"],"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