]>
Commit | Line | Data |
---|---|---|
fbe89be6 | 1 | Summary: dar makes backup of a directory tree and files |
2 | Name: dar | |
3 | Version: 1.1.0 | |
4 | Release: 1 | |
5 | License: GPL | |
6 | Group: Applications | |
7 | Source0: http://dar.linux.free.fr/%{name}-%{version}.tar.gz | |
8 | URL: http://dar.linux.free.fr/ | |
9 | BuildRequires: glibc-static | |
10 | BuildRequires: zlib-static | |
11 | BuildRequires: libstdc++-static | |
12 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) | |
13 | ||
14 | %description | |
15 | ||
16 | dar is a shell command, that makes backup of a directory tree and | |
17 | files. | |
18 | ||
19 | FILTERS: dar is able to backup from total file system to a single | |
20 | file. Additionally a mechanism of filters permits, based on the | |
21 | filename, to exclude or include some files while backing up or | |
22 | restoring a directory tree. In the other side, a secondary filter | |
23 | mechanism permits to exclude some branches of a directory tree, or to | |
24 | only include some branches. | |
25 | ||
26 | DIFFERENTIAL BACKUP: When making a backup with dar, you have the | |
27 | possibility to make a full backup or a differential backup. A full | |
28 | backup, as expected makes backup of all files as specified on the | |
29 | command line (with or without filters). Instead, a differential | |
30 | backup, (over filter mechanism), saves only files that have changed | |
31 | since a given reference backup. Additionally, files that existed in | |
32 | the reference backup and which do no more exist at the time of the | |
33 | differential backup are recorded in the backup. At recovery time, | |
34 | (unless you deactivate it), restoring a differential backup will | |
35 | update changed files and new files, but also remove files that have | |
36 | been recorded as deleted. Note that the reference backup can be a full | |
37 | backup or another differential backup. This way you can make a first | |
38 | full backup, then many differential backup, each taking as reference | |
39 | the last backup made. | |
40 | ||
41 | SLICES: Dar stands for Disk ARchive. From the beginning it was | |
42 | designed to be able to split an archive over several removable media | |
43 | whatever their number is and whatever their size is. Thus dar is able | |
44 | to save over old floppy disk, CD-R, DVD-R, CD-RW, DVD-RW, Zip, Jazz, | |
45 | etc... Dar is not concerned by un/mounting a removable medium, instead | |
46 | it is independent of hardware. Given the size, it will split the | |
47 | archive in several files (called SLICES), eventually pausing before | |
48 | creating the next one, allowing this way, the user to un/mount a | |
49 | medium, burn the file on CD-R, send it by email (if your mail system | |
50 | does not allow huge file in emails, dar can help you here also). By | |
51 | default, (no size specified), dar will make one slice whatever its | |
52 | size is. Additionally, the size of the first slice can be specified | |
53 | separately, if for example you want first to fulfil a partially filled | |
54 | disk before starting using empty ones. Last, at restoration time, dar | |
55 | will just pause and prompt the user asking a slice only if it is | |
56 | missing. | |
57 | ||
58 | COMPRESSION: last, dar can use compression. By default no compression | |
59 | is used. Actually only gzip algorithm is implemented, but some room | |
60 | has been done for bzip2 and any other compression algorithm. Note | |
61 | that, compression is made before slices, which means that using | |
62 | compression with slices, will not make slices smaller, but will | |
63 | probably make less slices in the backup. | |
64 | ||
65 | DIRECT ACCESS: even using compression dar has not to read the whole | |
66 | backup to extract one file. This way if you just want to restore one | |
67 | file from a huge backup, the process will be much faster than using | |
68 | tar. Dar first reads the catalogue (i.e. the contents of the backup), | |
69 | then it goes directly to the location of the saved file(s) you want to | |
70 | restore and proceed to restoration. In particular using slices dar | |
71 | will ask only for the slice(s) containing the file(s) to restore. | |
72 | ||
73 | HARD LINK CONSIDERATION: hard links are now properly saved. They are | |
74 | properly restored if possible. If for example restoring across a | |
75 | mounted filesystem, hard linking will fail, but dar will then | |
76 | duplicate the inode and file content, issuing a warning. | |
77 | ||
78 | EXTENDED ATTRIBUTES: support for extended attributes have to be | |
79 | activated at compilation time (see INSTALL). Dar is able to save and | |
80 | restore EA, all or just those of a given namespace (system or user). | |
81 | If no EA have been saved and restoration occurs over a file that has | |
82 | EA, they will be preserved. But if they have been saved empty for a | |
83 | given file, any existing EA for that file will be removed at | |
84 | restoration time, unless -u and/or -U is given on command-line. | |
85 | ||
86 | ARCHIVE TESTING thanks to CRC (cyclic redundancy checks), dar is able | |
87 | to detect data corruption in the archive. Only the file where data | |
88 | corruption occurred will not be possible to restore, but dar will | |
89 | restore the other even when compression is used. | |
90 | ||
91 | USING PIPES dar is now able to produce an archive to its standard | |
92 | output or named pipe. it is also able to read an archive through a | |
93 | pair of pipes, to take a remote archive as reference, or even to | |
94 | restore data from a remote archive. This way it is now possible to | |
95 | store an archive remotely and in total security (if using encrypted | |
96 | means) | |
97 | ||
98 | ISOLATION the catalogue (i.e.: the contents of an archive), can be | |
99 | extracted (this operation is called isolation) to a small file, that | |
100 | can in turn be used as reference for differential archive. There is no | |
101 | more need to provide an archive to be able to create a differential | |
102 | backup over it, just its catalogue is necessary. | |
103 | ||
104 | RE-SHAPE SLICES OF AN EXISTING ARCHIVE the external program named | |
105 | "dar_xform" is able to change the size of slices of a given archive. | |
106 | The resulting archive is totally identical to archives directly | |
107 | created by dar. Source archive can be taken from a set of slice, from | |
108 | standard input or even a named pipe. | |
109 | ||
110 | %prep | |
111 | %setup -q | |
112 | ||
113 | %build | |
114 | ||
115 | %{__make} | |
116 | ||
117 | %install | |
118 | rm -rf $RPM_BUILD_ROOT | |
119 | install -d $RPM_BUILD_ROOT{/bin,%{_mandir}/man1} | |
120 | install dar $RPM_BUILD_ROOT/bin | |
121 | install dar_xform $RPM_BUILD_ROOT/bin | |
122 | install dar_slave $RPM_BUILD_ROOT/bin | |
123 | install *.1 $RPM_BUILD_ROOT%{_mandir}/man1 | |
124 | ||
125 | %clean | |
126 | rm -rf $RPM_BUILD_ROOT | |
127 | ||
128 | %files | |
129 | %defattr(644,root,root,755) | |
130 | %doc BUGS CHANGES NOTES README TODO TUTORIAL | |
131 | %attr(755,root,root) /bin/* | |
132 | %attr(644,root,root) %{_mandir}/* |