Just hope a tornado/hurricane/flood/other calamity doesn't hit your
office and wipe out all your computers. That is the reason for offsite
backup. If all your computers are turned to garbage you need a recover
process that doesn't depend on them, but hopefully on an offsite, and
still safe, backup.
Casey
-----Original Message-----
From: Mike Brenner [mailto:mikeb@mitre.org]
Sent: Thursday, January 25, 2007 4:58 PM
To: marc gonzalez-carnicer; users@subversion.tigris.org
Subject: Re: repository administration tasks
I would like to answer this part of your question.
In many development environments and for reasonable projects, let's say
1,000,000 million lines of code or less, you might want to skip the
backups, and just have every developer check out the entire library to
their personal computer. They each back up each other, as long as they
check things back in, in a reasonable amount of time.
This theory fails, if people keep things checked out for a long period
of time, but that failure might still not induce you to take backups,
except at the moment when you have a successful test case, in which case
you would do a cold-start build and copy that into the test backup
location.
marc gonzalez-carnicer wrote:
> in particular, i guess i should provide scripts for daily incremental
> backups, and weekly whole backups, both at night. the last one is
> easy, but the first?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 26 00:06:39 2007