Lower Storage Costs for Infrequently Accessed Data • Migrate Data Between any File System and Storage Technology • Simplistic Monitoring and Policy-Based Data Movement
MODERN DATA MANAGEMENT CHALLENGES
Most data within an organization becomes static almost as soon as it is created. As a result, infrequently accessed data can become an expensive burden on the IT organization when factoring in the total cost of storage from hardware and management overhead to floor space and cooling costs. By migrating static or less frequently used files to more efficient storage platforms such as DDN WOS® Object Storage, businesses can optimize the use of primary storage, reducing the need and costs associated with purchasing additional capacity for that tier. In addition, when data is managed properly, and only the most recent or frequently changing files are included in the backup process, the backup window will be dramatically reduced.
A SINGLE MANAGEMENT TOOL TO SOLVE IT ALL
- Software manages archive and media, drive and library mirroring
- Delivers cost-effective archive and disaster prevention
- Retention management meets specific internal governance and compliance requirements
- Supports choice of proprietary or industry-standard file systems like LTFS
- Policy-based tiered storage and data management with WOS ArchiveDirector™
DDN DataMigrator is a storage management tool that uses advanced policies to monitor and automatically migrate data between any file system or a centralized archive. It delivers a robust set of storage and archive management tools, supporting all major file systems and protocols. By leveraging DDN DataMigrator, businesses can optimize the use of primary storage while reducing the need to purchase additional capacity at a premium cost.
FLEXIBLE DATA MANAGEMENT
With DDN DataMigrator, administrators have a powerful and wide range of policy settings that allow them to manage data according to their unique and broad retention requirements.
To ensure minimal impact on end users, files can remain fully accessible even after the data has been migrated to any tier of storage. A combination of file attributes can be used to control which information is selected: file creation, modification and last accessed date, file owner, file size and file extensions. Thresholds can be configured to initiate and end migration events or migration can be started at preset intervals. Separate policies can be created to manage file archive retention, and after the data expires it can be released for managed or automatic deletion.
For more efficient management and tracking of data usage, DDN DataMigrator provides simulation tools to test the impact of migration policies. Resulting reports can identify key data types to be migrated and the general age and status of data within an organization.
DDN DataMigrator Configurations & Specifications
DATA MIGRATION POLICY TYPES
|STUB AND MIGRATE||A stub containing new file location remains on primary storage, while file is migrated to secondary storage. Stubs created are not proprietary but are operating systems stubs; reparse points (Windows) or symbolic links (UNIX or Linux).|
|COPY||The file remains in primary storage and a copy is created on secondary storage.|
|MOVE||The file is removed from primary storage and stored on secondary storage. Can be used to decommission old storage, easily moves files from legacy storage to a new storage device.|
|DELETE||Securely deletes files at the end of the retention period. Also can be used to remove unwanted file types such as wav or mp3 files.|
Server (Physical or Virtual)
- Intel Xeon E3 Quad Core 2.3GHz (or better)
- 32GB RAM (64GB for larger file systems)
- Redundant Power Supply
- 1Gbit or 10Gbit (preferred) Fast Ethernet
- Capacity of 1KB per file stored in included PostgreSQL DB
- RAID or Mirrored Disk configuration
- SSD, FC or SAS drives preferred