- Mastering MariaDB
- Table of Contents
- Mastering MariaDB
- Credits
- About the Author
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Understanding the Essentials of MariaDB
- 2. Debugging
- 3. Optimizing Queries
- 4. Transactions and Locks
- 5. Users and Connections
- 6. Caches
- 7. InnoDB Compressed Tables
- 8. Backup and Disaster Recovery
- Types of backups
- Complete and incremental backups
- Creating a dump file with mysqldump
- Delimited text backups
- The --tab option of the mysqldump command
- Loading a dump file with the mysqlimport command
- Creating a text-delimited file with the SELECT … INTO OUTFILE command
- Dumping a table definition with the SHOW CREATE TABLE command
- Loading a dump file with the LOAD DATA INFILE statement
- Separator options and clauses
- An example to create and restore dump files
- Performing a backup using a CONNECT or CSV engine
- Physical backups
- Using the binary log for incremental backups
- Percona XtraBackup
- Securing backups
- Repairing tables
- Summary
- 9. Replication
- An overview of replication
- Choosing a binary log format
- Configuring replication
- Configuring a new replication master
- Configuring a new replication slave
- Starting a slave
- Checking whether a slave is running
- Reconfiguring an existing slave
- Importing the data into a master
- Importing the data into a slave from a master
- Filtering binary log events
- Filtering the replication of events on the slaves
- Checksums of the binary log events
- Configuring parallel replication
- Delaying a slave
- Multisource replication
- Replication logs
- Checking the replication for errors
- Troubleshooting
- Summary
- 10. Table Partitioning
- 11. Data Sharding
- 12. MariaDB Galera Cluster
- Index
If a database contains sensible data, its backups will contain sensible data too. This is something we must never forget. There are several good practices that companies should follow to keep backups safe:
- Setting proper permissions: Only the user who performed the backups, probably a DBA, should have the permissions to read or write them.
- Transfer backups in a secure way: If backups are performed on the database server and then copied into another machine, the transfer must be done in a safe way. For example, the
scpcommand can be used to copy the files with an SSH connection. - Encrypt backups: After all, in theory, stealing a backup is always possible.
- Physically store backups in a safe place: A safe place is a place that unauthorized persons cannot access. A safe place should also be equipped with antitheft and antifire devices.
If necessary, SELinux or firewalls can be used to improve security.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.