Tweet
Tweet

Slide 1

Slide 1 text

MySQL Backup Best Practices and Case Study: .IE Continuous Restore Process Marcelo Altmann Senior Support Engineer - Percona Mick Begley Technical Service Manager - IE Domain Registry

Slide 2

Slide 2 text

Agenda

Slide 3

Slide 3 text

3 Agenda • Why we need backups for ? • Types of backups • Encryption • Compression • Where to store ? • Restoration • Validation • Binlogs • Retention period

Slide 4

Slide 4 text

Who is speaking ?

Slide 5

Slide 5 text

5 Who is Speaking ? • Marcelo Altmann - Senior Support Engineer @ Percona • MySQL DBA @ IE Domain Registry - Certifications • Oracle Certified Professional, MySQL 5.6 Database Administrator • Oracle Certified Professional, MySQL 5.6 Developer • Oracle Certified Professional, MySQL 5 Database Administrator • Oracle Certified Professional, MySQL 5 Developer • Oracle Certified Associate, MySQL 5.0/5.1/5.5 - Oracle ACE Associate - blog.marceloaltmann.com - @altmannmarcelo

Slide 6

Slide 6 text

6 Who is Speaking ? • Mick Begley - Technical Services Manager @ IE Domain Registry CLG • Head of IT @ First Derivatives • Service Integration Manager @ HP - Certifications • IT and Psychology • Qualified ITIL Service Manager • PMI Certified Project Manager

Slide 7

Slide 7 text

Why we need backups for ?

Slide 8

Slide 8 text

8 Why we need backups for ? • Slave provisioning • Build Staging / Dev environments • Disaster recovery - Data Corruption - Malicious SQL - Software Bugs - Hardware failure

Slide 9

Slide 9 text

9 Replication as backup ? Yes • Master crashes • Database physical file corruption • Any physical hardware failure - CPU - RAM - Disk - Network card

Slide 10

Slide 10 text

10 Replication as backup ? No • Application Bug • Database Hack • Malicious SQL commands

Slide 11

Slide 11 text

Types of backups

Slide 12

Slide 12 text

12 Types of backups - Logical • Structure and data are saved as logical structure • CREATE DATABASE / TABLE • INSERT INTO • Can easily be used for selective restore (Only one database/table) • Good when physical file is fragmented / corrupted • Taken while MySQL is running • Slower than physical • Tools: mysqldump, mydumper, mysqlpump

Slide 13

Slide 13 text

13 Types of backups - Physical • Raw copy of your databases and tables • Can be used for selective restore (Only one database/table) • Fast for either Dump and restore • Can be taken while MySQL is running • Bad for table corruption • Tools: Percona XtraBackup, MySQL Enterprise Backup, snapshots, rsync, cp

Slide 14

Slide 14 text

14 Types of backups - Differential or Incremental • Differential - Full copy of the database - Each differential backup has all the changes since last full backup • Monday: FULL • Tuesday: Incremental since Monday • Wednesday: Incremental since Monday • Thursday: Incremental since Monday

Slide 15

Slide 15 text

15 Types of backups - Differential or Incremental • Incremental - Full copy of the database - Each incremental backup has all the changes since last backup • Monday: FULL • Tuesday: Incremental since Monday • Wednesday: Incremental since Tuesday • Thursday: Incremental since Wednesday

Slide 16

Slide 16 text

Am I done ?

Slide 17

Slide 17 text

N O ! ! !

Slide 18

Slide 18 text

Encryption

Slide 19

Slide 19 text

19 Encryption • Keep your backups safe from unwanted access • openssl • Percona XtraBackup • --encrypt=ALGORITHM - AES128, AES192, AES256 • --encrypt-key=ENCRYPTION_KEY or --encrypt-key-file=KEYFILE

Slide 20

Slide 20 text

20 Encryption • Encrypt - xtrabackup --backup --encrypt=AES256 \ --encrypt-key-file=/data/backups/keyfile --target-dir=/data/backups • --encrypt-threads (used with --parallel ) • Decrypt - xtrabackup --decrypt=AES256 \ --encrypt-key-file=/data/backups/keyfile --target-dir=/data/backups

Slide 21

Slide 21 text

Compression

Slide 22

Slide 22 text

22 Compression • Save storage space • Require less network when streaming • Percona XtraBackup -xtrabackup --backup --compress \ --parallel=4 --compress-threads=4 --target-dir=/data/compressed/ •zip / gzip / bzip

Slide 23

Slide 23 text

Where to store ?

Slide 24

Slide 24 text

24 Where to store ? • Where are you going to store your backups ?

Slide 25

Slide 25 text

25 Where to store ? • Where are you going to store your backups ? - Same Server ?

Slide 26

Slide 26 text

26 Where to store ? • Where are you going to store your backups ? - Same Server ?

Slide 27

Slide 27 text

27 Where to store ? • Where are you going to store your backups ? - Same Server ? - Same Data-Center?

Slide 28

Slide 28 text

28 Where to store ? • Where are you going to store your backups ? - Same Server ? - Same Data-Center?

Slide 29

Slide 29 text

29 Where to store ? • Where are you going to store your backups ? - Same Server ? - Same Data-Center? - Same Region ?

Slide 30

Slide 30 text

30 Where to store ? • Where are you going to store your backups ? - Same Server ? - Same Data-Center? - Same Region ?

Slide 31

Slide 31 text

31 Where to store ? • Where are you going to store your backups ? - Same Server ? - Same Data-Center? - Same Region ? •What type of disaster my data must survive ?

Slide 32

Slide 32 text

Attention ! ! !

Slide 33

Slide 33 text

R E S T O R E ! ! !

Slide 34

Slide 34 text

34 R E S T O R E ! ! ! •Most important thing when taking backups •If you don’t test your backup, you simple don’t have a backup. •Restore on a fresh server •Keep track of restoration times •Re-configure as a slave •Test PITR

Slide 35

Slide 35 text

Validate your data

Slide 36

Slide 36 text

36 Validate your data •Run checksum on your data •Ensures your backup has all the data and the data is consistent •Pt-table-checksum / mysqldbcompare

Slide 37

Slide 37 text

Backup your binlogs

Slide 38

Slide 38 text

38 Backup your binlogs •Store a safe copy of your binlogs •Allows you to do point-in-time recovery even if you lose your master •Mysqlbinlog - mysqlbinlog --read-from-remote-server --host=host_name --raw --stop-never binlog_file •MaxScale Binlog Server

Slide 39

Slide 39 text

Retention period / audits

Slide 40

Slide 40 text

40 Retention period / audits •How far back in time you may need your data ? •How are you going to store it? •Be prepared to restore

Slide 41

Slide 41 text

.ie Backup Mick Begley IE Domain Registry [email protected]

Slide 42

Slide 42 text

Agenda • Who are we? • How is our backup setup? • Schedule • Restore times • Questions

Slide 43

Slide 43 text

Who are the IEDR ? ● The IEDR is the registry for .ie Internet Domain names and maintains the database of .ie registered Internet names. ● Managing since 2000 ● Team of 20 ● Console, API application across Three Datacenters ● 2016 stats (219,858 total registrations, 34,615 new reg, 89% renewal rate) ● Today 231,826 Domains

Slide 44

Slide 44 text

44 What is DNS? ● Domain Name Servers (DNS) are the Internet's equivalent of a phone book. They maintain a directory of domain names and translate them to Internet Protocol (IP) addresses. ● Makes it easier to move around the Internet (dont have to remember IP addresses) ● Database of high importance ● Database pushes out zone file across the world ● Over 70 nodes

Slide 45

Slide 45 text

● Local slave and DR site backup slave ● Stop replication to slave ● Dump slave ● Restart replication ● Verify Dump, Compress Dump, Encrypt Dump ● Send to Backup Server How is our backup setup?

Slide 46

Slide 46 text

● Reset DR site backup slave ● Drop all DBs ● Decrypt Dump from backup, unCompress, Restore Dump ● Stop Server ● Compress DataDirectory , Encrypt DataDirectory ● Send to Backup Server How is our backup setup?

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

Backup Schedule ● Backups run at times outside of zone pushes ● Backups run at times outside of system batch processing (NRP, Invoicing)

Slide 49

Slide 49 text

Restore procedure

Slide 50

Slide 50 text

50 Thank You Sponsors!

Slide 51

Slide 51 text

51 SAVE THE DATE! CALL FOR PAPERS OPENING SOON! www.perconalive.com April 23-25, 2018 Santa Clara Convention Center

Slide 52

Slide 52 text

Questions ? Marcelo Altmann @altmannmarcelo Mick Begley @mickarooney