The robbery problem occurs to myself too, but somehow the server has to run. One can encrypt the HDD but as long as the server is on ...
And one will die one dead HDD encryption or automation. It's not much sense to have the HDD encrypted and the password on the comp/server.

So the second server is a mirror, and the DVD RAM ;)

:)

>Lutz,
>
>congrats, seems ike you have covered yourself very well. From cursory reading the only points to think about would be encrypting the things sent to trustworthy person (for things like robbery of physical machine) and I can resonate with the wish for not going to the bank vault each day, which is the other weakness you already identified.
>
>rgds
>
>thomas
>
>>what I do is a bunch of stuff on several levels.
>>
>>To the first I have my project gited and do atomic backups like described above. This means I use my Bin2Text tool you can found on VFPX to commit text representaions into git.
>>
>>I can backward inside this on a day to day base (or until a single, thread is done [eine Einzelaufgabe?]) and on "major" commits
>>
>>Those is remote to my local server gitosis, In case reachable via VPN, This is mostly used for the major steps and if I need to synch between comps. This is pretty forward, since there are no coworkers.
>>
>>Then I do (from the days of yore) a kind of hourly mirror that simply mirrors my plain project folder to a server folder, w/o git folder. This is done by a third party tool called SecondCopy. This runs on shutdown as well. (SecondCopy is an old friend. There might be a more elegant way with git, but to automate this I would like to understand PowerShell, what is a total fail with me. I'm more into bash)
>>
>>Nightly the server will run a bash script to gather my important data using tar incremental options and squeeeze this to a zip, not the tarball zipped, file by file zip.
>>Important are for example the git repos and the mirrored sources, mail server.
>>
>>Later the night the server copies this to a private, remote server via VPN located at a thrustworty persons place.
>>
>>The server then waits for an DVD-RAM, and copies the 7z to this. (there is enough space for mulitple copies each.)
>>The script does a 4level incremental thing (yearly, monthly, weekly and daily set) so that I need year, month, week and day to have a full restore in worst case.
>>
>>The DVD-RAM cirles to third place on a weekly base. (Daily would be better, but ...)
>>
>>Only manual is the change of the DVD-RAM and the git push operations.
>>
>>Partition cloning only on major computer related stuff, this is to space intensive.