Ssi vision. business continuity per ibm i

18
Antonio Assandri Sales & Marketing Manager - SSI 1 Business Continuity per IBM i Tecnologie diverse per esigenze differenti iEfficiency Cube Villa Borromeo – Cassano d’Adda 9 maggio 2017

Transcript of Ssi vision. business continuity per ibm i

Antonio Assandri Sales & Marketing Manager - SSI1

Business Continuity per IBM i

Tecnologie diverse per esigenze differenti

iEfficiency Cube

Villa Borromeo – Cassano d’Adda

9 maggio 2017

Disclaimer

Tutte le considerazioni e le conclusioni contenute nel presente documentosono da intendersi come sola espressione dell’opinione personale deirappresentati di SSI e valide alla data di redazione del documento stesso.

Business Continuity, High Availability, Disaster Recovery

>100,000hours Mean Time Between Failure (MTBF) for IBM Power System i

(IBM Technical Document 22053139)

High Availability = Alta Disponibilità

Business Continuity, High Availability, Disaster Recovery

Fonte: IBM HA Presentation, Eric Hess, April 2001

• Power Failures

• Network Failures

• Site Damage

• Human Errors

• Malfeasance

• Data backups

• Software upgrades, PTFs & data

conversions

• New application software installations

• Hardware upgrades

• System migrations

DR

HA

Facilità di utilizzo sistema secondarioFlessibilità

Remote Journaling BackupProduction

Rmt Jrnl

IBM i IBM i

Loc Jrnl

DataData

OS Based

Replication

Storage based

replication

BackupProduction

IBM i IBM i

IASP

SYSBAS

copy

SYSBAS

Handled separately

SAN SAN

copyGeographic Mirror

Metro Mirror

Global Mirror

Flash Copy

LUN Level Switch

IBM i Replication Technologies

Syncronous or Asyncronous

IBM i based replication over IP

Syncronous or Asyncronous

Storage based replication

Controlled by External storage

over FC or IP

Logical

replication

Syncronous or Asyncronous

Journal based replication over IP

Independent auxiliary storage pools (IASPs)

IASP AddressesAddress Space

Memory

Storage

Sin

gle

Level

Sto

rag

e

SYSBAS IASP

Independent auxiliary storage pools (IASPs) are fundamental

building blocks for implementing IBM PowerHA SystemMirror for i.

Independent disk pools allow you to store data and applications on

disk storage units that view themselves as independent from the

surrounding system and name space to which they are currently

connected.

Independent ASPs are user auxiliary storage pools that can either

be used on a single system or switched between multiple systems

or logical partitions.

These pools can be brought online, taken offline, and accessed

independently of the other pools on the system. They can even be

logically or physically switched between systems or logical

partitions.

Source: IBM Redbooks - IBM PowerHA SystemMirror for i: Preparation (SG24-8400-00)

IASP and SYSBAS

So what’s left in SYSBAS?

So what can go into an IASP?

Journaling

Journal

entries

Storage

Data

Storage

Data

Production Server Backup Server

Remote

Journal

entries

Data change to

journal at end of

transaction

Remote Journaling

Data saved to

storage later

MIMIX

Availability

SYSBAS SYSBAS

IASP IASP

Production Server Backup Server

MIMIX for PowerHA

Admin Domain

PowerHA

Replication

• Applications and data not in the IASP replicated with MIMIX for PowerHA

• Replication of all data in the IASP

• Peer to peer, not source to target

• Registered objects and attributes

PowerHA Environment

IBM i Remote Journal features

IBM Remote Journaling Target buffer

Journal entry

Remote

Journal

• Designed to conserve bandwidth

• Immediate transfer of journal entry

• Buffers data on the target

• Minimization of source CPU

• Sends compact, raw data

• Catch-up mode when behind

• Independent operation from apply to

target database

• Validity check for detecting double bit

errors over dirty networks

Priced Option 42 – Journal Performance

• Batch journal cache performance

• Journal Minimal Data

• Remote Journal filtering

• Source side filtering of objects

• Filters out SMAPP internal entries

Production Server

User Journal

System

Journal

Backup Server

Confronto funzionale Storage based Journal based

Topologia di replica (2 nodi, + nodi, on premise, cloud)

Disponibilità del sistema secondario per backup e query

Flessibilità aggiornamento SO

RPO

Facilità di installazione e gestione

Necessità di Banda

Completezza replica

RTO fermi pianificati

RTO fermi non pianificati

BRAND FAMILY

for PowerHA®

Cosa dicono i nostri clienti“Quando le tecnologie di replica storage based ci garantiranno un

RTO, costante e replicabile in tutte le condizioni, potremo fare a

meno di MIMIX. Sino a quel momento MIMIX rimane la soluzione

migliore per noi.”

CIO, Primaria banca italiana

“Quando abbiamo aggiornato i nostri sistemi ci è stata proposta

una soluzione di replica storage.

Un’analisi approfondita delle rispettive funzionalità, soprattutto in

termini di flessibilità e garanzie su RPO e RTO, ci ha convinto a

rimanere con MIMIX.”

CIO, Azienda di commercio elettronico

“Abbiamo adottato una struttura a tre nodi. Due sistemi in HA

locale con storage replica e un nodo di DR in replica logica. Per le

nostre esigenze rappresenta il compromesso ideale tra

funzionalità e garanzie.”

IT Manager, Brand del lusso

Elaborazione grafica SSI su dati

Help Systems - 2017 IBM i Marketplace Surveywww.helpsystems.com/resources/guides/2017-ibm-i-marketplace-survey-results

Cosa dice il mercato

None43,8%

PowerHA7,1%

Robot HA / RSF HA1,1%

Vision Solutions MIMIX17,3%

Vision Solutions iTera8,6%

Maxava3,9%

Rocket iCluster2,4%

Quick-EDD8,0% Other

7,8%

None

PowerHA

Robot HA / RSF HA

Vision Solutions MIMIX

Vision Solutions iTera

Maxava

Rocket iCluster

Quick-EDD

Other

Per domande e approfondimenti

ci trovate in

sala H