Evidian SafeKit Release Notes 7.0

SafeKit Release Notes
High Availability Software for
Critical Applications
Overview
Subject
This document provides information about SafeKit 7.0 release: major
changes, restrictions and known problems, migration instructions.
Content
1 Before Starting page 5
2 Major Changes page 9
3 Restrictions and Known Problems page 23
4 Migration Instructions page 29
Table of Contents page 37
Software
Required
SafeKit 7.0
Supported
Operating
Systems
Windows and Unix; for a detailed list of supported OS refer to 1.1
Supported Operating Systems page 5. The up-to-date list of supported
operating systems can be found at
https://support.evidian.com/supported_versions/#safekit
Web Site
Evidian marketing site:
http://www.evidian.com
Evidian support site:
https://support.evidian.com
Date
June 2012
If you have any comments or questions related to this documentation, please mail us at
institute@evidian.com
Copyright © Evidian, 2012
The trademarks mentioned in this document are the propriety of their respective owners. The terms Evidian,
AccessMaster, SafeKit, OpenMaster, SSOWatch, WiseGuard, Enatel and CertiPass are trademarks registered by
Evidian.
No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any
means, electronic, mechanical or otherwise without the prior written permission of the publisher.
Evidian disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customer. In no event is
Evidian liable to anyone for any indirect, special, or consequential damages.
The information and specifications in this document are subject to change without notice. Consult your Evidian
Marketing Representative for product or service availability.
39 A2 19LT Rev04-04
3
SafeKit Release Notes
4
39 A2 19LT Rev04-04
1. Before Starting
1.1 Supported Operating Systems page 5
1.2 SafeKit Documentation page 6
This document describes the latest releases of SafeKit 7.0. We encourage users of all
previous releases to upgrade to the latest release when it is possible.
1.1
Supported Operating Systems
At the time when this document was written, SafeKit 7.0.11 release is available only for:
Windows Server 2008 (Intel x86 32-bit and 64-bit kernel)
Windows Server 2008 R2 (Intel x86 32-bit and 64-bit kernel)
Windows 7 (Intel x86 32-bit and 64-bit kernel
Windows Server 2003 (Intel x86 32-bit and 64-bit kernel)
Windows Server 2003 R2 SP2 (Intel x86 32-bit and 64-bit kernel)
Red Hat Entreprise Linux 6 at least 6.1 (Intel x86 32-bit and 64-bit kernel)
Red Hat Enterprise Linux 5 at least 5.1 (Intel x86 32-bit and 64-bit kernel)
Use Safekit 7.0.10 for:
Red Hat Enterprise Linux 4 at least 4.4 (Intel x86 32-bit and 64-bit kernel)
Suse SLES 11 SP1 (Intel x86 32-bit and 64-bit kernel)
Suse SLES 11 (Intel x86 32-bit and 64-bit kernel)
Suse SLES 10 (Intel x86 32-bit and 64-bit kernel)
Suse SLES 9 SP3 (Intel x86 32-bit and 64-bit kernel)
Use Safekit 7.0.9 for:
AIX 6.1 (PowerPC 64-bit kernel)
AIX 5.3 (PowerPC 32-bit and 64-bit kernel)
AIX 5.2 (PowerPC 32-bit and 64-bit kernel)
Solaris 10 Update 8 (SPARC 64-bit kernel)
Use Safekit 7.0.4 for:
Solaris 10 Update 4 (SPARC 64-bit kernel)
Solaris 9 (SPARC 64-bit kernel)
Go to Section 3 Restrictions and Known Problems page 23 and carefully read known
problems about SafeKit releases.
39 A2 19LT Rev04-04
5
SafeKit Release Notes
The up-to-date list of supported operating systems can be found in the Software Release
Bulletin and at the following URL:
https://support.evidian.com/supported_versions/#safekit
1.2
SafeKit Documentation
The latest version of the SafeKit 7.0 documentation can be found at
https://support.evidian.com/safekit under Version 7.0/Documentation.
1.2.1 Global Documentation
The following documents are relevant for all 7.0 SafeKit releases. These documents are
located at https://support.evidian.com/safekit under Version 7.0/Documentation.
Name
Description
SafeKit Release Notes
It describes new features of major SafeKit 7.0
releases and provides migration instructions.
Software Release Bulletin
Technical release bulletin for all SafeKit 7.0 packages
with the description of problems that are fixed.
SafeKit Knowledge Base
List of known problems and restrictions on SafeKit
7.0.
1.2.2 Guide from 7.0.10 to 7.0.11 Releases
Since 7.0.10 release, there is a uniq guide that can be found at
https://support.evidian.com/safekit under Version 7.0/Documentation:
Name
Description
SafeKit User’s Guide (english
version)
Guide de l’utilisateur SafeKit
(french version)
It covers all phases of SafeKit implementation:
architecture, initial use, installation, configuration,
administration, troubleshooting, testing and
support.
1.2.3 Guide from 7.0.x to 7.0.9 Releases
Guide from 7.0.x. to 7.0.9 releases can be found at https://support.evidian.com/safekit
under Version 7.0/Documentation/Other Documentation.
6
39 A2 19LT Rev04-04
Before Starting
These guides were in fact updated for 7.0.8. For major changes between
releases you must refer to :
2.3 Major Changes between SafeKit 7.0.8 and SafeKit 7.0.9 page 16
2.4 Major Changes between SafeKit 7.0.4 and SafeKit 7.0.8 page 18
2.5 Major Changes between SafeKit 7.0.1 and SafeKit 7.0.4 page 19
2.6 Major Changes between SafeKit 7.0.0 and SafeKit 7.0.1 page 20
Name
Description
SafeKit User’s Guide
It describes how to install, configure and administer
a cluster of SafeKit servers
SafeKit Configuration Guide
It gives a full description for SafeKit configuration.
SafeKit Tutorial (English version)
Tutoriel SafeKit (French version)
It covers all phases of SafeKit implementation:
architecture, initial use, installation, configuration,
administration, troubleshooting, testing and support.
39 A2 19LT Rev04-04
7
SafeKit Release Notes
8
39 A2 19LT Rev04-04
2. Major Changes
2.1 Major Changes between SafeKit 7.0.10 and SafeKit 7.0.11 page 9
2.2 Major Changes between SafeKit 7.0.9 and SafeKit 7.0.10 page 11
2.3 Major Changes between SafeKit 7.0.8 and SafeKit 7.0.9 page 16
2.4 Major Changes between SafeKit 7.0.4 and SafeKit 7.0.8 page 18
2.5 Major Changes between SafeKit 7.0.1 and SafeKit 7.0.4 page 19
2.6 Major Changes between SafeKit 7.0.0 and SafeKit 7.0.1 page 20
2.7 Major Changes between SafeKit 6.2 and SafeKit 7.0.0 page 20
This section gives the list of new features introduced in SafeKit since release 6.2. Go to
Section 3 Restrictions and Known Problems page 23 and carefully read known problems
about SafeKit releases.
2.1
Major Changes between SafeKit 7.0.10 and SafeKit 7.0.11
2.1.1 SafeKit Web Console
With SafeKit 7.0.11, you can administer application modules on SafeKit servers with a
javascript capable web browser (tested browsers are Internet Explorer 8 and 9; Firefox
12; Chrome 18). For accessing the SafeKit web console, open the URL:
http://servername:9010 where servername is the network name or Ip address in dot
notation of the server you want to administer. See SafeKit User’s Guide for using the
web console.
Old SafeKit java console, SafeMonitor, is still delivered with the SafeKit package but we
encourage users to use the new SafeKit web console. For users that want to keep using
SafeMonitor, you can download it from the URL http://servername:9000.
The mirror.safe and farm.safe delivered with SafeKit 7.0.11 have changed,
compared to previous releases, for nice deployment with the web console.
Modules installed in previous releases can anyway be deployed with the web
console.
2.1.2 IPv6 support
SafeKit now supports using IPv6 addresses into configuration file. But there are some
restrictions described in Section 3.1.1 IPv6 support page 23.
2.1.3 Load-balancing rules configuration change
For load-balancing rules set in farm architecture, the configuration values for proto and
filter attributes have been restricted: proto="forward" and filter="on_route" are
no more supported.
2.1.4 IP address checker
Since SafeKit 7.0.9, the package delivers a custom checker for detecting IP address
conflicts. This custom checker has been replaced in 7.0.11 by an IP checker so as to
simplify user configuration. In UNIX and Windows, it checks that the IP address is locally
defined; in Windows it also detects IP conflicts. See SafeKit User’s Guide for configuring
39 A2 19LT Rev04-04
9
SafeKit Release Notes
an IP checker. The IP checker configuration is automatically generated for testing the
virtual IP address when writting check=”on” into the <virtual_addr> tag.
2.1.5 Split brain checker
SafeKit provides a new split brain checker that is suited for mirror architectures. Split
brain is a situation where, due to temporary failure of all network links between SafeKit
nodes, and possibly due to software or human error, both nodes switched to the primary
role while disconnected. This is a potentially harmful state, as it implies that the
application is running on both nodes. Moreover, when file replication is enabled,
modifications to the data might have been made on either node.
The split brain checker detects the loss of all connectivity between nodes and select only
one node to become the primary. See SafeKit User’s Guide for configuring a splitbrain
checker.
2.1.6 SafeKit package install
In Windows, since 7.0.10 you can choose the prefix for the root installation path of
SafeKit (see Section 2.2.4 SafeKit package install and upgrade page 13). SafeKit 7.0.11
handles embedded spaces in the prefix path name.
2.1.7 Security fix in Windows
In Windows, access to the SafeKit installation tree has been restricted to all users except
the administrator.
2.1.8 File replication configuration in Unix for Oracle Direct NFS
Since SafeKit 7.0.11, you can configure SafeKit file mirroring with Oracle 11g Direct NFS.
You have first to configure oracle for Direct NFS while SafeKit and Oracle are stopped.
For this refer to the Oracle documentation. It consists in changing the ODM library by
running:
cd $ORACLE_HOME/lib
cp libodm11.so libodm11.so_stub
ln –s libnfsodm11.so libodm11.so
Then you can start Oracle and check that Direct NFS is enabled. Oracle records the use of
Direct NFS in alert.log and also in internal catalog v$dnfs tables. For instance, you can
check the table of servers accessed using Direct NFS by running:
su - oracle
sqlplus
system (login)
system (password)
select * from v$dnfs_servers;
When Oracle is properly configured for Direct NFS, you can configure SafeKit file
mirroring for enabling Oracle NFS connections with SafeKit nfsbox process. Edit the
module configuration file userconfig.xml and insert into the <rfs> tag the
attribute: pmapset="on". This option can be applied only on one module. Then apply the
new configuration and start the module. You can check that Oracle uses Direct NFS and
connects to the nfsbox port instead of the default standard nfsd port 2049.
The nfsbox port is the nfs_port listed by the command safekit module getports -m
AM. To check connections, you can read the alert.log and v$dnfs tables. You can also
run the command lsof -Pnl +M -i4 (for IPv4) orlsof -Pnl +M -i6 (for IPv6) that
10
39 A2 19LT Rev04-04
Major Changes
lists all processes connections. You should have oracle processes that connect
to nfs_port.
To roll back to the standard Oracle configuration, stops the module, reconfigure it with
the attribute: pmapset="on" removed and revert Oracle configuration for Direct NFS.
2.2
Major Changes between SafeKit 7.0.9 and SafeKit 7.0.10
2.2.1 File reintegration changes
In previous SafeKit releases, when one file has been modified on the server being into
ALONE state, it is fully copied on the other server during the reintegration phase. This
can be over killing when the file is big and only some parts have been modified. File
reintegration has been improved in 7.0.10 to copy only modified zones of the file instead
of the full content. This is called zone reintegration and is enabled with
smartreintegration=”8” in <rfs> tag of module configuration file userconfig.xml.This
is the default value that can be set to “5” so as to disable zone reintegration.
The attribute ruzone_blocksize in <rfs> tag defines the size in bytes of zones. The
default value is 65536 and it must be multiple of packetsize attribute value. In UNIX,
packetsize is dynamically got from the NFS server. An error will be logged if it is not
compatible with the default value and you will have to change ruzone_blocksize value
in userconfig.xml.
To implement zone reintegration, rfs component must track all changes on the replicated
files. These changes are automatically saved on SafeKit nice stop into SAFEVAR directory
(/var/safekit in Unix and c:\safekit\var in Windows if SystemDrive=c:). For each
replicated files it saves (1300 + n*32) bytes where n is the number of modified zones.
Zone reintegration is automatically disabled:
on server or SafeKit crash since changes have not been saved ;
on replicated directories or files changes while SafeKit is stopped since changes
have not been tracked ;
on SafeKit upgrade since changes are not kept (for compatibility reasons).
on module re-configuration in Windows ; on replicated directory configuration
change in Unix.
In Windows, changes are tracked by the rfs driver. Thus, any time the rfs driver is
stopped, zone reintegration is also disabled. This is the case:
on rfs driver manual restart ;
on module configuration.
In Windows, to enable zone reintegration after reboot when the module has been
properly stopped, rfs component use the NTFS USN change journal to check that saved
information on zones are still valid after reboot. When the check succeeds, zone
reintegration can be applied on the file; otherwise, full reintegration must be used. To
enable the use of USN change journal, set namespacepolicy="3" in <rfs> tag (default
value is 1). Check based on USN change journal can fail when:
the NTFS volume does not have a USN change journal (see fsutil usn command
for creating USN change journal on a volume)
39 A2 19LT Rev04-04
11
SafeKit Release Notes
the USN change journal associated to the volume has been deleted/recreated for
administration reasons
a discontinuity in the USN journal is detected
In Windows and UNIX, all replicated files are now fully copied on special module start:
safekit prim, safekit primforce and safekit second. This policy applies for any
smartreintegration value configuration.
Special care must be taken when restoring replicated directory content from a backup.
For performance reason, it is better to restore data while SafeKit is stopped. Then, the
server with the up-to-date data must be started with safekit prim and the other one
with safekit second.
2.2.2 File replication configuration changes in Windows
From SafeKit 7.0.9.30, the attribute nfsbox_options has been added to <rfs>. It is used
to specify the policy to apply when a reparse point of type MOUNT_POINT is present in the
replicated directory tree. This policy applies to all replicated directories.
MOUNT_POINT reparse points in NTFS can represent two types of objects: an NTFS mount
point (for example the D:\directory) or an NTFS "directory junction" (a form of
"symbolic link" to another part of the file system namespace).
When nfsbox_options="cross", the MOUNT_POINT reparse point content itself is not
replicated/reintegrated. It is evaluated and the reintegration/replication process the
target content as it would do for the content of a standard directory. This is useful for
instance when a replicated directory is a mount point (e.g. replicating a "drive letter"
root). This is the default configuration value.
When nfsbox_options="nocross", the MOUNT_POINT reparse point content itself is
replicated/reintegrated, but not evaluated. Reintegration does not descend into the
target of the reparse point. This is useful for instance when a replicated directory tree
contains NTFS "junctions" that point to another part of the replicated tree (e.g. when
replicating a postgresql database, as postgresql is known to need such objects).
2.2.3 Replicated directory on-line verification
You can check that files are identical on the primary and the secondary, in order to verify
file reintegration and file mirroring, by using the following commands.
1. safekit rfsverify –m AM > /tmp/logverify
This command runs on-line verification of replicated directory trees and regular
files content of the module AM. It uses the same locking mechanisms as the one
used by the file reintegration so as to run the verification without stopping
accesses on the primary. When a difference in file content is detected, the error is
logged and the verifier stops. The verifier’s log is in XML format and can be saved
into a file (/tmp/logverify in the example).
2. cat /tmp/logverify | safekit -r flatlogdump -O [ stdout | <file name>
]
This command translates the XML log into a readable log on standard output or in
file.
12
39 A2 19LT Rev04-04
Major Changes
Since running the verifier leads to an overhead on the servers (for reading trees and files
with locking), it must be used with caution on a production server. Even with locking, the
verifier can detect an error while it is a transient inconsistency, in the following cases:
in Windows, because modifications are done on disk before being replicated;
when async="second" because reads can bypass the asynchronous writes.
To discriminate false error detection with true inconsistency, you have to run once again
the verifier while there is no more access on the primary (application activity) and on the
secondary (mirroring activity). If verifier logs an error again, the source and destination
are different. In Windows, some files may still be different while there is no
reintegration/mirroring error. This occurs on files that are modified with SetvalidData (it
extends a file without resetting the content of the new extend; the content is then the
one that is present on the disk at this time).
On-line verifier can be automatically called after file reintegration and before going into
the secondary state by setting verify=”on” in <rfs> tag. This option can be set for tests
but is not recommended on production servers for performance reasons.
2.2.4 SafeKit package install and upgrade
From latest 7.0.9 packages (produced after May 2010), SafeKit package upgrade
procedure has been improved. It mainly consists in not removing installed application
modules so as to not have to reinstall them after the upgrade. The upgrade procedure is
fully detailed in SafeKit User’s Guide (see Section 1.2.2 Guide from 7.0.10 to 7.0.11
Release page 6).
Since 7.0.10 package, Windows installation has been changed for providing new install
options. These options are get by clicking on “Options” button in “Before Starting
Installation” window. You get the following window.
39 A2 19LT Rev04-04
13
SafeKit Release Notes
You have to install the C Runtime of SafeKit Core but you can choose to not install
(install is the default):
the SafeKit Network Load Balancing Driver
NDIS5 IM Driver in Windows 2003 or NDIS6 IM Driver in Windows 2008 or above.
It is the kernel part of vip component. When not installed, you will not be able to
set <virtual_interface> that is needed for running farm modules with load
balancing.
the SafeKit File Replication Driver
It is the kernel part of rfs component. When not installed, you will not be able to
run mirror modules with file mirroring.
SafeKit Packet Driver
It provides the arpreroute feature (see “Virtual IP address takeover for
real_interface”) necessary in Windows 2008.
SafeKit Application Modules
It is the set of application modules templates delivered with SafeKit.
With the Browse button, you can set the prefix, a pathname that do not have embedded
spaces, for root installation path for SafeKit. By default, it is c:\safekit (if
SystemDrive=c:).
When a Safekit 7.0.10 version is installed on a Windows 2008 operating system (or
above):
The TCP/IP registry configuration setting (DisableDHCPMediaSense) is not applied
anymore, since this setting is now meaningless on those OS versions.
The NTFS registry configuration setting (NtfsDisable8dot3NameCreation = 1) is
not applied anymore, since the default value (volume-dependant configuration) is
more flexible. Beware that when short names (8.3 DOS compliant aliases) are
used to access files, Safekit replication may encounter problems on certain
patterns (involving name tunneling).Moreover, access using short names are not
guaranteed to work consistently across failover. Users are strongly encouraged to
disable short name creation on volumes containing Safekit replicated directories,
using the fsutil command. For example, to disable short names on the volume
whose GUID is{928842df-5a01-11de-a85c-806e6f6e6963}, type:
fsutil 8dot3name set Volume{928842df-5a01-11de-a85c-806e6f6e6963}
2.2.5 SafeKit Network Load Balancing Driver Install
In Linux, the SafeKit Network Load Balancing Driver (vip kernel module) is no more
automatically installed with SafeKit package. It will be installed (after compiling if
necessary) on module configuration if it uses <virtual_interface>.
In Windows, starting with 7.0.10.8, to avoid configuration problems on platforms using
software vlans, the vip kernel module is not attached to all network interfaces at
installation time. Rather, vip driver binding are activated on demand at configuration
time, at the first reference of a given network interface.
In Windows 2003, since the vip driver is an NDIS5 intermediate driver that is not WHQL
signed, an administrator must access the newly bound interface's property sheet (the
14
39 A2 19LT Rev04-04
Major Changes
one onto which the new virtual IP address will be added) and click OK to validate the
binding, otherwise the safekit module instance referencing this binding will not start (the
log will contain a line saying vipplug loading failed). This behavior is a consequence of a
Microsoft design choice, it is not overridable, and does not depend of the current driver
signing policy. On further references to the same network interface (possibly by other
Application Module configurations), the above procedure is not needed.
In Windows 2008, the loadbalancing uses an NDIS6 filter technology, and the above
procedure is not needed.
2.2.6 Virtual IP address takeover for real_interface in Windows 2008
Windows 2008 host do not perform anymore gratuitous ARP during IP address setting.
This means that ARP tables of switches, routers and other hosts are not refreshed, in
mirror architecture with real_interface, on module failover when the virtual IP address
moves on the standby server. Thus, clients are not rerouted to the new primary server.
To refresh ARP tables, you must set arpreroute="on" as shown below:
<vip>
<interface_list>
<interface check="off" arpreroute="on">
<real_interface>
<virtual_addr addr="VIRTUAL_TO_BE_DEFINED" where="one_side_alias"/>
</real_interface>
</interface>
</interface_list>
</vip>
2.2.7 Miscellaneous
SafeKit log messages
SafeKit log messages have been changed so as to ease log analysis by the end
user. The command safekit logview displays now only messages for the end user
(with levels I and E). To display all the messages from the log, use the command:
safekit logview –A.
SafeKit license
SafeKit 7.0.10 can now start with no license key, but it will stop every 3 hours.
SafeKit web server for IPv6
SafeKit Apache web server is now configured to support IPv6.
New module template: vhd.safe
vhd.safe is a module template that implements a mirror cluster (primarybackup), with real-time file replication and automatic failover of Windows 2008
Virtual Hard Disk (VHD).
Application modules templates layout
Since 7.0.10 SafeKit, application modules templates are now installed under:

SAFE/Application_Modules/generic
39 A2 19LT Rev04-04
15
SafeKit Release Notes
for generic modules mirror.safe and farm.safe

SAFE/Application_Modules/demo
for all other templates
(where SAFE is the root installation path).
2.3
Major Changes between SafeKit 7.0.8 and SafeKit 7.0.9
2.3.1 File reintegration and replication changes
File reintegration has been improved to not copy twice file blocks when file modification
and synchronization occur at the same time. This optimization, suited for big and log
files, is enabled with smartreintegration=”5” in <rfs> tag of module configuration file
userconfig.xml. This is the default value that can be set to “4” so as to revert to the
reintegration implementation of the 7.0.8.
In Windows, the rfs filter has been modified for better reliability and for logging
transactional opens provided by Windows 2008. This allows to detect file system
transactions that are not supported by SafeKit replicated file system.
2.3.2 Degraded mode for mirror architecture with file replication
The implementation of degraded mode, introduced in SafeKit 7.0.8.25, has been
enhanced thanks to the new daemon nfsadmin.
When nfsbox, the main rfs component, encounters a severe error, it goes into degraded
mode on the primary server instead of stopping. This mode is also enabled on abnormal
exit of nfsbox.
The secondary server, if one, then runs a stopstart and blocks until the other server
comes back into default mode. This improves operational continuity since there is no
restart or failover of the application. But in degraded mode, file mirroring and high
availability is no more provided. The alone degraded server must be restarted as primary
to come back into default mode. This is a manual operation that must be ran by the
administrator (stop-prim or stopstart via SafeMonitor or safekit command) when it
knows that stopping the application is not critical. The other server will then run file
reintegration and become secondary.
You can read server state to get its mode (state via SafeMonitor or safekit command).
For instance, the following shows the state of a server in degraded mode (ALONE state
and up value for resource rfs.degraded):
--------------------- mirror State --------------------Local (127.0.0.1) : ALONE (Service : Available)
Resources
Name State Since
heartbeat.0 up 2009-07-23 08:22:32
heartbeat.flow up 2009-07-23 08:22:32
rfs.uptodate up 2009-07-23 08:22:37
rfs.lastprimstate down 2009-07-23 08:22:37
rfs.swapping down 2009-07-23 08:22:32
16
39 A2 19LT Rev04-04
Major Changes
rfs.degraded up 2009-07-23
2.3.3 Extension of supported platforms
Windows 2008 is a new supported platform.
2.3.4 New module template: hyperv.safe
hyperv.safe is a module template that implements a mirror cluster (primary-backup),
with real-time file replication and automatic failover of Windows 2008 server
virtualization with HyperV. At this time, this module is experimental since some problems
remains. In particular, snapshots and virtual machine configuration changes are not
propagated to the secondary machine. Theses changes must then be manually reported
on the backup server.
2.3.5 Virtual Ip conflict detection in Windows
SafeKit 7.0.9 delivers a custom checker for detecting IP address conflicts useful in case
of return from network isolation conditions in the context of one_side_alias virtual IP
configurations. For instance, to check for absence of conflicts on virtual address
192.168.208.125 and run a stopstart if there is one, add a custom checker and a
failover rule as follows into the module configuration file userconfig.xml:
<check>
<custom ident="noipconflict" when="pre" exec="%SAFEBIN%\ipconflictcheck.exe" arg="-D -A
wait 192.168.208.125" />
</check>
<failover>
<![CDATA[
ipconflict:
if (custom.noipconflict == down) then stopstart();
]]>
</failover>
2.3.6 SafeKit web server
The SafeKit web server has been upgraded to Apache 2.2.11 and now provides a SafeKit
apache module for replying to SafeMonitor requests. This saves CPU cycles when
monitoring many safekit modules on low end servers.
2.3.7 SafeMonitor messages internationalization
From 7.0.9.26, SafeMonitor messages are located into a separate catalog messages file
so as to be able to change messages according to the language. SafeMonitor is delivered
with English messages. The following describes how to add a French catalog messages
file:
1. Unzip safemonitor.jar
2. Copy MessageCatalog.txt (English) in MessageCatalog_fr.txt
3. Edit MessageCatalog_fr.txt
39 A2 19LT Rev04-04
17
SafeKit Release Notes
It is a set of lines with key = value. Translate values in French.
4. Save in UTF-8 format
5. Install a Java SDK with native2ascii command in the bin directory
6. Run
native2ascii -encoding UTF-8 MessageCatalog_fr.txt MessageCatalog_fr.properties
MessageCatalog_fr.properties contains Unicode-encoded (\udddd notation)
characters required by java (java.util / ResourceBundle class).
7. Update safemonitor.jar with jar command in bin directory of Java SDK
jar uf0 safemonitor.jar resource/MessageCatalog_fr.properties
jar uf0 safemonitor.jar resource/MessageCatalog_fr.txt
The keywords Start, Stop, Restart, Swap, Prim, Second, ForceStop, StopStart
must be translated in a single word (without blank) else the enable/disable
logic of these buttons will not work.
When running safemonitor.jar with no parameter, the catalog is chosen depending on
your locale language and country. Either a
MessageCatalog_lang[_country].properties matches and is used ;
or default MessageCatalog.properties is used
For more information, see ResourceBundle in java.util of java documentation.
You can select the MessageCatalog_fr.properties by running:
java -jar safemonitor.jar -lang fr
You can also build a catalog with the country (ex.: MessageCatalog_fr_FR.properties)
and select it with:
java -jar safemonitor.jar -lang fr -country FR
2.3.8 New module template: drdb.safe
From 7.0.9.20 release, SafeKit delivers the application module drdb.safe that provides
file mirroring with DRDB in Linux. It can be interesting to use DRDB for file mirroring
instead of rfs to remove performance problems due to NFS and special kernel
dependency. But, this implies some prerequisites on disk organization and is more
complex to configure than rfs component.
2.4
Major Changes between SafeKit 7.0.4 and SafeKit 7.0.8
2.4.1 File replication enhancement
File replication has been improved for better scalability and performances. File replication
now supports 1,000,000 files and 500 GB of data.
The new framework is based on TCP for reliable communications; it offers asynchronous
IO on the secondary server for boosting write operations, and provides a new algorithm
for reducing resynchronization time on the backup server after failure.
18
39 A2 19LT Rev04-04
Major Changes
2.4.2 Extension of supported platforms
SafeKit 7.0.8 now supports Suse SLES 10 and Red Hat AS 5.1, but with some restrictions
when using file replication: see Section 3, "Restrictions and Known Problems" for more
details.
2.4.3 New module template: virtualserver.safe
virtualserver.safe is a module template that implements a mirror cluster (primarybackup), with real-time file replication and automatic failover of virtual servers.
The full virtual server status is replicated. It consists in the Windows operating system
and its configuration, applications with their license, and all the disk content.
In case of recoverable failure, the primary server dumps the virtual server
memory into replicated files. The backup server can then quickly restart the
virtual server from its latest status.
In case of unrecoverable failure, the failover procedure on the backup server
consists in rebooting the virtual server.
The required configuration for running SafeKit with Virtual Server is:
2 physical servers with Windows 2003.
Microsoft Virtual Server 2005 Enterprise Edition R2 installed on both physical
servers (free).
SafeKit package and virtualserver.safe installed on both physical servers.
2.5
Major Changes between SafeKit 7.0.1 and SafeKit 7.0.4
The virtual IP address component (<vip>) has been enhanced:

It allows the setting of one multicast Ethernet address as the virtual MAC
address associated with the virtual IP address(es) ;

It removes the restriction on virtual IP address configuration of SafeKit
7.0.1; the user can configure two modules with one virtual IP address on
the same physical network interface. Each virtual IP address will be
mapped onto its own virtual MAC address.
The virtual hostname component (<vhost>) is available on Windows.
The file replication component (<rfs>) offers a new configuration option (only on
UNIX) for specifying the list of non-replicated entries as a regular expression.
SafeKit provides a new built-in checker, the SafeKit application module checker
(<module> tag from <check> component). The module checker is used to test the
availability of an external (local or remote) module required to execute the
application correctly.
All these features are detailed in SafeKit Configuration Guide (see Section 1.2.3 Guide
from 7.0.x to 7.0.9 Releases page 6).
39 A2 19LT Rev04-04
19
SafeKit Release Notes
2.6
Major Changes between SafeKit 7.0.0 and SafeKit 7.0.1
SafeKit is available in AIX , Solaris, Windows and Linux.
The file replication component (<rfs>) has been redesigned to remove restrictions
on rename operations.
The file replication component supports the replication of file ACLs in Windows
(<rfs acl="on">).
For the free trial of the product, you have to first download the package and then
obtain a one-month free trial key at the following URL
http://www.evidian.com/safekit/requestevalkey.php
2.7
Major Changes between SafeKit 6.2 and SafeKit 7.0.0
With the new multiple application modules feature introduced in SafeKit 7.0.0, SafeKit
can run several applications simultaneously on the same physical servers with
independent fail-over.
Thus, sophisticated high availability architectures can be implemented.
2.7.1 Mix of farm and mirror applications on the same physical servers
Such architecture makes it possible to implement a multi-tiered architecture such as
apache.safe (farm with load balancing and fail-over) and mySQL.safe (mirror with file
replication and fail-over) on only two servers on which the two applications are running.
Thus, load balancing, file replication and fail-over can be consistently implemented on the
same physical servers.
2.7.2 Mutual takeover with 2 application servers
Each application server works as a backup for the other one. For example, the
Oracledb1.safe module has an execution priority on the first server, and
Oracledb2.safe has priority on the second server. When one application server fails, the
two applications, Oracledb1 and Oracledb2, are active on the remaining physical server.
And after the failed server is restarted, each application runs again on its default primary
server. Note that in case of failure of one server in such architecture, the remaining
server must be able to support the load of both applications.
2.7.3 N-1 architecture with N active application servers and only one backup
If one of the N active application servers fails, the single backup server restarts the
application that was running on the failed server. When the failed server restarts, the
application returns from the backup to the active server. Unlike the mutual-takeover
architecture, the backup server cannot be overloaded by the execution of several
applications, assuming that there is only one failure at a time. Note that the solution can
support several application server failures at the same time, but in this case all the failed
applications will be restarted on the single backup server.
20
39 A2 19LT Rev04-04
Major Changes
2.7.4 Independent application fail-over
One advantage of the multi-module feature is the existence of independent fail-over and
restart procedures per application.
With the old single-module restriction in release 6.2, three applications (Appli1, Appli2
and Appli3) had to be integrated in the same ".Safe". Start and stop scripts of the unique
".Safe" included the start and stop of all 3 applications. And if a critical Appli1 process
failed, all three applications (Appli1, Appli2 and Appli3) were restarted by executing the
unique stop and start scripts.
With the new multiple application modules feature, each application is integrated in a
different ".Safe" module (Appli1.Safe, Appli2.Safe, Appli3.Safe). Each module contains
start and stop scripts for one application. And if a critical process of Appli1 fails, only
Appli1 is restarted. The other application modules stay in their current state (no fail-over
for them).
2.7.5 Load balancing of applications controlled by an administrator
With the SafeKit console (a multi-platform Java application) and the multi-module
feature, an administrator can easily decide what application runs on what server. For
example, if Appli1, Appli2 and Appli3 are running on server1 and no application is
running on server2, the administrator can switch Appli3 to server2, just by clicking the
swap button in the SafeKit console. Appli3 will be stopped on server1 and started on
server2.
2.7.6 Process monitoring enhancement
The <errd> monitoring process has been enhanced with the multi-module feature.
Instead of only monitoring the name of processes, <errd> can be configured on the
name of the process plus its list of arguments. Also, it is possible to include regular
expressions in the list of arguments.
Example: name="oracle" argregex=".*db1.*" will monitor an oracle instance running
on the database "db1" (db1 being in the arguments of the oracle process).
39 A2 19LT Rev04-04
21
39 A2 19LT Rev04-04
22
3. Restrictions and Known Problems
3.1 Restrictions and Known Problems with SafeKit 7.0.11 page 23
3.2 Restrictions and Known Problems with SafeKit 7.0.10 page 24
3.3 Restrictions and Known Problems with SafeKit 7.0.9 page 26
3.4 Restrictions and Known Problems with SafeKit 7.0.8 page 26
3.5 Restrictions and Known Problems with SafeKit 7.0.4 page 27
This section lists the main restrictions and known problems with the latest 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 https://support.evidian.com.
Most of the problems listed here are also included in SafeKit Knowledge Base (with the
associated ID: SK-<num>). When problems are fixed, it will be reported into Software
Release Bulletin.
3.1
Restrictions and Known Problems with SafeKit 7.0.11
The restrictions on SafeKit 7.0.10 (see Section 3.2 Restrictions and Known Problems with
SafeKit 7.0.10 page 24) are still valid for SafeKit 7.0.11.
3.1.1 IPv6 support
SafeKit now supports configuration with Ipv6 addresses with the following restrictions.
3.1.1.1
Restrictions for mirror architectures
In mirror architecture, when defining a network, such as heartbeat network into
<heart> tag and replication flow into <rfs> tag, the 1st server address and the 2nd
server address must both be IPv4 or IPv6.
At the time the document was written, all hearbeat networks must be either IPv6 or
IPv4. It will be fixed and notified into SafeKit Software Release Bulletin.
3.1.1.2
Restrictions for farm architectures
The basic mechanism to synchronize a farm of servers is a group communication
protocol, named spread, which automatically detects the available memberships. Since
this protocol does not support IPv6, you must configure the farm topology, into the
<farm> tag, with Ipv4 addresses only. The virtual IP addresses can nonetheless be IPv6
addresses.
39 A2 19LT Rev04-04
23
SafeKit Release Notes
3.1.2 HTTPS
When using Internet Explorer 9 and HTTPS for running the SafeKit web console, you
may get an error when downloading files from the SafeKit web servers. To fix this
issue refer to http://support.microsoft.com/kb/2549423.
In
Manage tab/ Remote server, the operation
Save to Application_Modules is not
permitted when the server is configured for HTTPS.
3.1.3 Web console and IE 9
Latest KB2761451 Cumulative Update for I.E. 9 causes I.E. to stop responding.
3.2
Restrictions and Known Problems with SafeKit 7.0.10
The restrictions on SafeKit 7.0.9 (see Section 3.3 Restrictions and Known Problems with
SafeKit 7.0.9 page 26) are still valid for SafeKit 7.0.10.
3.2.1 File Replication in Windows 2008 SP2, Windows 2008 R2, Windows 7
File replication errors may occur when an application extends a file (most notably, in
write_through mode): this problem is due to misbehaviour of the Microsoft NTFS.sys
filesystem driver described on the Microsoft support site at
http://support.microsoft.com/kb/976538/en-us/. It is mandatory to update Windows
(2008 SP2, 2008 R2, 7) at least to the level indicated in the above Microsoft knowledge
base entry, otherwise files may not be correctly replicated.
3.2.2 Red Hat 6
If NetworkManager is used to manage network interfaces, SafeKit can't work properly in
case of network failure when configuring a <virtual_address>. To configure network
interfaces, you have to stop the NetworkManager and use system-config-network
instead. For this, on the SafeKit server run:
1.
service NetworkManager stop
2.
chkconfig NetworkManager off
3.
chkconfig network on
4.
service network start
And then, run system-config-system to manage your network interfaces.
See also SK-0034.
3.2.3 Virtual IP
When configuring <virtual_interface> in Windows 2003, you have to follow the
instructions described in 2.2.5 SafeKit Network Load Balancing Driver Install page 14.
Otherwise, the module start will fail (see also SK-0032).
3.2.4 Boot start of modules
Modules configured to start at boot (with safekit boot –m AM on) are automatically
started on boot by the SafeKit administration service (safeadmin). On some Windows
platforms, the module boot start fails because the network configuration is not ready.
Since a fix is not yet available, you can apply one of the wo workarounds below.
First workaround
24
39 A2 19LT Rev04-04
Restrictions and Known Problems
It consists in setting manual start for the safeadmin service and applying the following
procedure (it must be applied on all SafeKit servers):
Start the MMC console with the mmc command line
File - Add/Remove Snap-in Add - "Group Policy Object Editor" – OK
Then, under "Console Root"/"Local Computer Policy"/"Computer
Configuration"/"Windows Settings"/"Scripts (Start-up/Shutdown)", double click on
" Start-up "
Click on Add then set for "Script Name:"
<path for safekitbootstart.cmd>
The script safekitbootstart.cmd contains:
@echo off
rem change installation path if not installed on C:\safekit
c:\safekit\private\bin\sleep.exe 90
net start safeadmin
Second workaround
Alternatively, you may set the safeadmin start mode to "Automatic, delayed". As
administrator :
Start the "services" control panel applet
Select the "safeadmin" service, right-click on it to bring up the contextual menu, and
select "properties"
In the "properties" panel, change the "startup type" value to "Automatic (delayed
start)"
Close the "properties" panel
3.2.5 Zone reintegration after Windows server reboot
In Windows, to enable zone reintegration after reboot when the module has been
properly stopped, you must:
set namespacepolicy="3" in <rfs> tag of module configuration file
userconfig.xml.
Activate USN change journal on the volume containing the replicated directories
(see fsutil usn command for creating USN change journal on a volume).
Even with this configuration, full reintegration is used instead of zone reintegration
when:
the USN change journal associated to the volume has been deleted/recreated for
administration reasons
a discontinuity in the USN journal is detected
39 A2 19LT Rev04-04
25
SafeKit Release Notes
3.3
Restrictions and Known Problems with SafeKit 7.0.9
The restrictions on SafeKit 7.0.8 (see Section 3.4 Restrictions and Known Problems with
SafeKit 7.0.8 page 26) are still valid for SafeKit 7.0.9. But, there is now a work-around
for replicating a file system root in Linux (see SK-0030).
3.3.1 File Replication in Windows 2008 SP2, Windows 2008 R2
File system transactions provided with Windows 2008 are not supported.
SafeKit 7.0.9.30 brings a correction to file replication errors that may occur when an
application extends a file (most notably, in write_through mode). This problem is a part
due to misbehavior of the Microsoft NTFS file system driver and is described on the
Microsoft support site at http://support.microsoft.com/kb/976538/en-us/.
To avoid file corruption, it is mandatory to update the windows operating system at least
at the level indicated in the above Microsoft Knowledge Base entry, and to upgrade
SafeKit at least at the level 7.0.9.30.
3.3.2 Aix 5.2
Aix 5.2.0 system whose current ML is 5200-00 (i.e. base level), must be updated to the
maintenance level 01 (see
http://www-opensup.bull.com/PTF/packs/ml/aix52/00to01.html).
3.3.3 Solaris 10
SafeKit load-balancing and file mirroring features implies to install the SafeKit package
into the "global" zone (see SK-0028).
3.3.4 SuSe SLES 11
In SLES 11, modules in farm mode are unable to start because vip kernel module is not
allowed to load. See SK-0029 for solving this problem.
In SLES 11 SP1, vip kernel module is not supported. It means that you can not yet
implement a farm module solution on this operating system. It will be notified into
SafeKit Software Release Bulletin when it will be supported.
3.4
Restrictions and Known Problems with SafeKit 7.0.8
The restrictions on SafeKit 7.0.4 (see Section 3.5 Restrictions and Known Problems with
SafeKit 7.0.4 page 27) are still valid for SafeKit 7.0.8.
3.4.1 File Replication and Red Hat 5
The Red Hat 5 kernel freezes with file replication on heavy write load (see SK-0018). In
that case, the system hangs but the other server from the cluster does not detect the
error since network communication is still working. You then have to reboot the broken
server.
The kernel freeze is under investigation with Red Hat. In the meantime, you can try to
the change kernel parameters as follows:
26
39 A2 19LT Rev04-04
Restrictions and Known Problems
1. Insert into the file /etc/sysctl.conf:
vm.dirty_ratio=10
vm.dirty_background_ratio=2
2. Run sysctl -p
Our tests show that these settings help to solve the problem in some cases.
Linux kernel patches fix this problem but they are not yet integrated into Red Hat
distribution. To allow the use of SafeKit file mirroring with Red Hat 5, we deliver a
specific kernel that contains the appropriate patches. Refer to
https://support.evidian.com/data2/downloads/safekit/version_7.0/platforms/linux/curren
t_versions/linux_kernel/q006080.htm for downloading and installing this kernel.
3.4.2 SafeKit SNMP Agent in Windows
SafeKit SNMP agent (safesnmpagent service) does not work in Windows with SafeKit
7.0.8.7. This problem has been fixed in SafeKit 7.0.8.25.
3.5
Restrictions and Known Problems with SafeKit 7.0.4
3.5.1 File replication
Windows
File encryption and file compression are not supported on replicated files (see SK0009).
UNIX
Replicated directory cannot be a file system root when mountover="on"
(mandatory on Linux) (see SK-0010).
Linux
NFS server on RedHat 4 Update 3 does not support ACL. Thus, acl attribute for a
replicated directory cannot be set to “on" (see SK-0012).
All OS
NFS mounts of replicated directories are not supported (see SK-0014).
Hard links are not supported.
3.5.2 Virtual IP
Solaris
SafeKit 7.0.4.18 fixes the virtual interface support on recent Solaris 10 kernels
(see SK-0016).
This version needs the "IP stack multiple instances"API level in the Solaris
Kernel.These APIs are known to be available in the Solaris 10 update, Kernel
version 4.
39 A2 19LT Rev04-04
27
SafeKit Release Notes
As from release 7.0.4.18, the VIP feature will not be available in Solaris 10
kernels that do not export the above APIs. The incompatibility will be detected
during SafeKit configuration. This message can be seen during Safekit installation:
devfsadm: driver failed to attach: vipdrv
Warning: Driver (vipdrv) successfully added to system but failed to be attached.
There is no change for Solaris 9.
28
39 A2 19LT Rev04-04
4. Migration Instructions
4.1 Migrating from SafeKit 7.0.10 to SafeKit 7.0.11 page 29
4.2 Migrating from SafeKit 7.0.9 to SafeKit 7.0.10 page 30
4.3 Migrating from SafeKit 7.0.x (< 7.0.9) to SafeKit 7.0.10 page 31
4.4 Migrating from SafeKit 7.0.x to SafeKit 7.0.9 page 32
4.5 Migrating from SafeKit 7.0.x to SafeKit 7.0.8 page 32
4.6 Migrating from SafeKit 7.0.x to SafeKit 7.0.4 page 33
4.7 Migrating from SafeKit 6.2 to SafeKit 7.0.4 page 33
4.8 Migrating from SafeKit 6.1 to SafeKit 7.0.4 page 34
4.9 Upgrading SafeKit 6.x License Keys page 35
This section gives instructions and recommendations for SafeKit server migration.
4.1
Migrating from SafeKit 7.0.10 to SafeKit 7.0.11
4.1.1 Upgrade Procedure
The upgrade procedure is fully detailed in latest SafeKit User’s Guide (see Section 1.2.2
Guide from 7.0.10 to 7.0.11 Release page 6). The upgrade preserves modules that were
previously installed. If you plan to use the new SafeKit web console, re-configure the
modules with the Deploy tab of the console.
SafeKit releases 7.0.10 can be fixed with releases 7.0.11. These releases are compatibile
in term of file replication and reintegration.
4.1.2 Migrate SafeKit Web Server Configuration
The SafeKit Web Server configuration has been completely reorganized to implement the
SafeKit Web Console.
The directory <SAFE>/web/conf contains the SafeKit web server configuration files. Either
you do not perform any special configurations and the default configuration delivered
with SafeKit will be applied after upgrade, or you have made a special configuration and
then your files have been saved during uninstall with the date as suffix. You will then
have to put back your previous changes in the new configuration files.
In SafeKit 7.0.10, the command safekit -C d <action> <arg> permit to execute an
action on all servers specified in the file SAFEVAR/default_cluster.txt. Example: safekit
-C d module list: list modules on all servers defined in default_cluster.txt
The file default_cluster.txt contains for example:
http://192.168.0.1:9000
http://192.168.0.2:9000
In SafeKit 7.0.11, you have to edit this file and replace the port value 9000 with 9010.
39 A2 19LT Rev04-04
29
SafeKit Release Notes
4.2
Migrating from SafeKit 7.0.9 to SafeKit 7.0.10
4.2.1 Recommendation for Modules using <rfs>
Releases 7.0.9 of SafeKit are fixed with releases 7.0.10. In order to reduce the downtime
of applications, we have improved the migration procedure for mirror modules using file
replication (only with mode=”read_only”). For this run the following procedure:
1. server1 and server2 are up with the SafeKit 7.0.9. server1 is primary and server2
is secondary.
2. stop the module on server2 and upgrade the server with 7.0.10. Configure the
module and start it with safekit second. SafeKit 7.0.10 will detect that the primary
server is running 7.0.9 and will use the basic reintegration protocol.
3. After server2 reintegration, server1 is primary with 7.0.9 and server2 is
secondary with 7.0.10.
At this step, don’t swap since a primary server with 7.0.10 and a
secondary server with 7.0.9 will not work. The backward compatibility is
provided only for the secondary server.
4. stop module on server1 and upgrade the server with 7.0.10. Configure the
module and start it with safekit second. This time, the 7.0.10 reintegration
protocol is used.
5. server1 and server2 are up with the SafeKit 7.0.10. server1 is secondary and
server2 is primary.
6. At this step, you can use SafeKit as usual.
4.2.2 Recommendation for Modules using <vip>
In Windows 2008, when using real_interface in <vip> configuration, you must set
arpreroute="on" as shown below, for rerouting the virtual IP address on failover:
<vip>
<interface_list>
<interface check="off" arpreroute="on">
<real_interface>
<virtual_addr addr="VIRTUAL_TO_BE_DEFINED" where="one_side_alias"/>
</real_interface>
</interface>
</interface_list>
</vip>
In Windows 2003, when using virtual_interface in <vip> configuration, after the
module configuration and before starting the module, you must access the corresponding
network interface's property sheet (the one onto which the new virtual IP address will be
added) and click OK to validate the vip kernel module binding. This procedure is needed
only the first time that this interface is configured as virtual_interface (by one or
many modules).
30
39 A2 19LT Rev04-04
Migration Instructions
4.2.3 Upgrade Package
From latest 7.0.9 packages (produced after May 2010), SafeKit package upgrade
procedure has been improved. It mainly consists in not removing installed application
modules so as to not have to reinstall them after the upgrade. The upgrade procedure is
fully detailed in latest SafeKit User’s Guide (see Section 1.2.2 Guide from 7.0.10 to
7.0.11 Release page 6). It also covers the upgrade from older releases.
4.2.4 Migrate SafeKit Web Server Configuration
The SafeKit Web Server configuration has changed to implement the SafeKit Web
Console.
The directory <SAFE>/web/conf contains the SafeKit web server configuration files. Either
you do not perform any special configurations and the default configuration delivered
with SafeKit will be applied after upgrade, or you have made a special configuration and
then your files have been saved during uninstall with the date as suffix. You will then
have to put back your previous changes in the new configuration files.
4.2.5 SafeMonitor
Old SafeKit java console, SafeMonitor, is still delivered with the SafeKit package but we
encourage users to use the new SafeKit web console. For users that want to keep using
SafeMonitor, you can download it from the SafeKit home page.
4.2.6 Miscellaneous
SafeKit log messages
SafeKit log messages have been changed so as to ease log analysis by the end
user. This implies that integrations that parse log messages via safekit
logview/safekit logsave or SNMP traps must be changed. Moreover, the
command safekit logview displays now only messages for the end user (with
levels I and E).
vipifctrl command for support
In Windows, vipifctrl command has been renamed in vip_if_ctrl.
4.3
Migrating from SafeKit 7.0.x (< 7.0.9) to SafeKit 7.0.10
Migration instructions are the same as the ones described in Section 4.4 Migrating from
SafeKit 7.0.x to SafeKit 7.0.9 page 32.
SafeKit Releases < 7.0.9 can be fixed with releases 7.0.10, but these releases are not
compatible in terms of file replication protocol. Therefore, you have to stop and upgrade
servers at the same time when migrating to release 7.0.10.
39 A2 19LT Rev04-04
31
SafeKit Release Notes
4.4
Migrating from SafeKit 7.0.x to SafeKit 7.0.9
Migration instructions are the same as the ones described in Section 4.5 Migrating from
SafeKit 7.0.x to SafeKit 7.0.8 page 32. Releases 7.0.8 of SafeKit are fixed with releases
7.0.9, but these releases are not compatible in terms of file replication protocol.
Therefore, you have to stop and upgrade servers at the same time when migrating to
release 7.0.9.
4.5
Migrating from SafeKit 7.0.x to SafeKit 7.0.8
4.5.1 Recommendation
Releases 7.0.x of SafeKit are fixed with releases 7.0.8, but these releases are not
compatible in terms of file replication protocol. Therefore, you have to stop and upgrade
servers at the same time when migrating to release 7.0.8.
You may also need to modify the file replication configuration (<rfs>) as explained later.
4.5.2 Upgrade Procedure
The upgrade procedure is the one explained in "Upgrade/Fix SafeKit Package" section of
SafeKit User’s Guide (see Section 1.2.3 Guide from 7.0.x to 7.0.9 Releases page 6)
4.5.3 <rfs> Configuration
SafeKit 7.0.8 offers improvements and performance boosts for file replication. Thus, all
tunings set into the file replication configuration (<rfs>) for release 7.0.x are no longer
required.
Moreover, some attributes are no not supported any longer since they are specific to UDP
implementation that is replaced by TCP. The following obsolete attributes must be
removed from the configuration file: nbnfsd, nbbiod, maxnbretrans, synctime,
nfs_vers, transport.
A standard 7.0.8 <rfs> configuration looks like this:
<rfs mountover="on|off" acl="on|off"
[packetsize="buffer size in bytes to be specified only for Oracle"]>
…
</rfs>
Try this default configuration and refer to the <rfs> section in SafeKit Configuration
Guide (see Section 1.2.3 Guide from 7.0.x to 7.0.9 Releases page 6) if you encounter
any problems.
32
39 A2 19LT Rev04-04
Migration Instructions
4.6
Migrating from SafeKit 7.0.x to SafeKit 7.0.4
4.6.1 Recommendation
Releases 7.0.x of SafeKit are fixed with releases 7.0.4, but since SafeKit 7.0.x and 7.0.4
are not compatible in terms of file reintegration protocol, when you upgrade from release
7.0.x to release 7.0.4 with file replication, you have to stop and upgrade servers at the
same time. This is the only constraint when migrating to release 7.0.4.
4.6.2 Upgrade Procedure
The upgrade procedure is the standard one explained in "Upgrade/Fix SafeKit Package"
section of SafeKit User’s Guide (see Section 1.2.3 Guide from 7.0.x to 7.0.9 Releases
page 6).
4.7
Migrating from SafeKit 6.2 to SafeKit 7.0.4
4.7.1 Recommendation
When migrating from SafeKit 6.2 to 7.0, you have to stop and upgrade servers at the
same time.
You also need to upgrade your SafeKit license key as described in 4.9 Upgrading SafeKit
6.x License Keys page 35
Moreover, you have to change the software error detector configuration ( <errd>) of
your application module which has been modified in 7.0 with the multi-module feature.
This is explained later.
4.7.2 Upgrade Procedure
Follow the procedure explained in "Upgrade/Fix SafeKit Package" section of SafeKit User’s
Guide (see Section 1.2.3 Guide from 7.0.x to 7.0.9 Releases page 6) to upgrade from
SafeKit 6.2 package to SafeKit 7.0.
During the upgrade procedure, you have to reboot the system between
the uninstall and the install procedures.
4.7.3 <errd> Configuration
In SafeKit 7.0, <errd> configuration is different from the one in SafeKit 6.2.
The following shows how to translate a SafeKit 6.2 configuration to a SafeKit 7.0
configuration:
SafeKit 6.2 <errd> section for a process started in start_prim <user> script
<errd>
39 A2 19LT Rev04-04
33
SafeKit Release Notes
<proc name="cdsp" failureifexit="off" failureifexception="on" action="restart" />
<proc name="alw" failureifexit="off" failureifexception="on" action="restart" />
</errd>
SafeKit 7.0 <errd> section for a process started in start_prim <user> script
<errd>
<proc name="cdsp" atleast="1" action="restart" class="prim" />
<proc name="alw" atleast="1" action="restart" class="prim" />
</errd>
Refer to <errd> in SafeKit Configuration Guide (see Section 1.2.3 Guide from 7.0.x to
7.0.9 Releases page 6) for more information.
4.8
Migrating from SafeKit 6.1 to SafeKit 7.0.4
4.8.1 Recommendation
When migrating from SafeKit 6.1 to 7.0, you have to stop and upgrade servers at the
same time.
4.8.2 Upgrade Procedure
Uninstall SafeKit 6.1
on UNIX, run safekit uninstall and reboot;
on Windows, uninstall with "Add-Remove Program" and reboot.
Refer to the 6.1 manual.
Your original configuration files userconfig.xml and user scripts are kept in the
safekit/conf and safekit/bin directories.
Install SafeKit 7.0
Refer to the installation procedure in the SafeKit User’s Guide (see Section 1.2.3
Guide from 7.0.x to 7.0.9 Releases page 6).
Do not install any pre-configured application module.
4.8.3 Configuration Migration
For more information on configuration, refer to SafeKit User’s Guide and SafeKit
Configuration Guide (see Section 1.2.3 Guide from 7.0.x to 7.0.9 Releases page 6).
Run safekit module install –m <YourApplicationName>
<SAFE>/Application_Modules/expert/upgrade.safe
(<SAFE>=/opt/safekit on UNIX and SAFE=C:\safekit on Windows).
Copy your original SafeKit 6.1 configuration files in the following directories:
<SAFE>/modules/<YourApplicationName>/conf
<SAFE>/modules/<YourApplicationName>/bin
34
39 A2 19LT Rev04-04
Migration Instructions
Remove, from your old userconfig.xml <proxyudp> tag since it is not supported
in SafeKit 7.0.
Remove, from your old userconfig.xml in the <errd>, <vhost>, <custom>,
<proxyudp> sections, any references to special scripts with an absolute path using
the old SafeKit 6.1 path. Instead, put these special scripts in
<SAFE>/modules/<YourApplicationName>/bin and set inside userconfig.xml
relative path to this directory.
For more information, see the <errd>, <vhost>, <custom> tag configurations in
SafeKit Configuration Guide.
Remove from your old start and stop scripts in
<SAFE>/modules/<YourApplicationName>/bin any references to special scripts
with an absolute path using the old SafeKit 6.1 path. Use $SAFEUSERBIN or
%SAFEUSERBIN% in your scripts. See <user> tag 7.0 configuration in SafeKit
Configuration Guide for more information.
Remove <http /> and <snmp /> from your userconfig.xml.
If you have modified snmpd.conf or httpd.conf, copy your modifications in
<SAFE>/web/conf/httpd.conf and <SAFE>/snmp/conf/snmpd.conf. See SafeKit
User’s Guide for more information.
See Section 4.7 Migrating from SafeKit 6.2 to SafeKit 7.0.4 page 33 to complete
the migration.
Run <SAFE>/safekit config –m <YourApplicationName>
Reboot
Use the new SafeKit console, SafeMonitor as described in SafeKit User’s Guide.
Once tested, you can package your migration in a new application module with
<SAFE>/safekit module package –m <YourApplicationName>
<YourApplicationName>.safe (absolute path is mandatory for
<YourApplicationName>.safe). Before packaging, set "title" and "description"
inside the file safekit/modules/<YourApplicationName>/manifest.xml, so it
can be presented correctly in the "Server Admin" tabbed panel of the
SafeMonitor.
If you put <YourApplicationName>.safe package in
<SAFE>/safekit/Application_Modules/, then your application module will be
displayed in the "Server Admin" tabbed panel of the SafeKit console as an
installable Application Module, with the title and description previously set.
Without the "web" directory and the "index.lua" file after a migration, you will
get in the "Quick Configure" tabbed panel, the userconfig.xml file. For more
information on index.lua, see SafeKit Configuration Guide.
4.9
Upgrading SafeKit 6.x License Keys
You cannot use a SafeKit 6.x license key with SafeKit 7.0. An upgrade must be ordered
to get a permanent license key.
39 A2 19LT Rev04-04
35
SafeKit Release Notes
In the meantime, you can get a free one-month SafeKit 7.0 evaluation license key from
http://www.evidian.com/safekit/requestevalkey.php.
See "Install License Key" in the SafeKit User’s Guide (see Section 1.2.3 Guide from 7.0.x
to 7.0.9 Releases page 6) for more information.
36
39 A2 19LT Rev04-04
Table of Contents
SafeKit Release Notes High Availability Software for Critical Applications ......... 1
Overview ............................................................................................................ 3
1.
Before Starting ............................................................................................. 5
1.1
Supported Operating Systems ..................................................................... 5
1.2
SafeKit Documentation ............................................................................... 6
2.
1.2.1
Global Documentation ...................................................................................................... 6
1.2.2
Guide from 7.0.10 to 7.0.11 Releases ................................................................................ 6
1.2.3
Guide from 7.0.x to 7.0.9 Releases .................................................................................... 6
Major Changes .............................................................................................. 9
2.1
Major Changes between SafeKit 7.0.10 and SafeKit 7.0.11 ............................. 9
2.1.1
SafeKit Web Console ........................................................................................................ 9
2.1.2
IPv6 support ................................................................................................................... 9
2.1.3
Load-balancing rules configuration change.......................................................................... 9
2.1.4
IP address checker .......................................................................................................... 9
2.1.5
Split brain checker ......................................................................................................... 10
2.1.6
SafeKit package install ................................................................................................... 10
2.1.7
Security fix in Windows .................................................................................................. 10
2.1.8
File replication configuration in Unix for Oracle Direct NFS .................................................. 10
2.2
Major Changes between SafeKit 7.0.9 and SafeKit 7.0.10 .............................. 11
2.2.1
File reintegration changes............................................................................................... 11
2.2.2
File replication configuration changes in Windows .............................................................. 12
2.2.3
Replicated directory on-line verification ............................................................................ 12
2.2.4
SafeKit package install and upgrade ................................................................................ 13
2.2.5
SafeKit Network Load Balancing Driver Install ................................................................... 14
2.2.6
Virtual IP address takeover for real_interface in Windows 2008 ....................................... 15
2.2.7
Miscellaneous ................................................................................................................ 15
2.3
Major Changes between SafeKit 7.0.8 and SafeKit 7.0.9 ................................ 16
2.3.1
File reintegration and replication changes ......................................................................... 16
2.3.2
Degraded mode for mirror architecture with file replication ................................................. 16
2.3.3
Extension of supported platforms .................................................................................... 17
2.3.4
New module template: hyperv.safe................................................................................ 17
2.3.5
Virtual Ip conflict detection in Windows ............................................................................ 17
2.3.6
SafeKit web server ........................................................................................................ 17
2.3.7
SafeMonitor messages internationalization ........................................................................ 17
2.3.8
New module template: drdb.safe ................................................................................... 18
2.4
Major Changes between SafeKit 7.0.4 and SafeKit 7.0.8 ................................ 18
2.4.1
File replication enhancement ........................................................................................... 18
2.4.2
Extension of supported platforms .................................................................................... 19
2.4.3
New module template: virtualserver.safe .................................................................... 19
2.5
Major Changes between SafeKit 7.0.1 and SafeKit 7.0.4 ................................ 19
39 A2 19LT Rev04-04
37
SafeKit Release Notes
2.6
Major Changes between SafeKit 7.0.0 and SafeKit 7.0.1 ................................ 20
2.7
Major Changes between SafeKit 6.2 and SafeKit 7.0.0 ................................... 20
3.
2.7.1
Mix of farm and mirror applications on the same physical servers ........................................ 20
2.7.2
Mutual takeover with 2 application servers ....................................................................... 20
2.7.3
N-1 architecture with N active application servers and only one backup ................................ 20
2.7.4
Independent application fail-over .................................................................................... 21
2.7.5
Load balancing of applications controlled by an administrator.............................................. 21
2.7.6
Process monitoring enhancement .................................................................................... 21
Restrictions and Known Problems .............................................................. 23
3.1
3.1.1
IPv6 support ................................................................................................................. 23
3.1.2
HTTPS .......................................................................................................................... 24
3.1.3
Web console and IE 9 .................................................................................................... 24
3.2
File Replication in Windows 2008 SP2, Windows 2008 R2, Windows 7 .................................. 24
3.2.2
Red Hat 6 ..................................................................................................................... 24
3.2.3
Virtual IP ...................................................................................................................... 24
3.2.4
Boot start of modules..................................................................................................... 24
3.2.5
Zone reintegration after Windows server reboot ................................................................ 25
Restrictions and Known Problems with SafeKit 7.0.9 ..................................... 26
3.3.1
File Replication in Windows 2008 SP2, Windows 2008 R2 ................................................... 26
3.3.2
Aix 5.2 ......................................................................................................................... 26
3.3.3
Solaris 10 ..................................................................................................................... 26
3.3.4
SuSe SLES 11 ............................................................................................................... 26
3.4
Restrictions and Known Problems with SafeKit 7.0.8 ..................................... 26
3.4.1
File Replication and Red Hat 5 ......................................................................................... 26
3.4.2
SafeKit SNMP Agent in Windows ...................................................................................... 27
3.5
Restrictions and Known Problems with SafeKit 7.0.4 ..................................... 27
3.5.1
File replication............................................................................................................... 27
3.5.2
Virtual IP ...................................................................................................................... 27
Migration Instructions ................................................................................ 29
4.1
Migrating from SafeKit 7.0.10 to SafeKit 7.0.11 ............................................ 29
4.1.1
Upgrade Procedure ........................................................................................................ 29
4.1.2
Migrate SafeKit Web Server Configuration ........................................................................ 29
4.2
38
Restrictions and Known Problems with SafeKit 7.0.10 .................................... 24
3.2.1
3.3
4.
Restrictions and Known Problems with SafeKit 7.0.11 .................................... 23
Migrating from SafeKit 7.0.9 to SafeKit 7.0.10 ............................................. 30
4.2.1
Recommendation for Modules using <rfs>........................................................................ 30
4.2.2
Recommendation for Modules using <vip>........................................................................ 30
4.2.3
Upgrade Package........................................................................................................... 31
4.2.4
Migrate SafeKit Web Server Configuration ........................................................................ 31
4.2.5
SafeMonitor .................................................................................................................. 31
39 A2 19LT Rev04-04
Table of contents
4.2.6
Miscellaneous ................................................................................................................ 31
4.3
Migrating from SafeKit 7.0.x (< 7.0.9) to SafeKit 7.0.10................................ 31
4.4
Migrating from SafeKit 7.0.x to SafeKit 7.0.9 ............................................... 32
4.5
Migrating from SafeKit 7.0.x to SafeKit 7.0.8 ............................................... 32
4.5.1
Recommendation........................................................................................................... 32
4.5.2
Upgrade Procedure ........................................................................................................ 32
4.5.3
<rfs> Configuration ....................................................................................................... 32
4.6
Migrating from SafeKit 7.0.x to SafeKit 7.0.4 ............................................... 33
4.6.1
Recommendation........................................................................................................... 33
4.6.2
Upgrade Procedure ........................................................................................................ 33
4.7
Migrating from SafeKit 6.2 to SafeKit 7.0.4 .................................................. 33
4.7.1
Recommendation........................................................................................................... 33
4.7.2
Upgrade Procedure ........................................................................................................ 33
4.7.3
<errd> Configuration ..................................................................................................... 33
4.8
Migrating from SafeKit 6.1 to SafeKit 7.0.4 .................................................. 34
4.8.1
Recommendation........................................................................................................... 34
4.8.2
Upgrade Procedure ........................................................................................................ 34
4.8.3
Configuration Migration .................................................................................................. 34
4.9
Upgrading SafeKit 6.x License Keys ............................................................ 35
39 A2 19LT Rev04-04
39
Download PDF