Initial import

git-svn-id: https://svn.disconnected-by-peer.at/svn/linamh/trunk/linamh@415 6952d904-891a-0410-993b-d76249ca496b

app-backup/svnbackup/files/svnbackup.pod

@@ -0,0 +1,83 @@
+=head1 NAME
+
+svnbackup - Backup script for subversion repositories
+
+=head1 SYNOPSIS
+
+B<svnbackup.sh> [I<options>] svn_repository_path
+
+=head1 DESCRIPTION
+
+This script dumps a subversion repository to a series of compressed
+files.  It uses a local file to remember the last changeset dumped so
+the script can be used to generate files for backups.
+
+Using the --scp option, the backup files can be generated on one
+machine and copied to a backup server once dumped.
+
+=head2 OPTIONS
+
+=over 5
+
+=item B<-v >
+
+set verbose mode on
+
+=item B<-i increment>
+
+How many revisions to include in each dump file.
+
+=item B<-s start_rev>
+
+First revision to dump.
+
+=item B<--scp remote>
+
+Location for remote backups.  Files are transfered via scp,
+then removed from the local directory.
+
+=item B<--identity ssh-key>
+
+Identity file (private key) for scp transfer.
+
+=item B<--ssh-ops options>
+
+options to use for scp
+
+=item B<--history-file>
+
+Path and filename of history file to use. If you have more than one repository to
+backup you should have an own history file for each repository. Svnbackups stores
+the last revision dumped in this file.
+
+=item B<--out-dir directory name>
+
+Path where svn dump files should be written, defaults to "."
+
+=back
+
+=head1 EXAMPLES
+
+svnbackup.sh -v -i 100 --scp user@backupserver:/backups/svn /svn/Project
+
+=head1 ENVIRONMENT
+
+svnbackup uses no environment variables.
+
+=head1 AUTHOR
+
+Doug Hellman <doug.hellmann@gmail.com>
+
+=head1 SEE ALSO
+
+svnadmin   The subversion admin command for applying dumps
+
+=head1 BUGS
+
+None known.
+
+=head1 LATEST VERSION
+
+You can obtain the latest version from the author's homepage at
+http://www.doughellmann.com/projects/svnbackup/
+