onlineforums
Explorer
- Joined
- Oct 1, 2017
- Messages
- 56
How does FreeNAS handle replication when a dataset is renamed? Is the "original" before renaming kept using up disk space on the replication destination? Is ZFS smart enough to know that the new dataset name is the same as the replication destination old dataset name? What about when using zfs rename simply to move the dataset to a different location in the pool?
Example:
CURRENT: tank/replicate/current/ABC
AFTER ZFS RENAME: tank/replicate/archive/ABC
command: zfs rename tank/replicate/current/ABC tank/replicate/archive/ABC
What I'm trying to achieve is MOVING (using zfs rename) dataset "ABC" from the "current" dataset to the "archive" dataset once "ABC" dataset is no longer active. The replication from source FreeNAS is recursive from tank/replicate to a destination FreeNAS server.
If ABC dataset is 1GB, using the zfs rename on the original source dataset will keep it as 1GB but I'm not sure how the replication destination will handle it. Anyone know? Alternatively is there a better way to accomplish getting a dataset inactive (i'm thinking using ACL's and options as read-only may be an option)
Example:
CURRENT: tank/replicate/current/ABC
AFTER ZFS RENAME: tank/replicate/archive/ABC
command: zfs rename tank/replicate/current/ABC tank/replicate/archive/ABC
What I'm trying to achieve is MOVING (using zfs rename) dataset "ABC" from the "current" dataset to the "archive" dataset once "ABC" dataset is no longer active. The replication from source FreeNAS is recursive from tank/replicate to a destination FreeNAS server.
If ABC dataset is 1GB, using the zfs rename on the original source dataset will keep it as 1GB but I'm not sure how the replication destination will handle it. Anyone know? Alternatively is there a better way to accomplish getting a dataset inactive (i'm thinking using ACL's and options as read-only may be an option)