Questions About Backup Repository

[H***@icbc-axa.com]

Dear

We use TortoiseSVN to manage the code,and backup repository with svnsync.
We backup repository to remonte servicer with svnsync.
When edit anyone in the remote repository,the remote repository will be
breakdown and never to be used again.
We have no idea to revert it only to created a new remote repository.
Is there any idea to revert the damaged repository ?
Please recommend some current ideas for me to backup the repository.

Hopes your replay.
Thanks so much.






Õźç
ÐÅÏ¢¿ÆŒŒ²¿ ¿ÆŒŒ¹ÜÀ펊
¹€Òø°²Ê¢ÈËÊÙ±£ÏÕÓÐÏÞ¹«ËŸ
ÉϺ£ÊлÆÆÖÇø°²ÀœÂ·8ºÅ6Â¥
µç»°£º021-60392672
ÓÊÏ䣺***@icbc-axa.com

[Nico Kadel-Garcia]

Post by H***@icbc-axa.com
Dear
We use TortoiseSVN to manage the code,and backup repository with svnsync.
We backup repository to remonte servicer with svnsync.
When edit anyone in the remote repository,the remote repository will be
breakdown and never to be used again.

Never permit this if you expect scnsync to maintain a current copy of the
master repository. This is called "split-brain", and any working copies
from that modified svnsync repository should be considered corrupt.
Unfortunately, tracking down all the working copies can be very difficult,
since even logging on that server doesn't necessarily reveal who and what
made copies, especially local "file:///" based working copies.

We have no idea to revert it only to created a new remote repository.

Post by H***@icbc-axa.com
Is there any idea to revert the damaged repository ?
Please recommend some current ideas for me to backup the repository.

Create an entirely new svnsync based repository from scratch. Discard the
old one, and replace it.

It may be possible to simply delete all recent transactions from the
svnsync copy if you can identify when the inappropriate changes were made
on the new repository, especially if you have a good record of what the
last appropriate committed transaction was. But it's generally not worth
the work, and much safer to make a new svnsync repository from the old
master.

The big risk, I think, is not one that you can solve by fixing the damaged
svnsync repository. It's that you may have corrupted working copies based
on that corrupted svnsync copy. I'd strongly consider discarding whatever
URL you used to use for the old svnsync copy and switching to a new URL, to
help prevent any confusion about what the new valid read-only svnsync
repository is.

Nico Kadel-Garcia

Post by H***@icbc-axa.com
Hopes your replay.
Thanks so much.
*匠虹*
信息科技郚 科技管理倄
工银安盛人寿保险有限公叞
䞊海垂黄浊区安柜路8号6楌
<https://maps.google.com/?q=%E4%B8%8A%E6%B5%B7%E5%B8%82%E9%BB%84%E6%B5%A6%E5%8C%BA%E5%AE%89%E6%BE%9C%E8%B7%AF8%E5%8F%B76%E6%A5%BC&entry=gmail&source=g>
电话021-60392672