On Wed, 4 Jun 2014 17:51:49 +0100
Andreas Stieger wrote:
> Preaching backup during an uncovered recovery scenario may be fun and
> make you feel smirk, but it is rarely useful for the particular problem.
As backups are only useful when taken before the disaster a backup will
not help in this cas
Preaching backup during an uncovered recovery scenario may be fun and make you
feel smirk, but it is rarely useful for the particular problem. Your advice
jumps from generic (image and scan fs) to speculative (data recovery firms).
Would it not be better to address the specific problem?
db/curr
On Wed, Jun 04, 2014 at 09:07:30AM +0200, Henrik Carlqvist wrote:
> I was once told that the 3 most important tasks for a sysadm is:
>
> 1) backup
> 2) backup
> 3) backup
>
> It really does seem as if you need a sysadm who takes his job seriously.
Wasn't step 2 supposed to be 'test restore'? :)
On Tue, 3 Jun 2014 20:06:09 +
Curtis Stiebler wrote:
> we had a power flicker
Power flicker, physical hard disk crashes, fires, shit happens every now
and then...
> We do not have a backup of the repository structure
I was once told that the 3 most important tasks for a sysadm is:
1) backu
To all, we had a power flicker which in turn caused out Server that we use for
our Visual VSN recovery to reboot. Once it rebooted, we are unable to get to
our repository either through our Visual Studio Environment or through the
VisualSVN server tool. In the server tool, when we go the project
