Source:Novell Cluster: Difference between revisions
(Fixed broken link.) |
(Rewrite in progress.) |
||
Line 1: | Line 1: | ||
{{Copyright SEP AG | <noinclude><div class="noprint"><languages /> | ||
{{Copyright SEP AG|en}} | |||
{{Draft}} | |||
{{Navigation_latest|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Micro_Focus|Micro Focus archive]]}}</div><br /> | |||
== | ==Overview== | ||
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Additional resources</b></center> | |||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | |||
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Sesam_README_for_Micro_Focus_OES_Linux_and_OES_Netware]] | |||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |See also: [[Special:MyLanguage/Sesam_README_for_Micro_Focus_OES_Linux_and_OES_Netware|SEP sesam README for Micro Focus OES Linux and OES Netware]] – [[Special:MyLanguage/Backup_principles_using_SEP_sesam_in_a_Micro_Focus_OES_environment|Backup principles using SEP sesam in a Micro Focus OES environment]] | |||
|} | |||
=== | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" |[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ#backup_overview|FAQ]] | |||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |Check [[Special:MyLanguage/FAQ#backup_overview|FAQ]] to find the answers to most common questions. | |||
|} | |||
==== | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#NetWare]] | |||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |If you have a problem, check the [[Special:MyLanguage/Troubleshooting_Guide#NetWare|Troubleshooting Guide]]. | |||
|} | |||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | |||
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Micro_Focus]] | |||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |If you are using an older SEP sesam version, refer to [[Special:MyLanguage/Micro_Focus|Micro Focus archive]]. | |||
|}</div></noinclude> | |||
{{:Template:Novell rebrand en}} | |||
The | The SEP sesam backup and recovery solution provides a full cluster support for Micro Focus OES Linux/NetWare environments to ensure high availability and manageability of critical network resources. This solutions suits a complex IT environments and requires a profound knowledge of Micro Focus administration. | ||
With SEP sesam you can fully back up NSS volumes (including ''trustees''). If the data is lost or damaged, the volumes can be easily restored using the GUI restore wizard. Also the migration to the similar file structure on the Micro Focus OES platform is possible. | |||
This article describes backup options for Micro Focus OES cluster environments with SEP sesam. For details on the Micro Focus services requirements, connection (TSA protocol) and detailed backup procedure, see [[Special:MyLanguage/Sesam_README_for_Micro_Focus_OES_Linux_and_OES_Netware|SEP sesam README for Micro Focus OES Linux and OES Netware]]. | |||
=== {{anchor|license}}License requirements === | |||
There are not special licenses required to back up Micro Focus cluster environments, however, each clustered resource (e.g., GroupWise service, NSS, etc.) SEP sesam recognizes as a server, and therefore a SEP sesam backup Client license is required. The number of client licenses depends completely on the number of Micro Focus resources that need to be backed up. | |||
Optionally, a license for the backup devices and online backup modules can be added to the SEP sesam backup Server. This way the backup of the Micro Focus cluster can be easily incorporated into a comprehensive backup design and architecture. This allows a fast recreation of the most important components of your environment. | |||
Depending on the desired response times and functionality required, the licenses for the storage devices in ''SAN'' might also be taken into account. | |||
For details on SEP sesam licensing and the list of licenses, see [[Special:MyLanguage/Licensing|Licensing]]. | |||
== {{anchor|cluster}}Configuring a Micro Focus cluster == | |||
A Micro Focus cluster consists of several physical cluster nodes, sharing a common access to the storage device(s) used by the backup server. Note that a cluster should contain '''3+ nodes''' to achieve an optimal performance. | |||
In the examples, the services such as ''iPrint'', ''eDirectory'', ''GroupWise'' and ''NSS'' are described as ''resources''. | |||
'''''Standard 3-node cluster example''''' | |||
[[Image:Standard_3nodecluster.jpg|600px|link=]] | |||
To | You can configure a Micro Focus cluster in several ways. In practice, the two most often utilized methods are the automatic ''Fail Over'' or a ''Load'' cluster. | ||
With the ''Fail Over'' method, the access to a ''resource'' can be manually specified or automatically assigned (moved) from one cluster node to another. Node failure is the typical reason that a ''resource'' is reassigned. In the process, the availability of the desired resource is not interrupted and is fully accessible to system users. To the physical load or main cluster a task is assigned to insure that cluster assets are utilized efficiently. In the event of heavy activity, the load cluster divides processes and shares ''resources'' among the cluster nodes to provide efficient management of the entire cluster environment. The availability of the required ''resources'' is therefore normally assured. | |||
In order to provide a fast, reliable backup of the Micro Focus ''resources'', you must design a concept and configuration for implementing SEP sesam as well as determining the basis for accessing, backing up and restoring the data. Connection to a Micro Focus service can be achieved using the ''SMS/TSA'' protocol. An overriding requirement to successfully implement a properly running cluster backup solution with SEP sesam is a technically correct installation of the Micro Focus cluster TSAs. For details, see [[Special:MyLanguage/Sesam_README_for_Micro_Focus_OES_Linux_and_OES_Netware|SEP sesam README for Micro Focus OES Linux and OES Netware]]. | |||
=={{anchor|LAN}}Configuring LAN backup == | |||
The following example provides a typical backup configuration. The ''resources'' are listed on each node. | |||
The SEP sesam backup Server can be used on a computer running OES2 and automatically assumes direct communication to the desired ''resources''. In this example, the Micro Focus Storage Management Data Register (SMDR) is running on the SEP sesam OES2 server and allows the backup of both NetWare and Linux ''resources'' on the OES2 server. | |||
*On a Micro Focus cluster the access is provided using the Storage Management Services (SMS) architecture for utilizing the TSAs to access all running ''resources''. | |||
*The various SMS Target Service Agents (TSAs) have a system access to data from ''resources'', i.e., eDirectory, iFolder, GroupWise or NSS file systems. | |||
*The SMS architecture allows communication between the cluster ''resources'' to provide ''Failover'' and ''Fallback'' functionality. | |||
*The installation of various programs on the node or within the ''resource'' is not required, and no change in the cluster environments is needed. A cluster backup using NetWare or OES2 is supported. | |||
'''''Cluster LAN backup example''''' | |||
[[Image: | [[Image:OES-Cluster lan backup.jpg|800px|link=]] | ||
<br clear=all> | |||
To test the correct communication path and the TSA reachability (rights management), see [[Special:MyLanguage/Troubleshooting_Guide#NetWare|Checking the reachability of the TSA services]]. | |||
Now you can create a backup task in the SEP sesam GUI to complete your backup. SEP sesam GUI allows you to configure a complete backup schema for your environment. Every ''resource'' that need to be backed up must be entered in the GUI to become an integral part of the backup. | |||
==={{anchor|data_mover}}Cluster LAN data mover backup=== | |||
In the above example for Standard 3-node cluster, the SEP sesam backup Server is also the SMDR. The SMDR is designated by SEP sesam as the Micro Focus data mover. This configuration serves both, the backup, and in the event of a node failure or transfer of a ''resource'' to a new node, the restore path. | |||
It is also possible to install the Micro Focus SMDR and SMS as standalone services. However, in such implementation another Micro Focus OES server that acts as the data mover is required. The SEP sesam backup Server can be used on Windows, Linux or Unix clustered systems. | |||
[[Image:OES-Cluster_2_lan_datamover_backup.jpg|800px|link=]] | |||
<br clear=all> | |||
In this configuration an OES2 Linux | In this configuration an OES2 Linux server is installed with the SEP sesam Bbackup Client software and is designated and used as the Micro Focus data mover (Drawing 3). The data stream is then transferred to the appointed Cluster Node and further transferred using the TSA to the SEP sesam Client Server. The further communication and data transfer is completed using the SEP Transfer Protocol (STP). | ||
This configuration is suited to both backup and restore of Resource data in the event of failover or transfer of Resources. | This configuration is suited to both backup and restore of Resource data in the event of failover or transfer of Resources. | ||
Another variant that can be utilized is the use of the Novell Cluster Nodes as the Data Mover. This is possible when the Cluster is using Novell OES2 Linux. The nodes will be configured with a SEP sesam backup client and the setup in the SEP sesam GUI as backup clients configured with the Novell Data Mover Functionality. | Another variant that can be utilized is the use of the Novell Cluster Nodes as the Data Mover. This is possible when the Cluster is using Novell OES2 Linux. The nodes will be configured with a SEP sesam backup client and the setup in the SEP sesam GUI as backup clients configured with the Novell Data Mover Functionality. | ||
Note: This is a less reliable solution by backup and restore because node is also functioning as the SEP Novell Data Mover. | Note: This is a less reliable solution by backup and restore because node is also functioning as the SEP Novell Data Mover. | ||
== Configuring Micro Focus cluster LAN-free backup with SEP sesam == | |||
== | |||
TSA is a network protocol, in the event as a backup is desired, e.g. access to the eDirectory is required, the data from the Resource is directed, depending on definition, to the desired Data Mover and then further on to the designated SEP backup location on the SEP sesam Backup Server (disk, tape, NAS, SAN, etc.) | TSA is a network protocol, in the event as a backup is desired, e.g. access to the eDirectory is required, the data from the Resource is directed, depending on definition, to the desired Data Mover and then further on to the designated SEP backup location on the SEP sesam Backup Server (disk, tape, NAS, SAN, etc.) | ||
A | A LAN-free backup in a Novell Cluster environment is also possible and provides additional performance advantages. To accomplish this task the Novell Cluster Nodes in the previous examples are provided each with a SEP sesam Backup Client. Next, a location is specified in the SAN to direct the backup data stream to the new device, LAN-free. This is performed utilizing the SEP sesam SAN Remote Device module. | ||
=== SEP sesam Remote Device Server Base === | |||
The remote device function (tape or disk) allows the backup of data to a device that is directly attached to the backup client (e.g. Novell Cluster Node). With this extended functionality the diverse remote environments can utilize attached hardware and a highly efficient backup concept can be developed and implemented saving both time and maximizing ROI of current hardware. Further it allows the central management of data of remote data and servers. | The remote device function (tape or disk) allows the backup of data to a device that is directly attached to the backup client (e.g. Novell Cluster Node). With this extended functionality the diverse remote environments can utilize attached hardware and a highly efficient backup concept can be developed and implemented saving both time and maximizing ROI of current hardware. Further it allows the central management of data of remote data and servers. | ||
The complete data transfer happens via the Remote Device Server and only the control and protocol (meta) data are transmitted and stored at the main SEP sesam Backup Server. | The complete data transfer happens via the Remote Device Server and only the control and protocol (meta) data are transmitted and stored at the main SEP sesam Backup Server. | ||
The SEP sesam Remote Device Server and the SEP sesam Backup Server can be running different operating systems. | The SEP sesam Remote Device Server and the SEP sesam Backup Server can be running different operating systems. | ||
The Remote Device and Remote Device Server concept is available for implementation in SAN environments for LAN-free backup solutions. SEP sesam SAN environments are defined as data stored within the SAN, i.e. stored on drives within the SAN. | |||
The data stream flow and the communication paths are shown in the following diagram and show a LAN-free backup in a Novell Cluster. | |||
The | |||
'''''Cluster SAN backup example''''' | |||
[[Image:OES-Cluster 3 SAN backup.jpg|800px|link=]] | |||
<br clear=all> | |||
<noinclude> | |||
< | ==See also== | ||
[[Special:MyLanguage/Sesam_README_for_Micro_Focus_OES_Linux_and_OES_Netware|SEP sesam README for Micro Focus OES Linux and OES Netware]] – [[Special:MyLanguage/Backup_principles_using_SEP_sesam_in_a_Micro_Focus_OES_environment|Backup principles using SEP sesam in a Micro Focus OES environment]]</noinclude> |
Revision as of 13:58, 21 October 2020
Overview
The SEP sesam backup and recovery solution provides a full cluster support for Micro Focus OES Linux/NetWare environments to ensure high availability and manageability of critical network resources. This solutions suits a complex IT environments and requires a profound knowledge of Micro Focus administration.
With SEP sesam you can fully back up NSS volumes (including trustees). If the data is lost or damaged, the volumes can be easily restored using the GUI restore wizard. Also the migration to the similar file structure on the Micro Focus OES platform is possible.
This article describes backup options for Micro Focus OES cluster environments with SEP sesam. For details on the Micro Focus services requirements, connection (TSA protocol) and detailed backup procedure, see SEP sesam README for Micro Focus OES Linux and OES Netware.
License requirements
There are not special licenses required to back up Micro Focus cluster environments, however, each clustered resource (e.g., GroupWise service, NSS, etc.) SEP sesam recognizes as a server, and therefore a SEP sesam backup Client license is required. The number of client licenses depends completely on the number of Micro Focus resources that need to be backed up.
Optionally, a license for the backup devices and online backup modules can be added to the SEP sesam backup Server. This way the backup of the Micro Focus cluster can be easily incorporated into a comprehensive backup design and architecture. This allows a fast recreation of the most important components of your environment.
Depending on the desired response times and functionality required, the licenses for the storage devices in SAN might also be taken into account.
For details on SEP sesam licensing and the list of licenses, see Licensing.
Configuring a Micro Focus cluster
A Micro Focus cluster consists of several physical cluster nodes, sharing a common access to the storage device(s) used by the backup server. Note that a cluster should contain 3+ nodes to achieve an optimal performance.
In the examples, the services such as iPrint, eDirectory, GroupWise and NSS are described as resources.
Standard 3-node cluster example
You can configure a Micro Focus cluster in several ways. In practice, the two most often utilized methods are the automatic Fail Over or a Load cluster.
With the Fail Over method, the access to a resource can be manually specified or automatically assigned (moved) from one cluster node to another. Node failure is the typical reason that a resource is reassigned. In the process, the availability of the desired resource is not interrupted and is fully accessible to system users. To the physical load or main cluster a task is assigned to insure that cluster assets are utilized efficiently. In the event of heavy activity, the load cluster divides processes and shares resources among the cluster nodes to provide efficient management of the entire cluster environment. The availability of the required resources is therefore normally assured.
In order to provide a fast, reliable backup of the Micro Focus resources, you must design a concept and configuration for implementing SEP sesam as well as determining the basis for accessing, backing up and restoring the data. Connection to a Micro Focus service can be achieved using the SMS/TSA protocol. An overriding requirement to successfully implement a properly running cluster backup solution with SEP sesam is a technically correct installation of the Micro Focus cluster TSAs. For details, see SEP sesam README for Micro Focus OES Linux and OES Netware.
Configuring LAN backup
The following example provides a typical backup configuration. The resources are listed on each node.
The SEP sesam backup Server can be used on a computer running OES2 and automatically assumes direct communication to the desired resources. In this example, the Micro Focus Storage Management Data Register (SMDR) is running on the SEP sesam OES2 server and allows the backup of both NetWare and Linux resources on the OES2 server.
- On a Micro Focus cluster the access is provided using the Storage Management Services (SMS) architecture for utilizing the TSAs to access all running resources.
- The various SMS Target Service Agents (TSAs) have a system access to data from resources, i.e., eDirectory, iFolder, GroupWise or NSS file systems.
- The SMS architecture allows communication between the cluster resources to provide Failover and Fallback functionality.
- The installation of various programs on the node or within the resource is not required, and no change in the cluster environments is needed. A cluster backup using NetWare or OES2 is supported.
Cluster LAN backup example
To test the correct communication path and the TSA reachability (rights management), see Checking the reachability of the TSA services.
Now you can create a backup task in the SEP sesam GUI to complete your backup. SEP sesam GUI allows you to configure a complete backup schema for your environment. Every resource that need to be backed up must be entered in the GUI to become an integral part of the backup.
Cluster LAN data mover backup
In the above example for Standard 3-node cluster, the SEP sesam backup Server is also the SMDR. The SMDR is designated by SEP sesam as the Micro Focus data mover. This configuration serves both, the backup, and in the event of a node failure or transfer of a resource to a new node, the restore path.
It is also possible to install the Micro Focus SMDR and SMS as standalone services. However, in such implementation another Micro Focus OES server that acts as the data mover is required. The SEP sesam backup Server can be used on Windows, Linux or Unix clustered systems.
In this configuration an OES2 Linux server is installed with the SEP sesam Bbackup Client software and is designated and used as the Micro Focus data mover (Drawing 3). The data stream is then transferred to the appointed Cluster Node and further transferred using the TSA to the SEP sesam Client Server. The further communication and data transfer is completed using the SEP Transfer Protocol (STP). This configuration is suited to both backup and restore of Resource data in the event of failover or transfer of Resources. Another variant that can be utilized is the use of the Novell Cluster Nodes as the Data Mover. This is possible when the Cluster is using Novell OES2 Linux. The nodes will be configured with a SEP sesam backup client and the setup in the SEP sesam GUI as backup clients configured with the Novell Data Mover Functionality. Note: This is a less reliable solution by backup and restore because node is also functioning as the SEP Novell Data Mover.
Configuring Micro Focus cluster LAN-free backup with SEP sesam
TSA is a network protocol, in the event as a backup is desired, e.g. access to the eDirectory is required, the data from the Resource is directed, depending on definition, to the desired Data Mover and then further on to the designated SEP backup location on the SEP sesam Backup Server (disk, tape, NAS, SAN, etc.) A LAN-free backup in a Novell Cluster environment is also possible and provides additional performance advantages. To accomplish this task the Novell Cluster Nodes in the previous examples are provided each with a SEP sesam Backup Client. Next, a location is specified in the SAN to direct the backup data stream to the new device, LAN-free. This is performed utilizing the SEP sesam SAN Remote Device module.
SEP sesam Remote Device Server Base
The remote device function (tape or disk) allows the backup of data to a device that is directly attached to the backup client (e.g. Novell Cluster Node). With this extended functionality the diverse remote environments can utilize attached hardware and a highly efficient backup concept can be developed and implemented saving both time and maximizing ROI of current hardware. Further it allows the central management of data of remote data and servers. The complete data transfer happens via the Remote Device Server and only the control and protocol (meta) data are transmitted and stored at the main SEP sesam Backup Server. The SEP sesam Remote Device Server and the SEP sesam Backup Server can be running different operating systems.
The Remote Device and Remote Device Server concept is available for implementation in SAN environments for LAN-free backup solutions. SEP sesam SAN environments are defined as data stored within the SAN, i.e. stored on drives within the SAN. The data stream flow and the communication paths are shown in the following diagram and show a LAN-free backup in a Novell Cluster.
Cluster SAN backup example
See also
SEP sesam README for Micro Focus OES Linux and OES Netware – Backup principles using SEP sesam in a Micro Focus OES environment