{"id":33718,"date":"2019-10-31T21:54:20","date_gmt":"2019-10-31T18:54:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/optimizatsiya-raboty-pochtovyh-hranilishh-v-zimbra-collaboration-suite\/"},"modified":"2019-10-31T21:54:20","modified_gmt":"2019-10-31T18:54:20","slug":"optimizatsiya-raboty-pochtovyh-hranilishh-v-zimbra-collaboration-suite","status":"publish","type":"post","link":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/optimizatsiya-raboty-pochtovyh-hranilishh-v-zimbra-collaboration-suite","title":{"rendered":"Optimering af e-mail-lagring i Zimbra Collaboration Suite","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

I en af vores tidligere artikler<\/a><\/noindex>, som handlede om planl\u00e6gning af infrastrukturen ved implementeringen af Zimbra Collaboration Suite i virksomheder, blev det n\u00e6vnt, at den st\u00f8rste begr\u00e6nsning ved brugen af denne l\u00f8sning er ind- og udl\u00e6sningstempoet for diskene i e-maillagrerne. Og i sandhed, n\u00e5r flere hundrede medarbejdere i virksomheden samtidig tilg\u00e5r det samme e-maillager, kan b\u00e5ndbredden til at l\u00e6se og skrive information til harddiske v\u00e6re utilstr\u00e6kkelig for en responsiv service. Og hvis dette ikke bliver et stort problem for sm\u00e5 Zimbra-installationer, kan det i tilf\u00e6lde af store virksomheder og SaaS-udbydere f\u00f8re til en uresponsiv e-mail og deraf f\u00f8lgende nedsat medarbejdereffektivitet samt overtr\u00e6delse af SLA. Derfor er det vigtigt at fokusere p\u00e5 at optimere harddiskarbejdet i e-maillageret ved design og drift af store Zimbra-installationer. Lad os se p\u00e5 to cases og fors\u00f8ge at finde ud af, hvilke metoder til optimering af belastningen p\u00e5 diskstorage der kan anvendes i hver af dem.<\/p>\n

\"Optimering<\/a><\/noindex><\/p>\n

1. Optimering ved design af en stor installation af Zimbra<\/b><\/p>\n

Ved designfasen af en h\u00f8jbelastningsinstallation af Zimbra skal administratorerne v\u00e6lge, hvilket datalagringssystem de vil anvende. For at afg\u00f8re dette sp\u00f8rgsm\u00e5l er det vigtigt at vide, at den prim\u00e6re belastning p\u00e5 harddiskene skabes af databasen MariaDB, s\u00f8gesystemet Apache Lucene samt opbevaringen af BLOB-objekter, som udg\u00f8r Zimbra Collaboration Suite. Det er derfor n\u00f8dvendigt at anvende hurtig og p\u00e5lideligt udstyr til at k\u00f8re disse softwareprodukter under h\u00f8je belastninger. <\/p>\n

Under almindelige forhold kan Zimbra installeres b\u00e5de p\u00e5 en RAID af harddiske og p\u00e5 lagre, der forbindes via NFS-protokollen. I tilf\u00e6lde af meget sm\u00e5 installationer kan Zimbra ogs\u00e5 installeres p\u00e5 en almindelig SATA-disk. Men under forholdene ved store installationer viser alle disse teknologier forskellige ulemper i form af nedsat skrivhastighed eller lav p\u00e5lidelighed, hvilket er uacceptabelt hverken for store virksomheder eller, endnu mindre, for SaaS-udbydere.<\/p>\n

Derfor er det bedst at bruge SAN i store Zimbra-infrastrukturer. Dette system kan i \u00f8jeblikket levere den st\u00f8rste b\u00e5ndbredde til lagringsenheder, og ved mulighed for tilslutning af et stort antal cache-enheder b\u00e6rer det n\u00e6sten ingen v\u00e6sentlige risici for virksomheden. Det ville v\u00e6re en god id\u00e9 at anvende NVRAM, som bruges i mange SAN for at fremskynde skriveprocesser. For caching af data p\u00e5 selve diske er det derimod bedst at deaktivere det, da det kan f\u00f8re til uoprettelig skade p\u00e5 medierne og datatab i tilf\u00e6lde af str\u00f8mafbrydelser.<\/p>\n

N\u00e5r det kommer til valg af filsystem, vil det optimale valg v\u00e6re at bruge de standard Linux-filsystemer Ext3\/Ext4. Den vigtigste detalje ved filsystemet er, at det skal monteres med parameteren -noatime<\/b>. Denne parameter deaktiverer funktionen til at registrere tidspunktet for den seneste adgang til filer, hvilket derfor reducerer belastningen p\u00e5 l\u00e6se- og skriveoperationer betydeligt. Generelt b\u00f8r man ved oprettelse af et ext3 eller ext4-filsystem til Zimbra bruge f\u00f8lgende parametre fra v\u00e6rkt\u00f8jet mke2fs<\/b>:<\/p>\n

-j<\/b> \u2014 Til at oprette et filsystem med et ext3\/ext4 journal.
\n-L NAVN<\/b> \u2014 For at oprette et volumen navn, s\u00e5 det senere kan bruges i \/etc\/fstab
\n-O dir_index<\/b> \u2014 For at anvende et hash-baseret s\u00f8getr\u00e6 for at fremskynde fils\u00f8gningsprocessen i store mapper
\n-m 2<\/b> \u2014 For at reservere 2% af kapaciteten i store filsystmer til rodkataloget
\n-J size=400<\/b> \u2014 For at oprette et stort journal
\n-b 4096<\/b> \u2014 For at bestemme blokkens st\u00f8rrelse i byte
\n-i 10240<\/b> \u2014 For meddelelsesopbevaring skal denne parameter svare til den gennemsnitlige st\u00f8rrelse af meddelelserne. Man b\u00f8r v\u00e6re opm\u00e6rksom p\u00e5 denne parameter, da dens v\u00e6rdi ikke kan \u00e6ndres senere<\/p><\/blockquote>\n

\nDerudover anbefales det at aktivere dirsync<\/b> til BLOB-objektlagring, Lucene-s\u00f8gemetadataopbevaring og MTA-k\u00f8lagring. Dette b\u00f8r g\u00f8res, da Zimbra normalt anvender v\u00e6rkt\u00f8jet fsync<\/b> for guaranteed recording of blobs with data to disk. However, when the Zimbra mail storage or MTA creates new files during message delivery, there is a need to write to disk the changes made in the corresponding folders. That is why even if the file has already been recorded on disk using fsync<\/b>, the record of its addition in the directories may not be written to disk in time and as a result, it may be lost due to a sudden server failure. Thanks to the use of dirsync<\/b> these problems can be avoided.<\/p>\n

2. Optimization in a Working Zimbra Infrastructure<\/b><\/p>\n

It often happens that after several years of operation the number of users of Zimbra significantly increases and the service becomes less and less responsive day by day. The way out of this situation is obvious: it is necessary to simply add new servers to the infrastructure so that the service works as quickly as it did before. Meanwhile, it is not always possible to immediately add new servers to the infrastructure to improve its performance. Often, IT managers have to spend a long time coordinating the purchase af nye servere<\/a> with accounting or the security department; moreover, suppliers often let you down, delivering a new server late or bringing something entirely different.<\/p>\n

Of course, it is best to build your Zimbra infrastructure with a reserve, so that you always have a buffer for its expansion and do not depend on anyone, but if a mistake has already been made, the IT manager can only smooth over its consequences as much as possible. For example, the IT manager can achieve a slight increase in performance by temporarily disabling Linux system services that regularly access hard disks and can negatively affect Zimbra's speed. Temporarily, you can disable:<\/p>\n

autofs, netfs<\/b> \u2014 Remote file system discovery services
\ncups<\/b> \u2014 Print service
\nxinetd, vsftpd<\/b> \u2014 Built-in *NIX services that you are unlikely to need
\nportmap, rpcsvcgssd, rpcgssd, rpcidmapd<\/b> \u2014 Remote procedure call services that are usually used in conjunction with network file systems
\ndovecot, cyrus-imapd, sendmail, exim, postfix, ldap<\/b> \u2014 Duplicates of core utilities included in the Zimbra Collaboration Suite
\nslocate\/updatedb<\/b> Da Zimbra gemmer hver besked i en separat fil, kan en daglig k\u00f8rsel af tjenesten updatedb f\u00f8re til problemer, og det anbefales derfor at udf\u00f8re dette manuelt i perioder med lavest belastning p\u00e5 serverne.<\/p><\/blockquote>\n

\nSpareressourcerne ved at deaktivere disse tjenester vil ikke v\u00e6re meget betydelige, men selv dette kan v\u00e6re nyttigt under n\u00e6sten n\u00f8dssituationer. N\u00e5r den nye server er tilf\u00f8jet til Zimbra-infrastrukturen, anbefales det at genaktivere de tidligere deaktiverede tjenester.<\/p>\n

Det er ogs\u00e5 muligt at optimere Zimbras drift ved at flytte syslog-tjenesten til en separat server, s\u00e5 den ikke belaster harddiskene i maillagrene under driften. N\u00e6sten enhver computer, lige fra en billig enkeltskift Raspberry Pi, kan bruges til dette form\u00e5l.
\n
Kilde: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0412 \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u043d\u0430\u0448\u0438\u0445 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0441\u0442\u0430\u0442\u0435\u0439, \u043f\u043e\u0441\u0432\u044f\u0449\u0435\u043d\u043d\u043e\u0439 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b \u043f\u0440\u0438 \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0438 \u043d\u0430 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0438 Zimbra Collabortion Suite, \u0431\u044b\u043b\u043e \u0441\u043a\u0430\u0437\u0430\u043d\u043e, \u0447\u0442\u043e \u0433\u043b\u0430\u0432\u043d\u044b\u043c \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u0435\u043c \u043f\u0440\u0438 \u0440\u0430\u0431\u043e\u0442\u0435 \u044d\u0442\u043e\u0433\u043e \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u044c \u0432\u0432\u043e\u0434\u0430-\u0432\u044b\u0432\u043e\u0434\u0430 \u0434\u0438\u0441\u043a\u043e\u0432\u044b\u0445 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432 \u0432 \u043f\u043e\u0447\u0442\u043e\u0432\u044b\u0445 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430\u0445. \u0418 \u0434\u0435\u0439\u0441\u0442\u0432\u0438\u0442\u0435\u043b\u044c\u043d\u043e, \u0432 \u0442\u043e \u0432\u0440\u0435\u043c\u044f, \u043a\u043e\u0433\u0434\u0430 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0441\u043e\u0442\u0435\u043d \u0440\u0430\u0431\u043e\u0442\u043d\u0438\u043a\u043e\u0432 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f \u043e\u0434\u043d\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u043e \u043e\u0431\u0440\u0430\u0449\u0430\u044e\u0442\u0441\u044f \u043a \u043e\u0434\u043d\u043e\u043c\u0443 \u0438 \u0442\u043e\u043c\u0443 \u0436\u0435 \u043f\u043e\u0447\u0442\u043e\u0432\u043e\u043c\u0443 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0443, \u0448\u0438\u0440\u0438\u043d\u044b \u043a\u0430\u043d\u0430\u043b\u0430 \u0434\u043b\u044f […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":25398,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-33718","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Optimering af maillagernes drift i Zimbra Collaboration Suite | ProHoster","description":"I en af vores tidligere artikler, der omhandlede planl\u00e6gning af infrastrukturen ved implementering af Zimbra i en virksomhed.","canonical_url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/optimizatsiya-raboty-pochtovyh-hranilishh-v-zimbra-collaboration-suite","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"da_DK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041e\u043f\u0442\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u044f \u0440\u0430\u0431\u043e\u0442\u044b \u043f\u043e\u0447\u0442\u043e\u0432\u044b\u0445 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449 \u0432 Zimbra Collaboration Suite | ProHoster","og:description":"\u0412 \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u043d\u0430\u0448\u0438\u0445 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0441\u0442\u0430\u0442\u0435\u0439, \u043f\u043e\u0441\u0432\u044f\u0449\u0435\u043d\u043d\u043e\u0439 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b \u043f\u0440\u0438 \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0438 \u043d\u0430 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0438 Zimbra.","og:url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/optimizatsiya-raboty-pochtovyh-hranilishh-v-zimbra-collaboration-suite","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:54:20+00:00","article:modified_time":"2019-10-31T18:54:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"33718","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-02-08 20:33:43","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:35:31","updated":"2026-02-08 20:33:43","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/33718","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/comments?post=33718"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/33718\/revisions"}],"predecessor-version":[{"id":157961,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/33718\/revisions\/157961"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media\/25398"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media?parent=33718"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/categories?post=33718"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/tags?post=33718"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}