onlineforums
Explorer
- Joined
- Oct 1, 2017
- Messages
- 56
I'm looking for a sanity check and some tips on how to best organize data so that my snapshots don't get huge from "deleted" or "moved" data that is actually captured in a different snapshot.
I work with other people on projects that can be 1mb to 100mb large consisting of 5 to 50 files. Each project is unique and there can be dozens of "current" projects. After a project changes status (complete, hold, etc) then that project changes locations outside of the "current" folder to not clutter up the currently working on projects folder.
The current structure, outside of FreeNAS is as follows:
Basically a project MOVES from a status to another status folder (or in the above illustration, sub folders). So for example, when Project03 got completed it got moved from "CURRENT-PROJECTS" folder to "CURRENT-PROJECTS/NON-CURRENT"
The concern I have is associated with datasets, snapshots and replication tasks and looking for your tips.
Alternatively I was thinking of separating out NON-CURRENT outside of the CURRENT-PROJECTS folder/dataset as follows:
I'm looking for best practices where I can MOVE a Project folder from the "CURRENT-PROJECTS" folder to a NON-CURRENT/<status> folder, whether nested datasets or not.
My concern is that I don't want snapshots and replication tasks to basically increase in size for the moved folders as the data will be accounted for in the snapshot/replication of where the project got moved. For example, if all projects, including all statuses (complete and hold) is 6 GB then I want to move projects around while the new snapshot after moving folders to still be 6GB. This may be 2GB in CURRENT-PROJECTS, 2GB in COMPLETE and 2GB in HOLD. If I move 1GB from CURRENT-PROJECTS to COMPLETE I want to make sure that the totallity of all of the new snapshots is still only 6GB rather than 7GB. In other words, I don't want one snapshot to see the data as deleted, removed or changed but rather moved to a different dataset where that snapshot references the data.
I'll be playing around in a FreeNAS testbed on this but figured I would post this out there for some insight and to help me in my testing.
Thank you!
I work with other people on projects that can be 1mb to 100mb large consisting of 5 to 50 files. Each project is unique and there can be dozens of "current" projects. After a project changes status (complete, hold, etc) then that project changes locations outside of the "current" folder to not clutter up the currently working on projects folder.
The current structure, outside of FreeNAS is as follows:
Code:
CURRENT-PROJECTS | - Project01 | - <files> | - Project02 | - <files> | - NON-CURRENT | - COMPLETE | - Project03 |- <files> | - HOLD | - Project04 |- <files>
Basically a project MOVES from a status to another status folder (or in the above illustration, sub folders). So for example, when Project03 got completed it got moved from "CURRENT-PROJECTS" folder to "CURRENT-PROJECTS/NON-CURRENT"
The concern I have is associated with datasets, snapshots and replication tasks and looking for your tips.
Alternatively I was thinking of separating out NON-CURRENT outside of the CURRENT-PROJECTS folder/dataset as follows:
Code:
CURRENT-PROJECTS | - Project01 | - <files> | - Project02 | - <files> NON-CURRENT | - COMPLETE | - Project03 |- <files> | - HOLD | - Project04 |- <files>
I'm looking for best practices where I can MOVE a Project folder from the "CURRENT-PROJECTS" folder to a NON-CURRENT/<status> folder, whether nested datasets or not.
My concern is that I don't want snapshots and replication tasks to basically increase in size for the moved folders as the data will be accounted for in the snapshot/replication of where the project got moved. For example, if all projects, including all statuses (complete and hold) is 6 GB then I want to move projects around while the new snapshot after moving folders to still be 6GB. This may be 2GB in CURRENT-PROJECTS, 2GB in COMPLETE and 2GB in HOLD. If I move 1GB from CURRENT-PROJECTS to COMPLETE I want to make sure that the totallity of all of the new snapshots is still only 6GB rather than 7GB. In other words, I don't want one snapshot to see the data as deleted, removed or changed but rather moved to a different dataset where that snapshot references the data.
I'll be playing around in a FreeNAS testbed on this but figured I would post this out there for some insight and to help me in my testing.
Thank you!