1. CONFIDENTIAL Overview NTP Software Object Store and Cloud Connector™ (OSCC™) has a carefully structured architecture that includes a number of collaborative components Some elements are core (such as the ODDM file movement engine), and some elements are optional. Still others, such as the source and destination connectors, are not optional but exist in multiple versions The net result is policy and/or user-driven any-to-any file movement and the foundation for cloud and mobile access

2. CONFIDENTIAL The Heart of OSCC At the heart of OSCC are 3 key elements: 1. The file movement engine (ODDM). ODDM holds certain core configurations and policies and is responsible for orchestration of all file movement 2. A SQL Server database. The database contains additional configuration information, metadata for files managed by OSCC, and a record of all activity 3. A messaging engine that communicates with end-users and system administrators

3. CONFIDENTIAL Storage Host Connectors Source connectors Tightly integrated with certain source devices and their OSes (FAS, VNX, HDS, Windows, etc…) by way of proprietary interfaces and file system extensions developed by the OS provider Generic connectors for almost all other sources May use a local policy (e.g.: create, quota, data type, etc…) to trigger file movement Can create one of several types of stubs Destination connectors Integrated with the destination device May repackage the source file to fit the constraints of the destination (e.g.: Windows alternate streams on tape)

4. CONFIDENTIAL Optional Components Right-Click Archiving™ (RCA) – Using Windows Explorer or a web-based UI, an end-user selects files or directories and tells OSCC to move them. (Policies within OSCC may cause the files to be moved later and not right away.) Application-Based File Movement (ABFM) – by calling an OSCC API library, applications cause OSCC to move files, directories, or project data Web Portals – in the case of an infrastructure failure, OSCC supplied web portals provide administrators and end-users an alternative access method to managed objects and systems

5. CONFIDENTIAL Optional Cloud Connector Connects source and destination environments to private and public clouds, and/or Microsoft SharePoint, creating a seamless environment Moves objects into or out of the cloud based on policy or service requests Maintains synchronization between the cloud and the file/object stores Unifies the entire environment for tasks such as search or indexing

6. CONFIDENTIAL OSCC Tiering Fundamentals Share / export based Triggered by events, users, age, pretty much anything at all Configuration down to the level of individual files Nearly any source to almost all destinations, connected as: one-to-one, one-to-many, many-to-one, many-to-many Includes LTFS tape as a full participant Has 3 stubbing strategies to accommodate different environments Can reconcile / rebuild / move stubs, if needed

7. CONFIDENTIAL OSCC Refinements Can enhance, capture new, and/or extend metadata as files are moved Provides a web portal as an alternate access mechanism for object stores Maintains a SQL database for convenient reporting When the target is an object store, can snapshot the SQL database to the object store (full recovery from just the object store) Integrated with NTP Software File Reporter™ for reporting and billing Fully integrated with Microsoft SharePoint

8. CONFIDENTIAL In Summary OSCC seeks to include all of the top-tier storage hosts as sources and destinations With its 3 different stubbing strategies, OSCC allows end-users to reconnect with their files without adding risk to your environment OSCC fully exploits and augments the capabilities of object stores And sets the stage for universal access in a BYOD environment