{"id":1333,"date":"2013-04-15T20:13:07","date_gmt":"2013-04-15T19:13:07","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1333"},"modified":"2015-12-09T20:32:00","modified_gmt":"2015-12-09T19:32:00","slug":"changed-syntax-omnib2dinfo","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/04\/changed-syntax-omnib2dinfo\/","title":{"rendered":"Changed syntax for omnib2dinfo"},"content":{"rendered":"<p><b>omnib2dinfo:<\/b> Mit den letzten Patches f\u00fcr DP 7.01 vom 09.04.2013 wurde die Syntax f\u00fcr den Befehl <code>omnib2dinfo<\/code> ge\u00e4ndert. In vorherigen Versionen musste beim Aufrufen des Kommandos der Device Type und der Hostname mit angegeben werden, unabh\u00e4ngig davon ob es sich um den Software Store oder ein StoreOnce System handelt. Mit der neuen Version kann ein logischer Device Name angegeben werden. Zus\u00e4tzlich erm\u00f6glicht die \u00c4nderung das Ausf\u00fchren des Befehls auf dem Cell Server, statt auf einem Client mit installiertem Media Agent (Cell Server oder Client mit installiertem Media Agent).<\/p>\n<p>Neue Syntax:<\/p>\n<pre>\r\nomnib2dinfo -help | -h\r\nomnib2dinfo -version | -v\r\nomnib2dinfo -store_info -b2ddevice libraryname\r\nomnib2dinfo -list_stores -b2ddevice libraryname\r\nomnib2dinfo -list_objects -b2ddevice libraryname\r\nomnib2dinfo -get_server_properties -b2ddevice libraryname\r\n<\/pre>\n<p>Alte Syntax:<\/p>\n<pre>\r\nomnib2dinfo -help | -h\r\nomnib2dinfo -version | -v\r\nomnib2dinfo -list_stores -type=ObjectStore | StoreOnceSoftware (OS | SOS)\r\n                         -host=hostname\r\n                         [-port=portNumber]\r\n                         [-name=storeName]\r\n                         [-client=clientName]\r\nomnib2dinfo -list_objects -type=ObjectStore | StoreOnceSoftware (OS | SOS)\r\n                          -host=hostname\r\n                          [-port=portNumber]\r\n                          -name=storeName\r\n                          [-client=clientName]\r\nomnib2dinfo -get_server_properties -type=ObjectStore | StoreOnceSoftware (OS | SOS)\r\n                                   -host=hostname\r\n                                   [-port=portNumber]\r\n                                   [-client=clientName]\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>omnib2dinfo: Mit den letzten Patches f\u00fcr DP 7.01 vom 09.04.2013 wurde die Syntax f\u00fcr den Befehl omnib2dinfo ge\u00e4ndert. In vorherigen Versionen musste beim Aufrufen des Kommandos der Device Type und der Hostname mit angegeben werden, unabh\u00e4ngig davon ob es sich um den Software Store oder ein StoreOnce System handelt. Mit der neuen Version kann ein [&hellip;]<\/p>\n","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":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"de","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-lv","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1424,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/06\/storeonce-software-store-daily-maintenance\/","url_meta":{"origin":1333,"position":0},"title":"StoreOnce Software Store &#8211; daily maintenance","date":"6. Juni 2013","format":false,"excerpt":"{:en}When in Data Protector media of a StoreOnce software store become expired, the used disk space is not released immediately. The disk space will be released once the media is overwritten or deleted. The housekeeping process running in the background to release the space will start only when the media\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1350,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/05\/connections-gateway-storeonce-software-store\/","url_meta":{"origin":1333,"position":1},"title":"No available connections on gateway for StoreOnce Software Store","date":"7. Mai 2013","format":false,"excerpt":"{:en}When using the StoreOnce Software Store in Data Protector for jobs an error might be displayed: There are no available connections on gateway. This can occur when there are locked devices in the media managemt database of Data Protector. Normally the devices are released automatically or when the Data Protector\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1919,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/03\/omnispeed-2-0-data-protector-8-xx-hp-ux-linux-windows\/","url_meta":{"origin":1333,"position":2},"title":"OMNISPEED 2.0 for Data Protector 8.XX on HP-UX, Linux and Windows","date":"27. M\u00e4rz 2014","format":false,"excerpt":"{:en}The new version of OMNISPEED is available. Version 2.0 was especially developed for Data Protector 8.XX environments and supports HP-UX (Itanium) 11.31, Linux (RedHat and SUSE Linux Enterprise Server) and Microsoft Windows (2008 R2, 2012 and 2012 R2) for the Data Protector versions 8.00, 8.01 and 8.1X. The most important\u2026","rel":"","context":"In &quot;SCD&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2893,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/02\/data-protector-7-03-patches-build-108\/","url_meta":{"origin":1333,"position":3},"title":"Data Protector 7.03 Patches (Build 108)","date":"1. Februar 2016","format":false,"excerpt":"{:en}On 2016\/01\/29 HPE released new patches for Linux, Windows and HP-UX. As a requirement you need to have Patch Bundle 7.03 installed. It is strongly recommended to read the full description of each patch. If you own a valid support contract you can download the patch from https:\/\/softwaresupport.hp.com. For login\u2026","rel":"","context":"In &quot;DP A.07.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2262,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2015\/01\/data-protector-9-02-features-explained\/","url_meta":{"origin":1333,"position":4},"title":"Data Protector 9.02 features explained","date":"27. Januar 2015","format":false,"excerpt":"{:en} In December HP released the new Data Protector version 9.02. With this release additional features were implemented. Some of the new features are explained in more detail below. New Data Protector features: Pausing and Resuming Backup Jobs Reporting for Capacity Based Licensing VMware GRE for 3PAR Snapshots StoreOnce CoFC\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3016,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/05\/prepare-and-execute-eadr-cell-server-on-windows-2012-r2-data-protector-9-06\/","url_meta":{"origin":1333,"position":5},"title":"Prepare and execute EADR &#8211; Cell Server on Windows 2012 R2 and Data Protector 9.06","date":"13. Mai 2016","format":false,"excerpt":"{:en} In the past I often informed about the free EADR feature in Data Protector to recover clients and cell server. The last time I wrote an article in 2014 including two small scripts to get things prepared and automated - see https:\/\/www.data-protector.org\/wordpress\/2014\/04\/eadr-cell-server-dp-8-1x-windows-2012-r2\/. However, the batch files got broken due\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"EADR_23","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/05\/EADR_23.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1333"}],"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=1333"}],"version-history":[{"count":7,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1333\/revisions"}],"predecessor-version":[{"id":2664,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1333\/revisions\/2664"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1333"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1333"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1333"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}