To me the most valuable documents produced by EMC in relation to NetWorker or the modules are the Release Notes. These accompany any cited version update and typically contain at least the following chunks of information:<\/p>\n
This information is gold<\/em>. To anyone thinking of updating either a NetWorker server or a NetWorker module who isn’t planning on thoroughly reading the release notes first I say this: are you nuts?<\/em><\/p>\n I’m the first to admit that I don’t re-read the administration guides every time they are updated. There’s just too much content in them. Instead, I rely on the release notes to tell me what has been added, and if any of that is relevant to my needs, I go searching through the administration guides for said information. In fact, I consider the release notes important enough that they’re the only NetWorker documentation I ever print. Why do I print them? Because it means I can take them away from the computer and go sit down and read them carefully \u2013 very carefully.<\/p>\n The release notes don’t always contain all information about an update. They also may not fully elucidate on particular problems that have been fixed*.<\/p>\n To me the most important aspect to the release notes – the bit I check first, is the “Known problems and limitations”. Why? This is the bit that gives you the warnings of “things that don’t work”<\/em>, or “things that you may have to pay more attention to than you would otherwise think to”<\/em>. I.e., what is known<\/em> to not work. One would ignore these in particular at ones own peril.<\/p>\n So, next time you’re thinking of updating any part of your NetWorker environment, please, make sure you download and read the release notes.<\/p>\n — To me the most valuable documents produced by EMC in relation to NetWorker or the modules are the Release Notes.…<\/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":[16],"tags":[339,809],"class_list":["post-710","post","type-post","status-publish","format-standard","hentry","category-networker","tag-documentation","tag-release-notes"],"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
\n* I can attest to this when I review release notes and see LGTscABCDEF<\/em> numbers that have been created in response to bug filings I’ve made … a 2-3 line entry can’t convey all the details of sometimes complex, sometimes esoteric escalations.<\/p>\n","protected":false},"excerpt":{"rendered":"