Single Instance Storage and restoring shadow copies
I'm eyeing this up for the space-saving feature, more than anything. One copy of $large_reference_doc, rather than 300 across different homedirs would be handy.
But I'm not entirely sure how it works with shadow copies. I've read:
But what happens if someone with the original version accidentally deletes his link in his home directory and then tries to restore if from shadow copy / previous versions tab? Would he get the original or revised version back?
Two users receive the same e-mail with an attachment. They both save the attachment to their home folder. SIS runs in the background and detects the two identical files on the volume and moves one of the copies into the SIS common store and replaces both files with a pointer to the file in the SIS common store.
One of the users makes a change to the file. SIS immediately detects that an update is pending for the file removes the pointer in the users home folder and replaces it with a copy of the file in the SIS common store. The updates are then applied to a fresh copy of the original file. This is completely transparent to the application.
The other user's file remains in the SIS common store with a pointer in the user's home folder, even if there is only one pointer to the file. When the second user updates the file (assuming there are no other pointers) the pointer is deleted and replaced with a copy of the original file and the file in the SIS common store is deleted.