Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Full filesystem replication doesn't work incrementally

Description

Hi,

The UI and documentation explain that using "Full filesystem replication" should "Completely replicate the selected dataset. The target dataset will have all of the properties, snapshots, child datasets, and clones from the source dataset."

I believe this is true for the first replication (because -R is used), but not the case as soon as replications start running incrementally. Indeed, since -i is used instead of -I, intermediary snapshots do not get replicated (violating "all of the snapshots"). Moreover, if clones have been created on the local system, based on snapshots that are outside the replication schedule, those will fail to replicate too (violating "all of the clones").

Is it possible to make incremental replication use -I instead of -i when using "full filesystem replication"?

Thanks

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:
Bug Clerk
May 7, 2021 at 11:37 AM
Bug Clerk
May 7, 2021 at 11:26 AM
Bug Clerk
May 5, 2021 at 2:15 PM
Vladimir Vinogradenko
May 5, 2021 at 2:13 PM

we will fix the tooltip, thank you.

TrueNAS CORE 13 will not receive this fix, we will only upgrade the base OS itself.

Winnie Linnie
May 5, 2021 at 2:06 PM

"We will not risk integrating so many changes into stable version of TrueNAS."

 

Does this apply to TrueNAS Core 12.x, or TrueNAS Core in general (i.e, 13.x, 14.x 15.x, etc)?

 

To be clear, in SCALE (when this is fixed), selecting the option "Full Filesystem Replication" will behave as expected, as described in the tooltip and guide? (Equivalent to using ~I in a shell script?)

 

Should we file a separate bug report against the tooltip in Core? As it stands now, the language used does not reflect what is actually done, and like the OP and myself (and I'm sure others), it tricks us into thinking a true full filesystem backup (with all snapshots and clones) is being saved on a destination/backup pool. The only reason I bothered to look further into this is because I noticed a discrepancy in used space between my source pool and backup pool. "Hey, wait a second... why is it significantly smaller? They should be the same size. Oh, what's this... hey! All my snapshots in between are missing! But it said it will transfer all my child datasets, snapshots, and clones?"

Complete

Details

Assignee

Reporter

Labels

Impact

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created February 18, 2021 at 2:42 PM
Updated July 1, 2022 at 5:13 PM
Resolved June 30, 2021 at 3:29 PM