| •
ARCHIVE YOUR WORKING FILES
•
WHY ARCHIVE YOUR FILES?
•
WHERE IS YOUR IT DEPARTMENT?
•
WHAT TO ARCHIVE?
•
F.A.Q.
•
RECOVERY
•
SECURITY IS IMPORTANT
•
EASY CLEAN UP
•
YOUR WORK STILL GOES ON
•
USER MANUAL |
WHERE
IS THE ARCHIVE BUILT?
You specify the location of a directory on your computer when you
install the software. This location will be the root of
a tree that mimics your computer’s file system. The default
location is C:\Archive, or any place you have ample room. it
can be on an external device such as a USB drive, etc.
HOW MUCH ROOM WILL THE ARCHIVE TAKE
UP?
The amount of space you use proportional to the number and size of
the files that you archive. Katchall Archive needs a complete
copy of a recent file to rebuild the older compressed versions. By
keeping this copy it can restore any version even if your copy has
been destroyed.. Therefore, your cost on disk per file is (a)
the size of a copy, plus (b) the incremental differences
between the archived versions.
WHY
IS FILE SIZE LIMITED?
Although the differencing engine that compares one version against
another is efficient, it does use significant memory. For this
reason, the size of files that it will try to archive is limited to
20MB.
The size of any particular file’s archive is limited to .5GB.
For a normal sort of file of a few mega bytes in size, there will
be room for thousands of versions. For non-compressible encrypted
type files of the same size, there will be room for a few hundred
versions of a file. The limitation on the size an archive can grow
to is imposed to protect your computer.
SHOULD ALL MY USER FILES BE ARCHIVED?
Most files that you edit should be archived. However, there
are some considerations to be aware of. Katchall Archive’s
data differencing and compression is based on the assumption that
when a small modification to a file is made, then except for the part
of the file that actually changed, the resulting file will mostly
be the same. The truer this assumption is for a given file and
file type, the more compact the resulting archive.
*Encrypted
Files
Encrypted data files are an example of where this assumption is 100%
not valid. Any decent encryption scheme should completely alter
the encrypted contents of a file from one version to another.
You should not be able see any commonality between 2 versions of an
encrypted file if even 1 bit is changed. Encrypted files should be
marked for exclusion (so as not to be archived), or for “truncate
as needed” (if it is desired to have older version available).
*JPEGs
Although JPEGs are not encrypted, they are compressed, and the effect
of slight modifications to the file do cause wide spread modifications
to the binary in the files. By default, they are marked for Truncation
quietly. |