Fair enough on the backup after each commit. I guess my little world (all 6 of us) do so little that I set a cron job to do a hot backup of the repository twice a day. That seems to work for us. <knock on wood>
So as far as the sizes of the backups, as long as you are using FS rather than BDB, you should be fine. BDB stores pretty much everything in one large file. That would get yucky. But I think (based on the size of your repository) I would recommend FS anyway. I'm not a fan of BDB that large.
Regards,
Frank
>From: Patrick Burleson <pburleson@gmail.com>
>Date: Wed Apr 06 18:53:35 CDT 2005
>To: Frank Gruman <fgatwork@verizon.net>
>Cc: Eric Brown <svnhelp@yahoo.com>, users@subversion.tigris.org
>Subject: Re: Repository over Raid?
>On Apr 6, 2005 6:05 PM, Frank Gruman <fgatwork@verizon.net> wrote:
>> I have a question here.... If you do a commit, the only thing that is
>> changing is the file that you changed for that particular revision. So
>> each commit is not necessarily adding another 30 GB of data. Unless you
>> have some wonderfully productive developers, or the individual file
>> sizes are monstrous, I doubt they could realistically change much more
>> than 100 MB of files in a single day (on good day). That's not to say
>> an occassional new file will be larger than that.....
>>
>> But the key dispute I have is that the commit is only writing the
>> _CHANGED_ files and not the other 29+ GB of files that are not modified
>> by your developers on that day.
>>
>
>I think the implication here is a full backup every time a commit
>happens would be the whole 30GB.I agree the repository size would not
>have changed that much between commits. So incremental backs after
>each commit would be fine.
>
>Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 7 05:21:00 2005