Ignore:
Timestamp:
09/12/13 07:08:56 (11 months ago)
Author:
Kris Moore <kris@…>
Branches:
master, 9.2-release, releng/10.0, releng/10.0.1, releng/10.0.2
Children:
03c14f8
Parents:
651bd28
Message:

Update to lpreserver backend:

Added new "replicate init <dataset>" option, which will re-init the remote side of the replication server, cleaning up any corrupt datasets and preparing to sync fresh again.

Also added a check during replication, we won't try to kickoff a second replication task if a previous one is still running, to avoid collisions. In addition we will not delete any snapshots until the initial replication is finished, in order to prevent undercutting the active replication

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src-sh/lpreserver/lpreserver

    r7c0c657 rc0e6494  
    146146 
    147147Available Flags: 
     148 
     149         add - Add a new replication target 
     150        init - Initialize the remote side again 
    148151        list - List replication targets 
    149          add - Add a new replication target 
    150152      remove - Remove a replication target 
    151153 
     
    165167 
    166168        Will schedule replication of tank1 to tankbackup/backups at 10PM, notated in 24hour time 
     169 
     170 
     171Init Options: 
     172 
     173        init <localdataset/zpool>  
     174 
     175        Will re-init the remote side of the replication. This can be useful 
     176        when your replication gets stuck. Doing this option will remove 
     177        all the data on the remote side, and require a full re-sync again. 
    167178 
    168179Remove Options: 
     
    486497            case ${1} in 
    487498                add) add_rep_task "$2" "$3" "$4" "$5" "$6" "$7" ;; 
     499                init) init_rep_task "$2" ;; 
    488500                list) list_rep_task ;; 
    489501                remove) cat ${REPCONF} | grep -q "^${2}:"  
Note: See TracChangeset for help on using the changeset viewer.