info about moving trackers

git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@1474 57a73879-2fb5-44c3-a270-3262357dd7e2

diff --git a/doc/maintenance.txt b/doc/maintenance.txt
index dba485f51f774a40144b9ccdf79b0f9df482ca3a..98bed63022d0bb5c86e8ba58ecaafd251ac93d06 100644 (file)
--- a/doc/maintenance.txt
+++ b/doc/maintenance.txt
@@ -2,7 +2,7 @@
 Maintaining Roundup Trackers
 ============================
 
-:Version: $Revision: 1.1 $
+:Version: $Revision: 1.2 $
 
 .. contents::
    :depth: 1
@@ -59,6 +59,30 @@ Migrating Backends
 9. restart web and email frontends
 
 
+Moving a Tracker
+================
+
+If you're moving the tracker to a similar machine, you should:
+
+1. install Roundup on the new machine and test that it works there,
+2. stop the existing tracker web and email frontends (preventing changes),
+3. copy the tracker home directory over to the new machine, and
+4. start the tracker web and email frontends on the new machine.
+
+Most of the backends are actually portable across platforms (ie. from Unix to
+Windows to Mac). If this isn't the case (ie. the tracker doesn't work when
+moved using the above steps) then you'll need to:
+
+1. install Roundup on the new machine and test that it works there,
+2. stop the existing tracker web and email frontends (preventing changes),
+3. use the roundup-admin tool "export" command to export the contents of
+   the existing tracker,
+4. copy the export to the new machine,
+5. use the roundup-admin "import" command to import the tracker on the new
+   machine, and
+6. start the tracker web and email frontends on the new machine.
+
+
 -------------------
 
 Back to `Table of Contents`_