TSMCluster - · PDF fileVersion 5.2 „Subtle distinction ... (inconvenient for...

Preview:

Citation preview

High Availabilityfor TSM Server on UNIXOctober 2014

TSMTSMClusterluster®®Version 5.2 Version 5.2 „Subtle distinction“„Subtle distinction“

(c) 2014 by eXstor GmbH 206.10.2014

A cluster for TSM?

1. „No, it's just backup.“

TSM today is a 24x7 application. Continous database log archiving. A bunch of single file restores a day. Do you have service level agreements? Public law specifications.

2. „We have self-made scripts.“

This was very easy with TSM Version 5. But for Version 6? Are the scripts working with 6.2 / 6.3 / 6.4 / 7.1?? Try and error? Ongoing development needed. How many programmers do you have (Vacation? Sick??) Do you speak DB2? What are „Log pinning“, semaphores, IPC, sockets ...?

(c) 2014 by eXstor GmbH 306.10.2014

3. „We have an operating system cluster.“

OS cluster depend extremly on the underlying OS. This is desired. Each OS has its own cluster (HACMP, MSCS, ..) New OS / new patch means: New cluster. OS update = cluster update = downtime. The purpose of an OS Cluster is to cover every application. There is no predefined plugin for each application. Simple ressource monitoring. It is complex, ongoing education is needed. Hard to manage. TSM admin is not able to do this. OS staff <> TSM staff (inconvenient for troubleshooting/updates) Limited design (number of TSM instances / nodes). Complicated license model.

A cluster for TSM?

4. „It's expensive.“

NO!!

(c) 2014 by eXstor GmbH 406.10.2014

Our solution! TSMCluster® extends the standard TSM server and

build a high availability solution for it There is no need for additional cluster software Is part of the IBM Value Advantage Plus program

and an IBM certified solution. Listed on www.ibm.com as partner solution.

…..since 9 years in the market!!

(c) 2014 by eXstor GmbH 506.10.2014

Content of TSMCluster®

Monitoring of TSM server and their components Alerting via common interfaces Rule-based configuration with automatic failover Central configuration and management Online updates, no dependencies = no hassle Easy manual movement of TSM server Command line and Webinterface Adaption of customer supplied techniques ACSLS, TSLM and IBM 3494 integration IBM GPFS for Linux included Integration of HADR

...but what is the difference?

(c) 2014 by eXstor GmbH 606.10.2014

Content of TSMCluster®

...but what is the difference?

Simple integration:/etc/inittab/etc/environment

Node Manager ApplicationServer

Cluster starts with:> tsmcl cluster start

Status: RUNNINGor DEGRADEDor Suspended

tsmclDistLogServer

Log Server Cluster Lock

1 1

(c) 2014 by eXstor GmbH 706.10.2014

What is the difference?

TSMCluster® is easy to manage!!!

Administration and monitoring of the TSM components through the TSM admin.

TSM

TSM server, API and clientDB2 ressources, process andfilesystems, VGs, Files,disks, mirrors, snapshotsIP, bonds, etherchannel, portsSAN, FC adapter, tapes,semaphore, IPCS, ShMem,kernel parameter and logs,external ressources

(c) 2014 by eXstor GmbH 806.10.2014

WebinterfaceInformation about the physical nodes and TSM server in one view.

…all information in one picture.

(c) 2014 by eXstor GmbH 906.10.2014

Webinterface

New: Mouse-over information / page timestamp / quicker.Dynamic adaption of drop boxes.

(c) 2014 by eXstor GmbH 1006.10.2014

What is the difference?

TSM server „tsm01“IP Alias 10.10.1.21Port 1521

TSM server „tsm02“IP Alias 10.10.1.22Port 1522

TSM server „tsm03“IP Alias 10.10.1.23Port 1523

TSM server „tsm04“IP Alias 10.10.1.24Port 1524

TSM server „tsm05“IP Alias 10.10.1.25Port 1525

Any-to-any concept Multiple TSM server (instances) are running on

multiple machines / VMs (nodes)

= TSM Server/instance is running

(c) 2014 by eXstor GmbH 1106.10.2014

What is the difference?

Sensor based TSM control A sensor is like a stethoscope Multiple sensor allows „a view into the

future“ of the TSM Server (failover prediction)

Customizable sensor for the database, logs, DB2, OS etc.

Compares static and dynamic values Sensor changes the cluster behaviour Additional sensor can simply be added

(c) 2014 by eXstor GmbH 1206.10.2014

What is the difference? Sensor are the focus in the new version 5.2 They are stored in a SQL database Graphical/SQL interface to the data They help with:

– Additional measurement of resources– Rating of a node / instance– Problem visualization and determination– „last-minute decisions“– Alerting improvement

(c) 2014 by eXstor GmbH 1306.10.2014

What is the difference?

LAN SAN

tsm0110.1.1.21port 1521

tsm0410.1.1.24port 1524

tsmlm10.1.1.20port 1520

tsm0210.1.1.22port 1522

tsm0310.1.1.23port 1523

load: 40mem: 25%net: 80%o

Example for the sensors technology

load: 140mem: 67%net: 92%

o load: 18mem: 15%net: 10%

load: 128mem: 94%net: 90%o

oo o

o

oo

ooo

(c) 2014 by eXstor GmbH 1406.10.2014

What is the difference?

LAN SAN

tsm0110.1.1.21port 1521

tsm0410.1.1.24port 1524

tsmlm10.1.1.20port 1520

tsm0210.1.1.22port 1522

tsm0310.1.1.23port 1523

LANerr: 2SANerr: 0HDDerr: 0

Example for „predictive failover“

LANerr: 1624SANerr: 0HDDerr: 34

LANerr: 12SANerr: 4HDDerr: 0

LANerr: 20SANerr: 2HDDerr: 1

„predictive failover“to the machine with lowest degradation.

o

ooo o

oo

oo

ooo

(c) 2014 by eXstor GmbH 1506.10.2014

What is new in 5.2?

Sensor facility and SQL database with SQL interface Sensor interface for customers (easy addition) New message format Move all / node evacuation. Self disabling / self suicide (SMITH) Webinterface enhancements LVM support for Linux Support for GPFS 3.5 Support for SLES 12, RHEL 6.4 and 6.5 Integration of TSM server 7.1.0 and 7.1.1

(c) 2014 by eXstor GmbH 1606.10.2014

Supported platforms

TSM Server All IBM supported Releases: TSM Version 5.5,

6.x and 7.1 Mixed levels are possible, if enough nodes are

available All supported TSM clients All TSM add-ons

ISC/AdminCenter can be included (optional) Integration of Tivoli Operation Center 7.1 TSMManager or TSMReporter or … doesn‘t care

(c) 2014 by eXstor GmbH 1706.10.2014

Operating systems

IBM AIXVersion 6.1 and 7.1All MLs/TLs, JFS2 or GPFS

LinuxRHEL 5 and 6 with LVM or GPFSSLES 11/12 with LVM or GPFS

Other platformsPlease contact us

*Nodes can have different OS levels, e.g. AIX 6.1 on NodeA and AIX 7.1 on NodeB.**In a multiple-node-cluster a mixture of Linux and AIX is possible.

(c) 2014 by eXstor GmbH 1806.10.2014

Licensing

...no PVU.

(c) 2014 by eXstor GmbH 1906.10.2014

Contact us: Bruno Friess, bf@exstor.de Address:

eXstor GmbH

Hans-Bredow-Strasse 56

65189 Wiesbaden

web: http://www.tsmcluster.com

fon: +49 170 6326924

TSMCluster® is developed together with our partner META-LEVEL Software AG in Saarbrücken. http://www.meta-level.de

1

High Availabilityfor TSM Server on UNIXOctober 2014

TSMTSMClusterluster®®Version 5.2 Version 5.2 „Subtle distinction“„Subtle distinction“

NOTWENDIGE ANPASSUNGEN

Das Kundenlogo kann

-Gelöscht werden (in den weißen Kasten klicken und dann „Entf“ drücken). Wenn kein Logo gewünscht ist oder der blaue Hintergrund OK ist

-Geleert werden (in den Kasten klicken, Strg-A drücken, Entf drücken). Wenn ein leerer weißer Hintergrund für ein Kundenlogo benötigt wird.

Vorname Nachname in der fünften Zeile ersetzen oder diese Zeile komplett löschen

Bitte bei Bedarf und nach Änderungen im Menü „Ansicht // Kopf- und Fußzeile“ das Datum in der Fußzeile korrigieren.

Dieses steht fest auf 07.04.2008. Kopf- und Fußzeile wird auf der Titelseite nicht angezeigt.

(c) 2014 by eXstor GmbH 206.10.2014

A cluster for TSM?

1. „No, it's just backup.“

TSM today is a 24x7 application. Continous database log archiving. A bunch of single file restores a day. Do you have service level agreements? Public law specifications.

2. „We have self-made scripts.“

This was very easy with TSM Version 5. But for Version 6? Are the scripts working with 6.2 / 6.3 / 6.4 / 7.1?? Try and error? Ongoing development needed. How many programmers do you have (Vacation? Sick??) Do you speak DB2? What are „Log pinning“, semaphores, IPC, sockets ...?

(c) 2014 by eXstor GmbH 306.10.2014

3. „We have an operating system cluster.“

OS cluster depend extremly on the underlying OS. This is desired. Each OS has its own cluster (HACMP, MSCS, ..) New OS / new patch means: New cluster. OS update = cluster update = downtime. The purpose of an OS Cluster is to cover every application. There is no predefined plugin for each application. Simple ressource monitoring. It is complex, ongoing education is needed. Hard to manage. TSM admin is not able to do this. OS staff <> TSM staff (inconvenient for troubleshooting/updates) Limited design (number of TSM instances / nodes). Complicated license model.

A cluster for TSM?

4. „It's expensive.“

NO!!

(c) 2014 by eXstor GmbH 406.10.2014

Our solution! TSMCluster® extends the standard TSM server and

build a high availability solution for it There is no need for additional cluster software Is part of the IBM Value Advantage Plus program

and an IBM certified solution. Listed on www.ibm.com as partner solution.

…..since 9 years in the market!!

(c) 2014 by eXstor GmbH 506.10.2014

Content of TSMCluster®

Monitoring of TSM server and their components Alerting via common interfaces Rule-based configuration with automatic failover Central configuration and management Online updates, no dependencies = no hassle Easy manual movement of TSM server Command line and Webinterface Adaption of customer supplied techniques ACSLS, TSLM and IBM 3494 integration IBM GPFS for Linux included Integration of HADR

...but what is the difference?

(c) 2014 by eXstor GmbH 606.10.2014

Content of TSMCluster®

...but what is the difference?

Simple integration:/etc/inittab/etc/environment

Node Manager ApplicationServer

Cluster starts with:> tsmcl cluster start

Status: RUNNINGor DEGRADEDor Suspended

tsmclDistLogServer

Log Server Cluster Lock

1 1

(c) 2014 by eXstor GmbH 706.10.2014

What is the difference?

TSMCluster® is easy to manage!!!

Administration and monitoring of the TSM components through the TSM admin.

TSM

TSM server, API and clientDB2 ressources, process andfilesystems, VGs, Files,disks, mirrors, snapshotsIP, bonds, etherchannel, portsSAN, FC adapter, tapes,semaphore, IPCS, ShMem,kernel parameter and logs,external ressources

(c) 2014 by eXstor GmbH 806.10.2014

WebinterfaceInformation about the physical nodes and TSM server in one view.

…all information in one picture.

(c) 2014 by eXstor GmbH 906.10.2014

Webinterface

New: Mouse-over information / page timestamp / quicker.Dynamic adaption of drop boxes.

(c) 2014 by eXstor GmbH 1006.10.2014

What is the difference?

TSM server „tsm01“IP Alias 10.10.1.21Port 1521

TSM server „tsm02“IP Alias 10.10.1.22Port 1522

TSM server „tsm03“IP Alias 10.10.1.23Port 1523

TSM server „tsm04“IP Alias 10.10.1.24Port 1524

TSM server „tsm05“IP Alias 10.10.1.25Port 1525

Any-to-any concept Multiple TSM server (instances) are running on

multiple machines / VMs (nodes)

= TSM Server/instance is running

(c) 2014 by eXstor GmbH 1106.10.2014

What is the difference?

Sensor based TSM control A sensor is like a stethoscope Multiple sensor allows „a view into the

future“ of the TSM Server (failover prediction)

Customizable sensor for the database, logs, DB2, OS etc.

Compares static and dynamic values Sensor changes the cluster behaviour Additional sensor can simply be added

(c) 2014 by eXstor GmbH 1206.10.2014

What is the difference? Sensor are the focus in the new version 5.2 They are stored in a SQL database Graphical/SQL interface to the data They help with:

– Additional measurement of resources– Rating of a node / instance– Problem visualization and determination– „last-minute decisions“– Alerting improvement

(c) 2014 by eXstor GmbH 1306.10.2014

What is the difference?

LAN SAN

tsm0110.1.1.21port 1521

tsm0410.1.1.24port 1524

tsmlm10.1.1.20port 1520

tsm0210.1.1.22port 1522

tsm0310.1.1.23port 1523

load: 40mem: 25%net: 80%o

Example for the sensors technology

load: 140mem: 67%net: 92%

o load: 18mem: 15%net: 10%

load: 128mem: 94%net: 90%o

oo o

o

oo

ooo

(c) 2014 by eXstor GmbH 1406.10.2014

What is the difference?

LAN SAN

tsm0110.1.1.21port 1521

tsm0410.1.1.24port 1524

tsmlm10.1.1.20port 1520

tsm0210.1.1.22port 1522

tsm0310.1.1.23port 1523

LANerr: 2SANerr: 0HDDerr: 0

Example for „predictive failover“

LANerr: 1624SANerr: 0HDDerr: 34

LANerr: 12SANerr: 4HDDerr: 0

LANerr: 20SANerr: 2HDDerr: 1

„predictive failover“to the machine with lowest degradation.

o

ooo o

oo

oo

ooo

(c) 2014 by eXstor GmbH 1506.10.2014

What is new in 5.2?

Sensor facility and SQL database with SQL interface Sensor interface for customers (easy addition) New message format Move all / node evacuation. Self disabling / self suicide (SMITH) Webinterface enhancements LVM support for Linux Support for GPFS 3.5 Support for SLES 12, RHEL 6.4 and 6.5 Integration of TSM server 7.1.0 and 7.1.1

16

(c) 2014 by eXstor GmbH 1606.10.2014

Supported platforms

TSM Server All IBM supported Releases: TSM Version 5.5,

6.x and 7.1 Mixed levels are possible, if enough nodes are

available All supported TSM clients All TSM add-ons

ISC/AdminCenter can be included (optional) Integration of Tivoli Operation Center 7.1 TSMManager or TSMReporter or … doesn‘t care

17

(c) 2014 by eXstor GmbH 1706.10.2014

Operating systems

IBM AIXVersion 6.1 and 7.1All MLs/TLs, JFS2 or GPFS

LinuxRHEL 5 and 6 with LVM or GPFSSLES 11/12 with LVM or GPFS

Other platformsPlease contact us

*Nodes can have different OS levels, e.g. AIX 6.1 on NodeA and AIX 7.1 on NodeB.**In a multiple-node-cluster a mixture of Linux and AIX is possible.

18

(c) 2014 by eXstor GmbH 1806.10.2014

Licensing

...no PVU.

19

(c) 2014 by eXstor GmbH 1906.10.2014

Contact us: Bruno Friess, bf@exstor.de Address:

eXstor GmbH

Hans-Bredow-Strasse 56

65189 Wiesbaden

web: http://www.tsmcluster.com

fon: +49 170 6326924

TSMCluster® is developed together with our partner META-LEVEL Software AG in Saarbrücken. http://www.meta-level.de

Nicht benötigte Folien löschen:

Allgemeine Adressangaben der eXstor

Recommended