{"id":1354,"date":"2013-05-08T13:00:49","date_gmt":"2013-05-08T12:00:49","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1354"},"modified":"2015-12-09T19:03:21","modified_gmt":"2015-12-09T18:03:21","slug":"list-files-backed-catalog","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/list-files-backed-catalog\/","title":{"rendered":"List files backed up from catalog"},"content":{"rendered":"<p>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 when using &#8220;restore by query&#8221; function in Data Protector.<\/p>\n<p>With a simple command you now can retrieve the content of the backup done. The command queries the catalog of the internal database for a given session ID and object.<\/p>\n<p>The command I used: <code>omnidb -winfs server.demo.local:\/F \"server.demo.local [\/F]\" -session 2013\/04\/02-4 -catalog<\/code>.<\/p>\n<p>The output (cutted) is displayed below.<\/p>\n<p><b>Update:<\/b> If your session spawns one media only you might also use the command <code>omnimm -catalog < medium ><\/code> which delivers a similiar output. In GUI you could use the function &#8220;list from media&#8221; in restore context. <\/p>\n<pre>\r\nProtection    Owner    Group       Size    Time              Path\r\n===============================================================================\r\nd----w----       -2  nogroup          0  03.12.2012 11:04:11 \/Install\/NB\/8540p\/SWSetup\/\r\n----r-----       -2  nogroup     604672  27.04.2012 13:09:13 \/Install\/NB\/8540p\/sp48109.exe\r\n----r-----       -2  nogroup  266051536  27.04.2012 13:16:44 \/Install\/NB\/8540p\/sp53191.exe\r\n----r-----       -2  nogroup    8638840  27.04.2012 13:14:17 \/Install\/NB\/8540p\/sp53375.exe\r\n----r-----       -2  nogroup   23839856  27.04.2012 13:14:48 \/Install\/NB\/8540p\/sp53394.exe\r\n----r-----       -2  nogroup    4019352  27.04.2012 13:09:07 \/Install\/NB\/8540p\/sp53694.exe\r\n----r-----       -2  nogroup    9721920  27.04.2012 13:14:19 \/Install\/NB\/8540p\/sp53795.exe\r\n----r-----       -2  nogroup    8111712  27.04.2012 13:05:46 \/Install\/NB\/8540p\/sp53806.exe\r\n----r-----       -2  nogroup   28550392  27.04.2012 13:09:34 \/Install\/NB\/8540p\/sp54149.exe\r\n----r-----       -2  nogroup   22394016  27.04.2012 13:14:11 \/Install\/NB\/8540p\/sp54248.exe\r\n----r-----       -2  nogroup    9481856  27.04.2012 13:18:38 \/Install\/NB\/8540p\/sp54257.exe\r\n----r-----       -2  nogroup    4180808  27.04.2012 13:05:37 \/Install\/NB\/8540p\/sp54549.exe\r\n----r-----       -2  nogroup   81326552  27.04.2012 13:12:07 \/Install\/NB\/8540p\/sp54600.exe\r\n----r-----       -2  nogroup   48868760  27.04.2012 13:19:57 \/Install\/NB\/8540p\/sp54620.exe\r\n----r-----       -2  nogroup   28575632  27.04.2012 13:12:10 \/Install\/NB\/8540p\/sp54635.exe\r\n----r-----       -2  nogroup    6580120  27.04.2012 13:14:10 \/Install\/NB\/8540p\/sp54714.exe\r\n----r-----       -2  nogroup    2912216  27.04.2012 13:17:53 \/Install\/NB\/8540p\/sp54740.exe\r\n----r-----       -2  nogroup   27476040  27.04.2012 13:06:05 \/Install\/NB\/8540p\/sp54841.exe\r\n----r-----       -2  nogroup    4711104  27.04.2012 13:09:02 \/Install\/NB\/8540p\/sp54887.exe\r\n----r-----       -2  nogroup   24835752  27.04.2012 13:10:41 \/Install\/NB\/8540p\/sp54890.exe\r\n----r-----       -2  nogroup  251788408  27.04.2012 13:07:22 \/Install\/NB\/8540p\/sp55192.exe\r\n----r-----       -2  nogroup    8594016  27.04.2012 13:01:01 \/Install\/NB\/8540p\/sp56768.exe\r\nd----w----       -2  nogroup          0  03.12.2012 10:40:50 \/Install\/NB\/8540p\/SWSetup\/SP45229\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:41:03 \/Install\/NB\/8540p\/SWSetup\/SP46063\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:41:13 \/Install\/NB\/8540p\/SWSetup\/SP46768\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:41:15 \/Install\/NB\/8540p\/SWSetup\/SP46972\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:41:16 \/Install\/NB\/8540p\/SWSetup\/SP47231\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:41:18 \/Install\/NB\/8540p\/SWSetup\/SP47527\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:41:33 \/Install\/NB\/8540p\/SWSetup\/SP47593\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:43:18 \/Install\/NB\/8540p\/SWSetup\/SP47594\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:43:29 \/Install\/NB\/8540p\/SWSetup\/SP48061\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:45:26 \/Install\/NB\/8540p\/SWSetup\/SP48062\/\r\nd----w----       -2  nogroup          0  03.12.2012 10:45:51 \/Install\/NB\/8540p\/SWSetup\/SP480\r\nd----w----       -2  nogroup          0  03.12.2012 10:45:53 \/Install\/NB\/8540p\/SWSetup\/SP48109\/\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>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 when using &#8220;restore by query&#8221; [&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":[177,16],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","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-lQ","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":114,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/07\/614039-no-more-space-in-any-of-the-detail-catalog-directories\/","url_meta":{"origin":1354,"position":0},"title":"[61:4039] No more space in any of the Detail Catalog directories","date":"7. July 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 &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1428,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/06\/basics-dp-catalog-protection-data-protection\/","url_meta":{"origin":1354,"position":1},"title":"BASICS &#8211; DP Catalog Protection and Data Protection","date":"10. June 2013","format":false,"excerpt":"{:en}Within Data Protector the protection is set per backup job and not for the tape, which might be misunderstood by customers. In the GUI a distinction is made between \"Data Protection\" and \"Catalog Protection\". \"Data Protection\" describes how long the data is kept on media and \"Catalog Protection\" describes how\u2026","rel":"","context":"In &quot;BASICS&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":694,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":1354,"position":2},"title":"Data Protector Migration Unix to other OS","date":"29. July 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":62,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/06\/export-import\/","url_meta":{"origin":1354,"position":3},"title":"Export \/ Import","date":"28. June 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 &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1320,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/03\/advisory-c03705726\/","url_meta":{"origin":1354,"position":4},"title":"Advisory c03705726","date":"26. March 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 &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2284,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/02\/restart-failed-objects-data-protector-9-02\/","url_meta":{"origin":1354,"position":5},"title":"Restart Failed Objects with Data Protector 9.02","date":"23. February 2015","format":false,"excerpt":"{:en} With Data Protector 9.02 a restart of a backup with failed objects may fail with the error \"Invalid Message Format\". The error is caused by the introduction of the \"Pause \/ Resume\" feature in DP 9.02. As a solution you can add the variable UseJCEForRestartResume=0 to the configuration file\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1354"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=1354"}],"version-history":[{"count":7,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1354\/revisions"}],"predecessor-version":[{"id":2657,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1354\/revisions\/2657"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1354"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1354"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1354"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}