Configuring an AutoVirt Migration Policy
Scroll down for a walk through the AutoVirt policy wizard









An AutoVirt migration policy moves data from a share, volume, or filer to a target you select.
Synchronization. AutoVirt provides a
pre-migration copy and synchronization phase. During this phase,
AutoVirt copies any files it finds un-open from source to
destination. By pre-seeding your migration target, the majority of
your files will be copied when it comes time for the final migration
Scheduling. A
migration policy can be scheduled to begin at any time. You may stipulate a blackout window during which AutoVirt will pause the migration job
Open file handling.
Data integrity is protected by enforcing read-only file access during
the copying of each share. As soon as an individual share is copied,
write access is restored – even if the migration policy is still running on other shares
Share-by-share migration. As soon as a share is migrated, clients automatically access it in its new location. Individual files are unavailable only while their parent shares are being migrated. Share-by-share migration drastically reduces downtime, and eliminates the need to take an entire device offline during migration
Automatic client redirects. When a share copy is complete, client shortcuts automatically resolve to the new location of the data. Automatic client referrals eliminate post-project remapping