Linode snapshot - WordPress

Snapshots run at the file level. If you're running backups on a live site, I suggest you first make a file backup of your database, since a database being written as it's backed up can create an inconsistent copy.

Here's a guide on MySQL backups: https://www.linode.com/docs/databases/m … mp-utility">https://www.linode.com/docs/databases/mysql/back-up-your-mysql-databases#option-1-create-backups-of-an-entire-database-management-system-using-the-mysqldump-utility

Assuming your database isn't too large, you can consider setting up a cron job to create backup dumps on a schedule consistent (but before) your backups.

MySQL stores its files on the filesystem but as alexfornuto mentioned, it may or may not be exactly the same data as what's in ram depending on how busy your site is and what it's doing. Disk writes are slow and expensive so MySQL may wait awhile before it commits back to the file system.

mysqldump will do a table/row lock to make sure no other processes can add data during that time.

I'm a fan of automysqlbackup. It'll do the dirty work of dumping databases for you and rotating the backups. It's handy in case you get hacked or more likely bork something yourself (or a client) and need to go back to yesterday's data for example without having to restore a linode snapshot backup.