BackupT2BCloud: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 4: | Line 4: | ||
== Backup of the OpenNebula database == | == Backup of the OpenNebula database == | ||
The OpenNebula database being located in /var/lib/mysql, it is not backed up with the ZFS snapshots described in the previous section. That's why we have created a cron task to automatically do a regular dump of the mysql database into the /var/lib/one directory. | The OpenNebula database being located in /var/lib/mysql, it is not backed up with the ZFS snapshots described in the previous section. That's why we have created a cron task to automatically do a regular dump of the mysql database into the /var/lib/one directory. | ||
To avoid having to specify the user and password in the mysqldump command, we have created the file ~/.my.cnf with the following content : | |||
<pre> | |||
[mysqldump] | |||
user=mysqluser | |||
password=secret | |||
</pre> | |||
Revision as of 13:42, 30 August 2016
Backup of VMs
The whole /var/lib/one directory is mounted from the volta fileserver, and regular scheduled snapshots are done automatically to tesla. You can access to these snapshots going through /var/lib/one/.zfs.
Backup of the OpenNebula database
The OpenNebula database being located in /var/lib/mysql, it is not backed up with the ZFS snapshots described in the previous section. That's why we have created a cron task to automatically do a regular dump of the mysql database into the /var/lib/one directory.
To avoid having to specify the user and password in the mysqldump command, we have created the file ~/.my.cnf with the following content :
[mysqldump] user=mysqluser password=secret