AutoVirt Data Migration Policy
An AutoVirt migration policy relocates the master version of a data set by copying it from source to destination and automatically redirecting users to the new location. The source data can be scheduled for deletion any time after the job is complete.
Scheduling. A migration policy can be scheduled to run during a distinct, daily period until the job is complete. It can also be set to begin immediately and run until complete
Job Segmentation. Each AutoVirt migration job is automatically broken into share-sized increments. Shares are copied individually, from source to destination, until the job is complete
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 job is still in progress, with other shares being held read-only for copying
Automatic client redirects. When a share copy is complete, client shortcuts automatically resolve to the new location of the data
Two approaches to migration. There are two ways to complete a data migration using AutoVirt. Both are designed to minimize maintenance windows and limit impact to end-users and IT staff
Scheduling. A migration policy can be scheduled to run during a distinct, daily period until the job is complete. It can also be set to begin immediately and run until complete
Job Segmentation. Each AutoVirt migration job is automatically broken into share-sized increments. Shares are copied individually, from source to destination, until the job is complete
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 job is still in progress, with other shares being held read-only for copying
Automatic client redirects. When a share copy is complete, client shortcuts automatically resolve to the new location of the data
Two approaches to migration. There are two ways to complete a data migration using AutoVirt. Both are designed to minimize maintenance windows and limit impact to end-users and IT staff
- For a large number of small, personal shares
Because share size is small, each share will only briefly be subject to open-file rules. To migrate small shares, IT should simply select source and destination and schedule the policy to run as desired. - For a small number of large shares, such as those used by applications
In some cases, lacking write access during the entire copy period is unacceptable. In order to minimize the time during which shares are held read-only, AutoVirt provides a pre-migration copy and synchronization phase. AutoVirt recommends that IT use this phase to copy the bulk of the data to the destination before the actual migration begins.
Download this data sheet to learn more!
Complete this form to download the AutoVirt data sheet and learn more about automating data migration in your environment with AutoVirt 3.0.
* indicates a required field
"High-end file virtualization providers have nurtured the market – moving from the early adopters into the mainstream enterprise with demonstrable value, especially in file. Unfortunately, many of these products are too expensive or complicated for smaller to mid size organizations. AutoVirt is delivering an easy to manage, highly scalable solution that provides the value at an affordable cost."
Marc Staimer, Founder and President, Dragon Slayer Consulting