[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Taking mirror Backup of SVN Repos through 3rd Party Software

From: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Thu, 30 Jun 2011 07:21:56 +0200

Guten Tag Waseem Bokhari,
am Mittwoch, 29. Juni 2011 um 18:17 schrieben Sie:

> What's in all these *.txn folders (33740-q3q.txn, 1757-1d0.txn,
> 33753-q43.txn) Please guide ? Are they of any use? What is their importance
> for Us? Could they be ignored or excluded?

New commits start in those folders as they describe a new transaction.
Normally you should only see them as a new commit gets processed or if
an error occurs during a commit and the transaction doesn't get
deleted. Therefore, if you can ignore them or not depends on their
actuality. Normally best practices advice to delete old transactions
using a script.

> For some reason new set of files that are being dropped into these folders
> and they happen to be Alternate data streams, and which we do not seem to be
> able to pseudo mirror.

Every new commit starts as a transaction, but if successful should get
deleted. This is nothing to worry. Are you sure that Subversion
uses/creates those ADS? What's their name? I would have thought that
Subversion does not use those NTFS specific technics.

In general, I would advice not using third party software, too.
svnsync works on a differential basis as only fully commits get
synced. If your third party software would be a good tool for backup,
it would not have a problem with ADS in my opinion.

Mit freundlichen Grüßen,

Thorsten Schöning

Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
Telefon: Potsdam: 0331-743881-0
E-Mail:  tschoening_at_am-soft.de
Web:     http://www.am-soft.de
AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
Received on 2011-06-30 07:22:49 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.