Projects:
Bacula Projects Roadmap
- 06 January 2005
+ 22 July 2005
The following major projects are scheduled for 1.37:
-#3 Migration (Move, Copy, Archive Jobs)
-#4 Embedded Python Scripting (implemented in Dir)
-#5 Events that call a Python program (Implemented in Dir)
-#6 Select one from among Multiple Storage Devices for Job
-#7 Single Job Writing to Multiple Storage Devices
Below, you will find more information on those projects as
well of other projects planned at a future time.
Item 1: Implement Base jobs.
-
+ Status: Voted by users not to be implemented in 1.37
+
What: A base job is sort of like a Full save except that you
will want the FileSet to contain only files that are
unlikely to change in the future (i.e. a snapshot of
pulled in where necessary.
Why: This is something none of the competition does, as far as
- we know (except BackupPC, which is a Perl program that
+ we know (except perhpas BackupPC, which is a Perl program that
saves to disk only). It is big win for the user, it
makes Bacula stand out as offering a unique
optimization that immediately saves time and money.
list and compare it for each file to be saved.
Item 2: Add Plug-ins to the FileSet Include statements.
+ Status: In progress in 1.37 using Python scripting.
What: Allow users to specify wild-card and/or regular
expressions to be matched in both the Include and
Item 3: Implement a Migration job type that will move the job
data from one device to another.
-Coding begun in 1.35:
+ Status: Partially coded in 1.37 -- much more to do.
What: The ability to copy, move, or archive data that is on a
device to another device is very important.
Highwater size (keep total size)
Lowwater mark
-
-Item 4: Embedded Python Scripting (precursor to 5).
-Some testing done:
-
- What: On a configuration parameter, embed the Python language in
- Bacula.
-
- Why: The embedded Python scripting can be called to implement
- Events such as "Volume Name needed", "End of Tape",
- "Tape at x% of rated capacity", "Job started",
- "Job Ended", "Job error", ...
-
- Notes: This needs Events.
-
-
-Item 5: Implement Events that call the scripting language.
-
- What: When a particular user defined Event occurs, call the
- embedded Python interpreter.
-
- Why: This will provide the ultimate in user customization for
- Bacula. Almost anything imaginable can be done if Events
- are called at the appropriate place.
-
- Notes: There is a certain amount of work to be done on how
- the user defines or "registers" events.
-
-
-Item 6: Multiple Storage Devices for a Single Job
-Modifications to SD in progress: 1.35
-
- What: Allow any Job to use more than one Storage device.
-
- Why: With two devices, for example, the second device could
- have the next backup tape pre-mounted reducing operator
- intervention in the middle of the night.
-
-
-Item 7: Backup a Single Job Simultaneously to Multiple Storage Devices
-Modifications to SD in progress: 1.35
-
- What: Make two copies of the backup data at the same time.
-
- Why: Large shops typically do this and then take one set of
- backups off-site. Some design work it needed in how to
- specify the type of backup (backup, archive, ...) for
- each Device.
-
-
-
-Item 8: Break the one-to-one Relationship between a Job and a
- Specific Storage Device (or Devices if #10 is implemented).
-
- What: Allow a Job to simply specify one or more MediaType, and
- the Storage daemon will select a device for it. In
- fact, the user should be able to specify one or more
- MediaType, Storage daemon, and/or device to be used.
-
- Why: To allow more flexibility in large shops that have multiple
- drives and/or multiple drives of different types.
-
-
Item 9: Implement data encryption (as opposed to communications
encryption)
-Assigned: to Meno Abels (both data and communications encryption).
-
+ Status: Landon Fuller has agreed to work on this.
+
What: Currently the data that is stored on the Volume is not
encrypted. For confidentiality, encryption of data at
- the File daemon level is essential. Note, communications
- encryption encrypts the data when leaving the File daemon,
- then decrypts the data on entry to the Storage daemon.
+ the File daemon level is essential.
Data encryption encrypts the data in the File daemon and
decrypts the data in the File daemon during a restore.
Why: Large sites require this.
- Notes: The only algorithm that is needed is AES.
- http://csrc.nist.gov/CryptoToolkit/aes/
-
+Items completed for release 1.38.0:
+#4 Embedded Python Scripting (implemented in all Daemons)
+#5 Events that call a Python program (Implemented in all
+ daemons, but more cleanup work to be done).
+#6 Select one from among Multiple Storage Devices for Job.
+ This is already implemented in 1.37.
+#7 Single Job Writing to Multiple Storage Devices. This is
+ currently implemented with a Clone feature.
+#- Full multiple drive Autochanger support (mostly implemented).
+#- We will have built in support for communications
+ encryption (TLS) done by Landon Fuller.
+# We will most likely have support for Unicode characters
+ (via UTF-8) on Win32 machines thanks to Thorsten Engle.
+Item 8: Break the one-to-one Relationship between a Job and a
+ Specific Storage Device (or Devices if #10 is implemented).
Completed items from last year's list:
Item 1: Multiple simultaneous Jobs. (done)