Following is an update to my question of Jun 1, where I ask the following
question:
On Wed, Jun 1, 2016 at 9:58 AM, Michael Schwager wrote:
> ...
> My question is: How do I back (subversion repos) up reliably, and verify
> (them) so that I can deliver a 100% recovery guarantee t
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/s
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 ter
Wed, Jun 1, 2016 at 10:51 AM, Pavel Lyalyakin <
pavel.lyalya...@visualsvn.com> wrote:
> 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 t
gt; with svndump.
>
> Lastly, you probably owe it to your company to regularly test your
> backups to ensure that they are indeed viable. Just like buildings
> have fire drills, so should sysadmins have DR drills.
>
> Hope these suggestions are useful!
>
>
>
>
> On We
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
