opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
• -c [{gz,bz2,none}], --compression [{gz,bz2,none}]
Specify the compression method. none means no compression.
The default is bz2.
opsi-backup create -c bz2
101 / 193
• --flush-log
The backup of the mysql backend uses the mysqldump command. This means that all data known by the database
are backed up, no matter if they are on disk or only in the memory yet. This means, that your backup may be
more topical than your database files (which is really not a problem).
If you want to make sure, that the database stores all data to the disk before starting the backup, you may use the
--flush-log option. But before you may do this, you have to grant the required RELOAD-privileges to the opsi
database user, or your backup will fail. Check: RELOAD.
So use this option only if you really know what you are doing.
opsi-backup create --backends=mysql --flush-log
Example
opsi-backup create --no-configuration --backends=all opsi_backup.tar.bz2
13.5.2 Archive your backup files
opsi-backup has no features to archive the created backup files. So you have to do it by yourself (e.g. using a file
backup tool).
If you call opsi-backup with a target directory as option, please keep in mind that every call creates a new full backup
file and no older files will be deleted.
13.5.3 Verify a backup
The command opsi-backup verify is used to test the internal integrity of the created backup file. Special help for
the opsi-backup verify command is available by the command option --help.
Example
opsi-backup verify opsi_backup.tar.bz2
opsi-backup verify --help
usage: opsi-backup verify [-h] file [file ...]
required arguments:
file The backup archive to verify.
optional arguments:
-h, --help shows this help message and then exits
Tip
If you are calling opsi-backup verify at the console, it may be useful to avtivate messages at standardout using -v:
opsi-backup -v verify opsi_backup.tar.bz2