- Adding a License to Existing Cluster Nodes
- Adding a Net Ware Node to a Net Ware Cluster
- Adding a Post Office to the Existing Groupwise System on Netware
- Adding a Second Post Office to the Existing Groupwise System on Linux
- Adding the First Linux Node to the Netware Cluster
- Agents in OES
- An Identity Manager driver
- As it will be created in eDirectory
- Assigning Rights for Initiators in Different Trees
- Assigning Rights for Initiators in the Same Tree
- Availability Defined
- Backup Express Architecture
- Brain Detector
- Building a San With Fibre Channel or Iscsi
- Business Continuity Clustering
- Calculating Average Downtime
- Changing the Master IP Address
- Introduction to Clustering and High Availability
- Upgrading Clusters
- Using SUSE Linux Enterprise Server Clustering Options
- Introduction to Business Continuity Clustering
- Examining Novell Cluster Services Architecture
- Cluster Management
- ISCSI
- Cluster Enabled Applications
- Clstrlib
- Cluster Backups Explained
- Cluster Container
- Cluster Event Information
- Cluster Node
- Cluster Resource - 2
- Cluster Script Syntax
- Cluster Services Backup
- Cluster Services Management Agent
- Cluster System Services
- Cluster Templates
- Cluster Volume Resources
- Cluster Enable or
- Clustering a Simple Application on OES Linux
- Clustering a Simple Application on OES Net Ware
- Clustering Group Wise on Linux
- Clustering Group Wise on Net Ware
- Clustering iFolder 3 on OES Linux
- Clustering the Samba Server on OES Linux
- Clustering the Squid Web Proxy on Linux
- Clustering Without Shared Storage
- Configuration
- Configure NFS for Use in the Heartbeat Cluster
- Configure the Identity Manager eDirectory Drivers
- Configuring BCC
- Configuring iFolder 3 on the First Node
- Configuring the Cluster Resource
- Configuring the Initiator Software
- Configuring the Other Cluster Nodes
- Configuring the smbconf File
- Connecting to the iSCSI Target
- Copyright
- Create Shared Resources by Editing the haresources File
- Creating a Failover Matrix
- Creating Cluster Documentation
- Creating Clustered Volumes
- Creating Mount Points to Mount the Shared File System on All Servers
- Creating the iSCSI Target
- Creating the Samba Clustered Resource
- Creating the Shared File System
- Creating the Squid Cluster Resource
- Crm
- DNS Round Robin Configuration
- EDirectory driver are needed
- Edit the Sample Configuration Files
- Environment
- Execute NCF and Script Files from the Load and Unload Scripts
- Exploring eDirectory After Cluster Installation
- Failback
- Figure 111 The High Availability selection includes all software needed to run a Heartbeat cluster
- Figure 113 Each shared resource has its own unique IP address displayed on the server hosting the resource as a virtual IP address
- Figure 121 eDirectory tree structure for the BCC test tree
- Figure 1210 When all necessary software components are loaded you can enable Business Continuity features for both clusters
- Figure 1212 After successfully creating the mirror pair the mirrored partition will have a mirror ID added to it
- Figure 1213 To enable a resource for BCC migration you need to select the cluster peers for this resource and you have to add search and replace values that can be applied to the cluster load scripts
- Figure 1214 From BCC Manager select the resource you want to migrate to another cluster and then click BCC Migrate
- Figure 127 Import the Bccciuster Resourcesynchronization driver
- Figure 129 The DirXML Overview screen provides an overview of all Identity Manager drivers currently present in your eDirectory tree
- Figure 523 On OES Linux the cluster load script is a bash script
- Figure 526 If the resource does not load properly check
- Figure 62 Make sure that the cluster object is selected before modifying any of its properties
- Figure 64 Make sure that the most important resource in your cluster is listed first on this tab
- Figure 68 The Cluster Event Log provides an overview of all events that have occurred since the log was last cleared
- Figure 715 Remote Manager can be used to display session details
- Figure 72 The regular SCSI disk communication process
- Figure 75 iSCSI can be used to build a lowcost clustering solution
- Figure 77 With iSCSI data can be mirrored to a remote site
- Figure 81 Post office links must always be TCPIP links
- Figure 810 Configure the settings for the new post office
- Figure 811 We start with the volume and cluster resources configured
- Figure 813 Design for a Squid highavailability solution
- Figure 84 Configure the settings for the new post office
- Figure 87 Our starting point for the Group Wise cluster installation
- Finalizing the Netwareto Linux Cluster Upgrade
- Getting Started With Backup Express on OES
- Gipc
- Groupwise Addressing in a Cluster
- Groupwise Resources Explained
- Happening in the cluster
- Hardware
- Hardware Requirements
- Heartbeats Epoch Numbers and the Split Brain Detector
- High Availability Between Clusters
- High Availability Defined
- High Availability Solutions Overview
- How iSCSI Works
- How Many Nodes to Choose
- Imanager SMS Configuration Options
- Index - 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
- Info - 2 3 4 5 6
- Information you need to see
- Initiator name in the registry
- Install Applications on the Shared Disk
- Install Identity Manager
- Installing Groupwise on the Linux Cluster
- Installing iFolder 3 Software on All Nodes
- Installing NCS in VMware
- Installing NCS on Linux
- Installing NCS on OES Net Ware
- Installing New Cluster Hardware and Software from Scratch
- Installing the Groupwise System on Netware
- Installing the Imanager Plug Ins
- Installing the iSCSI Software on Linux
- Installing the iSCSI Target Software
- Instead
- Interface
- Introduction
- ISCSI Advantages
- ISCSI as a Low Cost Shared Storage Solution
- ISCSI as a Server OSIndependent Storage Platform
- ISCSI Design Guidelines
- ISCSI for Remote Storage
- ISCSI Initiator Configuration on OES Net Ware
- ISCSI Initiator Requirements
- ISCSI Introduction
- ISCSI Naming Guidelines
- ISCSI Support
- Linux
- Linux Cluster Preparations for iFolder
- Linux OES Installation
- Linux SBD Installation
- Load and Unload Scripts
- Loaded successfully
- Logging Event History and Alerting
- Low Cost Testing Solution
- M m
- Mainstream Hardware
- Making a Share Available from the Samba Clustered Resource
- Managing Backup Express
- Managing Cluster Resources on OES Net Ware with Remote Manager
- Managing Cluster Resources with iManager
- Managing Novell Cluster Services from the Command Line
- Manually Starting and Stopping NCS
- Master and Slave Nodes
- Meet The Netware 65 System Requirements
- Meet the Netware 65 System Requirements
- Membership Quorum and Timeout
- Migrating From Netware to Linux
- Migrating From Netware to Netware
- Migrating to a New Cluster
- Migrating to New Hardware and Software
- Mirror the Split Brain Detector Partition
- Mirrored
- Monitoring iSCSI Sessions
- N - 2
- Net Ware and Linux - 2
- Net Ware are under the Clustering header
- Netware Informational Resources
- Net Ware iSCSI Command Overview
- Netware Node Installation
- Netware SBD Installation
- Note - 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
- Novell
- Novell Cluster Services Defined
- Novells Backup Software
- One by one
- Post Configuration Tasks
- Preparations and System Requirements
- Prepare the Cluster
- Procedures
- Recreating the SBD Partition
- Redundant Disk Configurations With Hardware
- Redundant Disk Configurations With Software
- Relation Between Edirectory Objects and Local Files on the Cluster Node
- Removing a Failed Master Node
- Removing a Failing Slave Node
- Removing an OES Linux Node from the Cluster
- Removing an OES Net Ware Node from the Cluster
- Removing an Oes Netware Node From the Cluster
- Resource
- Rolling Cluster Upgrades
- Sbd
- Secondary IP Addresses
- Selecting Applications to Run in a Cluster
- Setting Up Access Control
- Shared Disk Access
- Shared resource was successful
- Single Disk Configurations
- Software
- Software Requirements
- Solving iScsi Ldap Problems
- Special and Bulk Sales
- Specifying the Name of the Shared Device
- Specifying Which Services Should be Loaded
- Split Brain Detector
- Starting and Stopping Novell Cluster Services on Linux
- Starting and Stopping Novell Cluster Services on Net Ware
- Starting the Initiator Connection
- Stopped no matter how
- Storage Management Services
- Summary - 2
- Syncsort Backup Express Feature Overview
- Table 121 Setup of iSCSI Targets
- Table 71 Most Common Iscsinit Control Commands
- Table 81 Overview of the Group Wise Net Ware Cluster Environment in This Section
- Testing the Cluster Resource
- Testing the New Groupwise System on Linux
- Testing The New Groupwise System on Netware
- The cluster is provided
- The console of the Net Ware server
- The File System
- The Final Test Migrate the Cluster Resources
- The list of available resources
- The Real Wizardry Post Migration Tasks
- The Server Consolidation Utility
- The Two Site Solution
- Things You Should Know About a Mixed Cluster Environment
- Tip - 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
- To enter authentication credentials
- Trademarks
- Triggers are applied
- Tune the Main Configuration File hacf on Both Nodes
- Upgrade the Cluster Software and Configuration
- Upgrade the Netware 51 Servers
- Upgrade the Netware 6 Servers With a Downed Cluster
- Upgrading a Net Ware 51 Cluster to Net Ware
- Upgrading a Net Ware 6 Cluster to Net Ware
- Upgrading a Net Ware 65 Cluster to Open Enterprise Server Linux
- Upgrading Existing Hardware and Software
- Use Authentication Keys to Ensure Secure Communications
- Use NIC Teaming
- Using a Heartbeat LAN or
- Using Backup Express in a Cluster Environment
- Using BCC to Create a Cluster of Clusters
- Using Remote Manager To Collect Session Information
- Using Scsi For Your Shared Storage
- Using the Server Consolidation Utility
- Mware Clustering Requirements
- Mware Usage Scenarios
- Volume
- What VMware Is
- When Not to Cluster Applications
- Will communicate