DIAP - Usage

Usage
usage: diap_setup.sh [-k accounts and keys] [-s setup dir and cron] [-u undo]

NB: There is a Development Mode which can be enabled in the config 
which will speed up testing by allowing the daily cycle to run hourly. 
Use small test files in this mode. 

REQUIREMENTS

Hardware 3 x :-

>800MHz CPU
>256MB RAM
LAN or WAN connection between each server, the 3 machines must be able to ping 
one another.

HDD Space - see README for size calculation

Software on each machine:-
Linux (Built and tested on Fedora core 6 x86)

root access for initial setup then runs in user-space

SSH server / client port visibility between each
crontabs
tcl
NTP - running or time set accurately on each node, for
the moment the same time zone.
iptables - ssh port 22 open
rsync

INSTALL

Script should be run from a different machine to the servers
i.e. your workstation.

Order of execution:-

Ensure you set the user variables as outlined in script config.sh

1st login to each machine manually with ssh to accept certificates
then:

1) diap_setup.sh -k
2) diap_setup.sh -s
3) Now change the diap password on machine A, B and C

If you want to undo the scripts (All files will be lost)

4) diap_setup.sh -u

With this option make sure you logout of any diap accounts first,
ALL files you used to test diap will be removed.

DATA ENTRY POINT:-

This machine contains directory ad00 and aFULL01 and is your machine A. 
Machine A is assumed to be your most robust and closest from a network 
perspective to your main backup facility. The files are assumed to be 
read/write by user id diap for the moment. Use aFull01 for your FULL copy 
and ad00 for all subsequent Differentials.

DATA RETRIEVAL:-

See README for diagram of data flow. Retrieval can be achieved
by manually using scp between the nodes and using rsync logs.