ApisBare Command line - Restoring your configuration

Restoring your configuration somewhere else

If the program is run with the command Restore [Filename], it will read the configuration from the specified file and ask if you want to restore each of the instances/databases found in the backupfile.

Note that the full path to the backupfile must be specified. If the backup is detected to contain incremental entries, the /Incremental option will be required. During the restore phase, all paths in the configuration starting with the standard hive-configuration path will be remapped from the original machine's config path to the target machine's config path if they differ. Likewise, connection strings, database names, ip-adresses and servernames containing the original machine's name/address will be replaced with the target machine's name/address. A list of an instance's configuration properties that may have to be manually changed are also printed before you are asked if you want to continue restoring the instance unless the /Yes option is specified.

Restore options

The restore command may be accompanied with the following options:

  • /Yes - Restore everything, will not ask for confirmation before restoring

  • /Hive - Only restore hive instances

  • /Honeystore - Only restore honeystore database configurations + data

  • /DataOnly - Only restore honeystore data, leaves the honeystore configuration unchanged

  • /ConfigOnly - Only restore configuration (hive + honeystore), do not restore honeystore or chronical data

  • /Wait - Wait for a keypress before exiting when the restore is completed

  • /FromDate:DateTime - Restore data starting at this time (Not fully implemented)

  • /ToDate:DateTime - Restore data up until this time (Not fully implemented)

Note that hive instances will be stopped prior to configuration being restored. Likewise, honeystore will be stopped before restoring a database's configuration, and then started in order to import the data. Honeystore might even be stopped/started several times in case of an incremental restore. If more than one database is restored, honeystore will be stopped and started for each instance being restored.