Show
Ignore:
Timestamp:
07/15/10 19:55:05 (4 years ago)
Author:
depesz
Message:

add more info about requirements, and important notices about usage

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • trunk/omnipitr/doc/omnipitr-archive.pod

    r156 r178  
    248248    archive_command='/.../omnipitr-archive -D /mnt/data/ -l /var/log/omnipitr/archive-^Y-^m-^d.log -dr gzip=rsync://slave/postgres/wal_archive/ -dr bzip2=backups@backupserver:/mnt/backups/wal_archive/ -dl /mnt/wal_archive/ -s /var/lib/postgres/.omnipitr/ "%p"' 
    249249 
     250=head2 IMPORTANT NOTICES 
     251 
     252=over 
     253 
     254=item * You need to provide state dir in case you have > 1 destination. This is 
     255crucial, as if you're using "-dr ... -db" - your number of destinations changes 
     256from 1 to 2 (depending on whether -db directory exists) - i.e. not all runs of 
     257I<omnipitr-archive> will catch lack of state-dir as error! 
     258 
     259=item * It is generally good to provide 2 destination - one used by slave system 
     260to keep warm standby, and another to be handy in case (for example) backup files 
     261get corrupted. This second set of xlogs should be cleared with cronjob that 
     262removes too old files. As for what is too old - 2x your backup schedule. I.e. if 
     263you're doing daily hot backups - you should keep 2 days worth of backup xlogs. 
     264 
     265=back 
     266 
    250267=head2 COPYRIGHT 
    251268