The AccuRev data repository should be physically located on the machine that runs the AccuRev Server process. (This is not an absolute restriction — see READ ME NOW: Assuring the Integrity of the AccuRev Repository on page 5.) The repository consists of multiple slices: the site slice contains information that pertains to the entire repository, and each depot has its own slice.
• The source machine — where the AccuRev server is currently running and the data repository is currently located.
• The destination machine — the machine to which you want to move the data repository.Note: the steps below always show UNIX/Linux pathname separators ( / ). When you’re executing commands on a Windows machine (either source or destination), be sure to use Windows pathname separators ( \ ).The procedure calls for multiple stops and starts of the AccuRev Server process. For details on how to accomplish this, see Controlling Server Operation on page 21.
1. Execute the accurev show slices and accurev show depots commands, and save the output for reference in the following steps.
1. Request a new license key for the destination machine by filling out the form at http://www.accurev.com/license-request.shtml. Save this key file to a location on the destination machine.
2. Perform a full AccuRev Server installation on this machine as described in the AccuRev Installation and Release Notes. The installation directory pathname need not be the same as on the source machine.
4. Note: Do not copy over the /storage/db directory on the destination machine. This directory should not have been included in the backup of the source machine repository, and you do not want to overwrite the /storage/db directory on the destination machine.
6. Change the locations of the slices to their locations on this machine using the output from the accurev show slices and accurev show depots commands on the source machine. To do so, run the following command for each slice:maintain chslice <slice-number> <new-location>
Borland |