> From: John Stoffel [mailto:j...@stoffel.org]
>
> I think the root cause of your failure here is that you assume ONE
> full backup is all you need. Instead you should be keeping multiple
> full backups instead.
Oh - heheheh. At any given time, I have a full backup on the attached disk, and
I h
Another way to look at this issue would be that backup frequency and
retention should be orthogonal. When and how you run a backup shouldn't
change the fact that the existing data should be retained for however long
the original policy stated.
Skylar
On Wed, Sep 9, 2015 at 7:21 AM, John Stoffel
> "Edward" == Edward Ned Harvey (lopser) writes:
>> From: tech-boun...@lists.lopsa.org [mailto:tech-boun...@lists.lopsa.org]
>> On Behalf Of Edward Ned Harvey (lopser)
>>
>> Just before midnight, I destroyed the machine. And then I started doing the
>> restore. Guess what time the backup scr
> From: tech-boun...@lists.lopsa.org [mailto:tech-boun...@lists.lopsa.org]
> On Behalf Of Edward Ned Harvey (lopser)
>
> Just before midnight, I destroyed the machine. And then I started doing the
> restore. Guess what time the backup script runs? Midnight. Guess what its
> behavior is? It notices
Thought you'd all enjoy hearing about my pain. ;-)
I have a VM, which is regularly backed up via block level snapshot. It started
failing - would not boot, complained about filesystem not cleanly unmounted -
so I decided to restore it from backup.
Just before midnight, I destroyed the machine.
