{"id":56,"date":"2010-06-28T15:41:44","date_gmt":"2010-06-28T13:41:44","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=56"},"modified":"2015-12-10T11:24:38","modified_gmt":"2015-12-10T10:24:38","slug":"mom-umgebung-und-lizenzen","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/06\/mom-umgebung-und-lizenzen\/","title":{"rendered":"MoM Umgebung und Lizenzen"},"content":{"rendered":"<p>In einer MoM Umgebung mit zentralisierter Medienmanagementdatenbank (CMMDB) werden die Lizenzen f\u00fcr Laufwerke komplett auf den Server \u00fcbertragen auf dem die CMMDB l\u00e4uft. In der Hilfe von Data Protector findet sich folgender Hinweis: <em>The centralized MMDB has a significant effect on licensing. Immediately after the MMDB is changed from local to remote, all the licenses associated with libraries and devices are taken (validated) from the MoM Manager and should be removed from client cells.<\/em> Das hei\u00dft das Lizenzen von Laufwerken und Libraries nicht im MoM verteilt werden d\u00fcrfen, da sonst unter Umst\u00e4nden Meldungen \u00fcber fehlende Lizenzen oder nicht gen\u00fcgend freie Laufwerke w\u00e4hrend einer Backupsession erscheinen. Alle anderen Lizenzen, wie zum Beispiel kapazitit\u00e4tsgebundene Lizenzen (Backup 2 Disk, ZDB\/IR) werden \u00fcber MoM auf die Zellen verteilt.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In einer MoM Umgebung mit zentralisierter Medienmanagement Datenbank gilt es besonders auf die Verteilung der Lizenzen zu achten&#8230;<\/p>\n<p><a class=\"excerpt-more\" href=\"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/06\/mom-umgebung-und-lizenzen\/\">Read More...<\/a><\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[11],"tags":[18,13,10],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"de","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":true},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-U","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":2095,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/08\/add-licenses-data-protector\/","url_meta":{"origin":56,"position":0},"title":"How to add licenses in Data Protector","date":"25. August 2014","format":false,"excerpt":"{:en}There are different ways to add licenses into Data Protector. Copy and paste the license file generated on the licensing portal (http:\/\/www.webware.hp.com) as ...\/Config\/Server\/cell\/lic.dat Copy and paste of a single or several licenses keys into exisiting lic.dat Copy and paste of a single license key using the Data Protector GUI\u2026","rel":"","context":"In &quot;BASICS&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":884,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/03\/drive-licenses\/","url_meta":{"origin":56,"position":1},"title":"Drive Licenses","date":"8. M\u00e4rz 2012","format":false,"excerpt":"{:de}Ein beliebtes Thema und immer wieder angefragt: Welche Lizenzen muss ich f\u00fcr Laufwerke verwenden wenn eine FC Library f\u00fcr das Backup im Windows \/ Linux Umfeld an einem (1!) Server genutzt wird? Die Antowrt ist eigentlich einfach: Solange die Laufwerke nicht von verschiedenen Servern angesprochen werden und im Data Protector\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2038,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/07\/data-protector-9-00-new\/","url_meta":{"origin":56,"position":2},"title":"Data Protector 9 &#8211; Initial Release (Build 87)","date":"8. Juli 2014","format":false,"excerpt":"{:en}Data Protector 9.00 has been released. The new version delivers new features: \"Federated Catalyst\" and \"Non-Staged recovery using GRE for VMware vSphere\". For customers with a valid support contract, the new version can be downloaded here: http:\/\/support.openview.hp.com. Customers using an older version of Data Protector (Pre-8.XX) will require new licenses\u2026","rel":"","context":"In &quot;DP A.09.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1710,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/01\/data-protector-8-10-whats-new\/","url_meta":{"origin":56,"position":3},"title":"Data Protector 8.10 available &#8211; whats new?","date":"7. Januar 2014","format":false,"excerpt":"{:en}Data Protector 8.10 has been released. The new version delivers some new features, my favorites are the new advanced scheduler and the file-system backup, which can be resumed. For customers with a valid support contract, the new version can be downloaded here: http:\/\/support.openview.hp.com. With Data Protector 8.1 new licenses are\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":694,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":56,"position":4},"title":"Data Protector Migration Unix to other OS","date":"29. Juli 2011","format":false,"excerpt":"{:de}Ich kenne nicht viele gute Gr\u00fcnde warum man eine Data Protector Installation von HP-UX auf ein anderes Betriebssystem wechseln sollte,\u00a0dennoch gibt es viele Kunden die diesen Schritt gehen wollen und zum Beispiel auf Windows oder Linux wechseln;\u00a0meist noch verbunden mit einem Upgrade auf eine aktuelle Version von Data Protector.\u00a0Und hier\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3004,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/07\/runbook-migrate-data-protector-7-0x-data-protector-9-0x\/","url_meta":{"origin":56,"position":5},"title":"RUNBOOK \u2013 Migrate Data Protector 7.0x to Data Protector 9.0x","date":"5. Juli 2016","format":false,"excerpt":"{:en} Update 2016\/0705: In section installation source it was recommended to use a patched installation source for the upgrade. This method must not be used for upgrades from Data Protector versionen 8.13 and newer, as it will cause serious damages in the internal database (no fix available\/possible). For versions older\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/56"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/comments?post=56"}],"version-history":[{"count":4,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/56\/revisions"}],"predecessor-version":[{"id":2764,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/56\/revisions\/2764"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=56"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=56"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=56"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}