Quote:
Originally Posted by Owl
Rolling back and fore is irrelevant, it just demostrates what is working and what is not. Snapshot C might have been zero size when created, but once B is deleted C acquires all the data that was in B.
RbRX does not precisely equate with Windows Restore. What WR does is to archive critical files, and restore them from the archive if required. RbRX actively manages the whole partition (or partitions), so the snapshots accumulate the differences, and then stepping back through the snapshots unwinds the differences. So naturally, deleting an intermediate differences snapshot means the two neighbouring snapshots have more differences to be recorded.
The management is through an intricate database, and the process of deleting snapshots or defragging them is actually a process of reorganising the database rather than actual deletions or defragmentation of the disk itself.
Thus, the "size" attributed to each snapshot is only a representation of how much disk space is referenced by the database pointers associated with that snapshot. Deleting the snapshot moves the pointers to the next snapshot in line (the data remains where it is on the disk). Defragging the snapshots detects where there maybe some redundant information (for example a write occured to change a particular disk sector in one snapshot, and then again in the next snapshot - combining the two only needs to keep the later change) and frees up a small amount of space.
Does that help, or confuse the issue more??
|
thanks for reply. See you have a good working knowledge of RBRX. Info helped a lot.
Verified what I thought. When I asked exact same question in rbrx chat support,
response was ' How can data be in c when you deleted b' meaning when
you delete b,data is gone. Did not press the issue. Will stick to forum for further advice.
Thanks a lot...