1DAR_MANAGER(1) General Commands Manual DAR_MANAGER(1)
2
6 dar_manager - disk archive manager
7
9 dar_manager [-v] [-j] -C [<path>/]<database>
10 dar_manager [-v] [-j] -B [<path>/]<database> -A [<path>/]<basename> [
12 [<path>/]<archive_basename>]
13 dar_manager [-v] [-j] -B [<path>/]<database> -l
15 dar_manager [-v] [-j] -B [<path>/]<database> -D <number>[-<number>]
17 dar_manager [-v] [-j] -B [<path>/]<database> -b <number> <new_ar‐
19 chive_basename>
20 dar_manager [-v] [-j] -B [<path>/]<database> -p <number> <path>
22 dar_manager [-v] [-j] -B [<path>/]<database> -o [list of options to
24 pass to dar]
25 dar_manager [-v] [-j] -B [<path>/]<database> -d [<path to dar command>]
27 dar_manager [-v] [-j] -B [<path>/]<database> [-w <date>] [-e <extra
29 options to dar>] -r [list of files to restore]
30 dar_manager [-v] [-j] -B [<path>/]<database> -u <number>
32 dar_manager [-v] [-j] -B [<path>/]<database> -f file
34 dar_manager [-v] [-j] -B [<path>/]<database> -s
36 dar_manager [-v] [-j] -B [<path>/]<database> -m <number> <number>
38 dar_manager [-v] [-j] -B [<path>/]<database> -i
40 dar_manager -h
42 dar_manager -V
44
47 dar_manager is part of the Disk Archive suite. Its purpose is to sim‐
48 plify the restoration of a set of few files present in many backup,
49 full or differential. This is achieved by gathering the catalogue of
50 each archive (this has to be done once). At any time you just have to
51 give the relative path to the files you want to restore, dar_manager
52 will call dar with the proper options and restore the last version of
53 each file (or the last version before given date). Note that dar_man‐
54 ager is to be used when you have remove some files by accident some
55 time ago and wish to recover them. It thus not adapted to restore the
56 state a directory tree had at a given time, in particular when some
57 files have to be removed. For that you must use dar directly with the
58 corresponding archive to the date for which you wish to restore the
59 state.
60 you can restore any file by hand without dar_manager , but if you make
62 a lot of differential backup, you may spend many time to find the ar‐
63 chive that contains the last version of your file, as dar will not save
64 it if it has not changed since previous backup. dar_manager simplify
65 the process by looking in its internal database, built from archive
66 "catalogues".
67
69 -C, --create [<path>/]<database>
70 creates an empty database that will collect infor‐
71 mations about several archives. The <database> is a
72 filename that is required for -B option. To destroy
73 a <database> just remove the file.
74 -B, --base [<path>/]<database>
76 specify the database to read or modify. The <data‐
77 base> file must exist, and have a database struc‐
78 ture (see -C option).
79 -i, --interactive use a keyboard interactive text menu to do opera‐
81 tions on the given database. So you may avoid read‐
82 ing the other options described in this manual
83 page, if you wish, and just use the interactive
84 option. You will however always have to create an
85 empty database (-C option) and restore files manu‐
86 ally (-r option).
87 -A, --add [<path>/]<basename> [ [<path>/]<archive_basename>]
89 add an archive to the database. An isolated cata‐
90 logue can also be used only if it has been produced
91 by dar version 1.2.0 or above. Why ? Because, an
92 isolated catalogue produced by older version will
93 always tell that no files are saved in the archive
94 of reference, in that case the solution is to pro‐
95 vide the archive itself as argument. An optional
96 second argument is the basename of the archive if
97 it is different from the first argument (need for
98 extraction of files). For example you could have an
99 isolated catalogue in first argument and the base‐
100 name of the original archive (where is stored the
101 data) as second argument. By default, dar_manager
102 will look for an archive of reference in the com‐
103 mand line used to create each archive, but in some
104 cases, it may be necessary to specify the archive
105 name (for example if you've changed its name).
106 -l, --list displays the informations about the archives com‐
108 piled in the database. In particular, a number is
109 given to each archive, which is required to some
110 other option to design a particular archive within
111 the database. Nothing avoids you to feed the data‐
112 base with several archive of the same basename !
113 You will just have to guess which one is asked
114 under this name. :-)
115 -D, --delete <number>[-<number>]
117 removes an archive (or a range of archive) from the
118 database. The number of the archive (or the min and
119 max number or the archive range) is correspond to
120 those given by the -l option. Note that all archive
121 number greater than the one(s) to be delete will be
122 decremented to keep continuous numbering of the ar‐
123 chive inside the database.
124 -b, --base <number> <new_archive_basename>
126 this option allows you to rename the archive base‐
127 name (used when restoring files from it)
128 -p, --path <number> <path>
130 this option allows you to change the location of a
131 given archive (used when restoring files from it)
132 -o, --options [list of option to pass to dar]
134 Specify the option to use when calling dar. Each
135 call erases the previous setting. Possible dar
136 options are all the available ones except "-x" and
137 simple arguments (the [list of path]) which will be
138 added by dar_manager itself.
139 -d, --dar [<path>] Set the path to dar. If no argument is given, dar
141 is expected to be located in the PATH
142 -r, --restore [list of files to restore]
144 dar_manager will restore all (an only) the given
145 files, asking for the proper archive only. Last
146 version of each file over several archive is based
147 on the modification time of the inode, thus if you
148 have a more recent backup that contains an old ver‐
149 sion of a given file, a older archive could be used
150 to restore the file, if its last modification time
151 (mtime) is more recent. Note that files listed
152 after -r option, must never have an absolute path.
153 They will be restored under the directory specified
154 with -R option of dar (thus using -o option), or by
155 default, in subdirectories of the current direc‐
156 tory.
157 -w, --when <date> alters the -r option behavior: still restores the
159 files in the most recent version available but only
160 before the given date (versions of more recent
161 dates are ignored). The <date> must respect the
162 following format [ [
163 [year/]month/]day-]hour:minute[:second]. For exam‐
164 ple "22:10" for 10 PM past 10 or the current day,
165 "7-22:10" for 10 PM past 10 the 7th of the current
166 month, "3/07-22:10" for the 7th of march at 22:10
167 of the current year, "2002/03/31-14:00:00" the date
168 of the first dar's release ;-). The given date must
169 be in the past, of course, and is compared to the
170 "last modification" date of the saved files and not
171 to the date at which archives have been done. Thus
172 if a file has been changed long ago but saved in a
173 recent (full) archive, it will be elected for
174 restoration even for dates older than the creation
175 of the archive. In the other way, a file saved long
176 time ago with a mtime that was set to a date in the
177 future will not be elected for restoration when
178 giving the date at which was done the archive.
179 -e, --extra <options>
181 pass some more options to dar. While the -o options
182 takes all that follows on the command line as argu‐
183 ment to pass to dar and write theses in the data‐
184 base, the -e option does not alter the database and
185 has only one argument. In other words, if you need
186 to pass several options to dar through the use of
187 the -e option, you need to use quotes (simple
188 quotes ' or double quotes ") to enclose theses
189 options. Example:
190 dar_manager -B database.dmd -e "-w -v -p -b -r -H 1" -r
192 some/files
193 -u, --used <number> list the files that the given archive owns as last
195 version available. Thus when no file is listed, the
196 given archive is no more useful in database, and
197 can be removed safely (-D option). If <number> is
198 zero, all available file are listed.
199 -f, --file <file> displays in which archive the given file is saved,
201 and what are the modification date (mtime) and
202 change date (ctime).
203 -s, --stats show the number of most recent files by archive.
205 This helps to determine which archive can be safely
206 removed from the database.
207 -m, --move <number> <number>
209 changes the order of archives in the database. The
210 first number is the number of the archive to move,
211 while the second is the place where it must be
212 shifted.
213 Archie order is important only in the case a file
215 to be restored has EA that has been saved in an ar‐
216 chive and data saved in another archive. This takes
217 place when making a differential backup for file
218 that have no change in data but changes in EA. In
219 that case, the database must be fed (-A option)
220 with archive in the order they have been created.
221 If dar_manager detects such a disorder, it issues a
222 warning is giving the name of the file that could
223 not be restored properly (only EA have not been
224 restored with the last version). Note that, if you
225 don't use EA the order of archives in the database
226 has no importance.
227 -Q Do not display any message on stderr when not
229 launched from a terminal (for example when launched
230 from an at job or crontab). Remains that any ques‐
231 tion to the user will be assumed a 'no' answer,
232 which most of the time will abort the program.
233 -j, --jog when virtual memory is exhausted, as user to make
235 room before trying to continue. By default, when
236 memory is exhausted dar aborts.
237 -v, --verbose displays additional information about what it is
239 doing.
240 -h, --help display help usage
242 -V, --version display software version
244
247 dar_manager exits with the following code:
248 0 Operation successful.
250 1 see dar manual page for signification
252 2 see dar manual page for signification
254 3 see dar manual page for signification
256 7 see dar manual page for signification
258 8 see dar manual page for signification
260 11 and above
262 dar
263 called from dar_manager has exited with non zero status.
264 Substract 10 to this exit code to get dar's exit code.
265
268 dar_manager acts like dar (see dar man page for list of signals), upon
269 certain signal reception dar aborts cleanly
270
273 dar(1), dar_xform(1), dar_slave(1), dar_cp(1)
274
277 at most 65534 archives can be compiled in a given database, which
278 should be enough for most users. Dar_manager does not support encrypted
279 archives for now and archive cannot neither be encrypted. See the FAQ
280 for a workaround.
281
284 none actually
285
288 http://dar.linux.free.fr/
289 Denis Corbin
290 France
291 Europe
2923rd Berkeley Distribution OCT 30th, 2006 DAR_MANAGER(1)