efficient upgrades n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Efficient Upgrades PowerPoint Presentation
Download Presentation
Efficient Upgrades

Loading in 2 Seconds...

play fullscreen
1 / 44

Efficient Upgrades - PowerPoint PPT Presentation


  • 135 Views
  • Uploaded on

Efficient Upgrades. Steve Mallam, Sales Engineer. Upgrade Considerations. Highly available systems 24/7/365 Service Level Agreements Mission critical operations Time sensitive work $$$£$. Efficient Upgrades. Efficient for the users Not necessarily for you

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Efficient Upgrades' - lore


Download Now An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
efficient upgrades

Efficient Upgrades

Steve Mallam, Sales Engineer

upgrade considerations
Upgrade Considerations
  • Highly available systems
    • 24/7/365
    • Service Level Agreements
  • Mission critical operations
  • Time sensitive work
  • $$$£$
efficient upgrades1
Efficient Upgrades
  • Efficient for the users
    • Not necessarily for you
  • Need to be planned in advance
  • Need to be appropriate for the application
basic upgrade process
Basic Upgrade Process
  • In-place installer upgrade

201x

  • Application is down for the duration
basic upgrade process1
Basic Upgrade Process
  • In-place installer upgrade

2012

2013

  • Application is down for the duration
  • Fall-back can be difficult
parallel installation
Parallel Installation
  • Install a second system alongside original

2012

2013

basic upgrade process2
Basic Upgrade Process
  • In-place installer upgrade

2012

parallel installation1
Parallel Installation
  • Install a second system alongside original
  • Then cut over

2012

2013

parallel installation2
Parallel Installation
  • Need to ensure data is up-to-date
  • Install a second system alongside original
  • Then cut over

2012

2013

separation of data and code
Separation of Data and Code
  • Store data and code in separate databases

2012

D

C

separation of data and code1
Separation of Data and Code
  • Store data and code in separate databases

2012

2013

D

C

C

separation of data and code2
Separation of Data and Code
  • Store data and code in separate databases

2012

2013

D

C

D

C

separation of data and code3
Separation of Data and Code
  • Store data and code in separate databases

2012

2013

D

C

D

C

mirroring
Mirroring

InterSystems’ High-Availability solution

  • Clients connect to virtual IP
  • Updates replicated across both instance

M2

M1

M

NB: For more details see “Mirroring for High Availability” academy

mirroring1
Mirroring

InterSystems’ High-Availability solution

  • Clients connect to virtual IP
  • Updates replicated across both instances
  • If M1 fails…

M2

M1

M1

M

NB: For more details see “Mirroring for High Availability” academy

mirroring2
Mirroring

InterSystems’ High-Availability solution

  • Clients connect to virtual IP
  • Updates replicated across both instances
  • If M1 fails…
  • …M2 can take over

M1

M2

M

NB: For more details see “Mirroring for High Availability” academy

mirroring3
Mirroring

How does this help us…?

  • Upgrade Backup

M2

M1

M1

M

mirroring4
Mirroring

How does this help us…?

  • Upgrade Backup
  • Force failover

M2

M1

M

mirroring5
Mirroring

How does this help us…?

  • Upgrade Backup
  • Force failover
  • Upgrade (original) Primary

M2

M1

M

mirroring6
Mirroring

How does this help us…?

  • Upgrade Backup
  • Force failover
  • Upgrade (original) Primary
  • (Optionally) fail back

M1

M2

M

enterprise cache protocol ecp
Enterprise Cache Protocol (ECP)

Solution for horizontal scaling

  • Introduce one or more Application Servers that execute code

D

App2

App1

enterprise cache protocol ecp1
Enterprise Cache Protocol (ECP)

Solution for horizontal scaling

  • Introduce one or more Application Servers that execute code
  • Can keep adding…

D

App2

App1

AppN

enterprise cache protocol ecp2
Enterprise Cache Protocol (ECP)

Connection lost when mirror fails over

M1

M2

M

NB: For more details see “Mirroring for High Availability” academy

enterprise cache protocol ecp3
Enterprise Cache Protocol (ECP)

Connection lost when mirror fails over

M2

M1

M

NB: For more details see “Mirroring for High Availability” academy

enterprise cache protocol ecp4
Enterprise Cache Protocol (ECP)

Connection lost when mirror fails over

M1

M2

M

NB: For more details see “Mirroring for High Availability” academy

enterprise cache protocol ecp5
Enterprise Cache Protocol (ECP)

Connection lost when mirror fails over

  • Introduce ECP

M1

M2

M

App1

NB: For more details see “Mirroring for High Availability” academy

enterprise cache protocol ecp6
Enterprise Cache Protocol (ECP)

Connection lost when mirror fails over

  • Introduce ECP
  • When mirror fails

M2

M1

M

App1

NB: For more details see “Mirroring for High Availability” academy

enterprise cache protocol ecp7
Enterprise Cache Protocol (ECP)

Connection lost when mirror fails over

  • Introduce ECP
  • When mirror fails
  • ECP maintains connection

M1

M2

M

App1

NB: For more details see “Mirroring for High Availability” academy

enterprise cache protocol ecp8
Enterprise Cache Protocol (ECP)
  • Still need to upgrade the Application Server…

Connection lost when mirror fails over

  • Introduce ECP
  • When mirror fails
  • ECP maintains connection

M1

M2

M

App1

NB: For more details see “Mirroring for High Availability” academy

minimal downtime upgrades
Minimal Downtime Upgrades

A truly robust solution

  • Mount code in separate instance

M

M1

M2

C

C

App2

App1

Load

Balancer

S

C

NB: For full details of this process see “Minimal Downtime Upgrades” academy

minimal downtime upgrades1
Minimal Downtime Upgrades

A truly robust solution

  • Mount code in separate instance
  • Recompile

M

M1

M2

C

C

App2

App1

Load

Balancer

S

C

NB: For full details of this process see “Minimal Downtime Upgrades” academy

minimal downtime upgrades2
Minimal Downtime Upgrades

A truly robust solution

  • Mount code in separate instance
  • Recompile
  • Mount on both mirror servers

M

M1

M2

C

C

C

C

App2

App1

Load

Balancer

S

C

NB: For full details of this process see “Minimal Downtime Upgrades” academy

minimal downtime upgrades3
Minimal Downtime Upgrades

Upgrade App1

  • Shutdown App1
  • Upgrade

M

M1

M2

C

C

C

C

App2

App1

Load

Balancer

minimal downtime upgrades4
Minimal Downtime Upgrades

Upgrade App1

  • Shutdown App1
  • Upgrade
  • Switch to new code
  • Restart App1

M

M1

M2

C

C

C

C

App2

App1

Load

Balancer

minimal downtime upgrades5
Minimal Downtime Upgrades

Repeat for App 2

  • Shutdown App2
  • Upgrade

M

M1

M2

C

C

C

C

App1

App2

Load

Balancer

minimal downtime upgrades6
Minimal Downtime Upgrades

Repeat for App 2

  • Shutdown App2
  • Upgrade
  • Switch to new code
  • Restart App2

M1

M

M2

C

C

C

App2

App1

Load

Balancer

minimal downtime upgrades7
Minimal Downtime Upgrades

Upgrade Mirrors

  • Prevent failover
  • Upgrade Mirror2

M1

M

M1

M2

C

C

App2

App1

Load

Balancer

minimal downtime upgrades8
Minimal Downtime Upgrades

Upgrade Mirrors

  • Prevent failover
  • Upgrade Mirror2
  • Force failover

M1

M

M2

M2

C

C

C

App2

App1

Load

Balancer

minimal downtime upgrades9
Minimal Downtime Upgrades

Upgrade Mirrors

  • Prevent failover
  • Upgrade Mirror2
  • Force failover
  • Prevent failover
  • Upgrade Mirror1

M

M1

M2

M2

C

C

C

App2

App1

Load

Balancer

summary
Summary
  • In-place upgrades
  • Parallel installations
  • Separation of code and data
  • Mirroring
  • ECP
minimal downtime upgrades10
Minimal Downtime Upgrades

Upgrade Mirrors

  • Prevent failover
  • Upgrade Mirror2
  • Force failover
  • Prevent failover
  • Upgrade Mirror1
  • (Optionally) fail back to Mirror 1

Application has NEVER been down!

M

M1

M2

C

C

App2

App1

Load

Balancer

recommendations
Recommendations
  • Understand user needs
  • Determine how you will handle upgrades
  • Design the system to support the approach
  • Speak to us!
follow on academies
Follow-On Academies
  • Mirroring for High Availability
    • Tuesday @ 11:00
    • Wednesday @ 08:30
  • Minimum Downtime Upgrades
    • Monday @ 16:30
    • Tuesday @ 08:30
    • Wednesday @ 14:00

Orlando M

Orlando N

efficient upgrades2

Efficient Upgrades

Steve Mallam, Sales Engineer