"Fossies" - the Fresh Open Source Software Archive

Member "dirvish-1.2.1/INSTALL" (19 Feb 2005, 3426 Bytes) of package /linux/privat/old/dirvish-1.2.1.tgz:

    1 	INSTALLATION and GETTING STARTED
    2 
    3 #KHL 2005-02-18  removed "exclude core" error
    4 
    5 
    6 PREREQUISITES
    7 
    8 	rsync version 2.5.6 or higher.
    9 	rsync version 2.6.0 or higher may be needed if backing up windows.
   10 
   11 	perl5 and these perl modules (if you aren't familiar with
   12 	perl see CPAN(3pm)).
   13 		POSIX
   14 		Getopt::Long
   15 		Time::ParseDate
   16 		Time::Period by Patric Ryan
   17 	
   18 	Lots of empty disk space.  I recommend using volume management
   19 	(see lvm(8)).
   20 
   21 	Ssh configured so root on the backup server can use ssh
   22 	non-interactively to the backup clients.  This does not
   23 	necessarily mean it has to be able to be root on those clients.
   24 
   25 INSTALL
   26 
   27 	Execute the install script "sh install.sh" from inside the
   28 	unpack/download directory.  The script will ask where to
   29 	install the various pieces.  Be sure you have write
   30 	permissions for the installation directories.
   31 
   32 
   33 CONFIGURATION
   34 
   35 	Dirvish will store the backup images in "vault"s.  Plan on one
   36 	vault per backup set.
   37 
   38 	Create one or more directories as "bank"s in which to place
   39 	the vaults.  You can create a large filesystem for each bank
   40 	but it is usually better to create a filesystem for each
   41 	vault.
   42 
   43 	Inside the banks create one mount-point directory (vault) for
   44 	each backup set (ex: home).  Start by making each filesystem
   45 	about 1.5 times the size of the filesystem or directory tree
   46 	it will be used to back up.  Mount 'em up.  The FAQ has
   47 	additional details about how these filesystems should be
   48 	built.
   49 	
   50 	create the file /etc/dirvish/master.conf on your backup server.
   51 	It might look something like this:
   52 		bank:
   53 			/e/backup1
   54 			/e/backup2
   55 		exclude:
   56 			lost+found/
   57 			*~
   58 			.nfs*
   59 		Runall:
   60 			app	22:00
   61 			data	22:00
   62 			home	22:00
   63 			site	22:00
   64 		expire-default: +15 days
   65 		expire-rule:
   66 		#       MIN HR    DOM MON       DOW  STRFTIME_FMT
   67 			*   *     *   *         1    +3 months
   68 			*   *     1-7 *         1    +1 year
   69 			*   *     1-7 1,4,7,10  1
   70 			*   10-20 *   *         *    +4 days
   71 
   72 
   73 	In each vault create a dirvish subdirectory.  In the dirvish
   74 	subdirectory of each vault create config files.  To keep it
   75 	simple here we will assume will only have one branch per vault
   76 	and use the default configfile name; so create
   77 	$BANK/$VAULT/dirvish/default.conf files.
   78 
   79 	Here is an example from my home vault:
   80 		client: leto
   81 		tree: /e/home /home
   82 		branch-default: daily
   83 		exclude:
   84 		        /**/.*/**/*cache/
   85 			/**/.*/*cache/
   86 			/**/.*/**/*Cache/
   87 			.kde/share/thumbnails/
   88 
   89 	Now that you are configured create an initial image by running
   90 	dirvish on the backup server like so:
   91 
   92 		root# dirvish --vault home --init
   93 	
   94 	If you add the --no-run option you will see what it will try
   95 	to do.
   96 
   97 	To do a regular backup you now only would need to execute
   98 	"dirvish --vault home"
   99 
  100 	After you create your image you can look at the log and summary
  101 	files to see what was done.
  102 
  103 	I strongly recommend reading the dirvish and dirvish.conf manpages.
  104 
  105 	Work on your exclude lists and have fun.
  106 
  107 	dirvish.runall will run dirvish on all of the vault[:branch]s
  108 	listed in the Runall list in /etc/dirvish.conf
  109 
  110 	Because dirvish handles calculating expiration dates
  111 	automatically you need only add two entries to crontab to
  112 	completely automate your dirvish backups.
  113 
  114 		10 03 * * *     root /site/sbin/dirvish-expire --quiet
  115 		18 03 * * *     root /site/sbin/dirvish-runall --quiet
  116 
  117 	Note that both dirvish-runall and dirvish-expire are scheduled
  118 	after 22:00 as specified in the Runall: parameter.