---
canonical: https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekituserguidehtml/documentation/safekituserguideen.htm
---
# 16. SafeKit cluster in the cloud
Section 16.1 “SafeKit cluster in Amazon AWS”
Section 16.2 “SafeKit cluster in Microsoft Azure”
Section 16.3 “SafeKit cluster in Google GCP”
You can install, configure, and administer
SafeKit modules that run on virtual servers in the cloud instead of on-premises
physical servers. This requires a minimum of cloud and/or server settings,
especially to implement the virtual IP address.
## 16.1 SafeKit cluster in Amazon AWS
In the following, we suppose that you are
familiar with:
·
Amazon Elastic Compute Cloud (Amazon EC2) that offers
computing capacity in the Amazon Web Services (AWS) cloud. For more information
about the features of Amazon EC2, see the Amazon EC2
product page.
·
AWS CloudFormation that helps deploying instances
and applications on Amazon EC2. It permits to save a lot of time and effort so
that you can spend less time managing EC2 resources and more time focusing on
your applications that run in AWS.
Before implementing a SafeKit module, the
administrator must:
1. Create instances (2 for a mirror module)
2. Make settings for AWS, instances, and SafeKit.
3. Then, apply specific settings for implementing your SafeKit module.
AWS settings
You must set AWS to:
·
associate public addresses to each instance if
you want to administer them with the SafeKit web console from the internet
·
configure the security groups associated with
network(s) to enable the communications of the SafeKit framework and the
SafeKit web console. The ports to open are described in section 10.3.3.2
·
use a high-bandwidth, low-latency network if
real-time replication is used in a mirror module
Virtual machine settings
In each instance, you must also:
·
install the SafeKit package
·
apply the HTTPS configuration to secure the
SafeKit web console (described in section 11)
SafeKit settings
Finally, you must enter the SafeKit cluster
configuration and apply it to all nodes (for details on cluster configuration, see
section 12). For example,
the SafeKit cluster configuration file would be:
The default lan is used
for SafeKit framework communications between cluster nodes.
### 16.1.1 Mirror cluster in AWS
Mirror module features are operational in
the AWS cloud (real-time file replication, failover, process death detection,
checkers, …), except the virtual IP address failover. Anyway, you can set up a
SafeKit mirror module on the cluster and use the Elastic load balancing
provided by AWS (see Elastic load balancing products in AWS)
in such way that all the traffic is routed only to the primary node. An IP address and/or DNS name is
associated with the load balancer that plays the role of the virtual IP.
You must configure yourself the AWS load
balancer and the security group.
For the load balancer, you must:
·
specify the rules for your application
·
set the SafeKit cluster nodes in the target
group
·
configure the health check. It tests whether the instance is in a healthy state or an unhealthy
state.
The load-balancer routes the traffic only
to healthy instances. It resumes
routing requests to the instance when this one has been restored to a healthy
state.
SafeKit provides a health checker for
SafeKit modules. For this, configure it in the load balancer with:
·
HTTP protocol
·
port 9010, the SafeKit web service port
·
URL /var/modules/*AM*/ready.txt, where *AM* is the module name
In a mirror module, the health checker:
·
returns OK, that means that
the instance is healthy, when the module state is
PRIM (Ready) or ALONE (Ready)
·
returns NOT FOUND, that means
that the instance is out of service, in all other states
The AWS network security group must be at
least configured to enable communications for the following protocols and
ports:
·
UDP - 4800 for the safeadmin service
(between SafeKit cluster nodes)
·
UDP - 8888 for the module heartbeat (between SafeKit cluster nodes)
·
TCP - 5600 for the module real time file
replication (between SafeKit nodes)
·
TCP - 9010 for the load-balancer health check and
the SafeKit web console in HTTP
·
TCP - 9453 for the SafeKit web console in HTTPS
·
TCP - 9001 for configuring the SafeKit web
console for HTTPS
| | |
| --- | --- |
| Commentaire important contour | The module’s port value depends on the module id (for details, see section 10.3.3.2).The previous values are the one for the first module installed on the node. |
### 16.1.2 Farm cluster in AWS
Most farm module features are operational
in the AWS cloud (process death detection, checkers), except the virtual IP
address with load balancing. Anyway, you can set up a SafeKit farm module on
the cluster and use the Elastic load balancing provided by AWS (see Elastic load balancing products in AWS).
An IP address and/or DNS name is
associated with the load balancer that plays the role of the virtual IP.
You must configure yourself the AWS load
balancer and the security group.
For the load balancer, you must:
·
specify the rules for your application
·
set the SafeKit cluster nodes in the target
group
·
configure the health check. These
tests whether the instance is in a healthy state or an unhealthy state.
The load-balancer routes the traffic only
to healthy instances. It resumes
routing requests to the instance when this one has been restored to a healthy
state.
SafeKit provides a health check for SafeKit
modules. For this, configure it in the load balancer with:
·
HTTP protocol
·
port 9010, the SafeKit web service port
·
URL /var/modules/*AM*/ready.txt, where *AM* is
the module name
In a farm module, the health check:
·
returns OK, that means that
the instance is healthy, when the module state UP (Ready)
·
returns NOT FOUND, that means
that the instance is out of service, in all other states
The AWS network security group must be at
least configured to enable communications for the following protocols and
ports:
·
UDP - 4800 for the safeadmin service
(between SafeKit cluster nodes)
·
TCP - 9010 for the load-balancer health check
and the SafeKit web console in HTTP
·
TCP - 9453 for the SafeKit web console in HTTPS
·
TCP - 9001 for configuring the SafeKit web
console for HTTPS
## 16.2 SafeKit cluster in Microsoft Azure
In the following, we suppose that you are
familiar with Microsoft Azure that is a cloud computing service created by
Microsoft for building, testing, deploying, and managing applications and
services through a global network of Microsoft-managed data centers. For more
information about the features and use of Azure, see the
Microsoft Azure portal.
Before implementing a SafeKit module, the
administrator must:
1. Create virtual machines (2 for a mirror module)
2. Make settings for Azure, virtual machines, and SafeKit.
3. Then, apply specific settings for implementing your SafeKit module.
Azure settings
You must set Azure to:
·
associate public IP addresses and DNS name to
virtual machines if you want to administer them with the SafeKit web console
from the internet
·
configure the network security group to enable
the communications of the SafeKit framework and the SafeKit web console. The
ports to open are described in section 10.3.3.2
·
use a high-bandwidth, low-latency network if
real-time replication is used in a mirror module
Virtual machine settings
On each virtual machine, you must also:
·
install the SafeKit package
·
apply the HTTPS configuration to secure the
SafeKit web console (described in section 11)
SafeKit settings
Finally, you must enter the SafeKit cluster
configuration and apply it to all nodes (for details on cluster configuration, see
section 12). For example,
the SafeKit cluster configuration file would be:
The default lan is used
for SafeKit framework communications between cluster nodes.
### 16.2.1 Mirror cluster in Azure
Mirror module
features are operational in the Azure cloud (real-time file replication,
failover, process death detection, checkers, …) except the virtual IP address
failover. Anyway, you can set up a SafeKit mirror module on the cluster and use
the load balancing provided by Azure (see Load Balancer in Azure) and route
request only to the primary node. An IP is associated with the load balancer that
plays the role of the virtual IP.
You must configure yourself the Azure load
balancer and the network security group.
For the load balancer, you must:
·
specify the rules for your application
·
set the SafeKit cluster nodes into the backend
pool
·
configure the probe. It tests
whether the instance is in a healthy state or an unhealthy state.
The load balancer routes traffic only to
healthy instances. It resumes
routing requests to the instance when the instance has been restored to a
healthy state.
SafeKit provides a probe for SafeKit modules.
For this, configure the probe in the load balancer with:
·
HTTP protocol
·
port 9010, the SafeKit web service port
·
URL /var/modules/*AM*/ready.txt, where *AM* is
the module name
In a mirror module, the probe:
·
returns OK, that means that
the instance is healthy, when the module state is
PRIM (Ready) or ALONE (Ready)
·
returns NOT FOUND, that means
that the instance is out of service, in all other states
The Azure network security group must be at
least configured to enable communications for the following protocols and
ports:
·
UDP - 4800 for the safeadmin service
(between SafeKit cluster nodes)
·
UDP - 8888 for the module heartbeat (between SafeKit cluster nodes)
·
TCP - 5600 for the module real time file
replication (between SafeKit nodes)
·
TCP - 9010 for the load-balancer health check
and the SafeKit web console in HTTP
·
TCP - 9453 for the SafeKit web console in HTTPS
·
TCP - 9001 for configuring the SafeKit web
console for HTTPS
| | |
| --- | --- |
| Commentaire important contour | The module’s port value depends on the module id (for details, see section 10.3.3.2).The previous values are the one for the first module installed on the node. |
### 16.2.2 Farm cluster in Azure
Most farm module features are operational
in the Azure cloud (process death detection, checkers), except the virtual IP
address with load balancing . Anyway, you can set up a SafeKit farm module on
the cluster and use the load balancing provided by Azure (see Load Balancer in Azure). An IP is
associated with the load balancer that plays the role of the virtual IP.
You must configure yourself the Azure load
balancer and the network security group.
For the load balancer, you must:
·
specify the rules for your application
·
set the SafeKit cluster nodes as backend
·
configure the probe. It tests whether the instance is in a healthy state or an unhealthy
state.
The load balancer routes traffic only to
healthy instances. It resumes
routing requests to the instance when the instance has been restored to a
healthy state.
SafeKit provides a probe for SafeKit
modules. For this, configure the probe in the load balancer with:
·
HTTP protocol
·
port 9010, the SafeKit web service port
·
URL /var/modules/*AM*/ready.txt, where *AM* is
the module name
In a farm module, the probe:
·
returns OK, that means that
the instance is healthy, when the farm module state is UP (Ready)
·
returns NOT FOUND, that means
that the instance is out of service, in all other states
The Azure network security group must be at
least configured to enable communications for the following protocols and
ports:
·
UDP - 4800 for the safeadmin service
(between SafeKit cluster nodes)
·
TCP - 9010 for the load-balancer health check
and the SafeKit web console in HTTP
·
TCP - 9453 for the SafeKit web console in HTTPS
·
TCP - 9001 for configuring the SafeKit web
console for HTTPS
## 16.3 SafeKit cluster in Google GCP
In the following, we suppose that you are
familiar with Google Cloud Platform (GCP) that
delivers virtual machines running in Google's innovative data centers and
worldwide fiber network. For more information about the features and use of
Google Cloud Platform, see the Google Cloud Computing documentation.
Before implementing a SafeKit module, the
administrator must:
1. Create virtual machines (2 for a mirror module)
2. Make settings for Google Compute Engine (GCP), virtual machines, and
SafeKit.
3. Then, apply specific settings for implementing your SafeKit module.
GCP settings
You must set GCP to:
·
associate an external IP address (and optionally
DNS name) to each virtual machine instance if you want to administer them with
the SafeKit web console from the internet
·
configure the firewall rules for the Virtual
Private Cloud (VPC) network to enable the communications of the SafeKit
framework and the SafeKit web console. The ports to open are described in section 10.3.3.2
·
use a high-bandwidth, low-latency network if
real-time replication is used in a mirror module
Virtual machine settings
On each virtual machine, you must also:
·
install the SafeKit package
·
apply the HTTPS configuration to secure the
SafeKit web console (described in section 11)
SafeKit settings
Finally, you must enter the SafeKit cluster
configuration and apply it to all nodes (for details on cluster configuration, see
section 12. For example,
the SafeKit cluster configuration file would be:
The default lan is used
for SafeKit framework communications between cluster nodes.
### 16.3.1 Mirror cluster in GCP
Mirror module features are operational in
the Google Cloud Platform (real-time file replication, failover, process death
detection, checkers, …) except the virtual IP address failover. Anyway, you can
set up a SafeKit mirror module on the cluster and use the load balancing
provided by GCP (see Load Balancer in GCP) and route request
only to the primary node. An IP is associated with the load balancer that plays
the role of the virtual IP.
You must configure yourself the Google load
balancer and the network firewall.
For the load balancer, you must:
·
specify the rules for your application
·
set the SafeKit cluster nodes as backend
·
configure the health check. It
tests whether the instance is in a healthy state or an unhealthy state.
The load balancer routes traffic only to
healthy instances. It resumes
routing requests to the instance when the instance has been restored to a
healthy state.
SafeKit provides a health check for SafeKit
modules. For this, configure the health check in the load balancer with:
·
HTTP protocol
·
port 9010, the SafeKit web service port
·
URL /var/modules/*AM*/ready.txt, where *AM* is
the module name
In a mirror module, the health check:
·
returns OK, that means that
the instance is healthy, when the module state
PRIM (Ready) or ALONE (Ready)
·
returns NOT FOUND, that means
that the instance is unhealthy, in all other states
The network firewall must be at least
configured to enable communications for the following protocols and ports:
·
UDP - 4800 for the safeadmin service
(between SafeKit cluster nodes)
·
UDP - 8888 for the module heartbeat (between SafeKit cluster nodes)
·
TCP - 5600 for the module real time file
replication (between SafeKit nodes)
·
TCP - 9010 for the load-balancer health check
and the SafeKit web console in HTTP
·
TCP - 9453 for the SafeKit web console in HTTPS
·
TCP - 9001 for configuring the SafeKit web
console for HTTPS
| | |
| --- | --- |
| Commentaire important contour | The module’s port value depends on the module id (for details, see section 10.3.3.2).The previous values are the one for the first module installed on the node. |
### 16.3.2 Farm cluster in GCP
Most farm module features are operational
in the Google Cloud Platform (process death detection, checkers), except the
virtual IP address with load balancing. Anyway, you can set up a SafeKit farm
module on the cluster and use the load balancing provided by GCP (see Load Balancer in GCP). An IP is
associated with the load balancer that plays the role of the virtual IP.
You must configure yourself the Google load
balancer and the network firewall.
For the load balancer, you must:
·
specify the rules for your application
·
set the SafeKit cluster nodes as backend
·
configure the health check. It tests
whether the instance is in a healthy state or an unhealthy state.
The load balancer routes traffic only to
healthy instances. It resumes
routing requests to the instance when the instance has been restored to a
healthy state.
SafeKit provides a health check for SafeKit
modules. For this, configure the health check in the load balancer with:
·
HTTP protocol
·
port 9010, the SafeKit web service port
·
URL /var/modules/*AM*/ready.txt, where *AM* is
the module name
In a farm module, the health check:
·
returns OK, that means that
the instance is healthy, when the farm module state is UP (Ready)
·
returns NOT FOUND, that means
that the instance is out of service, in all other states
The network firewall must be at least
configured to enable communications for the following protocols and ports:
·
UDP - 4800 for the safeadmin service
(between SafeKit cluster nodes)
·
TCP - 9010 for the load-balancer health check
and the SafeKit web console in HTTP
·
TCP - 9453 for the SafeKit web console in HTTPS
·
TCP - 9001 for configuring the SafeKit web
console for HTTPS
# 17. Third-Party Software
SafeKit comes with the third-party software
listed below.
For licenses details, refer to the links or
the license files into the SAFE/licenses directory
(SAFE=/opt/safekit in Linux and
SAFE=C:\safekit in Windows if %SYSTEMDRIVE%=C:).
| | |
| --- | --- |
| libnet | Packet Construction and Injection Libnet license - license Used for arpreroute and ping |
| swagger-ui | https://github.com/swagger-api/swagger-ui Apache2 License - https://github.com/swagger-api/swagger-ui/blob/master/LICENSE Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API Used for to visualize the SafeKit API |
| Sqlite3 | https://www.sqlite.org/about.html Public Domain License - https://www.sqlite.org/copyright.html SQLite is an in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine Used by SafeKit framework |
| Info-ZIP | https://infozip.sourceforge.net/ BSD like license - https://infozip.sourceforge.net/license.html Used to pack/unpack a .safe module |
And on Windows OS only:
| | |
| --- | --- |
| jansson | https://github.com/akheron/jansson MIT licence - https://github.com/akheron/jansson/blob/master/LICENSE Used by the SafeKit framework for configuration files |
| libxml | https://gitlab.gnome.org/GNOME/libxml2/-/wikis/home MIT license - https://gitlab.gnome.org/GNOME/libxml2/-/wikis/FAQ Used by the SafeKit framework |
| libxslt | https://gitlab.gnome.org/GNOME/libxslt/-/wikis/home MIT license - https://gitlab.gnome.org/GNOME/libxslt/blob/master/Copyright Used by the SafeKit framework |
| Net-SNMP | https://net-snmp.sourceforge.io/ BSD like license - https://www.net-snmp.org/about/license.html Used by SafeKit SNMP agent in Windows |
| HTTP server | https://httpd.apache.org/ Apache license - https://www.apache.org/licenses/LICENSE-2.0 Used by the SafeKit web service for the web console, the distributed commands, and the module checker |
| APR | https://apr.apache.org/ Apache license - https://www.apache.org/licenses/LICENSE-2.0 Used by the Apache HTTP server |
| PCRE | https://www.pcre.org/ BSD license - https://www.pcre.org/licence.txt Used by the Apache HTTP server |
| PCR2 | https://pcre2project.github.io/pcre2/ BSD-3-Clause WITH PCRE2-exception - https://pcre2project.github.io/pcre2/project/licence Used for anonymizing snapshots and logs |
| libexpat | https://github.com/libexpat/libexpat BSD license -https://github.com/libexpat/libexpat/blob/master/expat/COPYING Used by the Apache HTTP server |
| mod\_auth\_openidc | https://github.com/OpenIDC/mod\_auth\_openidc Apache2 License - https://github.com/OpenIDC/mod\_auth\_openidc/blob/master/LICENSE.txt Used by the Apache HTTP server |
| cURL | https://curl.se/ Curl license - https://curl.se/docs/copyright.html Used by the distributed commands and the module checker |
| OpenSSL | https://www.openssl.org/ dual OpenSSL and SSLeay license - https://openssl-library.org/source/license/ Used when securing the web console, the distributed commands, and the module checker |
| Lua | https://www.lua.org/ MIT license - https://www.lua.org/license.html Used by SafeKit framework and the web service |
| getopt.c | BSD License. Used to parse command arguments |
| oncw32 | SUN RPC License. Used to transport NFS rpc |
SafeKit uses the following third-party
packages for the SafeKit web console:
| | |
| --- | --- |
| Angular | https://angular.dev/ MIT licence - https://github.com/angular/angular-cli/blob/main/LICENSE Angular is an application-design framework and development platform for creating efficient and sophisticated single-section apps. @angular/material, @angular/animations, @angular/platform-browser, @angular/service-worker, @angular/cdk, @angular/forms, @angular/core, @angular/common, @angular/router, |
| jszip | https://stuk.github.io/jszip/ MIT OR GPL-3.0-or-later licence - https://github.com/Stuk/jszip/blob/main/LICENSE.markdown A library for creating, reading, and editing .zip files with JavaScript, with a lovely and simple API. |
| rxjs | https://github.com/ReactiveX/rxjs Apache2 licence - https://github.com/ReactiveX/rxjs/blob/master/LICENSE.txt Reactive Extensions For JavaScript |
| tslib | https://www.typescriptlang.org/ 0BSD Copyright (c) Microsoft Corporation Runtime library for typescript |
| vlq | https://github.com/Rich-Harris/vlq/blob/master/README.md MIT licence - https://github.com/Rich-Harris/vlq/blob/master/LICENSE Convert integers to a Base64-encoded VLQ string, and vice versa |
| ngx-logger | https://github.com/dbfannin/ngx-logger#readme MIT licence - https://github.com/dbfannin/ngx-logger?tab=MIT-1-ov-file NGX Logger is a simple logging module for angular |
| zone.js | https://github.com/angular/zone.js MIT licence - https://github.com/angular/zone.js/blob/master/LICENSE Implements Zones for JavaScript |
| material-icons | https://github.com/marella/material-icons Apache-2.0 licence - https://github.com/marella/material-icons/blob/main/LICENSE |
This list is
available in file: safekit/web/htdcos/console/3rdpartylicenses.txt.
**Log
Messages Index**
“Action …” messages
"Action forcestop called by admin@/SYSTEM/root",
125,
154
"Action prim called by admin@/SYSTEM/root",
125,108, 154
"Action primforce called by
SYSTEM/root", 115, 154
"Action restart called by admin@/SYSTEM/root",
125, 84, 89, 154
"Action restart|stopstart called by
errd", 95, 128, 154
"Action restart|stopstart from
failover rule c\_id", 101, 128, 154
"Action restart|stopstart from
failover rule t\_id", 96, 128, 154
"Action second called by admin@/SYSTEM/root",
108, 154
"Action shutdown called by
SYSTEM", 86, 94, 154
"Action start called at boot time",
86, 87, 94, 95, 154
"Action start called
automatically", 96, 101
"Action start called by admin@/SYSTEM/root",
83, 89, 125, 154
"Action stop called by admin@/SYSTEM/root",
83, 89, 125, 154
"Action stop called by maxloop", 129, 95, 96, 98, 99, 99, 100, 101, 128
"Action stopstart called by
failover-off", 112, 163
"Action stopstart called by
modulecheck", 99, 154
"Action stopstart called by admin@/SYSTEM/root",
125, 154
"Action stopstart from failover rule c\_id",
101, 128, 154
"Action wait from failover rule c\_id",
100, 127
"Action wait from failover rule t\_id",
96, 127
"Action wait from failover rule
degraded\_server", 111
"Action wait from failover rule
interface\_failure", 98, 127
"Action wait from failover rule
module\_failure", 99, 127
"Action wait from failover rule
notuptodate\_server", 110, 127
"Action wait from failover rule p\_id",
99, 127
"Action wait from failover rule
splitbrain\_failure", 127
"Action alone called by heart: no
heartbeat", 86
"Action alone called by heart: remote stop",
83
File replication
and reintegration messages
"Copied ", 85
"Data may be
inconsistent for replicated directories (stopped during reintegration)", 115
"Data may not be
uptodate for replicated directories (wait for the start of the remote
server)", 108, 110, 127
"If you are sure
that this server has valid data, run safekit prim to force start as
primary", 108, 110, 127
"If you are sure that this server has
valid data, run safekit primforce to force start as primary", 115
"Reintegration
ended (synchronize)", 85
"Updating
directory tree from /replicated", 85
Load-balancing messages
"farm load:
128/256 (group FarmProto\_0)" , 119, 91, 92
"farm
membership: node1 (group FarmProto\_0)", 91, 92
"farm membership: node1 node2 (group FarmProto\_0)"
, 119, 91, 92
"farm membership: node2 (group FarmProto\_0)",
92
“Local state …” messages
"Local state ALONE Ready", 107, 83, 87
"Local state PRIM Ready", 107,83
"Local state SECOND Ready",107, 83
"Local state UP Ready",118 ,119
"Local state WAIT NotReady", 127, 112
“Remote state …” messages
"Remote state ALONE Ready", 107,87
"Remote state PRIM Ready", 107, 83
"Remote state SECOND Ready",107, 83
"Remote state UNKNOWN Unknown", 86, 87
“Resource …” messages
"Resource custom.id set to down by customscript",
100, 127, 128
"Resource custom.id set to up by customscript",
100
"Resource heartbeat.0 set to down by
heart", 86, 87
"Resource heartbeat.flow set to down
by heart", 86, 87
"Resource intf.ip.0 set to down by
intfcheck", 98, 127
"Resource intf.ip.0 set to up by
intfcheck", 98
"Resource module.othermodule\_ip set to
down by modulecheck", 99, 127
"Resource module.othermodule\_ip set to
up by modulecheck", 99
"Resource ping.id set to down by
pingcheck", 99, 127
"Resource ping.id set to up by
pingcheck", 99
"Resource rfs.degraded set to up by
nfsadmin", 111
"Resource tcp.id set to down by
tcpcheck", 96, 96, 127, 128
"Resource tcp.id set to up by
tcpcheck", 96
“Script …” messages
"Script start\_prim", 305, 83, 86, 86
"Script stop\_prim", 305, 83, 86, 87
"Script start\_both", 305, 89, 94
"Script stop\_both", 305, 89
“Transition …” messages
"Transition RESTART|STOPSTART from
failover rule customid\_failure", 101
"Transition STOPSTART from
failover-off", 112
"Transition SWAP from
defaultprim", 114
"Transition WAIT\_TR from failover rule
customid\_failure", 100
"Transition WAIT\_TR from failover rule
interface\_failure", 98
"Action wakeup from failover rule
Implicit\_wakeup", 96, 98, 99, 99, 100
Other messages
"Process appli.exe not running", "Service mySQL not
running", 95, 128
"Failover-off
configured", 112
"Requested prim start aborted ", 115
"Split brain
recovery: exiting alone", 87
"Split brain
recovery: staying alone", 87
"Virtual
IP set", 84
"Virtual IP
set", 89
**Index**
| |
| --- |
| Architectures mirror, farm… - 17 cloud - 353 Installation install, upgrade… - 31 Console configuration, monitoring- 45 securing (https, …) - 197 Advanced Configuration cluster.xml - 223 userconfig.xml - 229 module scripts - 305 examples - 315 Administration mirror - 105 farm - 117 advanced - 169 command line - 149 Support tests - 79 troubleshooting - 121 support SafeKit - 147 log messages - 369 Other table of contents - 5 third-party software - 365 |