Storage Management
190
Titan SiliconServer
Configuring Data Migrator
In order to use Data Migrator on Titan, the following need to be defined:
❑
Data migration paths from primary to secondary storage.
❑
Data migration rules, which determine the properties of files that will be
migrated.
❑
Data migration policies, which define rules to apply to specific data migration
paths based on the available free space on the source file system or Virtual
Volume.
❑
Schedules in which the frequency with which the data migration policies will be
run.
Data Migration Paths
Before Data Migrator can be used, the primary and secondary storage must first be identified.
Primary storage, typically fibre channel disk arrays, will be the
source
for data migrations.
Secondary storage, typically ATA disk arrays, will be the
target
for data migrations. Once Data
Migrator has been configured, data will be migrated from primary to secondary storage based on
the rules defined, freeing up space and extending the capacity of the primary storage.
Note:
No attempt should be made to directly access data migrated to
Secondary Storage. The organizational structure of migrated data on
Secondary Storage does not mirror that of Primary Storage. Furthermore,
accessing files directly on Secondary Storage may alter access and
modification times of the files, resulting in unexpected results when
performing backups.
Data Migration Paths are used to define the relationship between primary and secondary
storage. The primary and secondary storage defined in the Data Migration Paths must be owned
by the same
EVS
.
Caution:
If either the primary or the secondary File System is moved to a
different EVS, access to migrated files will be lost.
When defining Data Migration Paths, a file system or Virtual Volume can be specified as the
primary storage. If a file system is selected as primary storage, then the entire file system,
including all Virtual Volumes, are included as a part of the Data Migration Policy. To create
individual policies per Virtual Volume, each Virtual Volume should be assigned a specific
Migration Path.
Note:
Once a Migration Path has been assigned to a Virtual Volume, a
subsequent Migration Path cannot be created to its hosting file system. Also,
once a Migration Path has been assigned to a file system, subsequent
Migration Paths cannot be created from Virtual Volumes hosted by that file
system.
