Login | Register
My pages Projects Community openCollabNet

Discussions > users > Taped backup of hotcopied repository

Project highlights: :. Download .: :. Support .: :. FAQ .: :. Translations .: :. Donate .: :. Report Bug .:

tortoisesvn
Discussion topic

Hide all messages in topic

All messages in topic

RE: Taped backup of hotcopied repository

Author "Toal, Michael (GE EntSol, Intelligent Platforms)" <michael dot toal at gefanuc dot com>
Full name "Toal, Michael (GE EntSol, Intelligent Platforms)" <michael dot toal at gefanuc dot com>
Date 2009-01-15 08:40:40 PST
Message Sorry, didn't mean to post this to the tsvn list

Michael Toal

Re: Taped backup of hotcopied repository

Author Andy Levy <andy dot levy at gmail dot com>
Full name Andy Levy <andy dot levy at gmail dot com>
Date 2009-01-15 08:38:10 PST
Message On Thu, Jan 15, 2009 at 11:25, Toal, Michael (GE EntSol, Intelligent
Platforms) <michael.toal@gef​anuc.com> wrote:
> Can anyone tell me if a taped backup of a hotcopied repository is safe?

Generally yes.

> We have an IT taped backup of a directory which has repositories
> hotcopied into.
>
> My concern was that if the hotcopy was being performed at the same time
> as the taped backup, then the taped backup could catch the directory
> half was through the hotcopy.

That would be a deficiency of your backup scheduling, possibly the
backup software itself. Schedule your hotcopies & backups so they
don't overlap.

Taped backup of hotcopied repository

Author "Toal, Michael (GE EntSol, Intelligent Platforms)" <michael dot toal at gefanuc dot com>
Full name "Toal, Michael (GE EntSol, Intelligent Platforms)" <michael dot toal at gefanuc dot com>
Date 2009-01-15 08:25:51 PST
Message Can anyone tell me if a taped backup of a hotcopied repository is safe?

We have an IT taped backup of a directory which has repositories
hotcopied into.

My concern was that if the hotcopy was being performed at the same time
as the taped backup, then the taped backup could catch the directory
half was through the hotcopy.

Cheers
Michael Toal

Re: Tricky case-sensitivity issue for "Authorization failed" when using svnserve

Author Ryan Schmidt <subversion-2008c at ryandesign dot com>
Full name Ryan Schmidt <subversion-2008c at ryandesign dot com>
Date 2008-12-19 20:41:25 PST
Message On Dec 15, 2008, at 17:57, si wrote:

> One of our developers fell into the following trap, it's the second
> time I've seen it happen, albeit in the 5-6 years we've been using
> Subversion, but I'd thought it worth mentioning.
>
> Summary: Checkout and Update will work fine if the repository name
> in the URL is incorrect due to case-sensitivity, but Commit will
> fail if repository name is specified in authz-db.

I believe that's this issue:

http://subversion.ti​gris.org/issues/show​_bug.cgi?id=2485

Re: Tricky case-sensitivity issue for "Authorization failed" when using svnserve

Author steveking
Full name Stefan K√ľng
Date 2008-12-16 08:30:48 PST
Message si wrote:
> Greetings,
>
> One of our developers fell into the following trap, it's the second time
> I've seen it happen, albeit in the 5-6 years we've been using
> Subversion, but I'd thought it worth mentioning.
>
> Summary: Checkout and Update will work fine if the repository name in
> the URL is incorrect due to case-sensitivity, but Commit will fail if
> repository name is specified in authz-db.
>
> Steps to reproduce:
>
> svnserve is running on localhost
>
> cd \temp
> svnadmin create testrepo
> edit svnserve.conf - enable password-db and authz-db
> edit password-db - enable user harry
> edit authz-db so that testrepo is a named repository
> [testrepo:/]
> harry = rw
> * =
>
> svn co svn://localhost/TESTREPO wc --username harry --password harryssecret
> Checkout out revision 0.
> svn up wc
> At revision 0.
> echo > wc\test.txt
> svn add wc\test.txt
> A wc\test.txt
>
> svn ci wc --username harry --password harryssecret -m "add test"
> svn: Commit failed (details follow):
> svn: Authorization failed
>
>
> Problem can be easily fixed by relocating working copy:
>
> svn switch --relocate svn://localhost/TESTREPO svn://localhost/testrepo wc
> svn ci wc --username harry --password harryssecret -m "add test"
> Adding wc\test.txt
> Transmitting file data .
> Committed revision 1.
>
>
> Hope that saves someone else some frustration.
>
> Personally I would have expected the checkout or update to fail, so that
> the read operation is working the same as the write operation...

You should report this to the Subversion mailing list.

Stefan

--
       ___
  oo // \\ "De Chelonian Mobile"
 (_,\/ \_/ \ TortoiseSVN
   \ \_/_\_/> The coolest Interface to (Sub)Version Control
   /_/ \_\ http://tortoisesvn.net
Attachments

Tricky case-sensitivity issue for "Authorization failed" when using svnserve

Author sshnug_si
Full name si
Date 2008-12-15 15:57:17 PST
Message Greetings,
One of our developers fell into the following trap, it's the second time
I've seen it happen, albeit in the 5-6 years we've been using Subversion,
but I'd thought it worth mentioning.

Summary: Checkout and Update will work fine if the repository name in the
URL is incorrect due to case-sensitivity, but Commit will fail if repository
name is specified in authz-db.

Steps to reproduce:

svnserve is running on localhost

cd \temp
svnadmin create testrepo
edit svnserve.conf - enable password-db and authz-db
edit password-db - enable user harry
edit authz-db so that testrepo is a named repository
[testrepo:/]
harry = rw
* =

svn co svn://localhost/TESTREPO wc --username harry --password harryssecret
Checkout out revision 0.
svn up wc
At revision 0.
echo > wc\test.txt
svn add wc\test.txt
A wc\test.txt

svn ci wc --username harry --password harryssecret -m "add test"
svn: Commit failed (details follow):
svn: Authorization failed


Problem can be easily fixed by relocating working copy:

svn switch --relocate svn://localhost/TESTREPO svn://localhost/testrepo wc
svn ci wc --username harry --password harryssecret -m "add test"
Adding wc\test.txt
Transmitting file data .
Committed revision 1.


Hope that saves someone else some frustration.

Personally I would have expected the checkout or update to fail, so that the
read operation is working the same as the write operation...


--
It's a wild world that we live in, you step to the vibe like a new
found religion, take your position, compile your vision, futurism,
algorithm has risen up! pfm - the western
Attachments
Messages per page: