summaryrefslogtreecommitdiff
path: root/fml/doc/en/tutorial/operations/backup.sgml
blob: ad2b449f18c447f34ba2bd4ce57c97d982d35050 (plain)
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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
<!--
   $FML: backup.sgml,v 1.1 2005/07/23 01:57:38 fukachan Exp $
   $jaFML: backup.sgml,v 1.3 2004/10/06 09:07:41 fukachan Exp $
-->


<chapter id="operations.backup">
	<title>
	Back Up Of Configurations
	</title>


<para>
To preserve &fml8; configurations, back up the following two directories:
<screen>
/usr/local/etc/fml/
$ml_home_prefix	(e.g. /var/spool/ml/, domain specific)
</screen>
Attention:
These directories holds all articles, log files and others et.al.
</para>

<para>
It is better to back up MTA configurations, too. 
For example, /etc/postfix in the case of Postfix.
</para>

<para>
In summary, the following three (generally speaking 2 + number of
domains fml8 operatates) are targets.
<screen>
/etc/postfix/
/usr/local/etc/fml/
$ml_home_prefix	(e.g. /var/spool/ml/)
</screen>
</para>


<sect1 id="operations.backup.fml8.include">
	<title>
	Back Up &fml8; Configurations
	</title>

<para>
To back up &fml8; configurations, it is enough to back up the
following two directories. But it is too large since they contains
articles, log files and all contents.
<screen>
/usr/local/etc/fml/
$ml_home_prefix	(e.g. /var/spool/ml/, domain specific)
</screen>
</para>

<para>
The hard disk is cheap. So it is safe to preserve all contents as
could as possible.
</para>

<para>
If you preserve only configuratoins, it is enough to back up the
following files.
</para>


<sect2>
	<title>
	Configuration Files To Back Up
	</title>

<para>
It is useful to make a list of targets based on the file naming
convension.
</para>

<para>
In the case of &fml8;, a file with .cf extension is a configuration
file.
The format of .cf file is 
<screen> 
key = value
</screen> 
style. This style configuration files follow
<screen>
/usr/local/etc/fml/main.cf
/usr/local/etc/fml/site_default_config.cf
/EACH_ML_HOME_DIRECTORY/config.cf
</screen>
et.al.
</para>

<para>
Configuration files with other syntax are
<screen>
/usr/local/etc/fml/mime_component_filter
/usr/local/etc/fml/ml_home_prefix
</screen>
This type of files are space separeted.
</para>

<para>
/usr/local/etc/fml/ contains only configuration files.
So back up all under them.
</para>

</sect2>


<sect2>
	<title>
	Address List To Back Up
	</title>

<para>
Lists of mail addresses are 
<screen>
/ML_HOME_DIRECTORY/members*
/ML_HOME_DIRECTORY/recipients*
</screen>
Article delivery uses both recipients and members. For other roles,
&fml8; uses members-$role and recipients-$role. So, back up all
members* and recipients* files.
</para>

<para>
Remote administration by command mail (admin command mail) uses 
the following password files
<screen>
/ML_HOME_DIRECTORY/etc/passwd-$role
</screen>
. Back up /ML_HOME_DIRECTORY/etc/ too.
</para>

</sect2>

</sect1>


<sect1 id="operations.backup.fml8.exclude">
	<title>
	Back Up All Files Except For Some Large Directories.
	</title>

<para>
It is easy to back up all files except for the following large
directories. They contains large data or temporary files.
<screen>
spool	articles
tmp	temporary files
var	useful data
</screen>
</para>

<para>
If you use rsync, rsync --exclude is useful.
</para>

</sect1>