auth权限配置，这里是个示例:
### This file is an example authorization file for svnserve.
### Its format is identical to that of mod_authz_svn authorization
### files.
### As shown below each section defines authorizations for the path and
### (optional) repository specified by the section name.
### The authorizations follow. An authorization line can refer to:
### - a single user,
### - a group of users defined in a special [groups] section,
### - an alias defined in a special [aliases] section,
### - all authenticated users, using the '$authenticated' token,
### - only anonymous users, using the '$anonymous' token,
### - anyone, using the '*' wildcard.
###
### A match can be inverted by prefixing the rule with '~'. Rules can
### grant read ('r') access, read-write ('rw') access, or no access
### ('').
[aliases]
# joe = /C=XZ/ST=Dessert/L=Snake City/O=Snake Oil, Ltd./OU=Research Institute/CN=Joe Average
[groups]
admin = jiabao,hehaizhou
client = jiabao,liweijia,ranxiaolei,wufuqiang,dabaoji,tangqueyue,lisugang,huangchenguang,shenwei,zhangshaojun,yaofeng,chenying,dongdanong,yangyiting,chenpengxiang
server = jiabao,hehaizhou,banben,liangwei,wangchengjie,fangxiaoting,xujiaqian,zhaotong,liuxishan,huangdinghui,jiaxuesong
server2 = zhangxiaohui
design = majie,wuxuejing,xiaodi,wangyelei,yuyijie,lilinying,tanghengyuan,zhuangchao,wangjiawei,shijinyang,zhaoxiang,yuanzhiyong,dongpengfei,chenzeyu,zhangbowen,yangyiting,linchaofan,gaofei,wuxin,limin
CeShi = pangbo,zhangxiaohui,pangdacheng,zhouzhenquan,chenan,zhangbo
artsUE = songchangming,yuyijie,konglixun,dailun
adproject = jiabao,wufuqiang,ranxiaolei,huangchenguang
tooproject = jiabao,chenying,tanghengyuan,wuxuejing,zhuangchao,dongpengfei,chenzeyu,gaofei
arts = lilinying,xiaodi,jiabao,chenying,tanghengyuan,wangjiawei,zhuangchao,shijinyang,wuxuejing
artsUI = jiangmina,tanshuangshan,songchangming,chenying,yuyijie,lilinying,tanghengyuan,jiabao,xiaodi,wangjiawei,liuyameng,liuange,luoruijun,wuxuejing,wangzhichao,gaofei,yangyiting,limin
ClientIos = zhangruidong,louhangfeng,tiandong,zhangqi,lijunjun
ClientTrunk = wufuqiang,xiaodi,chenying,jiabao
ClientBanShun = wufuqiang,jiabao,chenying,lilinying,tanghengyuan
ShuZhi = majie,wangyelei,jiabao
[/]
@admin = rw
*=
[/Client/Branch]
@client = rw
@server = rw
@design = rw
@artsUE = rw
@CeShi = rw
*=
[/Server]
@server = rw
*=
[/Client/IOS]
@ClientIos = rw
@client = rw
@server = rw
@design = rw
@CeShi= rw
*=
[/Client/Trunk]
@client = rw
@server = rw
@design = rw
@artsUE = rw
@CeShi = rw
*=
[/Client/Trunk2]
@ClientTrunk = rw
@CeShi =rw
*=
[/Client/ClientBug]
@client = rw
*=
[/Client/BanShu]
@ClientBanShun = rw
*=
[/Client/Tags]
@client = rw
@server = rw
@design =rw
@CeShi = rw
*=
[/Client/HW]
@client = rw
@server = rw
@design =rw
@CeShi = rw
*=
[/Client/YN]
@client = rw
@server = rw
@design =rw
@CeShi = rw
*=
[/Client/HT]
@client = rw
@server = rw
@design =rw
@CeShi = rw
*=
[/Client/WX]
@client = rw
@server = rw
@design =rw
@CeShi = rw
*=
[/Client/Test]
@CeShi = rw
@client =rw
@server = rw
@design = rw
@artsUE = rw
*=
[/Client/VersionsLog]
@CeShi = rw
@client =rw
@server = rw
@design = rw
@artsUE = rw
*=
[/Client/APK]
@server = rw
@client = rw
@design = rw
@CeShi = rw
@artsUE =rw
*=
[/Design]
@design = rw
@client = rw
@server = rw
@artsUE = rw
@CeShi = rw
*=
[/DesignWX]
@design = rw
@client = rw
@server = rw
@artsUE = rw
@CeShi = rw
*=
[/AndroidProject]
@adproject = rw
*=
[/AndroidStuioProject]
@adproject = rw
*=
[/ToolProject]
@tooproject = rw
*=
[/Arts]
@arts = rw
@artsUE = rw
*=
[/ArtsUI]
@artsUI = rw
*=
[/Numerical]
@ShuZhi = rw
*=
[/ArtsUIHP]
@artsUI =rw
*=
svn备份三种方式
优缺点分析：
第一种 svnadmin dump是官方推荐的备份方式，优点是比较灵活，可以全量备份也可以增量备份，并提供了版本恢复机制。
缺点是：如果版本比较大，如版本数增长到数万、数十万，那么dump的过程将非常慢；备份耗时，恢复更耗时；不利于快速进行灾难恢复。
个人建议在版本数比较小的情况下使用这种备份方式。
第二种 svnadmin hotcopy原设计目的估计不是用来备份的，只能进行全量拷贝，不能进行增量备份；
优点是：备份过程较快，灾难恢复也很快；如果备份机上已经搭建了svn服务，甚至不需要恢复，只需要进行简单配置即可切换到备份库上工作。
缺点是：比较耗费硬盘，需要有较大的硬盘支持。
第三种 svnsync实际上是制作2个镜像库，当一个坏了的时候，可以迅速切换到另一个。不过，必须svn1.4版本以上才支持这个功能。
优点是：当制作成2个镜像库的时候起到双机实时备份的作用；
缺点是：当作为2个镜像库使用时，没办法做到“想完全抛弃今天的修改恢复到昨晚的样子”；而当作为普通备份机制每日备份时，操作又较前2种方法麻烦。
将原来的Repository导出为一个文件dumpfile 。svnadmin dump 原先的repos的目录路径（/repository/directory） > dumpfile
svnadmin dump /alidata1/svnroot/back_code/ > back_code_20171127
2. 在另外一台机器上配置同样的SVN服务器。
参考：linux SVN安装及配置图解教程
3. 将dumpfile导入到新的repository 目录中。
svnadmin load 新建的repos的目录路径（/repository/directory） < dumpfile
svnadmin load /alidata1/svnroot/back_code/ < back_code_20171127
4. 将原先服务器的配置文件备份后复制到新服务器中
/opt/svn/iitshare/conf目录下 authz、passwd、svnserve.conf文件
hotcopy方法
1. 备份
svnadmin hotcopy /alidata1/svnroot/back_code/ back_code_20171127 --clean-logs
如果你传递–clean-logs选项，svnadmin会执行热拷贝操作，然后删除不用的Berkeley DB日志文件。
你可以在任何时候运行这个命令得到一个版本库的安全拷贝，不管其它进程是否使用这个版本库。
2. 还原
svnadmin hotcopy back_code_20171127 /alidata1/svnroot/back_code/
