On 03/13/2017 09:12 AM, Dan Ritter wrote:
On Sat, Mar 11, 2017 at 09:10:54AM -0600, Richard Owlett wrote:I have one partition that might be called a "production" environment, i.e. fairly stable and has the most valuable content. A second partition hosts my experiments - I've a project to create an optimal install. The third is the target of those experimental installs whose content doesn't rate explicit backups. The scripts for creating those installs being on the second partition. I've vague ideas of what backup pattern(s) I might follow. I'm looking for reading materials that might trigger "I hadn't thought of that" moments.A quick overview: Nobody wants backups. Everybody wants restores. The questions are: - what sort of disaster are you trying to recover from
Primarily operator error. This machine started out as a vehicle to experiment with Linux. And latter as a test-bed for how *I* think a personal system should be configured. My old Windows box served for internet connectivity and playing Solitaire.
I've got a setup configured *my way* so the Windows box has been demoted to Solitaire - not having experimented with wine.
- how often do you expect each to happen
More frequently than I'll admit.
- how much time are you willing to take recovering
Time is not much of an issue as I'm retired and this is a hobby environment. But recently Pastor has asked be to administer the church's new website (hosted elsewhere) so there will be some files which it would be annoying to have to recreate.
- how much are you willing to spend
Minimal. I'm intending to use a physically local hard drive as the primary backup medium. For church related files, likely will be flash drives stored at the church.
From what I've been reading the local backup of my machine will likely be a weekly incremental backup. The backup for church will be file copies as it will also serve as a record for Pastor's use.