Backup
Contents
Journal
200601
Project files are stored in a version repository, a backup and an archive.
+---------+
| archive |
+----+----+
^
|
+------------+ +----------+
| back-up | => | archived |
+------+-+---+ | back-up |
^ ^ +----------+
| |
+---------------+ +------+-----+
| version | ===================> | back-upped |
| repository | | repository |
+-------+-------+ +------------+
^ |
| |
+---------+ +-------+-------+ |
| project | | versioned | |
| files | | files | |
| | +---------------+ |
| | +---------------+ +---------------+ |
| | | non-versioned | | generated | |
| | | (ignored) | | files | ^
| | | files | +---------------+ |
| | | | +---------------+ +--------+---+
| | | | | non-generated | => | back-upped |
| | | | | files | | files |
+---------+ +---------------+ +---------------+ +------------+
non-versioned files
Files which are non-versioned, are actually ignored by the versioning program. But I do want to have a back-up of these non-versioned files, unless they can be generated by the versioned files. Subversion holds a list of the non-versioned files:
svn status --no-ignore | grep "^I"
but Subversion makes no distinction between generated and non-generated files. Is is useful to check which ignored files have changed after a certain date?
20060205
This backup thing is becoming way to complicated and unreliable. I want to be able to rely on full backups, and since I'm going to keep a machine running 24/7 I should be able to make a full backup each night.
Trying Disk ARchive.
No more complicated semantic differences between 'archive' and 'back-up'; they're synonyms.
20060220
I'm creating a back-up of data only. My theory is I don't need a back-up of the OS, since it can be re-installed easily from scratch. This is true if only if I am persistent in copying modified OS configuration files to my data area...
20060520
Want to encrypt backup, but dar says:
Aborting program. The requested operation needs a feature that has been disabled at compilation time: blowfish strong encryption support
