On Wed, Jun 1, 2016 at 11:20 AM, Stefan Hett wrote:
> To ensure the integrity of a backup close to 100% I go the fail safe way:
> 2. svnadmin dump to dump the current repository
> 3. svnadmin load the dump into a fresh repository
> 4. svnadmin dump the newly loaded repository
> 5. compare the fir
On Wed, Jun 1, 2016 at 11:29 AM, Pavel Lyalyakin <
pavel.lyalya...@visualsvn.com> wrote:
> Hello Michael,
>
> On Wed, Jun 1, 2016 at 7:18 PM, Michael Schwager
> wrote:
> ...
> > My intention is to perform the following:
> ...
> > * svnadmin verify /home/svn/hotcopy/repoX. If error, warn and ex
On Wed, Jun 1, 2016 at 11:20 AM, Stefan Hett wrote:
> On 6/1/2016 4:58 PM, Michael Schwager wrote:
>
> ...we ran into a bug that came about under 1.8 when working with older
> repos; the hotcopy exits with the following error:
>
> svnadmin: E22: Serialized hash missing terminator
>
> As far a
Yessity-yes-yes-ye! svnadmin freeze- I missed that one! That's
something I can really sink my teeth into! Awesome, thanks!
My intention is to perform the following:
* shut down httpd
Then, for each repoX:
* svnadmin verify /home/svn/hotcopy/repoX. If error, warn and exit.
* svnadmin hotcop
On Wed, Jun 1, 2016 at 10:58 AM, Pavel Lyalyakin
wrote:
> Hello Matt,
>
> Why do you use `rsync`?
>
> [1]: http://svnbook.red-bean.com/en/1.8/svn.ref.svnadmin.c.freeze.html
> [2]: http://svnbook.red-bean.com/en/1.8/svn.ref.svnadmin.c.hotcopy.html
I have no good reason! Backup scripts were setup
Hello Michael,
On Wed, Jun 1, 2016 at 7:18 PM, Michael Schwager wrote:
> Yessity-yes-yes-ye! svnadmin freeze- I missed that one! That's
> something I can really sink my teeth into! Awesome, thanks!
>
> My intention is to perform the following:
> * shut down httpd
> Then, for each repoX:
>
On 6/1/2016 4:58 PM, Michael Schwager wrote:
Hello,
We are very paranoid about our Subversion repo, notwithstanding the
fact that the previous sysadmin didn't back it up. But that's another
story. Now I'm here at my job, I've inherited the repo admin duties,
and I want to back it up reliably.
On Wed, Jun 1, 2016 at 11:55 AM, Michael Schwager
wrote:
> Thanks Matt. To your point,
>
> > my collection of backups probably does have some corrupt repo trees...
>
> that is really what I'm driving at. The RAID, offsite, number of backups
> (nightly in our case), and testing is all covered. In
Hello Divvela,
On Fri, May 27, 2016 at 9:52 PM, Divvela Chanukya <2chanu...@gmail.com> wrote:
> Hi,
>
> we are configured subversion(1.7.19) with webmethods(9.5) on windows 2012
> r2. when we try to move a service from one package to other package .
> getting the below error .
Subversion 1.7 is n
Hello Stefan,
On Sun, May 29, 2016 at 11:03 PM, Stefan wrote:
>
> I'm not 100% sure, but this might be related to issue #4364, which is fixed
> in SVN 1.8.8:
> lock of deleted pathes magically reappear when pathes are reused
>
> In this case upgrading to a later SVN version should resolve the iss
Hello Matt,
On Wed, Jun 1, 2016 at 6:45 PM, Matt Garman wrote:
>
> As you suggested, if you can make a fancier backup script that shuts
> down anyone's ability to make changes to the repo while the backup is
> taking place, that's even better.
There is `svnadmin freeze`[1] for this. And you can
Thanks Matt. To your point,
> my collection of backups probably does have some corrupt repo trees...
that is really what I'm driving at. The RAID, offsite, number of backups
(nightly in our case), and testing is all covered. In other words, I can
mitigate the effects of failure with all those tri
Hello Michael,
On Wed, Jun 1, 2016 at 5:58 PM, Michael Schwager wrote:
> Hello,
> We are very paranoid about our Subversion repo, notwithstanding the fact
> that the previous sysadmin didn't back it up. But that's another story. Now
> I'm here at my job, I've inherited the repo admin duties, and
I think there's two questions here: (1) what are general good backup
practices, and (2) how to backup svn repos specifically.
"If we lose it, we're all out of work." Hopefully your boss
recognizes this and has budgeted appropriately. In my experience
there is no perfect backup; the best you can
Hello,
We are very paranoid about our Subversion repo, notwithstanding the fact
that the previous sysadmin didn't back it up. But that's another story. Now
I'm here at my job, I've inherited the repo admin duties, and I want to
back it up reliably. If we lose it, we're all out of work.
My question
15 matches
Mail list logo
