1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
From 56c9f9d11f6a3cff16a2ad0ba6e4f86b9ff9a839 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves <dom@earth.li>
Date: Wed, 27 Mar 2013 23:36:30 +0000
Subject: Customise backup docs for Debian
Forwarded: not-needed
Patch-Name: debianize_backup_docs.diff
---
docs/system_administration/database.pod | 43 ++++++++++++++++++-------
1 file changed, 31 insertions(+), 12 deletions(-)
diff --git a/docs/system_administration/database.pod b/docs/system_administration/database.pod
index 43fbf753..9c197028 100644
--- a/docs/system_administration/database.pod
+++ b/docs/system_administration/database.pod
@@ -25,6 +25,13 @@ become an issue. You don't want to discover problems with your backups while
tensely restoring from them in a critical data loss situation.
=head2 Database
+
+This documentation has been modified by the Debian maintainers to be more
+specific to file locations in Debian. It removes the upstream recommendation
+to back up the distributed code, as this should be reinstalled via the
+Debian packaging system. However, this means it is important not to
+modify files in /usr/share directly (a good general rule) as those changes
+will be lost in the event of having to restore.
You should backup the entire RT database, although for improved speed and space
you can ignore the I<data> in the C<sessions> table. Make sure you still get
@@ -157,6 +164,12 @@ can run C<analyze verbose>.
=back
+=head2 Package Lists
+
+This will help you decide which packages to reinstall.
+
+ dpkg --get-selections > rt-get-selections-`date +%Y%M%d`
+
=head2 Filesystem
Although this section is mostly about database backups, there are other
@@ -165,19 +178,22 @@ You will want to back up, at the very least, the following directories and files
=over 4
-=item /opt/rt4
+=item /var/lib/request-tracker4
+
+Miscellaneous data, including GPG data, if it exists.
-RT's source code, configuration, GPG data, and plugins. Your install location
-may be different, of course.
+=item /etc/request-tracker4
-You can omit F<var/mason_data> and F<var/session_data> if you'd like since
-those are temporary caches. Don't omit all of F<var/> however as it may
-contain important GPG data.
+RT configuration files.
+
+=item /usr/local/share/request-tracker4
+
+Local code customisations and plugins.
=item Webserver configuration
-Often F</etc/httpd> or F</etc/apache2>. This will depend on your OS, web
-server, and internal configuration standards.
+If you're using Apache, as per the Debian default, this is in
+F</etc/apache2>.
=item /etc/aliases
@@ -195,9 +211,12 @@ The location of these files is highly dependent on what software you're using.
=item Crontab containing RT's cronjobs
-This may be F</etc/crontab>, F</etc/cron.d/rt>, a user-specific crontab file
-(C<crontab -l $USER>), or some other file altogether. Even if you only have
-the default cronjobs in place, it's one less piece to forget during a restore.
+As installed by Debian, this is F</etc/cron.d/request-tracker4> but
+you may have used additional files.
+
+Even if you only have the default cronjobs in place, it's one less piece
+to forget during a restore.
+
If you have custom L<< C<rt-crontool> >> invocations, you don't want to have to
recreate those.
@@ -218,7 +237,7 @@ regarding backups.
Simply saving a tarball should be sufficient, with something like:
- tar czvpf rt-backup-`date +%Y%m%d`.tar.gz /opt/rt4 /etc/aliases /etc/httpd ...
+ tar czvpf rt-backup-`date +%Y%M%d`.tar.gz /var/lib/request-tracker4 /etc/aliases /etc/httpd ...
Be sure to include all the directories and files you enumerated above!
|
