# 
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2012-09-05T08:49:33\n"
"PO-Revision-Date: 2012-09-05T08:49:33\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#, no-c-format
msgid "Kolab Groupware Components"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The Kolab Groupware Server consists of the primary components outlined in <xref linkend=\"item-Deployment_Guide-Kolab_Groupware_Components-Primary_Kolab_Groupware_Server_Components\" />. Each of these components allow scaling up and down both horizontally as well as vertically. This chapter outlines a high-level overview of your options."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Primary Kolab Groupware Server Components"
msgstr ""

#. Tag: title
#, no-c-format
msgid "IMAP Storage Backend"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Kolab Groupware stores the groupware information in IMAP folders. Contacts, events and other groupware related information is stored as an attachment to a mail message. A folder is <emphasis>annotated</emphasis> to indicate the type of groupware content stored in that folder."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Cyrus IMAP Recommended"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Kolab Systems recommends the use of Cyrus IMAP as the IMAP storage backend, as is the default that comes with Kolab Groupware. Cyrus IMAP is fast, efficient, scalable."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Mail Transfer Agent"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The mail transfer agent (<emphasis>MTA</emphasis>) is used to send and receive messages between nodes in the Kolab Groupware environment and to exchange mail with external applications, other groupware environments and the outside world."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Postfix Recommended"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Kolab Systems recommends you use Postfix as the mail transfer agent, as is the default that comes with Kolab Groupware. Postfix represents great flexibility, integration, security and scalability."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Authentication and Authorization Database"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The authentication (<emphasis>authn</emphasis>) and authorization (<emphasis>authz</emphasis>) database holds all user and group information, as well as, at your option, the <emphasis>global address book</emphasis>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Clients &amp; 3rd Party Applications"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Included in the category of server components are 3rd party applications integrated with the Kolab Groupware solution, such as the web mail interface, or XMPP services."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Traditional Kolab Groupware Deployment"
msgstr ""

#. Tag: para
#, no-c-format
msgid "A traditional Kolab Groupware deployment starts out with one Kolab server, which has all of the primary components installed. As the Kolab Groupware environment is used more extensively and/or more 3rd party applications are integrated with Kolab, the environment scales through attaching one or more slave nodes."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This type of scaling is illustrated in <xref linkend=\"figu-Deployment_Guide-Large_scale_Kolab_Groupware_Deployment-Scaling_amp_Positioning_Kolab_Groupware_Server_Components\" />. There is a number of constraints to this type of scaling architecture which impact its feasibility for larger environments, such as redundancy, high-availability and load-balancing capabilities."
msgstr ""

#. Tag: para
#, no-c-format
msgid "That is not to say the traditional model does not perform or is not sustainable. Typically, a traditional deployment of a Kolab Groupware environment &ndash;provided sufficient processing, memory and disk, of course&ndash; can scale up to serve thousands of users without problems."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Overview of a Traditional Kolab Groupware Server Environment Scaled Out"
msgstr ""

#. Tag: para
#, no-c-format
msgid "However, if any of the keywords listed in <xref linkend=\"item-Deployment_Guide-Traditional_Kolab_Groupware_Deployment-Keywords_to_Use_to_Recognize_Traditional_is_Not_For_You\" /> occur as prerequisites in the project planning, please refer to <xref linkend=\"sect-Deployment_Guide-Kolab_Groupware_Components-Large_scale_Kolab_Groupware_Deployment\" />."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Keywords to Use to Recognize \"Traditional\" is Not For You"
msgstr ""

#. Tag: para
#, no-c-format
msgid "High-availability"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Load-balancing"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Disaster Recovery"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Site-reliability"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Cold/Warm/Hot Standby Failover"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Storage Tiers"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Large-scale Kolab Groupware Deployment"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Large scale Kolab Groupware deployments require the ability to scale up one of the components listed in <xref linkend=\"item-Deployment_Guide-Kolab_Groupware_Components-Primary_Kolab_Groupware_Server_Components\" /> separate from the other components. This further reduces cost, maintenance overhead and overall environment architecture complexity."
msgstr ""

#. Tag: para
#, no-c-format
msgid "To that effect, Kolab Systems recommends considering the environment architecture illustrated in <xref linkend=\"figu-Deployment_Guide-Large_scale_Kolab_Groupware_Deployment-Scaling_amp_Positioning_Kolab_Groupware_Server_Components\" />, which shows the following characteristics;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "All components can, individually, be scaled up and down both horizontally as well as vertically,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Relevant components are split up so they can be positioned in the appropriate network segment,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Individual components are load-balanced across nodes, implicitly achieving some level of high-availability,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Each node can be taken out of rotation and serviced without impact to service availability<footnote> <para> Note that while service availability would not be impacted, service performance may be degraded during this service window. </para> </footnote>,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Individual components can be made highly available to a certain degree of saturation,"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Individual components can be positioned to use different tiers of virtualization, storage and network,"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Scaling &amp; Positioning Kolab Groupware Server Components"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Each of these components can be scaled up and down at your discretion, while the architecture allows for improved capacity planning, better monitoring, management and overall sustainability."
msgstr ""

#. Tag: title
#, no-c-format
msgid "In this Document"
msgstr ""

#. Tag: para
#, no-c-format
msgid "In this document, all individual components are zoomed in to separately, so that options and consequences in terms of sceurity, scalability, high-availability and load-balancing can be taken into account."
msgstr ""