1. Introduction
SFS Media is a cross-platform, enterprise-grade media storage and archive management solution. It is engineered for high-availability, scalability, and seamless integration with broadcast, post-production, and content management environments. SFS Media supports disk, tape, S3-compatible object storage, and DiskArchive. SFS Media provides robust APIs for integration with major MAM systems. SFS Media has 2 main product licenses, SF Archive and SF Migrate. SFS Media charges based on added features, and does not charge based on Number of libraries, drive counts, slot counts, or number of tapes used.
Features Include:
Avid Module, Socket Module, REST Module, Migrate Module, Changer Module, Queue Module, Workflow Module, ALTO Module, Browse Module and Node Count.
SF Archive License (core license)
Purpose:
SF Archive is designed for long-term, secure storage and management of media assets. It provides a comprehensive archive solution for organizations that need to preserve, organize, and retrieve large volumes of digital content.
Key Features:
- Full-featured media asset archiving (disk, tape, S3/object storage)
- Automated tape library and drive management
- Advanced metadata and search capabilities
- Grouping, tagging, and project-based organization
- Web UI for easy asset management and retrieval
- Integration with most MAM systems and third-party tools
- Robust archive, restore, and disaster recovery workflows
- Support for multiple tape formats (LTFS, AXF, TAR, UDF, etc.)
- Core application server
- 1 data mover with redundant application capability
- 1 Connector to an advanced asset manager, i.e., Avid, Grass Valley, Ross, Dalet
- 1 Archive conversion
- Partial file restoration
- Workflow engine for archival functions like LTO repacking, content duplication for DR, etc
- No restriction on content amount or storage locations
- Gold 24x7 level support
Use Cases:
- Broadcast and post-production facilities archiving completed projects
- Media companies with regulatory or contractual retention requirements
- Organizations needing secure, long-term preservation of digital assets
- Environments where fast, reliable retrieval of archived content is critical
SF Migrate License
Purpose:
SF Migrate is focused on high-speed, reliable migration of media assets between storage platforms, especially for moving content from legacy systems or tapes to modern storage (disk, cloud, or new tape formats).
Key Features:
- High-performance tape-to-tape, tape-to-disk, or tape-to-cloud migration
- Bulk migration tools for legacy archive systems (FlashNet, Kumulate, Diva, etc.)
- Ability to read and convert competitor tape formats
- Migration less - migration
- Continuous, non-stop tape migration (reads entire tape in one pass, even with missing EOF markers)
- Detailed migration logs and reporting
- Workflow automation for large-scale migration projects
- Minimal downtime and risk during migration
Use Cases:
- Media organizations consolidating or upgrading archive infrastructure
- Companies migrating from legacy tape formats or proprietary systems
- Disaster recovery projects requiring rapid tape duplication or offsite migration
SF Archive Mini Bundle
Purpose:
The mini bundle system is designed to replace mid-sized legacy archive systems, such as SDNA Evolution.
Key Features:
- Core application server
- 1 Connector to a basic asset manager, i.e., MAM.
- 1 Archive conversion
- Max 500TB of content in a single storage location, i.e., LTO library
- Silver 9x5 level support
SFS Archive – Cluster Module Requirements
- Cluster configuration is not always required.
Not every SFS Archive deployment needs clustering; it depends on the use case and the desired level of redundancy and failover. - Database/server failover is the client’s responsibility.
If a client wants a clustered automatic (failover) database, either they or their reseller must set up and maintain it themselves. SFS Media and Scale Logic Inc. do not provide database or server failover clustering as a service. - Purpose of the SFS Archive Cluster Module:
This module is specifically for clustering servers that perform the same function (for example, multiple data movers or automatic failover clustered database). The goal is to provide failover redundancy—if for example one data mover fails, another can take over seamlessly. - When the Cluster Module is not required:
If your deployment has servers with different roles (e.g., one is a database server, another is a data mover), clustering is not needed. The module is only for scenarios where you want multiple servers doing the same job, ready to take over for each other.
Scenarios
Cluster Module Needed:
- You have two or more data mover servers, and you want automatic failover if one fails.
- You want to ensure continuous operation of a specific function (like file movement or archiving) by having redundant servers for that function.
Cluster Module Not Needed:
- You have a single data mover server and a separate database server, each with unique roles.
- You do not require automatic failover or redundancy for a specific function.
- You are not clustering servers that perform the same task.
Summary Table
Feature/Use Case | SF Archive Mini Bundle | SF Archive | SF Migrate |
Long-term storage | Yes | Yes | No |
Asset management | Yes | Yes | Limited (migration-focused) |
Tape/disk/cloud support | Single location | Yes | Yes |
Migration tools | No | Basic (import/export) | Advanced (bulk, legacy, cross-format) |
Web UI | Yes | Full-featured | Streamlined for migration tasks |
MAM integration | Yes | Yes | Limited/optional |
Disaster recovery | Yes | Yes | Yes (for migration scenarios) |
Best for | Mid-sized legacy archive systems, such as SDNA Evolution | Ongoing archive operations | One-time or recurring migrations |
Cluster Module | No | If multiple servers doing same function and automatic failover is required. | If multiple servers doing same function and automatic failover is required. |