MariaDB Backup and Move
-
So I'm reading up on this (cause the customer hasn't asked yet)
Which seems pretty darn straight-forward.
mysqldump db_name > backup-file.sqlQuestion is there anything else to watch out for?
-
There are loads of things that can go wrong. If you have certain types of triggers they won't get caught that way.
-
@scottalanmiller care to elaborate?
-
@DustinB3403 said in MariaDB Backup and Move:
@scottalanmiller care to elaborate?
Not everything is always stored in the tables. So that backup method, while getting all the data, doesn't necessarily get the whole database.
-
Like pictures etc, correct?
-
@DustinB3403 said in MariaDB Backup and Move:
Like pictures etc, correct?
That would be data. Like code.
-
But are those the kinds of things that need to be watched for?
-
@DustinB3403 said in MariaDB Backup and Move:
But are those the kinds of things that need to be watched for?
Yes, that's why I listed them as a direct answer to your question of what needs to be watched out for.
-
@scottalanmiller cool, so if I am already collecting the rest of the database (see previous topic from today using rsync) then backing up the mariadb should grab what is left.
Then all that would be left is to push the backup to an secondary system and test that all works.
-
@DustinB3403 said in MariaDB Backup and Move:
@scottalanmiller cool, so if I am already collecting the rest of the database (see previous topic from today using rsync) then backing up the mariadb should grab what is left.
Then all that would be left is to push the backup to an secondary system and test that all works.
In theory. I've had unreliable recoveries from that. I don't know any method to get 100% backup if that code is stored in the database.
