Replication of snapshot fails cannot recieve incremental data

[rrichmond72130]

The freenas has been replicating fine for a little bit then all of sudden we are getting a message like this
(system was unable to replicate snapshot pool/desk to 192.168.1.179 ====================== cannot receive incremental stream: most recent snapshot of pool/desk does not match incremental source).
It started a couple days ago and we have not changed any settings. The hostname does not work in the replication and we have to use the IP, if that makes any difference.

we are working with
FreeNAS-9.2.1.8-RELEASE-x64
Intel(R) Xeon(R) CPU E5420 @ 2.50GHz
Memory 12266MB

 

[cyberjock]

So if you get a list of snapshots on the source and destination they probably don't match at all. So what you need to do is reinitialize the destination and resend the whole list of snapshots you have.

 

[rrichmond72130]

We have tried that 3 times already. We resend the snapshot and after a couple days it starts sending that message. We are also replicating 2 other snapshots to the same machine, and they work perfectly.

 

[cyberjock]

How often are you taking snapshots and when do they expire? Can you provide the list of snapshots for the applicable pool/dataset on both the source and destination?

Thanks.

 

[rrichmond72130]

We are taking snapshots every hour and deleting them every two weeks. On both the source and destination the snapshots are different. The size of the source snapshot is smaller then the size of the destination snapshot! Does this matter?

 

[cyberjock]

The size is only based on type of compression, block size, etc. The size isn't always expected to be identical, and this is totally normal.

Not sure what to say for your replication issue though. It works for me and the only time I've seen it get out of sync is when replication is being interrupted regularly (causing the servers to be out of sync beyond recovery) and if the user has done what can only be termed as "bad things" on their server. Note that "bad things" could be dozens of things, so I can't give you a short list. There's too many ways to break replication from the CLI. :P