On May 3, 2010, at 11:09, Vikrama Sanjeeva wrote: > We've recently shifted to SVN. Suppose there are three repositories R1, R2 > and R3. And each repostory has three projects in it. > > So we have: > R1: P1, P2, P3 > R2: P1, P2, P3 > R3: P1, P2, P3 > > R1-P1 and R1-P2 are changed almost daily, whereas, R1-P3 is changed very rare > (once a month) > > Change of rate in remaining repos R2 and R3 is also very rare (once in a > month) > > I call R1-P1 and R1-2 as "Active Repositories" whereas, R2 & R3 as "Sleeping > Repositories". > > In this case, I am more interested to take full backup of my active > repository once a week and daily incremental backup. > > And for Sleeping repositories, I am interested to take full backup once a > month. > > Please comment on above strategy. > > Also, is it ok to use "hot-backup.py" for full backups and and "svnadmin dump > myrepo --incremental " for incremental backups ?
Please consider backing up each revision as it is committed, in a post-commit hook. That way you won't lose even a single commit if something happens. Losing even a single commit will result in a more painful restore process for you and your users.
