Trivadis TechEvent 2016 Backup Methods from Practice - optimized and intelligent by Roland...

BASLE BERN BRUGG DÜSSELDORF FRANKFURT A.M. FREIBURG I.BR. GENEVA

HAMBURG COPENHAGEN LAUSANNE MUNICH STUTTGART VIENNA ZURICH

Backup Methods from PracticeOptimized and Intelligent

Roland StirnimannRobert Kruzynski

Backup Methods from Practice2 2016-09-09

DATA LOSS – Does it happen?

Agenda


1. Introduction

2. Present Backup Situation

3. Trivadis Backup ApproachInitial IdeaTrivadis Intelligent BackupAdded Value


Introduction

Reasons that argue for a Backup


Top causes of data loss

– Human errors

– Hardware or system malfunctions

– Software corruptions

– Computer viruses and malware

– Natural disasters

Murphy’s Law

– Concatenation of circumstances

– Backup as a very last stopgap

High Availability and Backup


Do we need a backup? We have Data Guard for Oracle and

AlwaysOn for Microsoft SQL Server!

High Availability does not replace the backup!

Restore can help for:

– Disaster restore (Murphy’s Law)

– Logical Corruption (unexpected feature)

– Restore for error analysis (system malfunction)

– Reverse mistakes that happened between the backrest and the keyboard


Present Backup Situation

Backup Load Peaks


Source: http://emgn.com/entertainment/23-ridiculously-overloaded-vehicles-from-all-around-the-world/

Backup Management Pains


Fixed scheduling plans

– Redundancy of backed up data

– No adaption of the plan because of a changed situation

– Overlapping of backup jobs

– Different SLA requirements in terms of backup

Decentral backup configuration

– Maintenance windows per server/database

– Difficult handling of different database categories

Manual restore tests

Backup monitoring

Reporting


Current, past and future situation

– Only visible in the log files

– What is going on right now?

– Planned jobs in the near future

Backup output (volume) and input (read i/o)

– Source of performance peaks

Multi-client and central reporting

Summary reports for the management/clients


Trivadis Backup Approach

Initial Position


Big customers have often serious backup issues

– Several hundreds of databases

– Lost tracking of backups

– Capacity problems during backup

One customer asked Trivadis to solve theses issues about 4 years ago

Our smart approach is in place for years

Since release 16.05 part of TVD-Backup Enterprise Edition

Customer statement: “We do not have to care about database backups anymore!”

Trivadis Intelligent Backup (TIB)


Uniqueness in the market because of the intelligent scheduling

TIB is part of TVD-BackupTM Enterprise Edition

Interacts with the existing backup component (rman_exec)

Lean and stable solution, based on Perl and PL/SQL (decision algorithm)

TIB knows the situation

– of all running database instances

– of all backups

TIB decides policy-based if a backup is necessary

Trivadis Intelligent Backup (TIB)


Resource Savings from a real Customer Case


I/O reduction thanks to

TIB

– TIB operating since

August 2012

DB188

– TVD-CapMan chart

shows RMAN I/O

(blue) and DB size

(brown)

– I/O reduction by

over 80%

– 15 TB less I/O per

month!

TIB Features (1)


Intelligent backup scheduling from central repository

– Policy-based decision algorithm

– Demand-oriented scheduling plan, no fix intervals

– Even load distribution thanks to foresighted backup planning

– Situation, rating and decision data is kept (forever)

Automatic detection and backup of new databases

Central backup management (e.g. maintenance windows)

Corrective actions in case of failures

Emergency mode for the backup agent in case of repository disconnect

TIB Features (2)


One policy/configuration for many databases

– SLA parameters (retention, RTO, transaction volume, frequency periods)

– Backup call definitions

– Backup windows

Backup reporting

– On the command line

– Starting with 16.11 in TVD-ReportService (PDF, Word, etc.)

Decision Algorithm Features


Interval ranges and time windows

Recovery time target

Archive destination free time target

Redo volume percentage

Current database role

Current backup load (per database, per server, per pool)

Can use RAC instance with lowest load (CPU or I/O)

Error handling

Forecasts next backup duration from previous runs and current redo volume

and much more…

tibctl – Database Configuration / Maitenance Mode


tibctl – Listing Backups


tibctl – Configuration Profiles


tibctl – Monthly Report


tibctl – DB Specific Reports


tibctl – Backup Job Distribution Report


Added Value


Cost savings by reducing the volume

Increased efficiency by preserving system/human resources

Reducing risks thanks to a reliable backup scheduling

Transparency with our comprehensive reports

Standardization and automation leads to quality improvements

TIBSimu – Get your potential Savings in a nutshell


TIBSimu calculates your potential savings in minutes

– Simulates backup runs based on existing RMAN catalog metadata

– Accepts several input parameters as backup policy

Customer # Databases Output Reduction

(Backup Volume)

Input Reduction (I/O)

Bank 1 64 -55% (160 TB) -60-70% (250-350 TB)

Bank 2 32 -76% (27 TB)

Backup compression

-73% (70 TB)

Retailer 37 -30% (21 TB) -27% (25 TB)

Questions & AnswersRoland Stirnimann

Business Development Manager

[email protected]

Phone +41 58 459 52 47

2016-09-09 Backup Methods from Practice29

Robert Kruzynski

Principal Consultant / Partner

[email protected]

Phone +49 89 99 27 59 30

Trivadis TechEvent 2016 Backup Methods from Practice - optimized and intelligent by Roland...

Technology

Transcript of Trivadis TechEvent 2016 Backup Methods from Practice - optimized and intelligent by Roland...