MicroNet Fibre to SAS/SATA II RAID Subsystem Spezifikationen

Stöbern Sie online oder laden Sie Spezifikationen nach Aufnahmegeräte MicroNet Fibre to SAS/SATA II RAID Subsystem herunter. MicroNet Fibre to SAS/SATA II RAID Subsystem Specifications Benutzerhandbuch

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 374
  • Inhaltsverzeichnis
  • FEHLERBEHEBUNG
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen

Inhaltsverzeichnis

Seite 1 - Technical Documentation

SteelEye Protection Suite for Linuxv8.1Technical DocumentationAugust 2012

Seite 2

Extending a Raw Device Resource Hierarchy 140Unextending a Hierarchy 140Creating a Resource Dependency 141Deleting a Resource Dependency 142Deleting a

Seite 3 - Table of Contents

Data Replication Configurationlibstdc++libraryrequirementWhile running the SPS Installation setup script, you may encounter a messageregarding a faile

Seite 4

Network ConfigurationItem DescriptionSteelEye DataKeeperdocumentationThe documentation for SteelEye DataKeeper is located within theSteelEye Protectio

Seite 5

Storage and Adapter ConfigurationItem DescriptionLocalizedOraclemountpointsLocalized Oracle environments are different depending on whether you connec

Seite 6

Storage and Adapter ConfigurationItem DescriptionHeavy I/O in Multipath ConfigurationsIn multipath configurations, performing heavyI/O while paths are

Seite 7

Storage and Adapter ConfigurationItem DescriptionSpecial Considerations for Switchovers withLarge Storage ConfigurationsWith some large storage config

Seite 8

Storage and Adapter ConfigurationItem DescriptionHP 3PAR V400The HP 3PAR V400 was tested by a SIOSTechnology Corp. partner with the followingconfigura

Seite 9

Storage and Adapter ConfigurationItem DescriptionHP MSA2000fcCertified by Hewlett-Packard Company withFibre Channel in both single path and multipathc

Seite 10

Storage and Adapter ConfigurationItem DescriptionHP P2000 G3 MSA SASCertified by SIOS Technology Corp. in multipathconfigurations using the Device Map

Seite 11

Storage and Adapter ConfigurationItem DescriptionHP XP20000/XP24000Certified by SIOS Technology Corp. usingLifeKeeper forLinux with DMMP ARK in RHEL5

Seite 12

Storage and Adapter ConfigurationItem DescriptionIBM DS3500(FC Model)Certified by SIOS Technology Corp. in singlepath and multipath configurations on

Seite 13

GUI Client 157Starting GUI clients 157Starting the LifeKeeper GUI Applet 157Starting the application client 158Exiting GUI Clients 158Configuring the

Seite 14

Storage and Adapter ConfigurationItem DescriptionIBM eServer xSeries Storage Solution ServerType445-R / Type445-FR for SANmelodyCertified by partner t

Seite 15

Storage and Adapter ConfigurationItem DescriptionDell PowerVault with Dell PERC and LSI LogicMegaRAID controllersSIOS Technology Corp. has certified t

Seite 16

Storage and Adapter ConfigurationItem DescriptionDell | EMC (CLARiiON) CX200EMC has approved two QLogic driver versionsfor use with this array and the

Seite 17

Storage and Adapter ConfigurationItem DescriptionDell EqualLogic PS5000The Dell EqualLogic was tested by a SIOSTechnology Corp. partner with the follo

Seite 18

Storage and Adapter ConfigurationItem DescriptionHitachi HDS 9570V, 9970V and 9980VCertified by SIOS Technology Corp. in a singlepath configuration wi

Seite 19

Storage and Adapter ConfigurationItem DescriptionHitachi HDS 9980VThere are certain specific “host mode” settingsrequired on the Hitachi arrays in ord

Seite 20

Storage and Adapter ConfigurationItem DescriptionFujitsu ETERNUS3000This storage unit was tested by a SIOSTechnology Corp. partner organization in asi

Seite 21 - Index 341

Storage and Adapter ConfigurationItem DescriptionFujitsu ETERNUS2000 Model 200This storage unit was tested by Fujitsu Limitedin a multipath configurat

Seite 22

Storage and Adapter ConfigurationItem DescriptionTID MassCareRAIDThis storage unit was tested by a SIOSTechnology Corp. partner with the followingsing

Seite 23 - Chapter 1: Introduction

Storage and Adapter ConfigurationItem DescriptionDataCore SANsymphonyThis storage device was successfully testedwith SUSE SLES 9 Service Pack 3, Devic

Seite 24 - Documentation and Training

Internet Explorer 168Status Table 168Properties Panel 169Output Panel 169Message Bar 170Exiting the GUI 170Common Tasks 170Starting LifeKeeper 170Star

Seite 25 - Technical Support

HP Multipath I/O ConfigurationsHP Multipath I/O ConfigurationsItem DescriptionMSA1000 andMSA1500MultipathRequirementswith SecurePathLifeKeeper support

Seite 26

HP Multipath I/O ConfigurationsMultipathSupport forEVA withQLogicFailover DriverLifeKeeper supports the EVA 3000/5000 and the EVA 4X00/6X00/8X00 with

Seite 27 - Chapter 2: SPS Installation

Device Mapper Multipath I/O ConfigurationsSingle Path onBoot Up DoesNot CauseNotificationIf a server can access only a single path to the storage when

Seite 28 - Optional Recovery Software

Device Mapper Multipath I/O ConfigurationsHardwareRequirementsThe Device Mapper Multipath Kit has been tested by SIOS Technology Corp. withthe EMC CLA

Seite 29 - Mapping Server Configurations

Device Mapper Multipath I/O ConfigurationsTransientpath failuresWhile running IO tests on Device Mapper Multipath devices, it is not uncommonfor actio

Seite 30

LifeKeeper I-O Fencing IntroductionLifeKeeper I-O Fencing IntroductionI/O fencing is the locking away of data from a malfunctioning node preventing un

Seite 31 - Storage and Adapter Options

Non-Shared StorageNon-Shared StorageIf planning to use LifeKeeper in a non-shared storage environment, the risk of data corruption thatexists with sha

Seite 32

I/O Fencing ChartQuroum/WitnessWatchdogWatchdog & Quorum/WitnessSTONITH (serial)Reservations OffNothingSTONITH (serial)CONFIRM_SO*Quorum/WitnessWa

Seite 33

Quorum/WitnessMost Reliable Least Reliable* While CONFIRM_SO is highly reliable (depending upon the knowledge of

Seite 34

Package Installation and ConfigurationPackage Installation and ConfigurationThe Quorum/Witness Server Support Package for LifeKeeper will need to be i

Seite 35

Column Width 180Viewing Message History 181Reading the Message History 181Expanding and Collapsing a Resource Hierarchy Tree 182Cluster Connect Dialog

Seite 36 - Supported Storage Models

Available Quorum ModesAvailable Quorum ModesThree quorum checking modes are available which can be set via the QUORUM_MODE setting in/etc/default/Life

Seite 37

Available Witness Modes# This can be either off/none or remote_verify. In remote_verify# mode, core event handlers (comm_down) will doublecheck the# d

Seite 38

Available Actions When Quorum is LostAvailable Actions When Quorum is LostThe witness package offers three different options for how the system should

Seite 39

Adding a Witness Node to a Two-Node ClusterGUI will not automatically connect to the other servers with established communication paths. Asthis behav

Seite 40 - DS4100 * Partner testing

Expected Behaviors (Assuming Default Modes)Simple Two-Node Cluster with Witness NodeServer A and Server B should already be set up with LifeKeeper cor

Seite 41

Scenario 4In this case, Server B will do the following:l Begin processing a communication failure event from Server A.l Determine that it can still co

Seite 42

SCSI ReservationsSCSI ReservationsStorage Fence Using SCSI ReservationsWhile LifeKeeper for Linux supports both resource fencing and node fencing, its

Seite 43

Alternative Methods for I/O Fencingfrom partially hung servers. In cases where a hung server goes undetected by LifeKeeper, watchdogwill begin recover

Seite 44 - Supported Adapter Models

Package RequirementsPackage Requirementsl VMware vSphere SDK Package (e.g. VMware-vSphere-SDK-4.X.X-XXXXX.i386.tar.gz)l VMware vSphere CLI (vSphere CL

Seite 45 - Adapter Model Certification

<vm_id>/opt/LifeKeeper/config/stonith.conf# LifeKeeper STONITH configuration## Each system in the cluster is listed below. To enable STONITH for

Seite 46

LifeKeeper Flags 196Resources Subdirectories 197Resource Actions 198Structure of LCD Directory in /opt/LifeKeeper 198LCM 199Communication Status Infor

Seite 47 - Configuring Shared Storage

Expected Behaviorsvmware-cmd -H 10.0.0.1 -U root -P secret/vmfs/volumes/4e08c1b9-d741c09c-1d3e-0019b9cb28be/lampserver/lampserver.vmxstop hardNote:

Seite 48

ConfigurationRead the next section carefully. The daemon is designed to recover from errors and will reset thesystem if not configured carefully. Plan

Seite 49 - VLAN Interface Support Matrix

UninstallNote: Configuring watchdog may cause some unexpected reboots from time to time. This is thegeneral nature of how watchdog works. If processes

Seite 50

Steeleye Protection Suite/vAppKeeper Recovery BehaviorSteeleye Protection Suite/vAppKeeper Recovery BehaviorSteeleye Protection Suiteand SteelEye vAp

Seite 51 - Installing the SPS Software

Meta Policiesprior to performing a failover. This policy setting can be used to turn on/off local recovery.l TemporalRecovery- Normally, Steeleye Pro

Seite 52

The lkpolicy ToolIn the above resource hierarchy, app depends on both IP and file system. A policy can be setto disable local recovery or failover of

Seite 53

Listing Policies[root@thor49 ~]# lkpolicy -l -d v6test4Please enter your credentials for the system 'v6test4'.Username: rootPassword:Confirm

Seite 54 - /var/LifeKeeper/license

Configuring CredentialsConfiguring CredentialsCredentials for communicating with other systems are managed via a credential store. This store canbe ma

Seite 55 - Subscription Licensing

LifeKeeper APIThis will show the entire man/help page for the command.LifeKeeper APIThe LifeKeeper API is used to allow communications between LifeKee

Seite 56 - Upgrading SPS

LifeKeeper AdministrationOverviewLifeKeeper does not require administration during operation. LifeKeeper works automatically tomonitor protected resou

Seite 57

Starting LifeKeeper 210Starting LifeKeeper Server Processes 211Enabling Automatic LifeKeeper Restart 211Stopping LifeKeeper 211Disabling Automatic Lif

Seite 58

Administrator TasksAdministrator TasksEditing Server Properties1. To edit the properties of a server, bring up the Server Properties dialog just as yo

Seite 59 - Protected Resources

Deleting a Communication PathHelp for an explanation of each choice.3. Select the Local Server from the list box and click Next.4. Select one or more

Seite 60

Server Properties - Failoverl Right-click on a server icon, then click Delete Comm Path when the server contextmenu appears.l On the global toolbar, c

Seite 61 - Software

Creating Resource HierarchiesTo commit your selections, press the Apply button.Creating Resource Hierarchies1. There are four ways to begin creating a

Seite 62 - Common Hardware Components

LifeKeeper Application Resource Hierarchies3. Select the Switchback Type and click Next.4. Select the Server and click Next. Note: If you began from t

Seite 63 - System Grouping Arrangements

Creating a File System Resource Hierarchybutton.l On the Edit menu, select Server, then click on Create Resource Hierarchy.2. A dialog entitled Create

Seite 64 - Active - Active Grouping

Creating a Generic Application Resource HierarchyCreating a Generic Application Resource HierarchyUse this option to protect a user-defined applicatio

Seite 65 - Active - Standby Grouping

Creating a Raw Device Resource Hierarchycause the resource state to be set to OSU following the create; selecting Yes will cause thepreviously provide

Seite 66

Editing Resource Properties7. Click Create Instance to start the creation process. A window titled Creating scsi/rawresource will display text indicat

Seite 67 - Resource Types

Using the Up and Down ButtonsThere are two ways to modify the priorities:l Reorder the priorities by moving an equivalency with the Up/Down buttons ,o

Seite 68 - Resource States

Data Replication 231IPv6 234Apache 237Oracle Recovery Kit 237NFS Server Recovery Kit 238SAP Recovery Kit 239LVM Recovery Kit 240DMMP Recovery Kit 241P

Seite 69 - Shared Equivalencies

Editing the Priority ValuesEditing the Priority Values1. Select a priority by clicking on a priority value in the Priority column of the Equivalencies

Seite 70

Extending a File System Resource Hierarchythe Pre-Extend Wizard dialog appears, select a Template Server and a Tag toExtend, clicking on Next after ea

Seite 71 - Detailed Status Display

Extending a Raw Device Resource Hierarchyextending resource hierarchies. After you have done that, you then complete the steps below, whichare specifi

Seite 72

Creating a Resource Dependencyl Right-click on the icon for the global resource hierarchy that you want to unextended.When the resource context menu a

Seite 73

Deleting a Resource Dependencyl On the Edit menu, point to Resource and then click Create Dependency. When thedialog comes up, select the server in th

Seite 74

Deleting a Hierarchy from All Serversservers in the cluster.4. If the output panel is enabled, the dialog closes, and the results of the commands to d

Seite 76 - Short Status Display

LifeKeeper User GuideThe User Guide is a complete, searchable resource containing detailed information on the manytasks that can be performed within t

Seite 77 - IP Local Recovery

Using LifeKeeper for LinuxUsing LifeKeeper for LinuxThe following topics provide detailed information on the LifeKeeper graphical user interface (GUI)

Seite 78 - Command Line Operations

Exiting GUI Clientstasks.l The context (popup) and global menus provide access to all tasks.Exiting GUI ClientsSelect Exit from the File Menu to disco

Seite 79

Suggested Action: 251Recovering from a Non-Killable Process 252Recovering From A Panic During A Manual Recovery 252Recovering Out-of-Service Hierarchi

Seite 80

MenusMenusSteelEye LifeKeeper for Linux MenusResource Context MenuThe Resource Context Menu appears when you right-click on a global (cluster-wide) re

Seite 81

Server Context MenuExtend Resource Hierarchy. Copy a resource hierarchy to another server for failover support.Unextend Resource Hierarchy. Remove an

Seite 82

File MenuFile MenuConnect. Connect to a LifeKeeper cluster. Connection to each server in the LifeKeeper clusterrequires login authentication on that s

Seite 83 - SPS Configuration Steps

Edit Menu - ServerEdit Menu - ServerDisconnect. Disconnect from a cluster.Refresh. Refresh GUI.View Logs. View LifeKeeper log messages on connected se

Seite 84 - Set Up TTY Connections

Help MenuProperties Panel. Display this component if the checkbox is selected.Output Panel. Display this component if the checkbox is selected.Options

Seite 85 - LifeKeeper Events Table

GUI ToolbarDisconnect. Disconnect from a LifeKeeper cluster.Refresh. Refresh GUI.View Logs. View LifeKeeper log messages on connected servers.Create R

Seite 86

Resource Context ToolbarCreate Dependency. Create a parent/child relationship between two resources.Delete Dependency. Remove a parent/child relations

Seite 87 - Configuration Tasks

Resource Context ToolbarRemove Dependency. Remove a parent/child relationship between two resources.Delete Resource Hierarchy. Remove a resource hiera

Seite 88 - Verifying the Configuration

Server Context ToolbarServer Context ToolbarThe server context toolbar is displayed in the properties panel when you select a server in the statustabl

Seite 89 - SNMP Troubleshooting

GUI Serverits configuration data. Since the LifeKeeper GUI is a client/server application, a user will run thegraphical user interface on a client sys

Seite 90

Scenario 4 262Installation and Configuration 265Before Configuring Your DataKeeper Resources 265Hardware and Software Requirements 265Hardware Require

Seite 91

Starting the application clientNOTE: When you run the applet, if your system does not have the required Java Plug-in, you will beautomatically taken t

Seite 92

GUI ConfigurationSee Running the GUI on a Remote System for information on configuring and running the GUI on aremote system outside your LifeKeeper c

Seite 93 - Optional Configuration Tasks

GUI LimitationsGUI LimitationsItem DescriptionGUI inter-operabilityrestrictionThe LifeKeeper for Linux client may only be used to administer LifeKeepe

Seite 94

LifeKeeper GUI Server ProcessesThis command halts all LifeKeeper GUI Server daemon processes on the server being administered ifthey are currently run

Seite 95 - Configuration Considerations

Java Security PolicyThey take effect on the user's next login or when the GUI server is restarted, whichever comes first.Each user has a single p

Seite 96 - Using Your Own Certificates

Policy File Creation and ManagementThe user policy file starts with `.` and is by default at:<USER.HOME>\.java.policyNote: USER.HOME refers to t

Seite 97 - Linux Configuration

Sample Policy Fileperm = new java.io.FilePermission("/tmp/abc","read");In this, the target name is "/tmp/abc" and the ac

Seite 98

Java Plug-InJava Plug-InRegardless of the browser you are using (see supported browsers), the first time your browserattempts to load the LifeKeeper G

Seite 99

Running the GUI on a Remote Systeml If you already have a user policy file, you can add the required entries specifiedin/opt/LifeKeeper/ htdoc/java.po

Seite 100 - Item Description

Applet TroubleshootingApplet TroubleshootingIf you suspect that the applet failed to load and initialize, try the following:1. Verify that applet fail

Seite 101 - Application Configuration

Overview 284Creating a DataKeeper Resource Hierarchy 284Extending Your Hierarchy 286Extending a DataKeeper Resource 287Unextending Your Hierarchy 288D

Seite 102

Browser Security Parameters for GUI Appletand password.4. Once a connection to the cluster is established, the GUI window displays a visualrepresentat

Seite 103

Properties Panelresources. It shows:l the state of each server in the top row,l the global (cross-server) state and the parent-child relationships of

Seite 104

Message Barthat command is added under this label. If you are running multiple commands at the same time(typically on different servers), the output f

Seite 105

Enabling Automatic LifeKeeper RestartNote: If you receive an error message referencing the LifeKeeper Distribution Enabling Packagewhen you start Life

Seite 106

Disabling Automatic LifeKeeper RestartDisabling Automatic LifeKeeper RestartIf you do not want LifeKeeper to automatically restart when the system is

Seite 107

Connecting Servers to a ClusterREGISTRY=internal -DGUI_WEB_PORT=81com.steeleye.LifeKeeper.beans.S_LKConnecting Servers to a Cluster1. There are two po

Seite 108

Viewing Connected Servers1. There are three possible ways to begin.l On the Global Toolbar, click the Disconnect button.l On the Edit Menu, select Ser

Seite 109

Viewing Server PropertiesALIVEClient has valid connection to the server.Comm paths originating from this server to an ALIVE remote server areALIVE.Com

Seite 110

Viewing Resource Tags and IDsl On the Edit Menu, point to Server, click View Log, then select the server that you wantto view from the Server list in

Seite 111

Global Resource StatusServerResourceStateVisualStateWhat it MeansActive Resource is operational on this server and protected. (ISP)DegradedResource is

Seite 112

This document and the information herein is the property of SIOS Technology Corp. (previouslyknown as SteelEye® Technology, Inc.) and all unauthorized

Seite 113

Example: 302Server Failure 303Resynchronization 303Avoiding Full Resynchronizations 304Method 1 304Procedure 304Method 2 305Procedure 305Clustering wi

Seite 114

Viewing Resource PropertiesVisualStateDescription What it Means / CausesNormalResource is active (ISP) and all backups areactive.WarningResource is ac

Seite 115

Setting View Options for the Status WindowSetting View Options for the Status WindowThe Options Dialog is available from the View menu. This allows yo

Seite 116

Resource TreeResource TreeThis option group allows you to specify the sorting order of the resources in the resource hierarchytree.l Sort By Resource

Seite 117

Viewing Message Historyl Automatic: Automatically resizes all columns to fill available space.Note: The 7 (seven) and 8 (eight) keys are defined as ho

Seite 118

Expanding and Collapsing a Resource Hierarchy TreeExpanding and Collapsing a Resource Hierarchy TreeIn this segment of the tree, the resource file_sys

Seite 119

Cluster Connect DialogNote: The "9" and "0" keys are defined as hot/accelerator keys to facilitate quickly expanding orcollapsing

Seite 120

Resource Properties DialogResource Properties DialogThe Resource Properties dialog is available from the Edit menuor from aresource context menu.Thi

Seite 121

Relations Tabresources can be active on only one of the grouped systems at a time.l Initialization. The setting that determines resource initializatio

Seite 122

General TabGeneral Tabl Name. Name of the selected server.l State. Current state of the server. These are the possible server state values:l ALIVE - s

Seite 123

General Tabl Administrator - the user can perform any LifeKeeper task.l Operator - the user can monitor LifeKeeper resource and server status, and can

Seite 124

Successful Migration 334Troubleshooting 337Index 341Table of Contents xix

Seite 125 - Disabling Reservations

CommPaths TabCommPaths Tabl Server. The server name of the other server the communication path is connected to in theLifeKeeper cluster.l Priority.Th

Seite 126 - I/O Fencing Chart

Resources TabThese are the possible communications path status values displayed below the detailed textin the lower panel:l NORMAL - all comm paths fu

Seite 127

Operator Tasksl Name. The tag name of a resource instance on the selected server.l Application. The application name of a resource type (gen, scsi, ..

Seite 128 - Quorum/Witness

Taking a Resource Out of Serviceservice without bringing its parent resource into service as well. Click In Service to bring theresource(s) into servi

Seite 129 - Configurable Components

Related TopicsThe LifeKeeper Configuration Database (LCD) maintains the object-oriented resource hierarchyinformation and stores recovery direction in

Seite 130 - Available Quorum Modes

Hierarchy DefinitionHierarchy DefinitionThese are the tasks required to construct the example application hierarchy:1. Create file system resources. T

Seite 131 - Available Witness Modes

Hierarchy DefinitionNote: Although you can create much of the definition using the LifeKeeper GUI, the rest of thisexample demonstrates the command in

Seite 132

LCD Configuration Datadep_create -d Server1 -p the-project-plan -c schedule-on-Server1dep_create -d Server2 -p the-project-plan -cschedule-from-Server

Seite 133

LCD Directory StructureDisks on a Small Computer System Interface (SCSI) bus are one example of equivalent resources.With the SCSI locking (or reserve

Seite 134 - Scenario 3

Resources Subdirectoriesdifferent resource type for other application resource hierarchies or app for generic or user-defined applications.lOther typi

Seite 136 - SCSI Reservations

Resource Actionsl actions. This directory contains the set of recovery action programs that act only on resourceinstances of the specific resource typ

Seite 137 - Using IPMI with STONITH

LCMLCMThe LifeKeeper Communications Manager (LCM) provides reliable communication betweenprocesses on one or more LifeKeeper servers. This process can

Seite 138 - Package Requirements

Communication Status Informationl Failover Recovery. If a resource fails on a system, the LCM notifies LifeKeeper to recoverthe resource on a backup s

Seite 139 - <vm_id>

Alarm ProcessingDefining additional scripts for the sendevent alarming functionality is optional. When you defineLifeKeeper resources, LifeKeeper prov

Seite 140 - Watchdog

Changing LifeKeeper Configuration Values2. If you are changing the uname of a LifeKeeper server, change the server's hostname using theLinux host

Seite 141 - Configuration

File System Health MonitoringValue Old Newuname Server1 Newserver1comm path address 172.17.100.48 172.17.105.49IP resource address 172.17.100.220 172.

Seite 142 - Resource Policy Management

Condition Definitionsl A warning message can be logged and email sent to a system administrator.l Local recovery of the resource can be attempted.l Th

Seite 143 - Standard Policies

Maintaining a LifeKeeper Protected Systeml mount point is busyl mount failurel LifeKeeper internal errorMaintaining a LifeKeeper Protected SystemWhen

Seite 144 - Meta Policies

Recovering After a Failover3. Restore the hierarchy. Use the LifeKeeper GUI to bring the resource hierarchy back inservice. See Bringing a Resource In

Seite 145 - The lkpolicy Tool

Removing via GnoRPMl Remove all packages. If you remove the LifeKeeper core, you should first remove otherpackages that depend upon LifeKeeper; for ex

Seite 146 - Removing Policies

Chapter 1: IntroductionAbout SteelEye Protection Suite for LinuxSteelEye Protection Suite (SPS) for Linux integrates high availability clustering with

Seite 147 - Configuring Credentials

LifeKeeper Communication Pathsnetwork access requirements.Note: If you wish to simply disable your firewall, see Disabling a Firewallbelow.LifeKeeper

Seite 148 - LifeKeeper API

Disabling a Firewallformula:10001 + <mirror number> + <256 * i>where i starts at zero and is incremented until the formula calculates a po

Seite 149 - N-Way Recovery

Starting LifeKeeper1. Make sure your IT department has opened the secure shell port on the corporate firewallsufficiently to allow you to get behind t

Seite 150 - Creating a Communication Path

Starting LifeKeeper Server ProcessesStarting LifeKeeper Server ProcessesIf LifeKeeper is not currently running on your system, type the following comm

Seite 151 - Deleting a Communication Path

Disabling Automatic LifeKeeper RestartThis command will remove the resources from service but does not set the !nofailover! flag [seeLCDIflag(1M)] on

Seite 152 - Server Properties - Failover

TuningLargeClusterSupportLifeKeeper supports large cluster configurations, up to 32 servers. There are manyfactors other than LifeKeeper, however, tha

Seite 153 - Creating Resource Hierarchies

LifeKeeper OperationsIPCSemaphoresand IPCSharedMemoryLifeKeeper requires Inter-Process Communication (IPC) semaphores and IPCshared memory. The defau

Seite 154 - Recovery Kit Options

LifeKeeper OperationsSystemPanic onLockedSharedDevicesLifeKeeper uses a lock to protect shared data from being accessed by other servers ona shared SC

Seite 155

Server ConfigurationServer ConfigurationItem DescriptionBIOS Updates The latest available BIOS should always be installed on all LifeKeeper servers.Pa

Seite 156

Set Block Resource Failover On:system administrator before allowing LifeKeeper to perform a failover recovery of a system that itdetects as failed.Use

Seite 157

SPS Core Package ClusterThe SPS for Linux image file includes a core package cluster containing the following softwarepackages:SPS Core Package Cluste

Seite 158 - Editing Resource Priorities

NFS Client Mounting ConsiderationsNFS Client Mounting ConsiderationsAn NFS Server provides a network-based storage system to client computers. To util

Seite 159 - Using the Up and Down Buttons

Expanded Multicluster ExampleSteelEye Protection Suite for Linux219

Seite 161

TroubleshootingThe Message Catalog (located on our Technical Documentation site under “Search for an ErrorCode”) provides a listing of all error codes

Seite 162 - Unextending a Hierarchy

InstallationDescriptionGUI does not work with default RHEL6 64-bitThere is a compatibility issue against Red Hat Enterprise Linux 6 64-bitSolution: In

Seite 163

LifeKeeper CoreLifeKeeper CoreSteelEye Protection Suite for Linux223

Seite 164

LifeKeeper CoreDescriptionLanguage Environment EffectsSome LifeKeeper scripts parse the output of Linux system utilities and rely on certain patterns

Seite 165

LifeKeeper CoreDescriptionlkscsid will halt system when it should issue a sendeventWhen lkscsid detects a disk failure, it should, by default,issue a

Seite 166

LifeKeeper CoreDescriptionThe use of lkbackups taken from versions of LifeKeeper previous to 8.0.0 requiresmanually updating /etc/default/LifeKeeper w

Seite 167 - LifeKeeper User Guide

LifeKeeper CoreDescriptionLifeKeeper syslog EMERG severity messages do not display to a SLES10 or SLES11host's console which has AppArmor enabled

Seite 168 - GUI Overview - General

TrainingSection DescriptionSPS for LinuxInstallationGuideProvides useful information for planning and setting up your SPS environment,installing and l

Seite 169 - Exiting GUI Clients

Internet/IP LicensingInternet/IP LicensingDescriptionINTERFACELIST syntax,/etc/hostssettings dependency/etc/hosts settings:When using internet-based

Seite 170 - Resource Context Menu

GUIGUIDescriptionGUI login prompt may not re-appear when reconnecting via a web browser after exitingthe GUIWhen you exit or disconnect from the GUI a

Seite 171 - Server Context Menu

GUIDescriptionJava Mixed Signed/Unsigned Code Warning - When loading the LifeKeeper Java GUIclient applet from a remote system, the following security

Seite 172 - Edit Menu - Resource

Data ReplicationDescriptionsteeleye-lighttpd process fails to start if Port 778 is in useIf a process is using Port 778 when steeleye-lighttpd starts

Seite 173 - View Menu

Data ReplicationDescription32-bit zlib packages should be installed to RHEL 6 (64-bit) for Set Compression LevelWhen using SDR with RHEL 6 (64-bit),

Seite 174 - GUI Toolbar

Data ReplicationDescriptionMirror resyncs may hang in early RedHat/CentOS 6.x kernels with a "Failed to removedevice" message in the LifeKee

Seite 175

IPv6IPv6234Troubleshooting

Seite 176 - Resource Context Toolbar

IPv6DescriptionSIOS has migrated to the use of theipcommand and away from theifconfigcommand.Because of this change,customers with external scrip

Seite 177

IPv6Description'IPV6_AUTOCONF = No' for/etc/sysconfig/network-scripts/ifcfg-<nicName>is not beinghonored on reboot or bootOn boot, a

Seite 178 - LifeKeeper GUI - Overview

ApacheDescriptionIPv6 resource reported as ISP when address assigned to bonded NIC but in 'tentative'stateIPv6 protected resources in LifeKe

Seite 179 - Starting GUI clients

Technical Supportl Log a Caseto report new incidents.l View Casesto see all of your open and closed incidents.l Review Top Solutionsproviding infor

Seite 180 - Running the GUI

NFS Server Recovery KitDescriptionThe Oracle Recovery Kit does not support the ASM or grid component features of Oracle10gThe following information ap

Seite 181 - GUI Configuration

SAP Recovery KitDescriptionNFS v4 cannot be configured with IPv6IPv6 virtual IP gets rolled up into the NFSv4 heirarchy.Solution: Do not use an IPv6 v

Seite 182 - Troubleshooting

LVM Recovery KitDescriptionWhen changes are made to res_state, monitoring is disabledIfProtection Levelis set toBASICand SAP is taken down manuall

Seite 183 - Configuring GUI Users

DMMP Recovery KitDMMP Recovery KitDescriptionDMMP: Write issued on standby server can hangIf a write is issued to a DMMP device that is reserved on an

Seite 184 - Java Security Policy

MD Recovery KitMD Recovery KitDescriptionMD Kit does not support mirrors created with “homehost”The LifeKeeper MD Recovery Kit will not work properly

Seite 185

Samba Recovery KitDescriptionMD resource instances can be adversely impacted by udev processing during restoreDuring udev processing, device nodes are

Seite 186 - Sample Policy File

Running from a Modem:e.g.:208.2.84.61 homer.somecompany.com homerThis should reduce the time it takes to make the first lookup.In addition, incorrect

Seite 187 - Java Plug-In

From Windows:addresses. When unresolvable names, WINS names or unqualified DHCP names are used, thiscauses Java to throw an UnknownHostException.This

Seite 188

From Linux:l Try editing the hosts file to include entries for the local host and the LifeKeeperservers that it will be connected to.On Windows 95/98

Seite 189 - Applet Troubleshooting

Unable to Connect to X Window Server:5. Try setting the hostname property to be used by the GUI client. This will need to be changedfor each administr

Seite 190 - Status Table

Chapter 2: SPS InstallationThe SteelEye Protection Suite (SPS) Installation Guide contains information on how to plan andinstall your SPS environment.

Seite 191 - Output Panel

Communication Paths Going Up and DownAs a result of this problem, your users may have trouble creating or changing resources during thefrozen interval

Seite 192 - Starting LifeKeeper

Restoring Your Hierarchy to a Consistent Stateresources for a hierarchy. In order to maintain consistency in a hierarchy, LifeKeeper requires thatprio

Seite 193 - Stopping LifeKeeper

No Shared Storage Found When Configuring a Hierarchy6. As a last resort, if the hierarchy cannot be repaired, you may have to delete and re-create the

Seite 194 - Viewing LifeKeeper Processes

Recovering from a LifeKeeper Server Failurewith "NU-" then LifeKeeper was unable to get a unique ID from the device.Without a unique IDLife

Seite 195 - Disconnecting From a Cluster

Recovering from a Non-Killable Process4. Finally, extend each resource hierarchy from the server where the resource hierarchy is in-service to the re-

Seite 196 - Viewing Connected Servers

Taking the System to init state S WARNING(RS-232 TTY) console can experience severe problems with LifeKeeper service. During operation,LifeKeeper gene

Seite 197 - Viewing Server Log Files

Suggested Action:reason for alarm. However, if this message is frequently in the log, or the number is 2 or 3, then twoactions may be necessary:l Atte

Seite 198 - Viewing Resource Tags and IDs

Chapter 4: SteelEye DataKeeper for LinuxIntroductionSteelEye DataKeeper for Linux provides an integrated data mirroring capability for LifeKeeperenvir

Seite 199 - Global Resource Status

Synchronous vs. Asynchronous Mirroringl Provides failover protection for mirrored data.l Integrates into the LifeKeeper Graphical User Interface.l Ful

Seite 200 - Viewing Resource Properties

Synchronization (and Resynchronization)that consists of a local disk or partition and a Network Block Device (NBD) as shown in the diagrambelow.A Life

Seite 201 - Resource Labels

SPS Core Package Clusteranswering Yes to each question in order to complete all the steps required by the installation imagefile.The SPS for Linux ima

Seite 202 - Column Width

Standard Mirror ConfigurationStandard Mirror ConfigurationThe most common mirror configuration involves two servers with a mirror established between

Seite 203 - Viewing Message History

Multiple Target ConfigurationMultiple Target ConfigurationWhen used with an appropriate Linux distribution and kernel version 2.6.7 or higher, SteelEy

Seite 204

SteelEye DataKeeper Resource HierarchyA given source disk or partition can be replicated to a maximum of 7 mirror targets, and each mirrortarget must

Seite 205 - Cluster Disconnect Dialog

Failover ScenariosThe resource datarep-ext3-sdr is the NetRAID resource, and the parent resource ext3-sdr is the filesystem resource. Note that subseq

Seite 206 - Resource Properties Dialog

Scenario 2Scenario 2Considering scenario 1, Server 2 (still the primary server) becomes inoperable during theresynchronization with Server 1 (now the

Seite 207 - Server Properties Dialog

Scenario 4Result: LifeKeeper will not bring the DataKeeper resource ISP on Server 2. When Server 1 comesback up, LifeKeeper will automatically bring t

Seite 209

Installation and ConfigurationBefore Configuring Your DataKeeper ResourcesThe following topics contain information for consideration before beginning

Seite 210 - CommPaths Tab

Software RequirementsSoftware Requirementsl Operating System – SteelEye DataKeeper can be used with any major Linux distributionbased on the 2.6 Linux

Seite 211 - Resources Tab

Changing the Data Replication Pathl This release of SteelEye DataKeeper does not support Automatic Switchback for DataKeeperresources. Additionally,

Seite 212 - Operator Tasks

Planning Your SPS EnvironmentThe following topics will assist in defining the SPS for Linux cluster environment.Mapping Server ConfigurationsDocument

Seite 213 - Advanced Tasks

Determine Network Bandwidth Requirementssufficient bandwidth to successfully replicate the partition and keep the mirror in the mirroring state asthe

Seite 214 - LCDI Commands

Measuring Detailed Rate of ChangeSteelEye DataKeeper can mirror daily, approximately:T1 (1.5Mbps) - 14,000 MB/day (14 GB)T3 (45Mbps) - 410,000 MB/day

Seite 215 - Hierarchy Definition

Analyze Collected Detailed Rate of Change Datamsg "\n";msg "This utility takes a /proc/diskstats output file that contains\n";msg

Seite 216

Analyze Collected Detailed Rate of Change Data'ios_pending' => 11,'ms_time_total' => 12,'weighted_ms_time_total' =

Seite 217 - LCD Configuration Data

Analyze Collected Detailed Rate of Change Datamy $dev = shift;my $blksize = shift;my $interval = shift;my ($max, $maxindex, $i, $first, $last, $total)

Seite 218 - LifeKeeper Flags

Analyze Collected Detailed Rate of Change Datareturn @totalvals;}# converts to KB, MB, etc. and outputs size in readable formsub HumanSize {# params:

Seite 219 - Resources Subdirectories

Graph Detailed Rate of Change Data# ./roc-calc-diskstats 2m “Jul 22 16:04:01” /root/diskstats.txtsdb1,sdb2,sdc1 > results.txtThe above example dump

Seite 220 - Resource Actions

Graph Detailed Rate of Change Data1. Open results.csv, and select all rows, including the total column.2. Open diskstats-template.xlsx, select the dis

Seite 221

Graph Detailed Rate of Change Data5. Make a note of the following row/column numbers:a. Total (row 6 in screenshot below)b. Bandwidth (row 9 in screen

Seite 222 - Alarm Classes

Graph Detailed Rate of Change Data“=diskstats.csv!$B$<row>:$<final_column>$<row>"example: “=diskstats.csv!$B$9:$R:$9"iv. C

Seite 223 - Maintenance Tasks

Table of ContentsChapter 1: Introduction 1About SteelEye Protection Suite for Linux 1SPSfor Linux Integrated Components 1SteelEye Protection Suite So

Seite 224

Sample Configuration Map for LifeKeeper Pairlocked resources at any given time. LifeKeeper device locking is done at the Logical Unit(LUN) level. For

Seite 225 - File System Health Monitoring

Confirm Failover and Block Resource Failover Settingsiv. Click OKc. Click OK to exit the Wizard8. The Bandwidth vs ROC graph will update.Please analy

Seite 226 - Condition Definitions

When to Select This Settingtime in seconds that LifeKeeper should wait before taking the default action (setting this to zeromeans “don’t wait before

Seite 227

Setting the Flags on Each Serverfailure. It will only block failovers due to local resource failures.Setting the Flags on Each Server1. Log in to the

Seite 228 - Removing LifeKeeper

Examples3. In the Set Block Resource Failover On column, select the checkbox for each server in thecluster as required.In the following example, Serve

Seite 229 - Removing via Command Line

Block Failover in One Direction3. In /etc/default/LifeKeeper, set the following:CONFIRMSODEF = 1CONFIRMSOTO = 04. Perform the above steps on each serv

Seite 230 - LifeKeeper Data Replication

Replicate New File Systemtype. There are several different DataKeeper resource types. The following information can help youdetermine which type is b

Seite 231 - Disabling a Firewall

Resource Configuration TasksResource Configuration TasksYou can perform all SteelEye DataKeeper configuration tasks via the LifeKeeper Graphical UserI

Seite 232

Creating a DataKeeper Resource HierarchyField TipsSwitchbackTypeYou must select intelligent switchback. This means that after a failover tothe backup

Seite 233

Extending Your HierarchyExtending Your HierarchyThis operation can be started from the Edit menu or initiated automatically upon completing theCreate

Seite 234 - Technical Notes

Extending a DataKeeper ResourceField TipsTargetPrioritySelect or enter the Target Priority. This is the priority for the new extendedDataKeeper hierar

Seite 235

Storage and Adapter Optionsreside on a disk array subsystem (Redundant Array of Inexpensive Disks, or RAID). LifeKeepersupports a number of hardware

Seite 236 - LifeKeeper Operations

Unextending Your HierarchyField TipsDataKeeperResourceTagSelect or enter the DataKeeper Resource Tag name.Bitmap FileSelect or edit the name of the bi

Seite 237

Deleting a Resource Hierarchy1. On the Edit menu, select Resourcethen Unextend Resource Hierarchy.2. Select the Target Server where you want to unext

Seite 238 - Server Configuration

Bringing a DataKeeper Resource In Servicebreaks the mirror, unmounts the file system (if applicable), stops the md device and kills the nbdserver and

Seite 239 - NFS Client Options

Performing a Manual Switchover from the LifeKeeper GUIIf you execute the Out of Service request, the resource hierarchy is taken out of service withou

Seite 241 - Expanded Multicluster Example

AdministrationAdministering SteelEye DataKeeper for LinuxThe following topics provide information to help in understanding and managing SteelEye DataK

Seite 242

GUI Mirror AdministrationGUI Mirror AdministrationA SteelEye DataKeeper mirror can be administered through the LifeKeeper GUI in two ways:1. By enabli

Seite 243 - Known Issues and Restrictions

Create and View Rewind BookmarksClick on each icon below for a descriptionor,2. By right-clicking thedata replication resourceand selecting an actio

Seite 244 - Description

Force Mirror OnlineForce Mirror OnlineForce Mirror Online should be used only in the event that both servers have become inoperable andthe primary ser

Seite 245 - LifeKeeper Core

Rewind and Recover Data1. The mirror is paused.2. A timestamp associated with previous disk write is selected and the disk is rewound to thattime.3. T

Seite 246

Supported Storage ModelsVendor Storage Model CertificationConsan CRD5440 SIOS Technology Corp.testingCRD7220 (f/w 3.00) SIOS Technology Corp.testingDa

Seite 247

Rewind and Recover DataDialog 34. The data is being rewound. After the data is rewound, the target disk is mounted for read-onlyaccess so that the dat

Seite 248

Set Compression Levelresynced to the old source disk. Click Finish. Rewind is complete.10. You are asked to manually copy files to the source system.

Seite 249

Command Line Mirror Administrationmaximum size. However, the log will wrap around and overwrite the earliest entries when it detectsthat it has run ou

Seite 250 - Internet/IP Licensing

Examples:Note: mirror_settings should be run on the target system(s) (or on all systems, if you want thesettings to take effect regardless of which sy

Seite 251

Monitoring Mirror Status via Command LineMonitoring Mirror Status via Command LineNormally, the mirror status can be checked using the Replication Sta

Seite 252

Server FailureServer FailureIf both your primary and backup servers become inoperable, your DataKeeper resource will bebrought into service/activated

Seite 253 - Data Replication

Avoiding Full ResynchronizationsAvoiding Full ResynchronizationsWhen replicating large amounts of data over a WAN link, it is desirable to avoid fullr

Seite 254

Method 27. Bring the mirror and dependent filesystem and applications (if any), into service. The bitmapfile will track any changes made while the dat

Seite 255

Clustering with Fusion-io3. Configure the communication paths in LifeKeeper.4. Create the mirror and extend to the target. A full resync will occur.5.

Seite 256 - 234Troubleshooting

NetworkNetworkl Use a 10 Gbps NIC: Flash-based storage devices from Fusion-io (or other similar productsfrom OCZ, LSI, etc.) are capable of writing da

Seite 257

Supported Storage ModelsVendor Storage Model CertificationEMC Symmetrix 3000 Series SIOS Technology Corp.testingSymmetrix 8000 Series Vendor support s

Seite 258

Configuration Recommendationsnet.ipv4.tcp_wmem = 4096 65536 16777216net.ipv4.tcp_timestamps = 0net.ipv4.tcp_sack = 0net.core.optmem_max = 16777216net.

Seite 259 - Oracle Recovery Kit

Multi-Site ClusterSteelEye Protection Suite for Linux Multi-Site ClusterThe SteelEye Protection Suite for Linux Multi-Site Cluster is a separately lic

Seite 260 - NFS Server Recovery Kit

Multi-Site Cluster Configuration Considerationsand are familiar with the SteelEye LifeKeeper graphical user interface, the SteelEye Protection SuiteMu

Seite 261 - SAP Recovery Kit

Multi-Site Cluster RestrictionsExample Description1Using the Multi-Site Cluster hierarchy’s mirror disk resource more than once in thesame or differen

Seite 262 - LVM Recovery Kit

Replicate New File SystemField TipsHierarchyTypeChoose the data replication type you wish to create by selecting oneof the following:l Replicate New F

Seite 263 - PostgreSQL Recovery Kit

Replicate New File System3. Select Back to select a different source disk or partition that is shared. Provide the remaininginformation to finish conf

Seite 264 - MD Recovery Kit

Replicate New File SystemField TipsBitmap FileSelect the bitmap file entry from the pull down list.Displayed in the list are all available shared file

Seite 265 - GUI Troubleshooting

Replicate Existing File SystemReplicate Existing File SystemThis option will unmount a currently mounted file system on a local disk or partition, cre

Seite 266 - Unknown Host Exception:

DataKeeper ResourceField TipsBitmap FileSelect the bitmap file entry from the pull down list.Displayed in the list are all available shared file syste

Seite 267 - From Windows:

DataKeeper ResourceField TipsSource Disk orPartitionThe list of Source Disks or Partitions in the drop down box contains all theavailable disks or par

Seite 268 - From Linux:

Supported Storage ModelsVendor Storage Model CertificationFujitsu ETERNUS3000 (w/ PG-FC105, PG-FC106, or PG-FC107), single path onlyPartner testingET

Seite 269

Extending Your HierarchyField TipsDataKeeperResourceTagSelect or enter a unique DataKeeper Resource Tag name for the DataKeeperresource instance.Bitma

Seite 270 - Incomplete Resource Created

Extending Your Hierarchyinput/confirmation, click Accept Defaults.2. The Pre-Extend Wizard will prompt you to enter the following information.Note: Th

Seite 271

Extending a DataKeeper Resource4. Depending upon the hierarchy being extended, LifeKeeper will display a series of informationboxes showingthe Resour

Seite 272

Extending a Hierarchy to a Disaster Recovery SystemDuring resynchronization, the DataKeeper resource and any resource that depends on it willnot be ab

Seite 273 - Suggested Action:

Extending a Hierarchy to a Disaster Recovery SystemNote: Depending upon the hierarchy being extended, LifeKeeper will display a series ofinformation b

Seite 274 - Serial (TTY) Console WARNING

Configuring the Restore and Recovery Setting for Your IP ResourceField TipsReplicationPathSelect the pair of local and remote IP addresses to use for

Seite 275 - Explanation

Migrating to a Multi-Site Cluster EnvironmentMigrating to a Multi-Site Cluster EnvironmentThe SteelEye Multi-Site Migrate feature is included in the S

Seite 276

Performing the MigrationPerforming the MigrationThere are three methods for configuring and performing a Multi-Site Migrate. You can:lSelect the Migra

Seite 277 - DataKeeper Features

Performing the Migrationl Select the file system resource and select the Migration icon from the Properties Paneltoolbar.326Multi-Site Cluster

Seite 278 - How SteelEye DataKeeper Works

Performing the MigrationIf you initiate the Migrate from the global toolbar icon, the following dialog box will display:1. Select the server where the

Seite 279

Supported Storage ModelsVendor Storage Model CertificationHitachi DataSystemsHDS RAID 700 (VSP) Partner testingHDS 7700 Vendor support statementHDS 58

Seite 280 - N+1 Configuration

Performing the Migration2. Select the root hierarchy tag that will be migrated and click Next. The root tag can be a filesystemor other application r

Seite 281 - Multiple Target Configuration

Performing the Migration3. Press Continue when the Continue button is enabled. The following bitmap dialog will display.SteelEye Protection Suite for

Seite 282

Performing the Migration4. Select a bitmap file for the file system you are migrating. Select Next.Important: Once you select Next, you will not be ab

Seite 283 - Failover Scenarios

Performing the Migration5. Select the second bitmap file for the second file system being migrated within the hierarchy.After selecting the first bitm

Seite 284

Performing the Migration7. This Summary screen displays all the configuration information you’ve submitted during theMigrate procedure. Once you selec

Seite 285

Performing the Migration8. The Migration status will display in this window. Press Finish when the Finish button isenabled.SteelEye Protection Suite f

Seite 286

Successful MigrationSuccessful MigrationThe following image is an example of a file system resource hierarchy after the Multi-Site migration iscomplet

Seite 287 - Hardware Requirements

Successful MigrationSteelEye Protection Suite for Linux335

Seite 289

TroubleshootingThis section provides information regarding issues that may be encountered with the use ofDataKeeper for Linux. Where appropriate, addi

Seite 290

Supported Storage ModelsVendor Storage Model CertificationHP/Compaq RA 4100 SIOS Technology Corp.testing14Planning Your LifeKeeper Environment

Seite 291

TroubleshootingSymptom Suggested ActionPrimary servercannot bring theresource ISP when itreboots after bothservers becameinoperable.If the primary ser

Seite 292

TroubleshootingSymptom Suggested ActionCore -LanguageEnvironmentEffectsSome LifeKeeper scripts parse the output of Linux system utilities and relyon

Seite 293

TroubleshootingSymptom Suggested ActionData Replication -GUI does not showproper state onSLES 10 SP2systemOn SLES 10 SP2, netstat is broken due to a

Seite 294

IndexIndexAActive/Active 42Active/Standby 43Adapter Options 9Administration 127API 126Asynchronous Mirroring 256Automatic LifeKeeper RestartDisabling

Seite 295

IndexConfiguration 61Application 79Concepts 40Data Replication 78General 266Network 79Verify Network Configuration 26Network and LifeKeeper 266Optiona

Seite 296

IndexServer Properties 185Disconnecting 173EEnvironmentSetup 25Error Detection 127Event Email Notification 67Configuration 69Overview 63Troubleshootin

Seite 297

IndexForce Mirror Online 296GGeneric Applications 39GUIAdding Icon to Desktop Toolbar 71Configuring 158Configuring Users 161Exiting 170Overview 156Run

Seite 298

IndexMirroring 255IP Addresses 39JJavaPlug-in 165Security Policy 162LLCD Interface (LCDI) 192License 31LifeKeeper Alarm Interface 200LifeKeeper Commun

Seite 299

IndexMenus 148Edit Menu - Resource 150Edit Menu - Server 151File 150Help 152Resource Context 148Server Context 149View 151Message Bar 170Mirror Admini

Seite 300 - Confirm Failover On

IndexRestore and Recover 323Restrictions 311NN-Way Recovery 127Nested File System 233Network BandwidthDetermine Requirements 267Measuring Rate of Chan

Seite 301 - Block Resource Failover On

Supported Storage ModelsVendor Storage Model CertificationMA / RA 8000 SIOS Technology Corp.testingMSA1000 / MSA1500 (active/active and active/passive

Seite 302

IndexRecoveryAfter Failover 206Non-Killable Process 252Out-of-Service Hierarchies 252Panic During Manual Recovery 252Server Failure 251Removing LifeKe

Seite 303 - Examples

IndexExtending 138, 286File System 139Generic Application 139Raw Device 140Hierarchy Relationships 47In Service 290Information 48Maintaining 205Out of

Seite 304

IndexFailover 130Viewing 175Shared Communication 41Shared Data Resources 40Shared Equivalencies 47Starting LifeKeeper 170, 210Status DisplayDetailed 4

Seite 305 - DataKeeper Resource

IndexGUITroubleshooting 243Incomplete Resource Created 248Incomplete Resource Priority Modification 248Known Issues 221Restrictions 221TTY Connections

Seite 307 - Field Tips

Supported Storage ModelsVendor Storage Model CertificationIBM FAStT200 SIOS Technology Corp.testing16Planning Your LifeKeeper Environment

Seite 308 - Extending Your Hierarchy

Supported Storage ModelsVendor Storage Model CertificationFAStT500 SIOS Technology Corp.testingSteelEye Protection Suite for Linux17

Seite 309

Supported Adapter Models 22Setting Up Your SPS Environment 25Installing the Linux OS and Associated Communications Packages 25Connecting Servers and S

Seite 310 - Unextending Your Hierarchy

Supported Storage ModelsVendor Storage Model CertificationDS4100 * Partner testing18Planning Your LifeKeeper Environment

Seite 311 - Deleting a Resource Hierarchy

Supported Storage ModelsVendor Storage Model CertificationDS4200 Partner testingDS4300 (FAStT600) * SIOS Technology Corp.testingDS4400 (FAStT700) * SI

Seite 312

Supported Storage ModelsVendor Storage Model CertificationJetStor JetStor II SIOS Technology Corp.testingMicroNet Genesis One Vendor support statement

Seite 313

Supported Storage ModelsVendor Storage Model CertificationSun StorEdge 3310 Partner testingStorEdge 3510 FC (w/ Sun StorEdge 2Gb PCI SingleFC Network

Seite 314

Supported Adapter ModelsSupported Adapter ModelsAdapterTypeAdapter Model CertificationDifferentialSCSIAdapterAdaptec 2944 W, Adaptec 2944 UW, orAdapte

Seite 315 - Viewing Mirror Status

Supported Adapter ModelsAdapterTypeAdapter Model CertificationFibreChannelQLogic QLA 2100, QLogic QLA 2200, QLogic QLA2340, QLogic QLA 200 (HP Q200)HP

Seite 317

Setting Up Your SPS EnvironmentNow that the requirements have been determined and LifeKeeper configuration has been mapped,components of this SPS envi

Seite 318 - Rewind and Recover Data

Verifying Network Configuration1. Partition disks and LUNs. Because all disks placed under LifeKeeper protection must bepartitioned, your shared disk

Seite 319

VLAN Interface Support Matrixb. Change the server’s hostname using the Linux hostname command.c. Before continuing, you should ensure that the new hos

Seite 320

System Grouping Arrangements 41Active - Active Grouping 42Active - Standby Grouping 43Intelligent Versus Automatic Switchback 44Logging With syslog 45

Seite 321 - Set Rewind Log Max Size

Installing and Setting Up Database Applicationsprimary server, that IP address “switches” to the backup server.If you plan to configure resource hiera

Seite 322 - Mirror Settings

Installing the SteelEye Protection Suite SoftwareInstall the SPS software on each server in the SPS configuration. Each SPS server must have thepackag

Seite 323 - Bitmap Administration

Installing the SPS SoftwareIMAGE_NAME is the name of the imageMOUNT_POINT is the path to mount location2. Change to the sps.img mounted directory and

Seite 324 - Example:

Obtaining and Installing the LicenseSPS for Linux requires a unique license for each server. The license is a run-time license, whichmeans that you ca

Seite 325 - Resynchronization

Primary Network Interface Change May Require a License Rehost3. Ensure you have your LifeKeeper Entitlement ID (Authorization Code). You should havere

Seite 326 - Method 1

Internet/IP LicensingInternet/IP LicensingFor information regarding Internet/IP Licensing, please see the Known Issue in the SPS for LinuxTroubleshoot

Seite 327 - Method 2

Obtaining an Internet HOST IDl If ownership of the license certificate has changed, please contact SIOS Technology Corp.support personnel to have the

Seite 328 - Clustering with Fusion-io

Upgrading SPSupgrade from the older version to one of the two acceptable versions, then perform the upgrade to thecurrent version.Note: If using lkbac

Seite 329 - TCP/IP Tuning

Upgrading SPSupgrades, LifeKeeper should not be started when a different version or release is resident and runningon another system in the cluster.36

Seite 330 - Configuration Recommendations

Chapter 3: SteelEye LifeKeeper for LinuxIntroductionSteelEye LifeKeeper for Linux provides high availability clustering for up to 32 nodes with manysu

Seite 331 - Multi-Site Cluster

Set Up TTY Connections 62LifeKeeper Event Forwarding via SNMP 63Overview of LifeKeeper Event Forwarding via SNMP 63LifeKeeper Events Table 63Configuri

Seite 332

LifeKeeper CoreLifeKeeper CoreLifeKeeper Core is composed of four major components:l LifeKeeper Core Softwarel File System, Generic Application, Raw I

Seite 333 - Cluster Resource Hierarchy

File System, Generic Application, IP and RAW I/O Recovery Kit Softwareindicates the server has failed.l LifeKeeper Alarm Interface - The LifeKeeper Al

Seite 334

LifeKeeper GUI SoftwareLifeKeeper GUI SoftwareThe LifeKeeper GUI is a client / server application developed using Java technology that provides agraph

Seite 335

Components Common to All LifeKeeper ConfigurationsLifeKeeper automatically manages the unlocking of the disks from the failed server and thelocking of

Seite 336

Active - Active GroupingIn an active/active group, all servers are active processors, but they also serve as the backup serverfor resource hierarchies

Seite 337

Active - Standby GroupingAppB and AppC, however, have several grouping options because all four servers have access to theAppB and AppC shared resourc

Seite 338

Intelligent Versus Automatic SwitchbackA standby server can provide backup for more than one active server. For example in the figureabove, Server 2 i

Seite 339

Logging With syslogl LifeKeeper never performs an automatic switchback from a higher priority server to a lowerpriority server.Logging With syslogBegi

Seite 340

Resource StatesResource StatesState MeaningIn-Service,Protected(ISP)Resource is operational. LifeKeeper local recovery operates normally. LifeKeeperin

Seite 341

Hierarchy RelationshipsHierarchy RelationshipsLifeKeeper allows you to create relationships between resource instances. The primary relationshipis a

Seite 342

How Certificates Are Used 74Using Your Own Certificates 74Linux Configuration 75Data Replication Configuration 78Network Configuration 79Application C

Seite 343

Resource Hierarchy InformationResource Hierarchy InformationThe resource status of each resource is displayed in the Detailed Status Display and the S

Seite 344

Resource Hierarchy ExampleResource Hierarchy ExampleDetailed Status DisplayThis topic describes the categories of information provided in the detailed

Seite 345 - IP Resource

Detailed Status DisplaySHARED equivalency with "apache-home.fred" on "roadrunner", priority = 10FAILOVER ALLOWEDipeth0-172.17.104.

Seite 346 - Before You Start

Resource Hierarchy Informationto machine=roadrunner type=TCP addresses=192.168.1.1/192.168.105.19state="DEAD" priority=2 #comm_downs=0LifeKe

Seite 347 - Performing the Migration

Communication Status Informationl these resources are dependent.If present, indicates the tag names of all parent resourcesthat are directly depende

Seite 348 - 326Multi-Site Cluster

LifeKeeper Flagspath in the DEAD state, which initiates a failover event if there are no othercommunications paths marked ALIVE.l Remote system writer

Seite 349

Shutdown StrategylOther typical flags include !nofailover!machine, !notarmode!machine, and shutdown_switchover. The !nofailover!machineand !notarmode

Seite 350

Communication Status Informationresources within the hierarchy indented appropriately to indicate dependency relationships betweenresources.The BACKUP

Seite 351

Local Recovery Scenariowhen a particular interface fails on a server, the protected IP address can be made to function on thebackup interface, therefo

Seite 352 - 330Multi-Site Cluster

Resource Error Recovery ScenarioThis operation will fail if there is no backup interface configured for this instance. If the specifiedresource instan

Seite 353

SCSI Reservations 114Storage Fence Using SCSI Reservations 114Alternative Methods for I/O Fencing 115STONITH 115Using IPMI with STONITH 115Package Req

Seite 354 - 332Multi-Site Cluster

Resource Error Recovery Scenario1. lkcheck runs. By default, the lkcheck process runs once every two minutes. When lkcheckruns, it invokes the appropr

Seite 355

Server Failure Recovery Scenariodetermines whether the failing resource or a resource that depends upon the failing resourcehas any shared equivalenci

Seite 356 - Successful Migration

Server Failure Recovery ScenarioThe following steps describe the recovery scenario, illustrated above, if LifeKeeper marks allcommunications connectio

Seite 357

Installation and ConfigurationSPS for Linux InstallationFor complete installation instructions on installing the SPS for Linux software, seethe SPS f

Seite 358

Set Up TTY Connections5. Perform any of the following optional configuration tasks:l Set the Server Shutdown Strategyl Configure the manual failover c

Seite 359

LifeKeeper Event Forwarding via SNMPecho Helloworld | /opt/LifeKeeper/bin/portio -p port -b baudwhere:l baud is the same baud rate selected for Server

Seite 360 - Symptom Suggested Action

LifeKeeper Events TableLifeKeeper Event/DescriptionTrap#Object IDLifeKeeper Startup CompleteSent from a node when LifeKeeper is started on that node10

Seite 361

Configuring LifeKeeper Event ForwardingLifeKeeper Communications Path UpA communications path to a node has become operational140 .1.3.6.1.4.1.7359.1.

Seite 362

Verifying the Configuration1. Ensure that the snmptrap utility is available as noted above.2. Specify the network management node to which the SNMP tr

Seite 363

SNMP TroubleshootingSNMP TroubleshootingFollowing are some possible problems and solutions related to SNMP Event Forwarding. For specificerror message

Seite 364

Adding or Changing Credentials 125Listing Stored Credentials 125Removing Credentials for a Server 125Additional Information 125LifeKeeper API 126Netwo

Seite 365

LifeKeeper Events Generating EmailTo disable Email Notification, either run lk_confignotifyalias (See thelk_confignotifyalias(1M) man page for an exa

Seite 366

Configuring LifeKeeper Event Email NotificationLifeKeeperCommunications PathUpA communications path to a node has become operational.LifeKeeperCommuni

Seite 367

Disabling Event Email NotificationLifeKeeper log can be inspected to determine if there was a problem sending the emailmessage.SeeEmail Notification

Seite 368 - Multi-Site Cluster 309

Optional Configuration Tasksgenerate email notification messages.Also, see theOverview of LifeKeeper Event EmailNotificationto see if the LifeKeepe

Seite 369

Tuning the LifeKeeper HeartbeatDo Not Switch OverResources (default)LifeKeeper will not bring resources in service on a backup serverduring an orderly

Seite 370

ExampleImportant Note: The values for both tunables MUST be the SAME on all servers in the cluster.ExampleConsider a LifeKeeper cluster in which both

Seite 371

Using Custom Certificates with the SPS APILCMNUMHBEATS=2LifeKeeper will use a 1 second interval for the TCP communications path, and a 2 second interv

Seite 372

Linux ConfigurationLinux ConfigurationOperatingSystemThe default operating system must be installed to ensure that all required packagesare installed.

Seite 373

Linux ConfigurationKernelupdatesIn order to provide the highest level of availability for a LifeKeeper cluster, the kernelversion used on a system is

Seite 374

Linux ConfigurationDynamicdeviceadditionPrior to LifeKeeper startup, Linux must configure all devices. If a LifeKeeperprotected device is configured

Kommentare zu diesen Handbüchern

Keine Kommentare