Hi,
the two FreeNAS boxes of mine are happily interacting, one as primary NAS, the other as backup for NAS' datasets. They are set-up according to https://doc.freenas.org/9.10/storage.html#replication-tasks and work flawlessly so far.
What the docs don't tell is which possible status codes the replication scripts holds. I'm asking this because to me they're a bit confusing. These a the ones I am aware of:
What exactly do they mean?
How are they bound together? Is there a sort of state machine where they are in?
the two FreeNAS boxes of mine are happily interacting, one as primary NAS, the other as backup for NAS' datasets. They are set-up according to https://doc.freenas.org/9.10/storage.html#replication-tasks and work flawlessly so far.
What the docs don't tell is which possible status codes the replication scripts holds. I'm asking this because to me they're a bit confusing. These a the ones I am aware of:
- Sending <pool>/<dataset>@<snapshot> (x %) is quite obvious: replication in progress. All fine.
- Up to date: this doesn't seem to be true while Sending ... is in progress on a different dataset. A long-running next-to job puts all other jobs on hold, thus they aren't up to date anymore after a while, new snapshots are lining up in the background. So, to me, Out of date would be a better designator. Or on hold.
- Succeeded: this status comes right after a successful transmission. Later, Succeeded gets replaced by Up to date. I havn't witnessed when. Under what criteria?
- Failure. E.g. if remote host isn't up. All fine here too.
What exactly do they mean?
How are they bound together? Is there a sort of state machine where they are in?
