The backup command makes a copy of the AccuRev metadata. During backup command execution, clients can continue to work. Only transactions that are complete at the time the backup command is invoked are included in the metadata backup. The backup may take a few seconds or a few minutes, depending on the amount of metadata on your system. After running the backup, you can make a complete copy of the file storage area (the storage directory tree), without worrying about synchronization or time-skew.CAUTION: Do not execute the backup command while you are copying the file storage area. This can place incorrect data into the backup copy of the repository.With the metadata backup and the copy of the file storage area, you can restore the repository to its state at the time you executed the backup command.
• Note that the live-backup scheme relies on the ability to copy files that are currently in use by the AccuRev Server process. To support this scheme, your backup/restore tool must be able to copy files that are currently “open” at the operating system level.accurev backup <backup-file-spec>By default, the backup is stored in the storage\site_slice\backup directory.
2. If your backup utility cannot copy files that are currently open at the operating system level, stop the AccuRev Server. (See Controlling Server Operation on page 17.)
3. Use a backup/restore tool to create a backup copy of the entire directory tree below the storage directory, except for the db directory. This backup can be all-at-once or piecemeal; for example, you can back up the site_slice directory and the subdirectories within the depots directory separately.Note: if your site slice is in a non-standard location (as specified by the SITE_SLICE_LOC setting — 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 backing up the entire repository is more complicated than simply to copy the storage directory.
4.
5. If you stopped the AccuRev Server in Step 2, start it again. (See Controlling Server Operation on page 17.)The procedure described above can also be used to back up a replica. If you are backing up a replica, you will also need to make a copy of the acserver.cnf file from the bin directory and save it with the backed-up data.pg_dump: WARNING: out of shared memory
pg_dump: attempt to lock table <table name> failed: ERROR: out of
shared memory
HINT: You may need to increase max_locks_per_transaction.To increase "max_shared_locks_per_transaction", edit the value of this variable in postgresql.conf using the following formula:NOTE: Supporting the backup of more than 1,000 depots may also require that you increase the value of SHMMAX to more than 32MB.
AccuRev, Inc. |
Phone: 781-861-8700 |
Fax: 781-861-8704 |
support@accurev.com |