restoredbs

This kandoMaintain command restores the backup of the GitCentric database created by backupdbs. Use the <path> argument to specify the location of the backup file. By default, the backup file is written to the same directory from which backupdbs was run, but it can be moved anywhere.

Syntax

kandoMaintain restoredbs -u <dbadmin> -P <dbpass> -Fb <path>

Options

The following table lists the options for this command.

-u <dbadmin>

The database administration user. This is the same user name as specified during installation (default is postgres). If this is required by the command you are using but you do not include it, kandoMaintain prompts you for it.

-P <dbpass>

The database administration password. This is the same user password as specified during installation. If this is required by the command you are using but you do not include it, kandoMaintain prompts you for it. If you write scripts that incorporate this option, be sure to secure the file against unauthorized access.
-c <dbconnectstring>

The database connection string: jdbc:postgresql://<host>:<port>/<dbname>

If you do not specify -c for a command that requires it, kandoMaintain assumes the default value jdbc:postgresql://localhost:5075/kando. If you do specify -c, then jdbc:postgresql:// is required as a minimum. Partial connection strings will have default values automatically supplied. For example, if you specify jdbc:postgresql://, kandoMaintain assumes a <host> of localhost, a <port> value of 5075 and a <dbname> of kando.

-Fc <path>

The path to a text file (such as <gc_home>/dbsettings.conf) containing values for three of the parameters used by kandoMaintain. The contents of this file should include:

  • DB_USER=<dbadmin> Eliminates the need for -u on the command line.
  • DB_PASS=<dbpassword> Eliminates the need for -P on the command line.
  • DB_CONNECT=<dbconnectstring> Eliminates the need for -c on the command line.

For example:

DB_USER=postgres

DB_PASS=postgres

DB_CONNECT =dbc:postgresql://localhost:5075/kando

Note: The settings and the values accepted by this configuration file can change without notice from release to release.

Back to top

See also: