The AccuRev Repository : Restoring the Repository

Restoring the Repository
If you have backed up the repository according to the directions above, you can easily restore the repository to the time at which you executed the backup command:
1.
2.
Restore the backup copy of the storage directory, using the backup/restore tool that you used to create it.
Note: if your site slice is in a non-standard location (as specified by the SITE_SLICE_LOC setting in the acserver.cnf file — see Server Configuration File on page 12), or if some depots are in non-standard locations (perhaps moved with the chslice command), then your job in restoring the backup of the entire repository is more complicated than simply to restore the storage directory.
3.
Steps 2 and 3 will restore the backed-up data to standard locations on an existing AccuRev system. For more complex restore operations, see Moving the AccuRev Server and Repository to Another Machine on page 53.
4.
maintain restore <backup-file-spec> <db-admin>
The maintain command will prompt you for the database admin password.
Note: the AccuRev Database Server must be running for this command to succeed.
5.
Note: suppose a particular depot’s files were not backed up for several hours after the backup command was executed. Even if several new versions of file gizmo.c were created with the keep command during that interval, the backed-up AccuRev metadata will have no record of those transactions. But you can still retrieve a copy of any or all of those versions from the backup medium: it’s in a container file in the data subdirectory of the depot directory.
Restoring a Replica
The procedure described above can also be used to restore a replica. After restoring the metadata, refer to the backed-up acserver.cnf file to ensure that the MASTER_SERVER, PORT, LOCAL_SERVER, and LOCAL_PORT settings are correct for your replication environment.

AccuRev, Inc.
Phone: 781-861-8700
Fax: 781-861-8704
support@accurev.com