BRICK FAQ: The script displays “Out of memory”<\/b>
\nThe script might display a message “Out of memory” and dies. This can happen when the filesize of the debug.log is too big (at least 1 GB). In this case try to cycle the debug.log.<\/p>\n
BRICK FAQ: The script cannot be started on RedHat<\/b>
\nAs the script was developed with the 32bit version of Perl (for compatibility), on RedHat systems you may receive the error: ‘\/lib\/ld-linux.so.2: bad ELF interpreter: No such file or directory’. In this case you may install some required libs with the command ‘yum -y install glibc.i686’ before you can use BRICK.<\/p>\n
BRICK FAQ: The generated BRICK reports show wrong values for Data Protector 8.0 environments<\/b>
The reports generated in BRICK utilize the standard Data Protector commands. As there is a bug in this version the result presented by BRICK might be wrong too. Please open a support request to get the fix. After applying the fix the advanced reports should display the correct values in reports.<\/p>\n
BRICK FAQ: The runtime of the BRICK script is very long and seems to hang for the DNS check<\/b> BRICK FAQ: The listing of the local groups is very slow and produces a large file<\/b> BRICK FAQ: During the execution of BRICK the RDS daemon \/ service dies unexpectly<\/b> BRICK FAQ: The script displays “Out of memory” The script might display a message “Out of memory” and dies. This can happen when the filesize of the debug.log is too big (at least 1 GB). In this case try to cycle the debug.log. BRICK FAQ: The script cannot be started on RedHat As the script […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"_mi_skip_tracking":false,"spay_email":""},"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_shortlink":"https:\/\/wp.me\/P28cjj-pF","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":984,"url":"https:\/\/www.data-protector.org\/wordpress\/brick\/","url_meta":{"origin":1591,"position":0},"title":"BRICK","date":"10. June 2015","format":false,"excerpt":"{:de}BRICK - Backup Related Information Collector and Keeper - neue Version 2.0 Was ist BRICK? Ein Tool f\u00fcr HP Data Protector, welches dazu verwendet wird die Data Protector Umgebung zu dokumentieren, bei der Fehleranalyse unterst\u00fctzt, alle relevanten Informationen der Umgebung geb\u00fcndelt zusammenstellt, sowie beim \u00d6ffnen von Support Cases unterst\u00fctzt. BRICK\u2026","rel":"","context":"With 119 comments","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1129,"url":"https:\/\/www.data-protector.org\/wordpress\/downloads\/","url_meta":{"origin":1591,"position":1},"title":"Downloads","date":"13. May 2016","format":false,"excerpt":"{:en}Please find below all available downloads from this blog. BRICK \u2013 Backup Related Information Collector and Keeper - Version 2.0 https:\/\/www.data-protector.org\/wordpress\/?s=BRICK EADR for Cell Server - DP 9.06 on Windows 2012 R2 https:\/\/www.data-protector.org\/wordpress\/2016\/05\/prepare-and-execute-eadr-cell-server-on-windows-2012-r2-data-protector-9-06\/ Data Protector Best Practice Guide https:\/\/www.data-protector.org\/wordpress\/?s=best+practice+guide BRICK \u2013 Backup Related Information Collector and Keeper - Version 1.20\u2026","rel":"","context":"With 3 comments","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1564,"url":"https:\/\/www.data-protector.org\/wordpress\/videotutorials\/","url_meta":{"origin":1591,"position":2},"title":"Video Tutorials","date":"17. August 2014","format":false,"excerpt":"{:en}Within the category video tutorials, some videos regarding HP Data Protector are published. There will be additional videos added from time to time, describing features in HP Data Protector and related products. For any feedback or to request a tutorial, please use the contact form below. The videos will be\u2026","rel":"","context":"With 12 comments","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4248,"url":"https:\/\/www.data-protector.org\/wordpress\/about\/team\/","url_meta":{"origin":1591,"position":3},"title":"Team","date":"27. June 2018","format":false,"excerpt":"In memoriam Daniel Braun\u00a0 \u00a0\ud83d\udd46 15.02.2017 Founder, inventor, creator, mastermind, and much more of data-protector.org. He might be gone but he shall not be forgotten by honoring his legacy here on this site. Administrator: Stephan Voss Contact: Stephan@data-protector.org Current owner of data-protector.org with a passion for perfection. Data Protector experience\u2026","rel":"","context":"Similar post","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":52,"url":"https:\/\/www.data-protector.org\/wordpress\/whitepaper\/","url_meta":{"origin":1591,"position":4},"title":"Whitepaper","date":"4. April 2016","format":false,"excerpt":"{:en} With friendly permission of HPE withhin this article known Data Protector whitepapers are listed. Older versions (pre DP 7) were removed. For some whitepaper a Passport Account may required. Data Protector 9.xx Whitepaper: Integrating data protection for VMware Infrastructure Cloud Service Automation and Data Protector Data Protector 7.0 Whitepaper:\u2026","rel":"","context":"With 2 comments","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4239,"url":"https:\/\/www.data-protector.org\/wordpress\/data-protector-links\/","url_meta":{"origin":1591,"position":5},"title":"Data Protector links","date":"19. June 2018","format":false,"excerpt":"{:en}Following you can find the most frequently searched URL's, we try to keep this as up to date as possible. Disclaimer: The preceding links refer to external websites of third parties on whose contents we have no influence. Therefore, we can not assume any liability for these external contents. The\u2026","rel":"","context":"Similar post","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/pages\/1591"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/page"}],"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=1591"}],"version-history":[{"count":12,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/pages\/1591\/revisions"}],"predecessor-version":[{"id":3422,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/pages\/1591\/revisions\/3422"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1591"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
In larger environments with many clients in cell or with slower DNS servers the runtime of BRICK might be higher than expected. In this case use the parameter -no_dns<\/code> to skip this specific check. This will increase the runtime of BRICK.<\/p>\n
The root cause of this problem can be found in the WMI query used in BRICK. If nested groups are used, the WMI query walks through the AD and will no limit the search to local groups, even if specified explicitly. This will cause a very long runtime of BRICK. At the moment no solution is available, however, the mechanism to retrieve local groups will be changed with version 1.1 of BRICK and will be configurable.<\/p>\n
For the checks done by BRICK Data Protector commands are used only. The unexpected event will be accour as well when the command is used without BRICK. The problem was reproducable in a non patched DP 6.20 cell. With the installation of the current patches the problem was solved.<\/p>\n","protected":false},"excerpt":{"rendered":"