summaryrefslogtreecommitdiff
path: root/Deployment_Guide/pot/High_Availability.pot
blob: 4856a346dd795d8a67a191f9a777b32e80425f8b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
# 
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2012-09-08T15:07:49\n"
"PO-Revision-Date: 2012-09-08T15:07:49\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 "High Availability"
msgstr ""

#. Tag: para
#, no-c-format
msgid "High availability is most commonly a prerequisite characteristic for deployments of application and/or service environments considered critical to an organization's day-to-day operations. The requirement to be able to guarantee service continuity is assigned a certain degree or level and translates into the following technical terms;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Service Availability &amp; Performance"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Data Redundancy &amp; Replication"
msgstr ""

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

#. Tag: para
#, no-c-format
msgid "Failover Scenarios"
msgstr ""

#. Tag: para
#, no-c-format
msgid "This appendix addresses high availability as it applies to the Kolab Groupware environment for using different failure and failover scenarios."
msgstr ""

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

#. Tag: para
#, no-c-format
msgid "The term site-reliability applies to complete failover of one or more application and/or service environments serviced from one site during normal operations, to then be serviced from another site upon failover."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Different degrees of site-reliability are available. For example, the failover site may have less resources available. Suppose the failover site can make available up to 50% of total processing capacity required for the service to operate at full capacity. The service may show degraded performance, but continues to be generally available. At a lower cost, this scenario still achieves a degree of site-reliability as availability of the service is impacted only for the duration to achieve the complete failover, despite the fact it may be available with significantly degraded performance."
msgstr ""