update docs

docs/30_Configuration/20_Filetransfer.md → docs/30_Configuration/30_Filetransfer.md

 The file transfer describes how local directories will be backed up
 
-* choose backup tool
+* choose backup tool; incremental or full backup
 * where to write data (backup target)
-* incremental or full backup
-* how to delete backup data
+* set password for local encryption
+* more options
+* how to cleanup old backup data
 
 Details to the the given config entries you find in the description for
 [transfer.job](50_File_transfer.job.md).
@@ -82,3 +83,95 @@ When restoring data ... this is the path for restored files:
 
 `restore-path = /restore`
 
+### Duplicity settings ###
+
+When writing backup data duplicity creates the target file and a index.
+By default the index is written to ~/.cache/duplicity/ (and to the backup target).
+If your /root partition has a limited size and/ or you have a lot of files
+(i.e. on a file server) then you can put the index files somewhere else:
+
+`duplicity_cachedir = [full path]`
+
+Duplicity with rsync needed an additional ssh-backend *pexpect* on Debian.
+It can be set with enabling:
+
+`# duplicity_ssh-backend = pexpect`
+
+On the backup target you can define the size of the chunks to write.
+This would allow to write the backup data to an additional medium with
+limited size (i.e. CD or DVD).
+
+Set a size in MB
+
+`duplicity_volsize = 350`
+
+### Restic settings ###
+
+When writing backup data restic creates a local index.
+By default the index is written to ~/.cache/restic/.
+If your /root partition has a limited size and/ or you have a lot of files
+(i.e. on a file server) then you can put the index files somewhere else:
+
+`restic_cachedir = [full path]`
+
+The default verbose of IML backup for restic is 2. During file transfer
+this shows unchanged/ new/ deleted files. Change it to a less value
+to generate less log data.
+
+`restic_verbose = 2`
+
+A file transfer can be tagged. Each restic backup gets a defined tag
+
+`restic_tag = imlbackup`
+
+For restore you can copy files to the restore location. With restic
+you can mount the backup volume into the local filesystem using fuse.
+Then you can browse in the snapshots of the backup data and copy
+the files and dirs with linux commands.
+
+The mountpoint for the backup storage is a full path (it will be created
+when selcting to mount in the restore).
+
+`restic_mountpoint = /mnt/restore`
+
+## Cleanup options ##
+
+### Duplicity ###
+
+Duplicity can set a value how long to keep backup data on the backup storage.
+It will keep all files of incremental and full backup to be able to restore 
+data of the given min. availability.
+
+Example if you defined a monthly full backup and keep backups for 6 monthes ... 
+then it keeps all files up to 6 monthes plus all older files up to the next
+full backup. You will find backup files up to 7 monthes.
+
+```text
+  1 month    (for monthly full backup)
++ 6 monthes  (min. availability for restore)
+---------------------------------------------
+  7 monthes  
+```
+
+The value duplicity_keep is a number and a letter for the time format.
+
+s, m, h, D, W, M, or Y (indicating seconds, minutes, hours, days, weeks, months, or years respectively)
+
+`duplicity_keep = 6M`
+
+### Restic ###
+
+Restic works like a repository and uses deduplication. The first run of a file backup
+is a full backup and all following runs make an incremental backup.
+
+You have the possibility to keep all younger backups and have the possibility to delete
+older backups but to keep N weekly, monthly and yearly snapshots.
+
+```text
+# prune 
+restic_keep-hourly = 100
+restic_keep-daily = 90
+restic_keep-weekly = 12
+restic_keep-monthly = 12
+restic_keep-yearly = 10
+```