SUMMARY
It is strongly recommended to backup your Flix data and not rely only on storage redundancy. This article describes how to backup Flix so you are prepared for disaster recovery.
MORE INFORMATION
The backup needs to include:
- The Flix assets
- The Flix schema from your MySQL server.
First, you need to backup your assets directory. It is defined by the asset_directory attribute in the config.yml file for your Flix server. You can backup your assets by copying them to a remote location or using backup software such as Veritas NetBackup.
You can backup your Flix MySQL schema by running the flix_server with the --db-backup flag. By default, the backup will go to the `backups` directory inside the directory where flix_server lives. You can specify the directory where you want your MySQL backups to go by updating the db_backup_directory attribute in the Flix server config.yml file.
You can backup the Flix MySQL schema with a variety of MySQL tools or specialized backup software such as Veritas NetBackup. If you go this route, please make sure the Flix schema is included in the backup.
You should do a full backup at least once a month, while an incremental backup should be done every day. If you don’t have an option for incremental backups, you should do full backups daily.
You can also do a backup using the mysqldump command on the MySQL database server. This can be especially useful for large databases. The command looks like this:
mysqldump -h MYSQL_HOSTNAME -uMYSQL_USERNAME -p MYSQL_FLIX_DATABASE | gzip > flix_mysql_backup.sql.gz
Where MYSQL_HOSTNAME is the hostname or IP of the MySQL server, MYSQL_USERNAME is the username that you use for Flix to connect to the database and flix_mysql_backup.sql.gz is the name of the backup file. You can change the file name and the path where it should be kept.
FURTHER READING
Q100567: How to restore a Flix 6 database backup
Q100551: Installing MySQL 8 on Red Hat/CentOS 7 or Rocky 9
Q100593: Optimum Flix 6 servers setup
We're sorry to hear that
Please tell us why