DryvIQ is an Enterprise Content and Data Integration platform capable of managing file/data transfer and synchronize operations across a myriad of different storage management platforms at scale. It offers significant business flexibility around all aspects of Enterprise Content and Data Integration including:
Large-scale file migration
Enterprise file analysis
Classification, compliance, and actions/outcome management
The DryvIQ platform is built on a pluggable, content–streaming architecture that enables highly–automated file/data transfer and synchronization capabilities for up to billions of files. File bytes stream in from one connection endpoint (defined by the administrator), across a customer owned and operated network and/or cloud service, and then stream out to a second connection endpoint. Content can also flow bidirectionally across two endpoints rather than solely from a "source" to a "destination."
DryvIQ is a "security–neutral" model, fully utilizing your existing infrastructure and security schema. Content and data bytes only exist in DryvIQ memory in chunks, which are immediately streamed from one endpoint (through DryvIQ) and out to another endpoint. Both incoming and outgoing bytes are transferred using the most secure protocol available for each connector. For example, DryvIQ will use SSL or TLS encryption along with OAuth (token–based) authorization for most cloud service connectors.
DryvIQ Platform Components
The server component of DryvIQ runs as a background service on at least one server. The DryvIQ service can also be deployed on multiple server nodes in a cluster.
DryvIQ utilizes an embedded PostgreSQL database as part of its standard installation process. Additional options include Microsoft SQL Server or hosted PostgreSQL. DryvIQ requires network connectivity with the database to function properly in all cases.
DryvIQ's Platform Connectors provide storage endpoint integration. Each storage connector has been carefully developed to implement all of the available security features via its native API. The connectors themselves can be deployed to execute in the context of the primary DryvIQ Server or in the context of one or more DryvIQ Remote Sites depending on the deployment model selected.
DryvIQ stores connection information such as the authenticated security token, URL, and UNC, and in some cases such as network file–shares, the user name and password are encrypted within the database. DryvIQ Connectors utilize all the default ports based on the platform's required communication protocol.
Security White Paper
DryvIQ Platform | Security Whitepaper
Scalability and Performance White Paper
DryvIQ Platform | Scalability and Performance Whitepaper
Region Settings must be set to English (United States).
Go to Control Panel > Clock and Region.
Select Region > Administrative tab.
Select Change system locale.
Set current system local to "English (United States)"
DryvIQ Processing Servers (1 - 10 per server farm)
DryvIQ servers should be installed in the same data center as the data repository or as close to the source as possible to reduce latency.
SQL Server Database Server (1 server per farm or availability group)
CPU cores: 16
RAM: 64GB (minimum)
OS_Vol: 100GB+ SSD – redundant/fault tolerant
OS: Windows Server 2016 or higher
Data_Vol1: 1TB premium SSD
Data_Vol2: 1TB premium SSD (optional)
Software/templates: SQL Server 2016 SP1 (or higher) enterprise
Supported Operating Systems
Server/Manager and Remote Sites
Windows Server 2019
Windows Server 2016
Server/Manager and Remote Sites
Supported: Google Chrome
Unsupported: Mozilla Firefox, Microsoft Edge, Microsoft Internet Explorer, and Safari
Administrator Password Requirements
Passwords must meet the following requirements:
At least 8 characters
No more than 64 characters
At least one uppercase letter (A-Z)
At least one digit (0-9)
At least one non-alphanumeric character (!@#$%)
Cannot contain the username
DryvIQ Platform Application
The DryvIQ Platform is a North American Language-based software solution that supports Unicode; however, it is neither localized or internationalized. In order to support our international customer base, we recognize that support for non-English language is required. As such, we have made significant investments in developing a solution that accepts and migrates a vast majority of data for most languages. While we continue to make added investments to ensure our solution will enable the migration of non-English language files and folders, it cannot account for all idiosyncrasies/caveats.
DryvIQ strongly recommends leveraging the following tools: