All Versions
Fisheye 4.2 DocumentationFisheye 4.1 Documentation
Fisheye 4.0 Documentation
More...
Managed repositories are not backed up by FishEye's built-in backup and restore feature. Instead, you will need to design and implement your own backup procedure.
All managed repositories are stored under a single directory in FishEye, which should be backed up regularly along with a copy of your config.xml
.
By default, this directory lives here:
FISHEYE_INST/managed-repos
This location can be configured by modifying your config.xml
file (see Setting your Repositories Root for more details on changing this value).
To back up the managed-repos
directory, you need to create a snapshot of the managed-repos
directory (including all subdirectories), then back up that snapshot. Note that the directory structure under the managed-repos
directory must be preserved in the snapshot. Your config.xml
file should also be backed up at the same time.
Creating this snapshot is an operating system-specific task, e.g.:
/etc/cron.daily
, backing up files to a directory like /var/backup/fisheye-repos
. It is best to copy an existing script in /etc/cron.daily
to ensure local conventions (file locations, lockfiles, permissions) are adhered to.Warning!
Restoring a backup requires you to revert your FishEye configuration to the point where the backup was made, and may require a full re-index of your repository, which may take a long time. Restoring a managed repository backup should only be done in a case of critical data loss.
To restore a backed up snapshot:
config.xml
file and managed-repositories directory, in case something goes wrong during the restore process.config.xml
file with the config.xml
file from your backup.managed-repos
directory with the contents of your backup snapshot.Note, it is possible to perform a manual restore for a single repository at a time by copying a single repository from your backup to your managed-repositories
directory and starting a re-index.