[[!toc levels=3]]
# Introduction
-The purpose of this document is to demonstarate to the reader how to restore data on a hammer
+The purpose of this document is to demonstrate to the reader how to restore data on a hammer
filesystem(files/directories). This will also cover how to adjust history retention.
# Getting history records of a file
If period hasn't passed since the previous cleanup run nothing is done.
-By the default configuration file will create a daily snapshot, basicly what it means is it will make a snapshot every 24hr for 60 days, you can find your snapshots in /var/hammer/<pfs>/snapshots.
-It will aslo do a daily pruning for example if you want it to run everyday for 30 minutes the configuration will look like this:
+By the default configuration file a daily snapshot will be created daily and kept for 60 days, you can find your snapshots in /var/hammer/<pfs>/snapshots.
+For the other actions (prune, rebalance, dedup, reblock, recopy), the second parameter is the maximum time the action may take.
- prune 1d 30m
+For instance
+ dedup 1d 30m
+means, that once per day, your hammer file systems will be deduplicated for up to 30 minutes.
-rebalancing, deduping(This feature is introduced in 2.9 DragonFly kernel version wich at the moment is being developed),
-reblocking - reblocking will reorder all elements and thus defragment the file system and free space for reuse. And do a montly recopy run.
+Reblocking will reorder all elements and thus defragment the file system and free space for reuse. And do a montly recopy run.
+
+You can read the full details HAMMER(8).