---
canonical: https://safekit.evidian.com/products/high-availability-software-for-application-clustering/safekit-release-notes-8-2/
SafeKit 8.2 Release Notes — Part 6 of 7 — Restrictions & Known Problems (section 3)
---
# 3. Restrictions and known problems
 [Section](#_Restrictions_with_all) 3.1 “Restrictions and known problems from 7.4.0 to 8.2”
 [Section](#_Restrictions_and_known_2) 3.2 “Restrictions and known problems with SafeKit 8.2”
 [Section](#_Restrictions_and_Known_13) 3.3 “Restrictions and known problems with SafeKit 7.5.2”
 [Section](#_Restrictions_and_Known_12) 3.4 “Restrictions and known problems with SafeKit 7.5.1”
 [Section](#_Restrictions_and_Known_11) 3.5 “Restrictions and known problems with SafeKit 7.4.0”
This section lists the main restrictions
and known problems with SafeKit release at the time the present document was
written. This list is not exhaustive and must be completed with:
* *SafeKit Knowledge Base*
An up-to-date
list of all known problems and restrictions.
* *SafeKit User’s Guide*
It gives some
information about each SafeKit component (file replication, fail-over and
network load balancing).
* Evidian Knowledge Base
It contains a
set of technical articles created and validated by Evidian Support. For this,
log on to .
Most of the problems listed here are also
included in *SafeKit Knowledge Base* (with the associated ID:
SK-). When problems are fixed, it will be reported into [*Software Release Bulletin*](https://customercare.evidian.com/space/PDA/1252786262/Software+Release+Bulletin+-+SafeKit+8.2).
## 3.1 Restrictions and known problems from 7.4.0 to 8.2
See the [SafeKit knowledge base](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2) for an uptodate
list.
### 3.1.1 Antivirus setup
Antivirus setup may be necessary if the
server's antivirus interferes with the operation of SafeKit. In Windows, since
this issue may occur sporadically but not systematically with Windows Defender,
it is recommended to configure it properly to prevent any malfunction.
See section “Antivirus settings” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf) for the list of
legitimate SafeKit directories and processes that should not be affected by the
antivirus.
### 3.1.2 Restrictions
#### 3.1.2.1 File replication
·
Hard links are not supported into replicated
directories
·
NFS mounts of replicated directories are not
supported
·
In Windows, file system transactions, file
encryption and file compression are not supported on replicated files
·
In Linux, replicated directory cannot be a file
system root. See [SK-0030](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0030---Linux) for a
workaround
#### 3.1.2.2 Virtual IP
For farm module, when configuring the
relative weight load balancing you must use the same node names as those
defined into the SafeKit cluster configuration.
When running
SafeKit into a virtual machine and configuring = 1 million). For
getting the estimation, directly run the command on the server: safekit rfsdiff –m AM
#### 3.1.2.4 Dynamic configuration of modules
Dynamic configuration of modules (in
ALONE/WAIT states) may not work properly in some cases, such as errd
re-configuration.
The tag and
full subtree can be changed with a dynamic configuration. But, when the class set
for the is defined by the user (i.e., different from prim, both, second, sec), the
process monitoring of these processes does not apply anymore after the dynamic
configuration.
It is recommended to limit the use of
dynamic configuration of modules.
### 3.1.3 Known problems
#### 3.1.3.1 Names into the cluster configuration
In Windows, if the cluster configuration
contains DNS or host names, bugs with name resolution leads to module start or
internal communication failures. See [SK-0101](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0101---Windows) for details.
#### 3.1.3.2 Templates modules
·
When using MySQL module on a Linux configured
with SELinux, MySQL may not properly work. See [SK-0071](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0071---Linux) and [SK-0072](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0072---Linux) for workarounds
·
Hyper-V module failover may fail when
prerequisites are not met. See [SK-0088](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0088---Windows)
#### 3.1.3.3 Web console and server
·
The SafeKit web console may not properly work
with some proxy configuration
·
The browser may hang when running the SafeKit
web console. In that case, kill the browser and launch a new web console. The
SafeKit web console also hangs when using invalid client certificates
·
The web console does not work properly when
mixing HTTP and HTTPS connections
## 3.2 Restrictions and known problems with SafeKit 8.2
·
SNMP monitoring is not supported on Ubuntu
·
Once the OpenID connection has expired,
the web console does not present the login page but only unauthorized page. See
[SK-0098](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0098---Windows-&-Linux) for a workaround.
·
On
RedHat, the SafeKit package install may fail as described in [SK-0102](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0102---Linux).
## 3.3 Restrictions and known problems with SafeKit 7.5.2
Restrictions and know problems with SafeKit
7.5.1 are still valid for SafeKit 7.5.2.
## 3.4 Restrictions and known problems with SafeKit 7.5.1
Restrictions and know problems with SafeKit
7.4.0 are still valid for SafeKit 7.5.1.
·
Administer all the clusters of the inventory
with the web console
Since SafeKit
7.5, this global administration of modules from all clusters is incompatible
with the configuration of user authentication based on file or LDAP/AD server.
This means that it is incompatible with the default configuration of the
SafeKit web service. If you need this feature, change the default configuration
to the unsecure one or the secured one based on HTTPS and client certificates.
Refer to section “Securing the SafeKit web service” in the *SafeKit User’s
Guide*.
## 3.5 Restrictions and known problems with SafeKit 7.4.0
·
Since SafeKit 7.4.0.16, you can set DNS names
into the cluster configuration. It remains some problems in Windows in some
cases described in [SK-0101](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0101---Windows).
·
In Windows 10 Pro, the execution policy of PowerShell scripts must be changed as
described in [SK-0083](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0083---Windows).
·
When the Linux Network Manager is used to manage
network interfaces, if the network cable is unplugged, the network interface is
automatically unconfigured by the Network Manager. When the cable is plugged,
SafeKit may not properly detects it and sometimes requires the module stop and
start (safekit stop
–m AM ; safekit start –m AM) or dynamic update (safekit update –m AM) to use this network again.
·
In Linux, the SafeKit web server start fails
when using port 80 or LDAP/AD basic authentication. See [SK-0093](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0093---Linux).
·
SafeKit relies on a certificate for securing
module internal communications. With SafeKit <= 7.4.0.31, the validity
period for this certificate is 1 year. When this certificate expires in a
mirror module with file replication, the data synchronization fails. See [SK-0084](https://support.evidian.com/solutions/downloads/safekit/version_7.4/documentation/safekitknowledgebase.htm#SK-0084) for a solution.