Users must understand, however, that the purpose of such rapid-fire backups is to ensure quick recovery, not longer-term protection against data deletion or corruption. Such synchronizations provide whatever the user defines as real time backups, much as a RAID 1 (mirrored) array creates a duplicate (mirror) disk that is up to date at the level of seconds or even fractions of a second (depending on input/output load). For example, a schedule can ensure frequent synchronizations such as once an hour – or every few minutes, for that matter. ViceVersa has a companion product, VVEngine which provides a wide range of options for running synchronizations without human intervention. However, once a source and a target are synchronized, it's unlikely for ordinary users that huge data volumes will have to be carried over from source to target. Faster synchronization is particularly useful for large data transfers and for operations carried out while the user waits. The increase in speed meant that ViceVersa completed the synchronization in about one third the time that SyncToy took. The successful transfer of files seems comparable across the two products, as does the speed of synchronization of the two products varied considerably however, the largest transfer (Program Files) did show a much faster transfer rate in ViceVersa than in SyncToy: 4.5MBps for ViceVersa and 1.5MBps for SyncToy. Perhaps the staffers at TGRMN will be interested in extending the tests to provide a more thorough exploration of performance characteristics of their product with different types of files. These tests are not statistically valid trials, since there are only a few samples involved they should be viewed as exploratory data. I carried out some simple comparisons between SyncToy and ViceVersa using a couple of different options to explore possible differences in coverage and performance. This feature means, for example, that if one forgets to close an e-mail client before synchronizing files, even the open e-mail database will be copied to the target. In contrast, ViceVersa handles open files (e.g., Outlook. The option Use Volume Shadow Copy Service to copy open files solves a problem that afflicts SyncToy: it cannot copy open files. For example, if an address book has been changed on both the source and the target since the last synchronization, it would be appropriate to identify which changes should be merged into the file (e.g., new entries).
VICE VERSA SOFTWARE MANUAL
The Tracking Database allows identification of pairs of files in which both the source version and the target version have changed from a previous state during synchronization, such pairs are identified as potentially requiring manual reconciliation. Consolidation: like synchronization except that no deletions are involved – for example, if a file was deleted from the source but still present on the target, it would be copied back to the source.Īnother sophisticated feature is the Tracking Database, which is required for synchronization.