{"id":2999,"date":"2016-05-06T16:07:09","date_gmt":"2016-05-06T15:07:09","guid":{"rendered":"https:\/\/www.data-protector.org\/wordpress\/?p=2999"},"modified":"2016-06-10T16:04:47","modified_gmt":"2016-06-10T15:04:47","slug":"brick-options","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/05\/brick-options\/","title":{"rendered":"BRICK options"},"content":{"rendered":"<p>Ich werde immer mal wieder gefragt welche Parameter bei der Verwendung von BRICK zur Verf\u00fcgung stehen. Wenn man <code>brick --help<\/code> ausf\u00fchrt, dann wird eine Liste der verf\u00fcgbaren Parameter und deren Beschreibung angezeigt. Nachfolgend sind die Beschreibungen nochmals aufgef\u00fchrt (in Englisch).<\/p>\n<ul>\n<li><code>--full, -f<\/code> &#8211;> runs all checks &#8211; recommend for maximum 75 server in cell (includes check of the internal database and reports for the last 7 days, &#8230;)<\/li>\n<li><code>--reduced, -r<\/code> &#8211;> runs reduced checks &#8211; recommended for larger cell (no check of the internal database, reports for the last 2 days, &#8230;)<\/li>\n<li><code>--long, -l<\/code> &#8211;> runs additional IDB checks &#8211; not recommended for larger cells as runtime of script will increase. Use this mode in smaller environments or when requested.<\/li>\n<li><code>--config, -c<\/code> &#8211;> &#8222;config file&#8220;, example: -c=c:\\temp\\brick.conf Runs the checks configured in the config file only. Use &#8220; to quote directories with spaces in Windows.<\/li>\n<li><code>--path, -p<\/code> &#8211;> &#8222;output directory&#8220;, example: -p=c:\\temp or -p=\/tmp Use &#8220; to quote directories with spaces in Windows.<\/li>\n<li><code>--support, -s<\/code> &#8211;> collects additional files to support the process to open service requests.<\/li>\n<li><code>--dnscheck<\/code> &#8211;> executes the DNS check, recommend in smaller environments. Parameter will overwrite the settings in config file. (valid for coming version 2.10)<\/li>\n<li><code>--no_dns, -n<\/code> &#8211;> disables the DNS check. Parameter will overwrite the settings in config file. (valid for current version)<\/li>\n<li><code>--rep_start<\/code> &#8211;> defines the start date for the reports to be generated. variable to be used with &#8211;config option only. The format must be YYYYMMDD, i.e. &#8222;20150420&#8220;. The start time is set to 0:00.<\/li>\n<li><code>--rep_end<\/code> &#8211;> defines the end date for the reports to be generated. Variable to be used with &#8211;config option only. The format must be YYYYMMDD, i.e. &#8222;20150515&#8220;. The end time is set to 23:59.<\/li>\n<li><code>--update, -u<\/code> &#8211;> checks for newer version of BRICK. For this option a working internet connection is required.<\/li>\n<li><code>--debug, -d<\/code> &#8211;> debug mode, output is written to brickdebug.log.<\/li>\n<li><code>--exitcodes, -e<\/code> &#8211;> prints out the exit codes used in program.<\/li>\n<li><code>--version, -v<\/code> &#8211;> displays the script version.<\/li>\n<li><code>--help, -h<\/code> &#8211;> prints this help.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Ich werde immer mal wieder gefragt welche Parameter bei der Verwendung von BRICK zur Verf\u00fcgung stehen. Wenn man brick &#8211;help ausf\u00fchrt, dann wird eine Liste der verf\u00fcgbaren Parameter und deren Beschreibung angezeigt. Nachfolgend sind die Beschreibungen nochmals aufgef\u00fchrt (in Englisch). &#8211;full, -f &#8211;> runs all checks &#8211; recommend for maximum 75 server in cell (includes [&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":[1],"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-Mn","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":694,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":2999,"position":0},"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":1412,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/06\/basics-installation-order-patches\/","url_meta":{"origin":2999,"position":1},"title":"Installation order of Patches","date":"3. Juni 2013","format":false,"excerpt":"{:de}Immer wieder stellt sich die Frage in welcher Reihenfolge die Patches f\u00fcr Data Protector installiert werden. Zwischen den einzelnen Patches ergeben sich Abh\u00e4ngigkeiten, welche man in den Beschreibungsdateien zum Patch nachlesen kann; diese m\u00fcssen bei der Installation eingehalten werden. Generell gilt folgende Reihenfolge f\u00fcr die Installation: sofern vorhanden: Patchbundle, Core,\u2026","rel":"","context":"In &quot;History&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1183,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/11\/dp-701-patch-bundle-unix-cell-server-mom-environment\/","url_meta":{"origin":2999,"position":2},"title":"DP 701 patch bundle on Unix Cell Server in MoM environment","date":"21. November 2012","format":false,"excerpt":"{:en}During the installation of patch bundle DPUXBDL_00701 in a MoM environment the installation might fail and the dedupe and the core patch cannot be installed. When checking with swinstall you will get the information that the pre checks were not successful. The error has been seen in an environment with\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1884,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/03\/workaround-vmware-gre-dp-7-038-1x-vcenter-5-1-u2\/","url_meta":{"origin":2999,"position":3},"title":"Workaround: VMware GRE &#8211; DP 7.03\/8.1X &#8211; vCenter 5.1 U2","date":"25. M\u00e4rz 2014","format":false,"excerpt":"{:en}After updating to vCenter 5.1 update 2 and with Data Protector 7.03 or 8.1X a blank page might be displayed when using VMware GRE. The reason might be a change in Tomcat of vCenter. When looking into the log files (i.e. C:\\ProgramData\\VMware\\VMware VirtualCenter\\Logs\\localhost.YYYY-MM-DD.log) the error VMwareGRE: runCGI (stderr):Can't open perl\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4379,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/10\/data-protector-upgrade-paths\/","url_meta":{"origin":2999,"position":4},"title":"Data Protector Upgrade Pfade","date":"29. Oktober 2018","format":false,"excerpt":"{:en} Lately, we've been receiving more requests for potential Data Protector upgrade paths. This post includes a simple overview to guide you including intermediate steps necessary to upgrade to the latest version of the software. To reduce the amount of manual effort to a minimum you should always use the\u2026","rel":"","context":"In &quot;History&quot;","img":{"alt_text":"DP_Upgrade_Paths","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"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":2999,"position":5},"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 &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\/2999"}],"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=2999"}],"version-history":[{"count":3,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/2999\/revisions"}],"predecessor-version":[{"id":3002,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/2999\/revisions\/3002"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=2999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=2999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=2999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}