バックアップ/afbackup
の編集
Top
/
バックアップ
/
afbackup
[
トップ
] [
編集
|
凍結
|
差分
|
添付
|
リロード
] [
新規
|
一覧
|
検索
|
最終更新
|
ヘルプ
]
Active
Rubyチートシート
成果物リスト
勉強会ログ
↑
アイデア
Webサービス案
Androidアプリ案
電子工作案
GreaseMonkey案
contribute
編集
↑
Recent
2023-11-12
自動車保険
2023-08-04
HDDリスト
2023-08-03
docker
2023-05-17
Rubyチートシート
2023-03-30
RAID5/トラブル20230324
2023-03-25
PC/misuzu
2023-03-24
PC
2023-03-23
PC/DESKTOP-7SL5J8R
2022-12-16
Linux
2022-11-09
Linux/ディスクイメージ取得
2021-05-23
CTF
2021-03-17
PC/misumi
2020-08-31
COMP
2020-03-28
PC/misumi/ubuntu
Windows 10
2018-06-04
Microsoft decode 2018 2日目
Microsoft decode 2018 1日目
2018-04-07
カメラ
2018-01-06
電力自由化
2017-12-21
CROSS×BEATS
B
I
U
D
H
[[]]
<br>
--
**FAQ ripped from /usr/share/doc/afbackup/FAQ.gz 34: How to make afbackup reuse/recycle tapes automatically ? There are two parameters in the client side configuration, that affect reusing tapes. One of them is NumIndexesToStore. A new index file is started with each full backup. For all existing indexes the backup data listed inside of them is protected from being overwritten on the server. This is achieved by telling the server, that all tapes, the data has been written to, are write protected. The parameter NumIndexesToStore tells the client side, how many indexes in addition to the current one that is needed in any case are kept. More i.e. older index files are removed and the related tapes freed. A common pitfall is, that the number configured here is one too high. If the number is e.g. 3, the current index file plus 3 older indexes are kept, not 3 in total. Note furthermore, that afbackup only removes an older index, when the next full backup has succeeded. DaysToStoreIndexes can be configured the number of days, how old index file contents may become. | |Amanda | afbackup | |Can backup file system whose size is bigger than a tape. |NO(2) | YES | |> Why not ? | | | | | | | |Can append to tape. |NO(4) | YES | |> Normal append is supported since ever. As of version | | | |> 3.2.6 full append mode is implemented, i.e. also, if | | | |> an administrator has requested to write to another | | | |> tape now, the current one will be appended to, if there | | | |> is no space left on any available tape. Since 3.2.7 | | | |> there is also a variable append mode making the server | | | |> append to any supplied tape having remaining space | | | |> and not being in read-only state | | | | | | | |Supports a tape verify option (just verifying the tape) |YES | NO | |> Don't see the use of this. | | | | | | | |Supports a data verify option (compare with fs). |NO(5) | YES | |> (very pedantic) | | | | | | | |Database backup support (by saving arbitrary dump | | | |command output) |NO | YES | |> No, Amanda requests it to be sent to a file, first. | | | |>> So e.g. for an online database backup a huge | | | |>> temporary disk space is required | | | | | | | |Per file preprocessing (for safety, if the whole stream | | | |is e.g. compressed and a single bit is wrong during restore | | | |all the rest is lost) |NO | YES | |> Amanda compresses the whole backup if requested. | | | |>> (AF's comment: crazy in my opinion) | | |
タイムスタンプを更新
テキスト整形のルールを表示する
Last-modified: 2014-12-24(水) 16:49:51