Solutions
Data Migration
  • Complete your project faster, with minimal downtime
  • Support pre-migration UNC names in shortcuts and embedded links

AutoVirt facilitates share-by-share migration, which means that there is no need to take an entire device offline during migration.  AutoVirt breaks each migration job into share-sized increments.  To preserve data integrity, files are held read-only while their parent shares are being migrated.  As soon as a share is migrated, full read/write access is restored.  The AutoVirt global namespace is updated with the new share location, and clients are automatically redirected to their share.  Share-by-share migration drastically reduces downtime, and automatic client referrals eliminate post-project shortcut remapping.

To limit the time that large shares are held read-only, AutoVirt offers a pre-migration synchronization period.  The sync period can be scheduled to recur as many times as you like.  During the first sync period, AutoVirt copies all un-open files it finds, skipping the rest.  Each recurring sync will copy any new files it finds un-open, and will synchronize changes at the source with files that have already been copied to the destination.  The synchronization period will be reduced over time, until AutoVirt is syncing only a small number of changes between source and destination.

When you schedule the final migration, the share will be held read-only as final changes are synced from source to destination.  When the sync is complete, clients are automatically redirected to the new share location read/write access is restored.




Resources




Using AutoVirt for Data Migration:
Read this paper to learn more





View screenshots of AutoVirt's
data migration policy wizard