15.2. svnadminThe svnadmin program provides an interface for administrative tasks associated with the repository itself. It provides command-line tools for creating new repositories, maintaining repositories, and performing backups/migration of data. Online help for each of svnadmin's subcommands can be obtained by running the program as: svnadmin help [COMMAND]. Options
SubcommandsThe svnadmin commands (with alternate names in parenthesis) are
15.2.1. svnadmin createThis command creates a new repository. Basic Usage$ svnadmin create --fs-type bdb REPOSITORY_NAME or $ svnadming create --fs-type fsfs REPOSITORY_NAME Options
15.2.2. svnadmin dumpThis command outputs the contents of a repository (or selected range or revisions), in a format that is portable across Subversion versions. This can be useful for creating backups of a repository, or when upgrading across major version changes (the only ones allowed to change the database format). Basic Usage$ svnadmin dump REPOSITORY > REPOSITORY.dump Options
15.2.3. svnadmin help (?, h)This command outputs documentation for the svnadmin command. To get help on a specific subcommand, run help with the name of the command. Basic Usage$ svnadmin help [COMMAND] OptionsNone 15.2.4. svnadmin hotcopyThis command makes a copy of a repository, without requiring exclusive access. Basic Usage$ svnadmin hotcopy REPOSITORY REPOSITORY_BACKUP Options
15.2.5. svnadmin list-dblogsThis command lists all of the log files associated with a Berkeley DB backend for the given repository. Be very careful though. You should never delete logfiles that are still in use (see svnadmin list-unused-dblogs). This command only applies to Berkeley DB-based repositories. Basic Usage$ svnadmin list-dblogs REPOSITORY OptionsNone 15.2.6. svnadmin list-unused-dblogsThis command lists all of the unused log files associated with a Berkeley DB backend for the given repository. Deleting these files does not harm your repository. Basic Usage$ svnadmin list-unused-dblogs OptionsNone 15.2.7. svnadmin loadThis command loads the contents of a dumpfile (created with svnadmin dump) into the given repository. If the repository already contains data, the data in the dumpfile is added as new revisions. If the repository is empty, the UUID of the repository is changed to match the UUID in the dumpfile. Basic Usage$ cat OLD_REPOSITORY.dump | svnadmin load REPOSITORY Options
15.2.8. svnadmin lstxnsThis command lists all of the transactions currently in the repository, which have not yet been completely committed. Basic Usage$ svnadmin lstxns REPOSITORY OptionsNone 15.2.9. svnadmin recoverThis command runs a Berkeley DB recovery on the supplied repository. It only applies to a Berkeley DB-based repository, and does nothing on an FSFS repository. Make sure that you have exclusive access to the repository when this is run, as any other access during the recovery procedure could result in a corrupted repository. In Subversion 1.1 or later, if recover detects another process accessing the repository when it is run, it automatically exits. Basic Usage$ svnadmin recover REPOSITORY Options
15.2.10. svnadmin rmtxnsThis command removes the given transaction(s) from the repository. Basic Usage$ svnadmin rmtxns REPOSITORY TRANSACTION... Options
15.2.11. svnadmin setlogThis command sets the log message for a given revision to the contents of the supplied file. This change is immediate and permanent. Because Subversion doesn't version revision properties, the old message is lost. This triggers any pre-revprop-change or post-revprop-change hook scripts. Basic Usage$ svnadmin setlog REPOSITORY -r REVISION FILE Options
15.2.12. svnadmin verifyThis command runs a verification procedure on the repository to check the integrity of the data contained therein. Basic Usage$ svnadmin verify REPOSITORY OptionsNone |