The point of the posting was to let Aitor_Ibarra (the thread starter) know that the idea was not trash and that there is a production use for a completely volatile RAMsan. I am requesting no feature be added and have replied to clarify your questions. The implementation of the RAMsan software is run...

There are many ways to skin a cat (c) ... You can handle everything on hypervisor level (diff clones) or you may use deduplicated storage where SAN will take care of mapping the same data to the same blocks and caching them deduplicated. Result would be pretty much the same. For any normal filing s...

It makes since and is perfectly safe. The whole point of a parent differencing disk is that all traffic is read only. When you have multiple child disks the read demand on the parent disk is raised for each new child disk. All changes the VM makes to the drive (write traffic) is sent to the child di...

I had a similar idea with a practical production need that led me to stumble upon this thread. We have a number of large Hyper-V SAN servers that host VMs as they are built before migrating them to standard diskless hosts (16x 2.8Ghz Processors, 256GB RAM, Quad 10Gb/s SFP+ NICs, 24x 512G SSDs, 48x 1...