If you have a configuration file named
phpbu.xml in your current working directory you can execute phpbu like this
phpbuphpbu 6.0.0 by Sebastian Feldmann and Contributors. OK (1 backup, 0 checks, 0 encryption, 0 syncs, 0 cleanups)
If you want to use a custom name for your configuration file you have to use the
phpbu --configuration=MyConfig.xmlphpbu 6.0.0 by Sebastian Feldmann abd Contributors. OK (1 backup, 0 checks, 0 encryption, 0 syncs, 0 cleanups)
Here is the list of available options for the command line runner.
phpbu --helpphpbu 6.0.0 by Sebastian Feldmann and Contributors. Usage: phpbu [option] --bootstrap=<file> A "bootstrap" PHP file that is included before the backup. --configuration=<file> A phpbu configuration file. --colors Use colors in output. --debug Display debugging information during backup generation. --generate-configuration Create a new configuration skeleton. --limit=<subset> Limit backup execution to a subset. --simulate Perform a trial run with no changes made. -h, --help Print this usage information. -v, --verbose Output more verbose information. -V, --version Output version information and exit. --version-check Check whether phpbu is up to date. --self-update Upgrade phpbu to the latest version.
A "bootstrap" PHP file that is included before executing the backup.
Path to the phpbu config file to use. See Chapter 2 for more details.
Use colors in output.
Display debugging information during backup generation.
Limit backup execution to a subset. See the limit section for details.
Output a guide how to restore your backup.
For this to work all your
Crypts have to implement the
Execute phpbu without actually executing any backup, check, encryption, sync or cleanup task. See the simulation section for details.
In order to check what actions phpbu would perform, phpbu supports a simulation mode where no backup is actually created and no sync and cleanup tasks are executed. In simulation mode, phpbu will show you, what it would have done, if it would not have been a simulation run. You will get detailed output, which enables you to track every action phpbu would have performed.
This is a great way to test if the correct backup commands will be executed and if all the right backups will be cleaned up.
If phpbu has to use any kind of credentials executing a binary, like for example the
mysqldump command, this credentials will maybe displayed in the simulation output.
If you are extending phpbu, you can support simulation as well. You can find detailed information on this in Chapter 11.
If you don't want to execute all of your configured backups you can define a subset of backups by using the limit option.
All you have to to, is to set the limit option to a comma separated list of backup names (nameA,nameB,nameC).
If you don't define explicit backup names, phpbu will use the source type as backup name as fallback.