Confidentiality Notice
The ideas and designs set forth in this document are the property of DryvIQ and may not be disseminated, distributed, or otherwise conveyed to third persons without the express written permission of DryvIQ

DryvIQ , Inc.

PO Box 546 A2 | Ann Arbor, MI 48106 | 888.550.3721

Contact

For more information regarding DryvIQ Platform Infrastructure & Hardware Considerations, please contact:
info@dryviq.com

Content

Infrastructure Recommendations

Hardware	Recommendations
DryvIQ Processing Server {#} of Server(s) required	CPU cores: 8 RAM: 32GB (minimum) OS disk: 500GB (minimum) OS: Windows Server 2016 or higher If using a cloud server, the following templates are recommended: AWS: 2xlarge Azure: D8S_V3 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.
DryvIQ SQL Database Server {#} of Database Server(s) required 1 per server farm	CPU cores: 16 RAM: 64GB (minimum) OS_Vol: 100GB+ SSD – redundant / fault tolerant OS: Windows Server 2016 Data_Vol1: 1TB premium SSD Data_Vol2: 1TB premium SSD (optional) Software/templates: SQL Server 2016 SP1 (or higher) enterprise If using a cloud server, the following templates are recommended: AWS: 4xlarge Azure: D16S_V3
Supported Operating Systems	Windows Server 2022 Windows Server 2019 Windows Server 2016
Supported Databases	Database Embedded PostgreSQL 10.10-2+ SQL Server 2016 SP1 (or higher)
Supported Browser	Goggle Chrome
Communication Ports	Communication with the following: Port 9090: To access the DryvIQ web interface or REST API, port 9090 will need to be opened on the DryvIQ server. If there are multiple DryvIQ servers in a cluster, port 9090 only needs to be opened on one of them. It is also possible to use RDP to connect to a DryvIQ server to facilitate access to the web interface and REST API without having to open port 9090 on the firewall of any DryvIQ servers. Port 1433: Communication with SQL Server portalarchitects.com for DryvIQ License Acquisition API Ports for Cloud Storage Platforms
Application services/processes	Allow List: Skysync.exe

Security Requirements

DryvIQ Platform requires a service account with interactive login rights.
Local admin on the DryvIQ Processing Server(s)
Database Owner (DBO) access to DryvIQ database
Transfer account passwords used by the DryvIQ Platform should be set to not expire
The DryvIQ Platform will need Administrative access to the source and destination storage systems.
- DryvIQ will need the username and password, so any validation/investigation can be done.
Allow api.portalarchitects.com for DryvIQ License Acquisition.
Application Services/Processes Allow List: skysync.exe

Architecture Firewall/Communication Port Requirements

Port 9090 will need to be opened for communication between servers, when more than one DryvIQ Processing Server is used.
Port 1433: Communication with SQL Server
From the DryvIQ server, access the storage platform/repositories should be opened for normal traffic, including HTTP (80) and HTTPS (443).
For best results for data migrations that reside on premise, DryvIQ servers should be installed or co-located in the same data center to reduce latency of source data access.

DryvIQ Service Account

These are the general account best practices when running a DryvIQ Platform clustered install.

Create a service account (DryvIQ User) whose password does not expire.
Ensure you have an Admin/Power User account who has full access to both sides (Source and Destination).
Ensure you are able to get to api.portalarchitects.com from the server.
For Office 365/OneDrive for Business and Box, all users have to be provisioned.
For Office 365/OneDrive for Business, the DryvIQ Transfer account(s) have to be added to Site Collection Administrator of each and every user.

Proxy Server

DryvIQ supports proxy server environments and utilizes the proxy settings from the underlying host Operating System; however, additional prerequisites may be necessary for a fully functional implementation. Note that proxy servers may introduce some latency in the transfer process. If a proxy is utilized, ensure that the DryvIQ servers have the manual proxy setup configured correctly. Proxy server environments add a layer of complexity and additional management that may impact troubleshooting, rate limiting, and overall performance.

Log in to DryvIQ server(s) with the DryvIQ Service Account.
Go to Windows Settings > Proxy Settings.
Enable the "Use a proxy server..." setting.
Update the Address and Port with the applicable proxy values.
Select Save.

Remote Desktop Access

The Consultative Services team will require Remote Desktop Access to the DryvIQ servers for setup, configuration, and monitoring of the system during the Transfer Management phase.
Access via direct RDP access or via VPN
Admin level rights to the server(s) to install and configure
Provide DryvIQ access to the username and password/admin-level access rights to the DryvIQ servers for setup, configuration, and monitoring of the system.

Screen Sharing Control (Optional)

DryvIQ requests a resource that allows our team to leverage screen sharing control with an online meeting service, such as Microsoft Teams or Go to Meeting, so DryvIQ can perform the installation and configuration of the DryvIQ platform.

User-Account Mapping Files

The mapping files are used for two steps in the transfer process:
1) Identifying the users/groups that will be migrated
2) Mapping source accounts to destination accounts.
Mapping file(s) that identify the users source account information and their new destination account must be provided.
DryvIQ recommends gathering this information from Active Directory, if possible.
Accounts must be created and provisioned on the destination platform prior to migration.
Group(s) must be already exist on the destination for the mapping to be successful.

Further information can be found:

Job Mapping Files

The DryvIQ Platform will need a file that maps the users accounts to the specific location as defined by Client. For example:
* User A on Box will need to be mapped to a specific OneDrive location.
* User B on Box will need to be mapped to a specific SharePoint Site location.
A sample .csv file can be provided by the Consultative Services team.

Download Recommended Tools

Web Browser | Google Chrome

Download the following https://www.google.com/chrome/browser-features/?xpv=3 to the server where DryvIQ will be installed.

REST API Tool | Postman

Download the following https://www.postman.com/downloads/ to the server where DryvIQ will be installed.
The DryvIQ Consultative Services team will configure Postman during our installation session.

Account Provisioning

Accounts must be created and provisioned on the destination platform prior to migration.

File Transfer Performance

All cloud-service platforms have both API-call and throughput rate limits. They can vary from tenant to tenant, time of day, as well as other factors that are solely controlled by the platform vendor(s). These limits can significantly impact DryvIQ file transfer speeds. DryvIQ understands the limitations of these platforms and will monitor the migration to ensure throughput is optimized and may request additional hardware, if needed to meet the project timeline.
If hardware recommendations made by DryvIQ (both database and the DryvIQ application servers) are not feasible to be implement by the Client, transfer performance and timelines could be impacted. DryvIQ will request a specific number of servers at the beginning of the migration. If throughput numbers are lower than expected due to each platform vendor, DryvIQ may request additional servers to preserve project timelines.
The DryvIQ architect will tune the system at the beginning of each wave migration and will ensure optimal throughput is achieved throughout the duration of the migration.
The Client will be responsible for ensuring the availability and stability of the network where the hardware is provisioned. Latency with internet connections or bandwidth can impact file transfer performance. If latency issues occur, the DryvIQ architect will work with the Client's team to resolve.

Browser not supported