
Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
Solved!
Go to SolutionSaving pool space with Nocopy clones
Folks,
We have a very large db replicated to a VMAX, running 5876 code, from the R2 we have 4 different test,dev,Backup,QA clone copies. We figured we could save a ton of space using nocopy clones, none of these environments require high performance.
The problem is the default behavior on a nocopy clone is copy on access. How do we change that behavior to copyonwrite?
We have thought about changing the whole operation and using the new -vse and making it a Snap but like the idea of being able to make it a full clone copy if the need arises. Thanks in advance.
If anyone has good documentation on the differences between a nocopy clone and the vse option that would be welcome as well.
Responses (0)
Solutions (0)
