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
|
Source: afbackup
Build-Depends: debhelper, c-shell, zlib1g-dev
Section: utils
Priority: optional
Maintainer: Torsten Werner <twerner@debian.org>
Standards-Version: 3.5.6
Package: afbackup
Architecture: any
Depends: tcsh | c-shell, netbase (>= 3.04-1), debianutils (>= 1.6), ${shlibs:Depends}
Suggests: afbackup-client, wish
Conflicts: afbackup-i, afbackup-client-i
Description: Client-Server Backup System (Server side)
This is a client-server backup system offering several workstations a
centralized backup to a special backup server. Backing up only one
computer is easily possible, too. Any streaming device can be used
for writing the data to it, usually this will be a tape
device. Writing backups is normally done sequentially: The next
writing to tape goes to the end of the previous write no matter where
you have restored from in the meantime.
.
Features:
- Authentication of the client is performed before it can take over control
- Access restriction for the streamer device -> security
- Client-side per-file compression -> reliability
- Data stream is written to tape in pieces -> fast finding of files
- Tape position logging for each file
- Tape capacity is fully used
- Full / incremental backups
- Raw partitions can be backed up
- Client and Server buffering for maximal throughput is done
.
Note: Tk is required if you want to use the graphical configuration
tool instead of the text configuration tool.
Package: afbackup-client
Architecture: any
Replaces: afbackup-client-i
Depends: tcsh | c-shell, netbase (>= 3.04-1), debianutils (>= 1.6), ${shlibs:Depends}
Suggests: wish, sharutils
Conflicts: afbackup-client-i, afbackup-i
Description: Client-Server Backup System (Client side)
This is a client-server backup system offering several workstations a
centralized backup to a special backup server. Backing up only one
computer is easily possible, too. Any streaming device can be used
for writing the data to it, usually this will be a tape
device. Writing backups is normally done sequentially: The next
writing to tape goes to the end of the previous write no matter where
you have restored from in the meantime. THIS IS ONLY THE CLIENT, YOU
NEED TO HAVE A SERVER RUNNING ON EITHER THIS OR ANOTHER HOST.
.
Features:
- Authentication of the client is performed before it can take over control
- Access restriction for the streamer device -> security
- Client-side per-file compression -> reliability
- Data stream is written to tape in pieces -> fast finding of files
- Tape position logging for each file
- Tape capacity is fully used
- Full / incremental backups
- Raw partitions can be backed up
- Client and Server buffering for maximal throughput is done
.
Note: Tk is required if you want to use the graphical configuration
tool instead of the text configuration tool.
|
