Nachfolgend findet ihr n\u00fctzliche Data Protector Befehle auf einem Blick, der Artikel wird immer mal wieder aktualisiert und erweitert werden…<\/p>\n
01. Stoppt, startet und fragt den Status der Dienste ab – 02.Stoppen des Schedulers – Unix – 03. Anzeigen von gelockten Laufwerken in einer MoM Umgebung – 04. Zero Downtime Backup – Synchronisieren der SMI-S DB: Nachfolgend findet ihr n\u00fctzliche Data Protector Befehle auf einem Blick, der Artikel wird immer mal wieder aktualisiert und erweitert werden… 01. Stoppt, startet und fragt den Status der Dienste ab – omnisv -stop, omnisv -start, omnisv -status 02.Stoppen des Schedulers – Unix – omnitrig -stop 03. Anzeigen von gelockten Laufwerken in einer MoM Umgebung – […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[1],"tags":[8,10,9],"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\/s28cjj-commands","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":150,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/07\/reorganisation-der-internen-datenbank\/","url_meta":{"origin":42,"position":0},"title":"Internal Database error – reorganize your IDB","date":"15. Juli 2011","format":false,"excerpt":"{:en}Update: There are still a lot of old Data Protector installations (version 6.0, 6.1) and in all cases I've seen there is still the old errror described below. Thats why I updated and enhanced this article from August 2010. When updating from a former Data Protector (5.X to 6.0 to\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":62,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/06\/export-import\/","url_meta":{"origin":42,"position":1},"title":"Export \/ Import","date":"28. Juni 2010","format":false,"excerpt":"{:en}No translation for this article available.{:} {:de} Immer wieder mal findet man Anleitungen wie ein Export \/ Import der internen Datenbank von Data Protector vorzunehmen ist. Diese Prozedur wird immer dann eingesetzt wenn Probleme in der Datenbank auftreten (korrupte Medien, ...) - Stichwort Healthcheck und omnidbcheck. Bei der nachfolgenden Prozedur\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4340,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/09\/appserver-issues-when-upgrading-to-10-x\/","url_meta":{"origin":42,"position":2},"title":"AppServer Probleme beim Upgrade auf 10.x beheben","date":"26. September 2018","format":false,"excerpt":"{:en}The AppServer has become an integral part of Data Protector. When it fails neither user authentication, scheduling or reporting will work. A critical issue has been identified that may cause upgrades to fail and\/or run-time issues caused by invalid data stored in the jce_service_description and jce_service_property tables in the Data\u2026","rel":"","context":"In "Advisory"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3262,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/12\/migrate-dp-9-0x-dp-9-0x-hardware-microsoft-windows\/","url_meta":{"origin":42,"position":3},"title":"Migrate DP 9.0X to DP 9.0X using new hardware and Microsoft Windows","date":"8. Dezember 2016","format":false,"excerpt":"{:en}I already wrote several articles on how to migrate the internal database to a new hardware, new Data Protector version, or new operating system (see link). With the introduction of PostgreSQL as internal database for Data Protector and compared to previous versions (DP 6 and DP 7), some more steps\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"writedb","src":"https:\/\/i1.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/12\/writedb.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1892,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/03\/migrate-dp-8-xx-dp-8-xx-hardware-ms-windows-operating-system\/","url_meta":{"origin":42,"position":4},"title":"Migrate DP 8.XX to DP 8.XX using new hardware or different MS Windows operating system","date":"26. M\u00e4rz 2014","format":false,"excerpt":"{:en}The migration of the internal database to new hardware or to a new Microsoft Windows operating system was no big deal in the past and before the release of Data Protector 8.xx. With the introduction of PostgreSQL as the new internal database this has been changed and several steps are\u2026","rel":"","context":"In "HowTo"","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":42,"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 "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/42"}],"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=42"}],"version-history":[{"count":11,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/42\/revisions"}],"predecessor-version":[{"id":2765,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/42\/revisions\/2765"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=42"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=42"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=42"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}omnisv -stop, omnisv -start, omnisv -status<\/code><\/strong><\/p>\nomnitrig -stop<\/code><\/strong><\/p>\nomnidbutil -show_locked_devs -all<\/code><\/strong> Mit Data Protector 6.11 und aktuellen Patches funktioniert der Befehl omnidbutil -show_locked_devs<\/code><\/strong> nicht mehr, es ist ein -all<\/code><\/strong> anzuf\u00fcgen um den Status aller momentan in Jobs genutzten Laufwerke zu erhalten.<\/p>\nomnidbsmis -sync -preview<\/code><\/strong> (Vorschau f\u00fcr die Synchronisation) und omnidbsmis -sync -force<\/code><\/strong> (f\u00fchrt die Synchronisation mit der Appliance durch) <\/p>\n","protected":false},"excerpt":{"rendered":"