In Data Protector wird die Schutzfrist des Bandes anhand des Sicherungsjobs und nicht wie oft gedacht f\u00fcr das Band festgelegt. Hierbei wird zwischen der „Data Protection“ und der „Catalog Protection“ unterschieden. „Data Protection“ gibt an wie lange die Daten auf dem Band gesch\u00fctzt bleiben, „Catalog Protection“ gibt an wie lange die Daten in der internen Datenbank vorgehalten werden. Diese Schutzfrist f\u00fcr die „Catalog Protection“ kann dabei unabh\u00e4ngig von der „Data Protection“ gesetzt werden, die Standardeinstellung in Data Protector ist gleich der „Data Protection“. Die Information \u00fcber den Katalog bleiben solange in der internen Datenbank bis die eingetragene Frist erreicht ist oder die „Data Protection“ endet und das Band \u00fcberschrieben wird. Zu beachten ist dass die Information \u00fcber den Katalog erst dann aus der internen Datenbank enfernt wird wenn alle Sicherungen auf dem Band keine Schutzfrist mehr haben. Die Einstellung eines h\u00f6heren Wertes f\u00fcr die „Catalog Protection“ macht deshalb nur dann Sinn, wenn die Schutzfrist auf permanent gesetzt wird, da in diesem Fall der Katalog erst entfernt wird wenn das Band gel\u00f6scht oder exportiert wird. Die Einstellung eines niedrigeren Wertes ist f\u00fcr gr\u00f6\u00dfere Umgebungen sinnvoll, da bei entsprechender Einstellung das Wachstum der internen Datenbank beeinflusst werden kann. Allerdings muss unter Umst\u00e4nden in diesem Fall f\u00fcr einen Restore erst die Kataloginformation erneut in die interne Datenbank importiert werden. F\u00fcr weiterf\u00fchrende Informationen zum Thema empfiehlt sich die Data Protector Hilfe –> Index: „catalog protection“.<\/p>\n","protected":false},"excerpt":{"rendered":"
In Data Protector wird die Schutzfrist des Bandes anhand des Sicherungsjobs und nicht wie oft gedacht f\u00fcr das Band festgelegt. Hierbei wird zwischen der „Data Protection“ und der „Catalog Protection“ unterschieden. „Data Protection“ gibt an wie lange die Daten auf dem Band gesch\u00fctzt bleiben, „Catalog Protection“ gibt an wie lange die Daten in der internen […]<\/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":[183],"tags":[184,185,186],"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-n2","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":114,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/07\/614039-no-more-space-in-any-of-the-detail-catalog-directories\/","url_meta":{"origin":1428,"position":0},"title":"[61:4039] No more space in any of the Detail Catalog directories","date":"7. Juli 2010","format":false,"excerpt":"{:en}The error [61:4039] could occur when the limit of the detail catalog is reached. In Data Protector 6.11 the size limit for a DCBF directory was increased up to 16 GB, in former versions the limit was set to 4 GB. For my customers I usually add at least addidtional\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":1428,"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":1354,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/05\/list-files-backed-catalog\/","url_meta":{"origin":1428,"position":2},"title":"List files backed up from catalog","date":"8. Mai 2013","format":false,"excerpt":"{:en}Have you ever asked yourself what have been backed up in a Data Protector job? In the internal database, within sessions you only see the objects done, however no information regarding backed up files and folders. You normally would see the files and folders when browsing to restore context or\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1320,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/03\/advisory-c03705726\/","url_meta":{"origin":1428,"position":3},"title":"Advisory c03705726","date":"26. M\u00e4rz 2013","format":false,"excerpt":"{:en}With document ID c03705726 on 2013\/03\/20 an advisory for HP Data Protector and 7.0 (7.01) was released, describing a problem when a backup was taken to a backup to disk device and in restore context of DP GUI the file size is displayed as zero. As a workaround the list\u2026","rel":"","context":"In "Advisory"","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":1428,"position":4},"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":[]},{"id":4315,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/09\/data-protector-10-updated-release-a-10-10-build-xxx\/","url_meta":{"origin":1428,"position":5},"title":"Data Protector 10 \u2013 Updated Release A.10.10 (Build 134)","date":"18. September 2018","format":false,"excerpt":"{:en}Data Protector\u00a0A.10.10 (Build 134)\u00a0has been released on September 17, 2018. The new version is another full install to simplify the upgrade and installation process.This will be the default for all future Data Protector versions. Data Protector 10.10 does not require any previous version to install the latest version of Data\u2026","rel":"","context":"In "DP A.10.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1428"}],"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=1428"}],"version-history":[{"count":3,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1428\/revisions"}],"predecessor-version":[{"id":2644,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1428\/revisions\/2644"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1428"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1428"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1428"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}