Changes between Version 43 and Version 44 of FeatureRequests
- Timestamp:
- 11/10/2009 20:13:07 (11 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FeatureRequests
v43 v44 170 170 On logging in, compare a hash of the key material with a record on the server, to give a better error when you use the wrong key file. 171 171 172 == Default Configuration File 172 == Default Configuration File == 173 173 174 174 In bbackupd.conf, put _all_ possible configuration values with good describing comment (e.g. with the unit of values (seconds, bytes, ...)) (I believe this is now done by bbackupd-config -- Chris) … … 214 214 215 215 Similarly, it'd be nice to be able to use the same long list of exclusions in multiple !BackupLocations using a variable of some sort (or maybe even reading from an external file, or, egads, maybe even downloading from a web service of some sort, like http://myserver.com/template.txt) (a variant of my 2006-12-11 Feature Request above). (bbackupd.conf doesn't need to become a programming language. Use m4/perl/python -- Chris) 216 217 == Redundant Servers == 216 218 217 219 In bbackupd.conf, it might help make for easy geographic redundancy by being able to enter 2 or more !StoreHostname records, with the client either backing up to both of them each cycle, or maybe even just alternating between them if that is acceptable to the user. (PeteJ 2007-05-16) … … 326 328 I don't like the "Subdirectory" directive because it should also be applicable to files or a list of files, but I couldn't think of another one. 327 329 328 This is unbelievably complex and unimplementable. Box Backup doesn't need to do this. We should have an interface to an external program that can tell us whether or not to back up a particular file, and then you can implement wh etever policy asyou like. (Chris)330 This is unbelievably complex and unimplementable. Box Backup doesn't need to do this. We should have an interface to an external program that can tell us whether or not to back up a particular file, and then you can implement whatever policy you like. (Chris) 329 331 330 332 == Configuration File/Installation Issues ==
