versioncontrol:databaserecovery

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
versioncontrol:databaserecovery [2006/11/10 17:45] – Typos. OllivierRobertversioncontrol:databaserecovery [2022/10/07 01:47] (current) – Move bakeoff stuff under a single namespace KubilayKocak
Line 5: Line 5:
  
 ===== SVN Implementation ===== ===== SVN Implementation =====
 +
 +svn uses 'svnadmin recover' to fix bdb backends.  There is no parallel for fsfs backends because completed commit chunk files never change - they're ascii text.  You can take a md5/sha1 and it will never change.  Should a problem arise, there are various tools available including dump/restore of metadata, editing the dump files, comparing signatures of committed chunks, etc.  Automated detection of corruption is as simple as keeping and checking md5/sha checksums of the chunk files and keeping copies of the chunk files.
  
 ===== Hg Implementation ===== ===== Hg Implementation =====
  
 ===== Git Implementation ===== ===== Git Implementation =====
 +
 +Git includes a fsck tool to help repair damage to a repository if it were to occur.
  
 ===== Monotone Implementation ===== ===== Monotone Implementation =====
 **Supported** **Supported**
  
-["Monotone"]'s developers are quite paranoid about correctness, it has been the primary objective since the beginning.+[[/Monotone|Monotone]]'s developers are quite paranoid about correctness, it has been the primary objective since the beginning.
  
 Integrity of data is assured with SHA1 hashes, that are checked during every 'important' operation. Integrity of data is assured with SHA1 hashes, that are checked during every 'important' operation.
  • versioncontrol/databaserecovery.1163180756.txt.gz
  • Last modified: 2006/11/10 17:45
  • by OllivierRobert