Back to files

INSTALLATION

UPGRADING

first, make a backup of your existing dmzBackup package. you can use the script '_scripts/snapshot.sh' to make it.

when upgrading to version 0.3.1 you have to take care about the following files (please don't just replace new files with your existing ones):

        CONFIG/BACKUP.CONF
        - compare the old config/backup.conf with the new one, there are possible more
          options to define
        -       set the 'mail_to' and 'mail_from' options
          ('mail_to' was called 'admin' in older versions)
        - set the command paths
        - set the running 'system' type  
        - set the 'follow_symlinks' option
        
        CONFIG/<<HOST>>.CONF
        - there are minor changes in version 0.3.1 host config files
        - although there is backward compatibility you may want to remove the
          'dir:' and 'file:' prefixes of your 'src_path' option
        
        AFTER THAT
        - remove the old package files within the dmzBackup directory:
                $ cd /path/to/old
          $ rm _notes/ _scripts/ config/ temp/* -rf
        - copy the new files in place:
          $ cp dmzBackup-0.3.1/_notes/ dmzBackup-0.3.1/_scripts/ dmzBackup-0.3.1/config/ /path/to/old

FILE PERMISSIONS

use the following commands within the dmzBackup directory to fix wrong file permissions:

$ chown root:root * -R
$ find -type f -exec chmod 644 {} \;
$ find -type d -exec chmod 755 {} \;
$ chmod 700 _scripts/*
$ chmod 600 _scripts/functions.sh

RESTRICTIONS AND DONTS

normally an error message describes the problem very exact. but sometimes the solutions seems to be clear, although you can't do anything :-) the following restrictions contain these cases:

/*
DEPRECATED THROUGH 0002
ID 0001
TITLE LOGFILES (APACHE, SYSTEMLOGS)
ERROR

ERR: /bin/tar: /path/to/access_log: file changed as we read it DESCRIPTION
logfiles tend to change their contents during backup. you may notice an error message like 'file changed as we read it'. this happens only if the logfile is very large (more than 100 MB) and cannot be read completly to memory by tar. there is no way of locking the file or stopping processes writing to the logfile. so try to avoid large logfiles as it is a common way of system administration.
*/

ID 0002
TITLE FILESYSTEMS (XFS)

        ERROR
                ERR: /bin/tar: /path/to/access_log: file changed as we read it
        DESCRIPTION     
                this error occurs with files on xfs filessystem which change their contents 
                while processing through the tar command. there is no easy way of locking
                the file without the loss of data (f.e. otherwise logfiles could not retrieve
                new entries)
        SOLUTION
                version 0.3.1 is planned to contain the possibility of using pre and post backup
                commands.       my way was to copy the file to an other directory and backup up 
                that source.            
        KEYWORDS
                xfs, filesystem, logfile