PowerCenter High Availability
Informatica GCS
PowerCenter High Availability Overview
Informatica PowerCenter High Availability Option provides high availability of all PowerCenter components, seamless failover and recovery of stopped or interrupted work, and simplified set up and management through a web-based administration console. PowerCenter HA relies on the underlying IT infrastructure to achieve endto-end HA. i.e. highly available database, file system, network and hardware servers. High availability is not a solution for disaster recovery. You can use high availability features to implement a disaster recovery solution.
PowerCenter High Availability Benefits
Resilience. Highly available systems can tolerate temporary connection failures until a timeout period expires or the failure is resolved. The system tries to reconnect for a specified period of time. If the failure is resolved, there is no interruption in end user activity. Restart and failover. In highly available systems, when a machine becomes unavailable, processes running on the machine can be restarted on the same machine or on a backup machine. By allowing processes to restart on the same machine or fail over to another machine, the system minimizes or eliminates the downtime due to the failure and maximizes the system operational time. Recovery. In highly available systems, an interrupted service can complete its operations after it is restarted. A service may be statefulthat is, it records its state of operation in a shared location periodically. When a failure occurs, the system must retrieve the state of the affected service so that it can automatically restart or recover jobs that have terminated abnormally.
Reducecostsandrisksassociatedwithdatadowntime
3
PowerCenter HA Capabilities
Servicefailoverfromprimarytobackupservicesandnodes.
Automaticallyensuresserviceavailabilityonprimaryorbackupserversshould theprimaryserverfail.
Sessionandworkflowrecoveryfromcheckpoints.
Automaticorconfigurablerecoveryforsessionsaffectedbyservicefailures.
Resiliencytonetworkandexternalfailures.
Automaticreconnectwithinresiliencetimeoutconstraintshandlestransient networkerrorsandconnectionfailures.
Centralizedwebbasedconfigurationandadministration
Abilitytocreate,manageandmonitorahighavailabilityconfigurationofall PowerCenterservicesthroughawebbasedadministrationconsole. EnableAdministratorstovisuallyidentifysinglepointoffailureswithinthe Informaticaenvironment.
PowerCenter High Availability
Automatic Failover Simulation
Component Failure (HW/SW)
Automatic Failover Restart Recovery
Data Integration Services
Backup Services Config
Repository Services
IntegrationServicealsosupportsActiveActivemode.
5
Achieving PowerCenter HA
Core Services Availability
At least 2 nodes configured w/ core services for fail-over
Application Services Availability
At least 2 nodes configured as primary and backup for services
Informatica Services (Tomcat Service Manager)
Configure service to restart automatically if it terminates unexpectedly
External Systems Availability
For Repository, Source/Target/Lookup database to be highly available, use highly available versions of databases (e.g. Oracle RAC, IBM DB2) Use highly available FTP servers and Message Queues. Configure network to be highly available Need shared directory for config, log files, storage (stores state for session and workflow recovery). Shared directory should be on HA file system (e.g. Veritas Cluster File System, IBM GPFS) to remove point of failure
Achieving PowerCenter HA
KeyunderlyingcomponentstoachieveaPowerCenterHighAvailability solutionare:
HighlyAvailableDatabase HighlyAvailableSharedFileSystem RedundantNetwork
General Recommendations: Network 1 GB > HA CFS w/ Heartbeat and Failover Redundant Network Actual config depend on environment and SLA reqs.
DR with PowerCenter
IncorporatingPowerCenterintoDisaster RecoverySolutions: PrimaryDataCentershouldbeconfigured withPowerCenterHAincludingunderlying HAinfrastructure. BackupInformatica Nodes&Services configuredpassive(coldstandby)mode. ExternalSystemsareactivelyreplicated acrossDataCentersbyrespective vendors.
Active Active Active
Active
Active
Active
Passive
Passive
DR with PowerCenter
IncorporatingPowerCenterintoDisaster RecoverySolutions: PrimaryDataCentershouldbeconfigured withPowerCenterHAincludingunderlying HAinfrastructure. BackupInformatica Nodes&Services configuredpassive(coldstandby)mode. ExternalSystemsareactivelyreplicated acrossDataCentersbyrespective vendors. BackupInformatica Nodes&Services becomeactiveonlywhenPrimaryData Centergoesdownandreplicationof requireddatahasbeencompleted. Requiresscripting/integration with3rdpartyoperation managementtools.
Recover, Re-initialize
Active
Active
High Availability Scenarios Detailed Walkthrough
10
10
Common Failure Scenarios
Domain
Domain DB
Source DB
Typical single node setup where most jobs complete within a specific window of time. Unexpected failures require sessions to be restarted losing precious time.
Repository DB
Target DB
11
Common Failure Scenarios
Domain
Domain DB
Source DB
Typical single node setup where most jobs complete within a specific window of time. Unexpected failures require sessions to be restarted losing precious time.
Repository DB
Target DB
Transient network failures result in the PowerCenter losing connectivity to sources and targets.
12
How Does It Work? Network Resiliency
Domain
HAFileSystem SharedDirectory
SourceDB
With HA, session does not immediately fail once connectivity to target is lost.
TargetDB
HADatabase RepositoryDB
13
How Does It Work? Network Resiliency
Domain
HAFileSystem SharedDirectory
SourceDB
With HA, session does not immediately fail once connectivity to target is lost. Session will try to reconnect to the target for a specific amount of time.
TargetDB
HADatabase RepositoryDB
14
How Does It Work? Network Resiliency
Domain
HAFileSystem SharedDirectory
SourceDB
With HA, session does not immediately fail once connectivity to target is lost. Session will try to reconnect to the target for a specific amount of time. Once transient network failure is resolved, session resumes processing.
15
TargetDB
HADatabase RepositoryDB
How Does It Work? Failover & Recovery
Domain
HAFileSystem SharedDirectory
SourceDB
Node 1 is running on a machine that encounters an unexpected failure.
TargetDB
HADatabase RepositoryDB
16
How Does It Work? Failover & Recovery
Domain
HAFileSystem SharedDirectory
SourceDB
Node 1 is running on a machine that encounters an unexpected failure. Integration Service fails-over to Node 2
TargetDB
HADatabase RepositoryDB
17
How Does It Work? Failover & Recovery
Domain
HAFileSystem SharedDirectory
SourceDB
Node 1 is running on a machine that encounters an unexpected failure. Integration Service fails-over to Node 2. Workflow and session restart with recovery and continue from last checkpoint.
18
TargetDB
HADatabase
Recovery
Architectural recovery
If the Service Manager and Repository Service recover, but the Integration Service cannot recover the restart is not successful and has little value to a production environment
Procedural recovery
Recovery strategy set to the workflow/session level which can recovered manually or automatically.
19
20
Powercenter File System certification
The following shared file systems are certified by Informatica for use in Integration Service failover and session recovery Storage Array Network: Veritas Cluster Files System (VxFS) IBM General Parallel File System (GPFS) Network Attached Storage using NFS v3 protocol: EMC UxFS hosted on an EMV Celerra NAS appliance NetApp WAFL hosted on a NetApp NAS appliance For more information, see the Statement of Support Regarding File System Support for Informatica PowerCenter High Availability Service Failover and Session Recovery on my.informatica.com.
21
Thanks
22
22
23
