Guten Tag Christian Gils, am Mittwoch, 18. Mai 2011 um 15:33 schrieben Sie:
> I'm kind of stuck as to how to fix this. Can I try to insert mocked-up > empty revisions in place of the zeroed ones so that svn can proceed with > dumping the more recent half of the repository or is there a better way > to do this? We had the same issue some months ago. If you don't have a backup of the corrupted revisions, you should create a new repository with only the working revisions loaded into, checkout that and merge your existing data of the current working copies into the new repository as a filesystem operation, e.g. just overwrite everything or however complex your changes were. I would recommend doing that now, even if all your users have to wait and checkout again, but the newly created revisions won't be of any benefit unless you can't restore the damaged ones. And afterwards change you backup strategy and sync every repository to another server pretty often or create a post commit hook that backups each committed revision elsewhere or stuff like that. Our error repeated for example one day after I repaired everything because a filesystem error or stuff like that in an already backed up broken VM and it resulted in days of work. Now we sync everything every 30 minutes to another server and I feel much safer. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig Telefon: Potsdam: 0331-743881-0 E-Mail: tschoen...@am-soft.de Web: http://www.am-soft.de AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
