On 11/21/2012 1:34 PM, Bear wrote:
> H-Man <Sp...@bites.fs> wrote in news:k8j9dm$pc2$
1...@dont-email.me:
>
>> On 21 Nov 2012 16:12:17 GMT, Bear wrote:
>>
>>> Incremental/differential backups leave the possibility of corruption.
>>
>> That's one of the big differences in incremental and differential
>> backups. With incremental the possibility is that I will have to
>> restore to sometime before the last backup. Could be Monday, could be
>> later than that. With differential backups, if I have one backup go
>> bad, if it's not the last one, then I'm good. The down side is the
>> diff backups take progressively longer. For me a couple of days is no
>> biggie, so I'm okay with it.
>>
>> That said, yes they do leave the possibility of corruption. On the
>> Friday Backup, I rename the weeks and last Fridays backup and create a
>> new set, just in that eventuality. One never knows. I always have at
>> least 1 week and 1 day to fall back on.
>>
>> On Linux I do the same, however, files are backed up using a backup
>> program, the system get's imaged less frequently as it tends to get
>> changed far less often, and is far less vulnerable.
>>
>
> Such plans are good. Plans that preclude the possibility without any
> possibility for data loss due to corruption or malware infection are the
> best.
>
> Is there any possibility with your plan that your system could become
> infected and you save that infection to image?
>
> What my plan does is preclude that possibility as I never image a system
> that has been used. I always load a clean image, make the changes and
> reimage. My data files and portable programs are always seperated from
> the process and managed without imaging. If something happens to any of
> those, I always have a clean set to fall back on. There is no
> possibility for corruption.
>
But, what if a plane crashed into your house, while your out, and its
completely destroyed. How would you recover?
--
Steal a little and go to jail, steal a lot and become King.
http://twovoyagers.com/improve-usenet.org/