-
-
-==========================================
-
-Beta version 1.39.20:
-- Writing DVDs should work much better thanks to Richard Mortimer.
-- Many cleanups/enhancements for Win32 systems.
-- Correct improperly formated list command output reported by Dan.
-- Eric fixed RunScripts, which I (Kern) had broken in the last beta.
-- Correct Client migration SQL as pointed out by Marc.
-
-
-Warning for version 1.39.18 and greater:
-- If you have an old pre 1.39.18 database, you must update it using
- the update_bacula_tables script. Please backup your database before
- updating just in case.
-- You *should* be able to use 1.38.x FDs with version 1.39.18 Director
- and SD providing you do not use any of the new features (runscript,
- data encryption). It seems to work here, but we do not guarantee it.
-- Your Director and SD must be simultaneously upgraded.
-- The restore command no longer uses the MediaType as the primary method
- of finding a suitable Storage device. Normally it will select the last
- device used to write a Volume. If no storage device is defined, it
- will use the old algorithm which selects the first Storage resource
- with the correct MediaType.
-- The MD5/SHA1 hash codes kept in the database are now kept in a binary
- format compatible with the rest of the world. If you are running verify
- jobs, you *must* do an InitCatalog or all files will show an MD5
- difference. Also, authentication uses the new algorithm by
- default, but *should* accept connections from older components (FD) using
- the old non-compatible algorithm. This has been tested, but more
- more testing is still needed.
-- The --mandir ./configure option now points to the top level man
- directory. The man files will be installed under mandir/man8 and
- mandir/man1 as appropriate.
-- The "Accept Any Volume" directive has been removed. It was never
- implemented. Bacula will always accept any valid tape that is in
- the drive for appending.
-
-
-A Lot of New features for 1.39.18: