File: Features.html

package info (click to toggle)
dar 2.6.13-2
  • links: PTS
  • area: main
  • in suites: bullseye
  • size: 10,364 kB
  • sloc: cpp: 77,385; sh: 6,192; ansic: 776; makefile: 435; python: 242; csh: 95; perl: 43; sed: 16
file content (1335 lines) | stat: -rw-r--r-- 56,042 bytes parent folder | download | duplicates (2)
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
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>DAR's FEATURES</title></head><body style="background-color: rgb(221, 221, 221); color: rgb(0, 0, 170);" alink="#ff0000" link="#0000ff" vlink="#000055">
<center>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; width: 161px;"><a href="index.html"><img style="border: 0px solid ; width: 160px; height: 120px;" alt="Dar Documentation" src="dar_s_doc.jpg"></a><br>
      </td>
      <td style="vertical-align: top;">
      <h1 style="text-align: center;"><br>
      </h1>
      <h1 style="text-align: center;">DAR's FEATURES</h1>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<div style="text-align: justify;">
<hr style="width: 100%; height: 2px;"><br>
<br>
<table style="width: 90%; margin-right: auto; margin-left: auto; text-align: left;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top;" align="justify">Here follow the
main
features of dar/libdar tool. For each feature an overview is presented with
some pointers you are welcome to follow for a more detailed
information.</td>
    </tr>
  </tbody>
</table>
<br>
</div>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">HARD
LINK CONSIDERATION </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>
hard links are properly saved in any case and properly restored if possible. For example, if restoring across
a mounted file system, hard linking will fail, but dar will then
duplicate the inode and file contents, issuing a warning. Hard link
support includes the following inode types: plain files, char devices,
block devices, symlinks (Yes, you can hard link symbolic links! Thanks to Wesley Leggette for the info ;-) )<br>
 </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">SPARSE FILES<br>
 </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">--sparse-file-min-size, -ah
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>By default Dar takes care of sparse files, even if the underlying filesystem does
not support sparse files(!). When a long sequence of zeroed bytes is
met in a file during backup, those are not stored into the archive but
the number of zeroed bytes is stored instead (structure known as a "hole"). When comes the time to
restore that file, dar restores the normal data but when a hole is met
in the archive dar directly skips at the position of the data following
that hole. If the underlying filesystem supports sparse files,
this will (re)create a hole in the restored file, making a sparse file.
Sparse files can report to be several hundred gigabytes large while they
need only a few bytes of disk space, being able to properly save and restore them
avoids wasting disk space at restoration time and in archives.<br>
 </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">EXTENDED
ATTRIBUTES (EA)<br>
      </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><span style="font-weight: bold;">MacOS
X FILE FORKS / ACL</span><br>
      </td>
      <td style="vertical-align: top;">keywords: -u -U -am -ae --alter=list-ea<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top;">
      <div style="text-align: justify;"><span style="font-style: italic;"></span> Dar is able to
save and restore EA, all or just those matching a given pattern.
      </div>
      <br>
      <div style="text-align: justify;">File Forks (MacOS X) are implemented over
EA as well as Linux's ACL, they are thus transparently saved, tested,
compared and restored by <span style="font-style: italic;">dar</span>.
Note that ACL under MacOS seem to not rely on EA, thus while they are
marginally used they are ignored by <span style="font-style: italic;">dar</span>.<br>
      </div>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
<tbody><tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">FILESYSTEM SPECIFIC ATTRIBUTES (FSA)<br>
      </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><span style="font-weight: bold;">MacOSX/FreeBSD Birthdate, Linux FS attributes</span><br>
      </td>
      <td style="vertical-align: top;">keyword: --fsa-family<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top;">
      <div style="text-align: justify;"><span style="font-style: italic;"></span>
Since release 2.5.0 dar is able to take care of filesystem specific
attributes. Those are grouped by family strongly linked to the
filesystem they have been read from, but perpendicularly each FSA is
designated also by a function. This way it is possible to translate FSA
from a filesystem into another filesystem when there is a equivalency
in role. </div>
      <br>
      <div style="text-align: justify;">currently two families are present:<br>
      <ul><li><span style="font-weight: bold;">HFS+</span> family contains only one function : the <span style="font-weight: bold;">birthtime</span>.
In addition to ctime, mtime and atime, dar can backup, compare and
restore all four dates of a given inode (well, ctime is not possible to
restore).<br>
        </li><li><span style="font-weight: bold;">extX </span>family
contains 12 functions (append_only, compressed, no_dump, immutable,
journaling, secure_deletion, no_tail_merging, undeletable,
noatime_update, synchronous_directory, synchronous_update,
top_of_dir_hierarchy) found on ext2/3/4 and some other Linux
filesystems. Dar can thus save and restore all of those for each file
depending on the capabilities or permissions dar has at restoration
time.<br>
        </li></ul>
</div></td></tr></tbody>
</table>
<br>
<br>
<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-weight: bold; width: 33%;">DIRTY FILES<br>
</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: --dirty-behavior , --retry-on-change<br>
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;">At
backup time, dar checks that each saved file had not changed at the
time it was read. If a file has changed in that situation, dar retries
saving it up to three times (by default) and if it is still changing, is
flagged as "dirty" in the archive, and handled differently from other
files at restoration time. The dirty file handling is either to warn
the user before restoring, to ignore and avoid restoring them, or to ignore
the dirty flag and restore them normally.<br>
      <br>
Note that dar precision when readng/writing inode dates (atime, ctime, mtime, birthtime) is the <span style="font-weight: bold;">microsecond</span>. Thus a file is seen as having changed even if a very small modification occurres in it very frequently.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%;"><span style="font-weight: bold;">FILTERS</span><br>
      </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> /&nbsp;<a href="usage_notes.html#filtering">command line usage notes</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -I -X -P -g -[ -] -am --exclude-by-ea<br>
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;"><span style="font-style: italic;">dar</span>&nbsp;
is able to backup from a total file system to a single file, thanks to
its filter mechanism. This one is dual headed: The first head let one
decide which part of a directory tree to consider for the operation
(backup, restoration, etc.) while the second head defines which type of
file to consider (filter only based on filename, like for example the
extension of the file). <br>
      <br>
For backup operation, files and directories can also be filtered out if
they have been set with a given user defined EA.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">NODUMP
FLAG </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: --nodump</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>Many filesystems, like ext2/3/4 filesystems provide for each inodes a set of flags, among which is the "<span style="font-weight: bold;">nodump</span>" flag. You can instruct dar to avoid saving files that have this flag set, as does the so-called
      <span style="font-style: italic;">dump</span> backup program.  <br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">ONE
FILESYSTEM </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -M</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;">By default <span style="font-style: italic;"></span>dar
does not stop at filesystems boundaries unless the filtering mechanism
described above exclude such directory that matches another mounted
filesystem. But you can also ask dar to avoid changing of filesystem
without the burden of finding and listing the directories to be
excluded from the backup: dar will manage alone to only save files of
the current filesystem.<br>
 </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-weight: bold; width: 33%;">CACHE DIRECTORY TAGGING STANDARD<br>
</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: --cache-directory-tagging<br>
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;">Many software use cache directories (<a href="http://www.mozilla.org/">mozilla web browser</a> for example), directories where is stored temporaneous data that is not interesting to backup. The <a href="http://www.brynosaurus.com/cachedir/">Cache Directory Tagging Standard</a>
provides a standard way for software applications to identify this type
of data, which let dar (like some other backup softwares) able to take into account and avoid saving them.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">DIFFERENTIAL
BACKUP </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a>/<a href="Tutorial.html">TUTORIAL</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -A</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;">When making a backup
with dar, you have the possibility to make a <span style="font-weight: bold;">full backup</span> or a
      <span style="font-weight: bold;">differential backup</span>. A full backup, as expected, makes backup of all
files as specified on the command line (with or without filters).
Instead, a differential backup, (over filter mechanism), saves
only files that have changed since a given reference backup.
Additionally, files that existed in the reference backup and which do
no more exist at the time of the differential backup are recorded in
the backup as "been removed". At recovery time, (unless you deactivate it), restoring a
differential backup will update changed files and new files, but also
remove files that have been recorded as "been removed". Note that the
reference backup can be a full backup or another differential backup (this second method is usually designed as <span style="font-weight: bold;">incremental backup</span>).
This way you can make a first full backup, then many incremental
backups, each taking as reference the last backup made, for example. </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-weight: bold; width: 33%;">DECREMENTAL BACKUP</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> / <a href="usage_notes.html#Decremental_Backup">Decremental backup</a> </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -+ -ad<br>
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;">As
opposed to <span style="font-weight: bold;">incremental backups</span>, where the older one is a full backup
and each subsequent backup contains only the changes from the previous
backup, <span style="font-weight: bold;">decremental backup</span> let the full backup be the more recent while
the older ones only contain changes compared to the just more recent one. This
has the advantage of providing a single archive to use to restore a whole
system in its latest known state, while reducing the overall amount
of data to retain older versions of files (same amount required as with
differential backup). It has also the advantage to not have to keep
several set of backup as you just need to delete the oldest backup when
you need storage space. However it has the default to require at each
new cycle the creation of a full backup, then the transformation of
the previous full backup into a so-called decremental backup. Yes, everything has
a cost!<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-weight: bold; width: 33%;">DELTA BINARY<br>
</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: --delta sig, --include-delta-sig, --exclude-delta-sig, --delta-sig-min-size, --delta no-patch<br>
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;">Since
release 2.6.0, for incremental and decremental backups, instead of
saving an entire whole file when it has changed, dar/libdar provides
the ability to save only the part that has changed in it. This feature
called binary delta relies on librsync library. It is not activated by
default considering the non null probability of collision between two
different versions of a file. This is also the choice of the dar user
community.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-weight: bold; width: 33%;">PREVENTING ROOTKITS AND OTHER MALWARES<br>
</td>
      <td style="vertical-align: top;"><a href="usage_notes.html#Decremental_Backup">references: </a><a href="man/index.html">man dar</a> </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -asecu
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;">At backup time when a<span style="font-weight: bold;"> differential, incremental or decremental backup</span> is
done, dar compares the status of inode on the filesystem to the
status they had at the time of the last backup. If the ctime of a file
has changed while no other inode field changed dar issues a warning
considering that file as suspicious. This does not mean that your
system has been compromised but you are strongly advised to check
whether this concerned file has been recently updated (Some package
manager may lead to that situation) or has its Extended Attributes
changed since last backup was made. In normal situation this type of
warning does not show often (false positive are rare but possible).
However in case your system has been infected by a virus or compromised
by a rootkit, dar will signal the problem if the intruder tried to hid
its forfait.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">DIRECTORY
TREE SNAPSHOT </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -A +<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;">Dar can make a
snapshot of a directory tree and files recording the inode status of
files. This may be used to detect changes in filesystem, by "diffing" the
resulting archive with the filesystem at a later time. The resulting
archive can also be used as reference to save file that have changed
since the snapshot has been done. A snapshot archive is very small
compared to the corresponding full backup but it cannot be used to
restore any data. </td>
    </tr>
  </tbody>
</table>

<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">SLICES
      </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man
dar</a>/<a href="Tutorial.html">TUTORIAL</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -s -S -p -aSI -abinary<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;">Dar
stands for Disk
ARchive. From the beginning it was designed to be able to split an
archive over several removable media whatever their number is and
whatever their size is. To restore from such a splitted archive, dar
will directly fetch the requested data in the correct slice(s). Thus
dar is able to save and restore using old floppy disk,
CD-R, DVD-R, CD-RW, DVD-RW, Zip, Jazz, etc... However, Dar will not
un/mount removable media because it is independent of hardware.
Given the size, it will split the archive in several files (called
SLICES), eventually pausing before creating the next one, allowing this
way the user to un/mount a medium, burn the file on CD-R, send it by
email (if your mail system does not allow huge file in emails, dar can
help you here also.. but OK, this is bad doing so :-)). By default, (no
size specified), dar will make one
slice whatever its size is. Additionally, the size of the first slice
can be specified separately, if for example you want first to fulfill a
partially filled disk before starting using empty ones. Last, at
restoration time, dar will just pause and prompt the user asking a
slice only if it is missing, so you can choose to have more than one
slice per medium without penalty from dar. Note that all these
operation can be
automatized using the "user command between slices" feature (presented
below), that let dar do all you want it to do once a slice is created
or before reading a slice.<br>
 </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">COMPRESSION
      </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> <br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -z<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;">dar</span>
can use compression. By default
no compression is used. Actually gzip, bzip2, lzo, xz/lzma algorithms
are available, and there is still room available for any other
compression
algorithm. Note that, compression is made before slicing, which means
that using compression together with slices, will not make slices
smaller, but
will probably make less slices in the backup. </td>
    </tr>
  </tbody>
</table>
<br>
<br style="font-weight: bold;">

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">SELECTIVE
COMPRESSION </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a>/<a href="samples/index.html">samples</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -Y -Z -m -am<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>dar can be given a special
filter that determines which files will be compressed or not. This way
you can speed up the backup operation by not trying to compress *.mp3,
*.mpg, *.zip, *.gz and other already compressed files, for example. Moreover another
mechanism allow you to say that files under a given size (whatever their
name is) will not be compressed. </td>
    </tr>
  </tbody>
</table>

<br>
<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">STRONG
ENCRYPTION </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -K -J -# -* blowfish, twofish, aes256, serpent256, camellia256<br>
</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>Dar can use blowfish, twofish, aes256, serpent256 and camellia256 algorithms to encrypt the
whole archive. Two "elastic buffers" are inserted and encrypted with
the
rest of the data, one at the beginning and one at the end of the
archive to
prevent a clear text attack or codebook attack. </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">PUBLIC KEY ENCRYPTION<br>
 </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -K, --key-length<br>
</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>Encryption
based on GPG public key is available. A given archive can be encrypted
for a recipient (or several recipients without visible overhead) using
its public key. Only the recipient(s) will be able to read such
encrypted archive.<br>
</td>
    </tr>
  </tbody>
</table>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">PRIVATE KEY SIGNATURE<br>
 </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: --sign<br>
</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>When
using encryption with public key it is possible in addition to sign an
archive with your own private key(s). Your recipients can then be sure
the archive has been generated by you, dar will check the signature
validity against the corresponding public key(s) each time the archive
is used (restoration, testing, etc.) and a
warning is issued if signature does not match or key is missing to
verify
the signature. You can also have the list of signatories of the archive
while listing the archive content.<br>
</td>
    </tr>
  </tbody>
</table>



<br>

<br>


<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">


  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">SLICE HASHING<br>
 </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">--hash, md5, sha1, sha512<br>
</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>When
creating an archive dar can compute an md5, sha1 or sha512 hash before the
archive is written to disk and produce a small file compatible with
md5sum, sha1sum or sha512sum that let verify that the medium has not
corrupted the archive slices.<br>
</td>
    </tr>
  </tbody>
</table>


<br>
<br>


<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">


  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">DATA
PROTECTION </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a>/<a href="usage_notes.html#Parchive"><span style="text-decoration: underline;">Parchive integration</span></a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -al<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>Dar is able to detect corruption in any part of a dar archive, but it cannot fix it.<br>
      <br>
Dar relies on the <a href="usage_notes.html#Parchive">Parchive</a>
program for data
protection against media errors. Thanks to dar's ability to run user
command or script and thanks to the ad hoc provided scripts, dar can use Parchive
as simply as adding a word (par2) on command-line. Depending on the
context (archive creation, archive testing, ...), dar will by this mean
create parity data for each slice, verify and if necessary repair the
archive slices.<br>
      <br>Without
Parchive, dar can workaround a corruption by not restoring the
concerned file. For some more vital part of the archive, like the
"catalog" which is the table of contents, dar has the ability to use an
isolated catalog as backup of the internal catalog of an archive. It
can also make use of tape marks that are used inside the archive for
sequential reading as a way to overcome catalog corruption. The other
vital information is the slice layout which is
replicated in
each slice and let dar overcome data corruption of that part too. As
a last resort, Dar also
proposes a "<span style="font-weight: bold;">lax</span>" <span style="font-weight: bold;">mode</span> in
which the user is asked questions (like the compression algorithm used,
...) to help dar recover very corrupted archives and in which, many
sanity checks are turned into warnings instead of aborting the
operation. However this does not
replace using Parchive. This "lax" mode has to be considered as the
last resort
option.<br>
      </td>
    </tr>
  </tbody>
</table>


<br>



<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">TRUNCATED ARCHIVE REPARATION<br>
</td>
      <td style="vertical-align: top;">reference: <a href="man/index.html">man dar</a>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keyword: -y<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>Since
version 2.6.0 an truncated archive (due to lack of disk space, power
outage, or any other reason) can be repaired. A truncated archive lacks
a table of content which is located at the end of the archive, without
it you cannot know what file is saved and where to fetch its data from,
unless you use the sequential reading mode which is slow as it implies
reading the whole archive even for restoring just one file. To allow
sequential reading of an archive, which is suitable for tape media,
some metadata is by default inserted all along the archive. This
metadata is globally the same information that should contain the
missing table fo content, but spread by pieces all along the archive.
Reparing an archive consists of gathering this inlined metadata and
adding it at the end of the repaired archive to allow direct access
mode (default mode) which is fast and efficient. <br>
      </td>
    </tr>
  </tbody>
</table>

<br>
<br>


<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">DIRECT
ACCESS </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span> even using compression and/or encryption <span style="font-style: italic;">dar</span> has not
to read the whole backup to extract one file. This way if you just want
to restore one file from a huge backup, the process will be much faster
than using <span style="font-style: italic;">tar.</span> Dar first reads the catalogue (i.e. the contents of the
backup), then it goes directly to the location of the saved file(s) you
want to restore and then proceeds to restoration. In particular using slices,
dar will ask only for the slice(s) containing the file(s) to restore.<br>
      <br>
Since version 2.6.0 dar can also read an archive from a remote host by
mean of FTP or SFTP. Here too dar can leverage its direct access
ability to only download the necessary stuff in order to restore some
files from a large archive, or list the archive content or even compare
a set of file with live filesystem.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">SEQUENTIAL ACCESS <br>
</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;">(suitable for tapes)<br>
      </td>
      <td style="vertical-align: top;">--sequential-read, -at<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>The
direct access feature seen above is well adapted to random access media
like disks, but not for tapes. Since release 2.4.0, dar provides a
sequential mode in which dar sequentially read and write archives. It
has the advantage to be efficient with tape but suffers from the same
drawback as tar archive: it is slow to restore a single file from a
huge archive. The second advantage is to be able to repair a truncated
archive (lack of disk space, power outage, ...) as described above.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">


  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">MULTI-VOLUME TAPES<br>
</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar_split</a>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: --sequential-read
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>The independant <span style="font-weight: bold;">dar_split </span>program
provides a mean to output dar but also tar archives to several tapes.
If takes care of splitting the archive when writing to tapes and gather
pieces of archive from several tapes for dar/tar to work as if it was a
single pieced archive.<br>
      </td>
    </tr>
  </tbody>
</table>

<br>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">ARCHIVE
TESTING </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a>/<a href="Tutorial.html">TUTORIAL</a>/
      <a href="Good_Backup_Practice.html">Good
Backup Practice</a><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -t<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;">thanks
to CRC
(cyclic redundancy checks), dar is able to detect data corruption in an
archive. Only the file where data corruption occurred will not be
possible to restore, but dar will restore the others even when
compression or encryption (or both) is used.</td>
    </tr>
  </tbody>
</table>
<br>
<br>
<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">ISOLATION
      </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> <br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -C -A -@<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span> the <span style="font-style: italic;">catalogue</span> (i.e.: the contents of an
archive), can be copied (this operation is called <span style="font-style: italic;">isolation</span>)
to a small file, that
can in turn be used as reference for differential archive. There is
then no need to provide an archive to be able to create a differential
backup based on it, just its <span style="font-style: italic;">catalogue</span>
is can be used instead. Such an isolated <span style="font-style: italic;">catalogue</span>
can also be used to rescue the archive it has been isolated from in the case the archive's internal <span style="font-style: italic;">catalogue</span> has been corrupted<span style="font-style: italic;"></span>. Such isolated catalogue can be created at the same time as the archive (operation called <span style="font-style: italic;">on-fly isolation</span>) or as a separate operation (called <span style="font-style: italic;">isolation</span>).<br>
      </td>
    </tr>
  </tbody>
</table>

<br>

<br>
<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">FLAT
RESTORATION </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -f</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>It is possible to restore any
file without restoring the directories and subdirectories it was in at
the time of the backup. If this option is activated, all files will be
restored in the (-R) root directory whatever their real position is recorded inside the archive.<br>
 </td>
    </tr>
  </tbody>
</table>

<br>
<br>

<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">USER
COMMAND BETWEEN SLICES </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar dar_slave
dar_xform</a>/<a href="usage_notes.html#command_from_dar">command line usage notes</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -E -F -~<br>
</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span> several hooks are provided for dar
to call a given command once a slice has been written or before reading
a slice. Several macros allow the user command or script to know the
requested slice number, path and archive basename. </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">USER
COMMAND BEFORE AND AFTER SAVING A DIRECTORY OR A FILE<br>
 </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a>/<a href="usage_notes.html#command_from_dar">command line usage notes</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -&lt; -&gt; -=<br>
</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;">It
is possible to define a set of file that will have a command executed
before dar start saving them and once dar has completed saving them.
This is especially intended for saving live database backup. Before
entering a directory dar will call the specified user command, then it
will proceed to the backup of that directory. Once the whole directory
has been saved, dar will call again the same user command (with
slightly different arguments) and then continue the backup
process. Such user command may have for action to stop the database and
to reactivate it afterward for example.<br>
</td>
    </tr>
  </tbody>
</table>

<br>

<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">CONFIGURATION
FILE </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar,</a> <a href="usage_notes.html#user_targets">conditional syntax and user targets</a><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -B<br>
</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>dar can read parameter from
file. This is a way to extends the command-line limited length
input. A configuration file can ask dar to read (or to include) other
configuration files. A simple but efficient mechanism forbids a file to
include itself directly or not, and there is no limitation in the
degree of recursion for the inclusion of configuration files. <br>
      <br>
Two special configuration files $HOME/.darrc and /etc/darrc are read if
they exist. They share the same syntax as any configuration file which
is the syntax used on the command-line, eventually completed by
newlines and
comments. <br>
      <br>
Any configuration file can also receive conditional statements, which
describe which options are to be used in different conditions.
Conditions are: "extract", "listing", "test", "diff", "create",
"isolate", "merge", "reference", "auxiliary", "all", "default" (which may be useful in case
or recursive inclusion of files) ... more about their meaning and use cases in dar man page.<br>
 </td>
    </tr>
  </tbody>
</table>
<br style="font-weight: bold;">
<br>

<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">REMOTE
OPERATIONS </td>
      <td style="vertical-align: top;">references: <a href="usage_notes.html#dar_remote">command line usage notes</a>, <a href="man/index.html">man dar/dar_slave/dar_xform</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top; font-weight: bold;"> <br>
</td>
      <td style="vertical-align: top;">keywords: -i -o - -afile-auth<br>
</td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>dar is able to read and write an archive to a remote server in three different ways:<br>
      <br>
1 - dar
is able to produce an
archive to its standard output or to a named pipe and is able to read
an archive from its standard input or from a named pipe<br>
<br>2 - if the previous approach is fine to write down an archive over
the network (through an ssh session for example), reading an archive
from a remote sever that way (using a single pipe) requires dar to read
the
whole archive which may be inefficient to just restore a
single file. For that reason, dar is also able to read
an archive through a <span style="text-decoration: underline;">pair of pipes</span> (or named pipes) using <span style="font-weight: bold;">dar_slave </span>at the other side of the
pipes. From the pair of pipes, one pipe let dar asking to
dar_slave which portion of the archive it has to send through the other pipe.
This makes a remote restoration much more efficient and still allows these bidirectional exchanges
to be encrypted over the network, simply running dar_slave through an ssh session.<br>
      <br>
3 - last, since release 2.6.0 dar can make use FTP or SFTP protocols to
read or write an archive from or to a remote server. This method does
not rely on anonymous or named pipes, is as efficient as option 2 for
reading a remote archive and is compatible with slicing and slice
hashing. however this option is restricted to these two network
protocols: FTP (low CPU usage but insecure) SFTP (secure)<br>
 </td>
    </tr>
  </tbody>
</table>

<br>

<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">DAR
MANAGER </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man
dar_manager</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span> The advantage of differential
backup is that it takes much less space to store and time to complete
than always making full backup. But, in the other hand, it may lead you having a
lot of them due to the reduces space requirements. Then if you want to restore a particular file, you may
spend time to figure out in which backup is located the most recent version.
To solved this, <span style="font-weight: bold;">dar_manager</span> gathers contents information of all your backups. At restoration
time, it will call dar for you to restore the asked file(s) from the
proper backup.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">RE-SHAPE
SLICES OF AN EXISTING ARCHIVE </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar_xform</a></td>
    </tr>
    <tr>
      <td style="vertical-align: top; font-weight: bold;"> <br>
</td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;">the
provided program
named "<span style="font-weight: bold;">dar_xform</span>" is able to change the size of slices of a given
archive. The resulting archive is totally identical to archives
directly created by dar. Source archive can be taken from a set of
slice, from standard input or even a named pipe. Note that dar_xform
can work on encrypted and/or compressed data without having to
decompress or even decrypt it.<br>
 </td>
    </tr>
  </tbody>
</table>

<br>

<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%; font-weight: bold;">ARCHIVE
MERGING </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -+ -ak -A -@<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>From version 2.3.0, dar supports the merging of two
existing archives into a single one. This merging operation is assorted by
the same filtering mechanism used for archive creation. This let the
user define which file will be part of the resulting archive.<br>
      <br>
By extension, archive merging can also take as single source archive
as input. This may sound a bit strange at first, but this let you make
a subset of a given archive without having to extract any file to disk.
In particular, if your filesystem does not support Extended Attributes
(EA), thanks to this feature you can still cleanup an archive from
files you do not want to keep anymore without loosing any EA or
performing any change to standard file attributes (like modification
dates for example) of files that will stay in the resulting archive.<br>
      <br>
Last, this merging feature give you also the opportunity to change the
compression level or algorithm used as well as the encryption algorithm
and passphrase. Of course, from a pair of source archive you can do all
these sub features at the same time: filtering out files you do not
want in the resulting archive, use a different compression level and
algorithm or encryption password and algorithm than the source
archive(s), you may also have a different archive slicing or no slicing
at all (well <span style="font-style: italic;">dar_xform</span> is more efficient for this feature only, see above "<span style="font-style: italic;">RE-SHAPE
SLICES OF AN EXISTING ARCHIVE</span>" for details).<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: left; width: 33%;"><span style="font-weight: bold;">ARCHIVE SUBSETTING</span><br>
      </td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> <br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -+ -ak<br>
      </td>
    </tr>
    <tr>
      <td colspan="2" rowspan="1" style="vertical-align: top; text-align: justify;"><span style="font-style: italic;"></span>As seen above under the "archive merging" feature description, it is possible to define a
subset of files from an archive and put them into a new archive without
having to really extract these files to disk. To speed up the process, it is also possible to avoid
uncompressing/recompressing files that are kept in the resulting archive or change
their compression, as well change the encryption scheme used. Last, you
may manipulate this way files and their EA while you don't have EA
support available on your system.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<br>
<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-weight: bold; width: 33%;">DRY-RUN EXECUTION<br>
</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: -e<br>
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;">You
can run any feature without effectively performing the action. Dar will
report any problem but will not create, remove or modify any file.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<br>
<br>
<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-weight: bold; width: 33%;">ARCHIVE USER COMMENTS<br>
</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: --user-comment, -l -v, -l -q<br>
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;">The
archive header can encompass a message from the user. This message is
never ciphered nor compressed and always available to any one listing
the archive summary (-l and -q options). Several macro are available to
add more confort using this option, like the current date, uid and gid
used for archive creation, hostname, and command-line used for the
archive creation.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<br>
<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; font-weight: bold; width: 33%;">PADDED ZEROS TO SLICE NUMBER<br>
</td>
      <td style="vertical-align: top;">references: <a href="man/index.html">man dar</a> </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">keywords: --min-digits<br>
      </td>
    </tr>
    <tr align="justify">
      <td colspan="2" rowspan="1" style="vertical-align: top;">Dar
slice are numbered by integers starting by 1. Which makes filename of
the following form: archive.1.dar, archive.2.dar, ..., archive.10.dar,
etc. However, the lexicographical order used by many directory listing
tools, is not adapted to show the slices in order. For that reason, dar
let the user define how much zeros to add in the slice numbers to have
usual file browsers listing slices as expected. For example, with 3 as
minimum digit, the slice name would become: archive.001.dar,
archive.002.dar, ... archive.010.dar.<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
</center>
</body></html>