BIG-IP : sync-failover device-group sync options

Forums Technical Forums
, , ,
1

F5 BIG-IP Virtual Edition v11.4.1 (Build 635.0) LTM on ESXi

For a device-group of type sync-failover, the admin browser provides these options :

Automatic Sync 
Full Sync
Maximum Incremental Sync Size (KB)

Could someone please explain these options ?

Are syncs on a time-schedule ?

Or are syncs triggered by any change to the primary ? Or exactly what types of changes will trigger a sync ?

Specifically, will a change to a data-group file ( e.g. add/delete a line ) trigger a sync ?

2

Automatic Sync - Sync is automatic and not manual. Done almost immediatelly after a change is made

Full Sync - if checked will do a FULL sync and if left unchecked, only an incremental sync

Maximum Incremental Sync Size (KB) - 1024 - if you make more than this default value it goes into FullSync mode. (number is a variable)

support.f5.com has further info on this. Hope this helps for now.

3

Automatic Sync - Sync is automatic and not manual. Done almost immediatelly after a change is made

Full Sync - if checked will do a FULL sync and if left unchecked, only an incremental sync

Maximum Incremental Sync Size (KB) - 1024 - if you make more than this default value it goes into FullSync mode. (number is a variable)

support.f5.com has further info on this. Hope this helps for now.

4

thanks NikhilB .. what would motivate a full-sync vs an incremental-sync ? are there scenarios where an incremental-sync is not fully reliable ?

5

thanks NikhilB .. what would motivate a full-sync vs an incremental-sync ? are there scenarios where an incremental-sync is not fully reliable ?

6

Hi, opening this after some time… I am also curious what would motivate you to select full-sync over incremental-sync?

7

Hi, opening this after some time… I am also curious what would motivate you to select full-sync over incremental-sync?

8

Hi, we forced full-sync over incremental-sync because we get lot of issues with incremental since we are using many iapps. There is a known issue and should have been fixed in latest bigip version.

9

Hi, we forced full-sync over incremental-sync because we get lot of issues with incremental since we are using many iapps. There is a known issue and should have been fixed in latest bigip version.