Deprecated
FileFly 2 support expires on April 2020. Contact DataCore for help licensing and migrating to the current version of FileFly. See the License change instructions in the FileFly 3.1 Release Notes.
- FileFly 2 Release Notes
- FileFly 2 Administration Guide
- 1 Introduction
- 2 Deployment
- 3 Policy Operations
- 4 Sources and Destinations
- 5 FileFly Admin Portal Reference
- 6 Configuration Backup
- 7 Storage Backup
- 8 System Upgrade
- 9 Disaster Recovery
- A Network Ports
- B File and Directory Exclusion Examples
- C Admin Portal Security Configuration
- D Advanced FileFly Agent Configuration
- E Troubleshooting
1.1 What is Caringo FileFly?
Caringo FileFly™ is a heterogeneous Data Management System. It automates and manages the movement of data from primary storage locations to Caringo Swarm or CloudScaler object storage.
Files are migrated from primary storage locations to the object store. Files are demigrated transparently when accessed by a user or application. FileFly also provides a range of Disaster Recovery options.
What is Migration?
From a technical perspective, file migration can be summarized as follows: first, the file content and corresponding metadata are copied to secondary storage as an MWI file/object. Next, the original file is marked as a 'stub' and truncated to zero physical size (while retaining the original logical size for the benefit of users and the correct operation of applications). The resulting stub file will remain on primary storage in this state until such time as a user or application requests access to the file content, at which point the data will be automatically returned to primary storage.
Each stub encapsulates the location of the corresponding MWI data on secondary storage, without the need for a database or other centralized component.
1.2 Conventions used in this Book
References to labels, values and literals in the software are in 'quoted italics'.
References to actions, such as clicking buttons, are in bold.
References to commands and text typed in are in fixed font.
Notes are denoted: Note: This is a note.
Important notes are denoted: Important: Important point here.
Figure 1.1: FileFly System Overview
1.3 System Components
Figure 1.1 provides an overview of a FileFly system. All communication between FileFly components is secured with Transport Layer Security (TLS). The individual components are described below.
Caringo FileFly Admin Portal
FileFly Admin Portal is the system's policy manager. It provides a centralized web-based configuration interface, and is responsible for task scheduling, policy simulation, server monitoring and file reporting. It lies outside the data path for file transfers.
Caringo FileFly Agent
Caringo FileFly Agent performs file operations as directed by Admin Portal Policies. FileFly Agent is also responsible for retrieving file data from secondary storage upon user/application access.
File operations include migration and demigration, as well as a range of operations to assist disaster recovery. Data is streamed directly between agents and storage without any intermediary staging on disk.
When installed in a Gateway configuration, FileFly Agent does not allow migration of files from that server.
Optionally, Gateways can be configured for High-Availability (HA).
Caringo FileFly FPolicy Server
FileFly FPolicy Server provides migration support for NetApp filers via the NetApp FPolicy protocol. This component is the equivalent of Caringo FileFly Agent for NetApp filers.
FileFly FPolicy Server may also be configured for High-Availability (HA).
Caringo FileFly DrTool
Caringo FileFly DrTool is an additional application that assists in Disaster Recovery scenarios.