Hi,
I am looking for some direction on creating a job in napp-it for Cloning file systems.
I would like to setup a VM to download and continually update a folder/drive for Win10 games and for that folder/drive to be available for a number of other virtual and physical machines, each able to read and write to it without corrupting each other's folder/drive. I expect this will accumulate to quite a large quantity of of data and I would prefer not to store multiple copies of it. I should probably avoid deduplication, as it rarely seems to be the answer.
I thought ZFS Clones, which take up very little space initially, with a napp-it: Jobs > Other > 'Create a job' scheduled once a day early in the morning.
I understand most games are ok being located on mounted SMB network shares; however, some require iSCSI to trick the game the drive is local. Also, perhaps the games are split between the NVMe and HDD pools, depending on performance required for each game. I'm not very familiar with iSCSI, but I tried it recently and I was pleased with the speed over 10Gbe; however, iSCSI has its drawbacks when compared to the flexibility of SMB/NFS, so a mixture might be the answer.
I'm hoping all game saves are stored on the user's local profiles, or cloud saves, and that their games folder/drive can be destroyed and replaced with new data each night. I'll test this when I next get an opportunity.
It could go like this:
- Updater-VM (not used for gaming) to write to an SMB folder or iSCSI target all day, except for a time early in the morning when it is scheduled not to be written to.
- In napp-it: Jobs > Other > 'Create a job'
- Take a snapshot of the original SMB and iSCSI File Systems
- Make Clones from the original snapshot for each machine requiring access, and set to r/w
- Mount the Clones as SMB shares or iSCSI targets
- Each machine's SMB share is updated and they are reconnected to their iSCSI target with full read/write permissions for use throughout the day
- At next scheduled snapshot from original file system, existing Clones are destroyed and new Clones are created including updated data
- the cycle repeats as scheduled and manually if required
I am looking for some direction on creating a job in napp-it for Cloning file systems.
I would like to setup a VM to download and continually update a folder/drive for Win10 games and for that folder/drive to be available for a number of other virtual and physical machines, each able to read and write to it without corrupting each other's folder/drive. I expect this will accumulate to quite a large quantity of of data and I would prefer not to store multiple copies of it. I should probably avoid deduplication, as it rarely seems to be the answer.
I thought ZFS Clones, which take up very little space initially, with a napp-it: Jobs > Other > 'Create a job' scheduled once a day early in the morning.
I understand most games are ok being located on mounted SMB network shares; however, some require iSCSI to trick the game the drive is local. Also, perhaps the games are split between the NVMe and HDD pools, depending on performance required for each game. I'm not very familiar with iSCSI, but I tried it recently and I was pleased with the speed over 10Gbe; however, iSCSI has its drawbacks when compared to the flexibility of SMB/NFS, so a mixture might be the answer.
I'm hoping all game saves are stored on the user's local profiles, or cloud saves, and that their games folder/drive can be destroyed and replaced with new data each night. I'll test this when I next get an opportunity.
It could go like this:
- Updater-VM (not used for gaming) to write to an SMB folder or iSCSI target all day, except for a time early in the morning when it is scheduled not to be written to.
- In napp-it: Jobs > Other > 'Create a job'
- Take a snapshot of the original SMB and iSCSI File Systems
- Make Clones from the original snapshot for each machine requiring access, and set to r/w
- Mount the Clones as SMB shares or iSCSI targets
- Each machine's SMB share is updated and they are reconnected to their iSCSI target with full read/write permissions for use throughout the day
- At next scheduled snapshot from original file system, existing Clones are destroyed and new Clones are created including updated data
- the cycle repeats as scheduled and manually if required