On Tue, Jul 31, 2012 at 6:55 AM, Mat Booth <mat.booth_at_wandisco.com> wrote:
> On 31 July 2012 11:01, Nico Kadel-Garcia <nkadel_at_gmail.com> wrote:
>> On Tue, Jul 31, 2012 at 5:31 AM, Mat Booth <mat.booth_at_wandisco.com> wrote:
>>> On 30 July 2012 20:52, Fernando Gomes <Fernando.Gomes_at_grupospring.com> wrote:
>>>> Hello all,
>>>>
>>>> I am a rather experienced developer and I’m currently trying to use SVN to back up a batch of files automatically every X hours. The problem is that some of the files are open and the commit fails entirely.
>>>> I have managed to invoke a non-persistent Shadow Copy over the volume but since I am not using a windows server but windows 7 the shadow copy is read-only. (I am using the vscsc.exe variant of the Shadow Copy SDK from Microsoft).
>>>>
>>>> Everything would work just fine if this Shadow Copy was write-enabled because the .svn folder files cannot be edited and because so the script (running "svn add" or "svn commit") cannot complete.
>>>>
>>>> Has anyone tried this scenario before? If so is there any way to invoke a simple "svn commit" over open files (using shadow copy or not) on an non-server based operating system?
>>>>
>>>> Thank you for any thoughts,
>>>>
>>>> Fernando M. A. Gomes
>>>>
>>>
>>>
>>> Subversion is not a backup system. Usually you would arrange for a
>>> separate system to backup your Subversion repositories.
>>>
>>> I can't help feeling there is a better tool out there for your use-case.
>>
>> Matt, it looks like he wants to back up working copies, not
>> repositories.
>
> Exactly, but as I've said Subversion itself isn't a backup system and
> shouldn't really be used as such.
Well, no, it's not. But an automated, frequent commit process is
invaluable in certain types of production environments. DNS, for
example, can really benefit from a frequent commit process and logs of
when changes were recorded.
Received on 2012-07-31 14:47:23 CEST