Term
|
Definition
| Redundant Array of Inexpensive Nodes. Each node has its own Linux OS and CentraStar software and utilizes a distributed work load. |
|
|
Term
|
Definition
| Content Address Storage. Used for fixed content. Uses Content Address to store / retrieve object. Centera. |
|
|
Term
|
Definition
1) Efficiently stores content by eliminating storage of duplicate content
2) Scale easily
3) Low admin costs (self-config, self-healing, self-managing)
4) Provides online access with assured content authenticity
5) Guarantee set retention periods
6) WORM (Write Once Read Many)
7) GUID (Globally Unique Identifier) |
|
|
Term
|
Definition
| Uses C-Clip technology. Address is globally unique. |
|
|
Term
| Protected Copy (Mirror or RAID 6 + 1) |
|
Definition
|
|
Term
| Centera Remote Replication |
|
Definition
| Replicates content from local repository to remote repository. Can be unidirectional or bidirectional (copies data in two directions). |
|
|
Term
| Financial Services: SEC Rule 17a-4 |
|
Definition
| Storage media requirements written into SEC (Security Exchange Commission) |
|
|
Term
| Life Sciences: 21 CFR Part 11 |
|
Definition
| Detects altered/compromised records. Content authenticity / integrity checking. |
|
|
Term
|
Definition
| Centera's Content Addressing, time/date stamping and lifecycle integrity checking. Also offers, Data Shredding (ensuring privacy and eliminating liability) |
|
|
Term
|
Definition
| Centera meets HIPPA requirements with: Centera Content Addressing, mirroring, replication, data shredding |
|
|
Term
|
Definition
| Application that runs Centera |
|
|
Term
|
Definition
| Writes client applications. Application store / retrieval requests are sent to Access Node via "public" IP connections. Access Node uses unique Content Address to locate requested information from storage nodes over private internal LAN and gives info back to client via API. |
|
|
Term
| # of Nodes in Centera cabinet |
|
Definition
| 32 w/ minimum configuration containing 8 nodes |
|
|
Term
|
Definition
| Content Protecton Parity. Data is fragmented into 6 segments with a parity segment and each segment a different node. |
|
|
Term
|
Definition
| Content Protection Mirrored. Every data object is mirrored. Each copy resides on different node. |
|
|
Term
|
Definition
| Automatic Transfer Switch. Ensures power is suppolied to the Centera cabinet if 1 of 2 power sources fails. |
|
|
Term
|
Definition
| Minimum of 2 nodes connected to customer's LAN and to storage nodes. Each storage node contains 1+ TB of usable capacity. 2- 48-port cube switches that provide communication bwtn nodes. |
|
|
Term
|
Definition
| used for connecting 3+ cabinets into single cluster |
|
|
Term
| Continuous Content Integrity Checking |
|
Definition
1) Validates integrity of data objects and structures
2) Ongoing background data scrubbing and protection of data
3) Constant authenticity checking to prevent data corruption
4) Automated Garbage Collection |
|
|
Term
|
Definition
| Application Programming Interface. Set of function calls enabling communication btwn applications or app and OS. Facilitates access from app server to Centera cluster. Typical applications that interface with Centera: X-rays, check images, scanned contracts. Part of the Centera SDK (Software Development Kit). Separates actual data (BLOB) from metadata. |
|
|
Term
|
Definition
| Binary Large Object. Actual data without descriptive information (metadata). IT is the DBS. |
|
|
Term
|
Definition
| Distinct Bit Sequence. Represents actual content of a file. Independent of filename and physical location. |
|
|
Term
|
Definition
| Package containing user's data and associated metadata. |
|
|
Term
|
Definition
| Content Address that the system returns to the client. Points to the CDF file which, in turn, contains the CA to retrieve the C-Clip file. |
|
|
Term
|
Definition
| C-Clip Descriptor File. XML file that the API creates when it separates metadata from actual data. This file includes the Content Addresses for all referenceds BLOBs and their associated metadata (C-Clips) |
|
|
Term
|
Definition
| 128-bit. Identifier that uniquely addresses the content of a file and not its location. Unlike location-based addresses, Content Addresses are inherently stable and, once calculated, they never change and always refer to the same content. Calculated from object's binary representation. |
|
|
Term
|
Definition
| Data about data. Describes content, quality, condition, and other characteristics of data. |
|
|
Term
| Message Digest 5-hash algorithm |
|
Definition
| If a single byte changes in the file then MD5 calculation will be different. Creates 128-bit number. Used as Content Address. |
|
|
Term
|
Definition
| Globally Unique Identifier. Industry accepted way to generate identifiers. Can be used with MD5 content address calculation to eliminate chance of collision. Use of is optional and must be set using API mode. |
|
|
Term
|
Definition
1) Client presents data to API to be archived
2) Unique content Address is calculated and inserted into XML file (CDF)
3) Object is sent to Centera via Centera API over IP |
|
|
Term
|
Definition
1) Client presents data to API to be archived
2) Unique Content Address is calculated |
|
|
Term
|
Definition
1) Client presents data to API to be archived
2) Unique content Address is calculated
3) Object is sent to Centera via Centera API over IP
4) Centera validates the CA and stores the object. Ensures content of object has not changed. If data has been modified, new CA will be generated, and object will be stored separately as its own blob. |
|
|
Term
|
Definition
| 5) Acknowledgement returned to application. Returned to API once a mirrored copy of C-Clip Descriptor File (CDF) and protected copy of BLOB have been safely stored in Centera repository. Once data object is stored in Centera repository, API is given a C-Clip ID. |
|
|
Term
|
Definition
| 6) C-Clip ID is a content address of the CDF, which contains CA of actual data on Centera. Using C-Clip Handle/reference, application can read data back from Centera at any time. Where data is stored on Centera is transparent to application. There is no centralized directory, pathnames, or URLs. |
|
|
Term
|
Definition
1) Object is required by user/ app
2) Application queries local table of C-Clip IDs and locates C-Clip ID for needed objects |
|
|
Term
|
Definition
3) Using Centera API, request is sent along with C-Clip ID to the Centera
4) Centera delivers requested info to application which, in turn, delivers to the client. |
|
|
