Imported Debian patch 2.4.5-1

[debian/amanda] / docs / upgrade.txt

diff --git a/docs/upgrade.txt b/docs/upgrade.txt
new file mode 100644 (file)
index 0000000..81db04e
--- /dev/null
+++ b/docs/upgrade.txt
@@ -0,0 +1,68 @@
+
+        Chapter 28. Upgrade Issues
+Prev  Part VI. Historical files  Next
+
+-------------------------------------------------------------------------------
+
+Chapter 28. Upgrade Issues
+
+
+Stefan G. Weichinger
+
+XML-conversion
+AMANDA Core Team
+<sgw@amanda.org>
+
+Note
+
+Refer to http://www.amanda.org/docs/upgrade.html for the current version of
+this document.
+AMANDA 2.4.0 has introduced a major incompatibility in the AMANDA protocol.
+This means that pre-2.4.0 clients won't interoperate with a 2.4.0 server, nor
+will 2.4.0 clients interoperate with pre-2.4.0 servers. You have to upgrade
+them all at the same time.
+To ease the upgrade process AMANDA has, from release 2.4.0 on, a configure flag
+(--with-testing) that will cause AMANDA to use alternate service names (AMANDA-
+test) instead of the standard ones. This allows you to keep using your old
+version of AMANDA while you test the new one.
+Depending upon the version of AMANDA you are upgrading from, AMANDA may use a
+different database library to store the backup information, and the new AMANDA
+may not be able to read the old AMANDA database files. In this case, you will
+want to do something like the following:
+Before the upgrade (using the old version of amadmin):
+
+       # cd /var/AMANDA/CONFIG
+       # amadmin CONFIG export > zzz
+       # mkdir backup
+       # mv curinfo* backup
+       
+
+and after the upgrade (using the new version of amadmin):
+
+       # cd /var/AMANDA/CONFIG
+       # amadmin CONFIG import < zzz
+       
+
+and a month :-) after you are happy with the new version:
+
+       # cd /var/AMANDA/CONFIG
+       # rm -rf backup
+       
+
+After 2.4.0, the structure of the directory holding the index files was changed
+to have three levels instead of being flat. This greatly reduces the number of
+files in a given directory, which was a problem for some systems.
+The new layout is:
+[indexdir]/hostname/filesystem/YYYYMMDD_L.gz
+where hostname and filesystem are "sanitized" versions of the names from
+disklist, i.e. '/' characters are converted to '_' and so on. This new naming
+convention matches the one used for the text formatted database.
+A script is available to convert the flat directory structure to the new
+layout:
+http://www.amanda.org/2.4-conv/msg00428.html
+-------------------------------------------------------------------------------
+
+Prev                                   Up                            Next
+Chapter 27. Response to CPIO Security Home  Chapter 29. What once was new
+Notice Issue 11: 
+