/
User Migration Guides | Network File Share to Dropbox for Business

User Migration Guides | Network File Share to Dropbox for Business

 

 

 

PRINT TO PDF

 

 

Contents

Introduction 

DryvIQ is an enterprise data integration platform that enables organizations to maximize business value and productivity from their content.  It connects disparate storage platforms and business applications together, allowing organizations to move, copy, synchronize, gather, and organize files as well as their related data across any system. DryvIQ empowers your users with unified access to the most relevant, complete, and up-to-date content—no matter where it resides.    

DryvIQ delivers a user-friendly, web-based experience optimized for PC, tablet, and mobile phone interfaces, so you can monitor and control your file transfers anywhere, from any device.   

DryvIQ’s true bi-directional hybrid/sync capabilities enable organizations to leverage and preserve content across on-premises systems and any cloud service. Seamless to users, new files/file changes from either system are automatically reflected in the other.  


How does DryvIQ Work? 

Cloud storage and collaboration platforms continue to be the driving force of digital transformation within the enterprise. However, users need to readily access the content that resides within your existing network file systems, ECM, and other storage platforms—enabling them to be productive, wherever they are.  DryvIQ is purpose-built to provide boundless enterprise content integration possibilities. The DryvIQ Platform is 100% open and provides a highly-scalable architecture that enables enterprises to meet evolving technology and user demands—no matter how complex. 

The DryvIQ platform provides: 

  • A low risk approach to moving content to the cloud while maintaining on-premises systems

  • No impact to users, IT staff, business operations, or existing storage integrations

  • The ability to extend cloud storage anywhere/any device capabilities to locally-stored content

  • Easy integration of newly acquired business storage platforms into existing infrastructures

The Engine 

DryvIQ’s bi-directional synchronization engine enables your enterprise to fully-integrate and synchronize your existing on-premises platforms with any cloud service. It empowers your users to freely access the content they need while IT staff maintains full governance and control. DryvIQ integrates with each system's published Application Program Interface (API) at the deepest level—optimizing transfer speeds and preserving all file attributes. 

Security 

DryvIQ’s 100% security-neutral model does not incorporate or use any type of proxy cloud service or other intermediary presence point. All content and related data is streamed directly via HTTPS [256-bit encryption] from the origin to the destination system(s). Additionally, DryvIQ works with native database encryption. For more information, please see DryvIQ Platform | Security Whitepaper

Analyzer | Simulation Mode

The DryvIQ analyzer is a powerful enterprise file transfer simulation that eliminates the guesswork. You will gain granular insight into your entire content landscape including its structure, usage, age, type, applicable metadata, and more no matter where the files are located (in local storage, remote offices, or on user desktops). 

Simulation mode allows you to create a job with all desired configuration options set and execute it as a dry-run. In this mode, no data transfers, no permissions are set, and no changes are made to either the source or the destination. This can be useful in answering several questions about your content prior to running any jobs against your content.

Command and Control 

Via highly-advanced web, DryvIQ Command-line Interface (CLI), RESTful API, and/or .NET interfaces, DryvIQ administrators can easily integrate systems, control interactions and behaviors, or create and control end-user experiences for advanced self-service capabilities. 

Features and Functionality 

The DryvIQ Platform enables you with complete integration and control over: 

  • User accounts 

  • User networked home drives 

  • User and group permissions 

  • Document types, notes, and file attributes 

  • Timestamps 

  • Versions 

  • Departmental, project, and team folders 

  • Defined and custom metadata 

Architecture and Performance 

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) and across a customer-owned and operated network and/or cloud service. They are then streamed out to a second connection endpoint. Content can also flow bidirectionally across two endpoints rather than solely from an "origin" to a "destination."

Supported Features

The DryvIQ Platform Comparison tool allows you to compare platform features and technical details to determine which are supported for your transfer scenario. Viewing the Platform Comparison results for your integration will display a list of features of each platform and provide insight early in the integration planning process on what details may need further investigation.

The Platform Comparison tool is available through the Platforms menu options. For further information, see Platform Comparison.

Connection Setup

DryvIQ is built on a concept of connections. A connection is made to the source platform, and another connection is made to the destination platform. A job is created to tie the two platforms together. When DryvIQ connects to a content platform, it does so by using the publicly available Application Programming Interface (API) for the specific platform. This ensures DryvIQ is “playing by the rules” for each platform. 

Connections “connect” to a platform as a specific user account. The user account requires the proper permissions to the platform to read, write, update, and/or delete the content based on the actions the DryvIQ job is to perform. The connection user account should also be set up so the password does not expire; otherwise, the connection will no longer be able to access the platform until the connection has been refreshed with the new password. Most connections require a specific user account and its corresponding password. The user account is typically an email address. 

Authenticated Connections

Authenticated Connections are accounts that have been verified with the cloud-based or network-based platform when created. The connection can be user/password-based or done through OAuth2 flow, where a token is generated based on the granting authorization to DryvIQ through a user login. This authorization allows DryvIQ access to the user's drive information (files and folder) on the platform. These connections are used as the source or the destination authentication to transfer your content.

 

OAuth2 Interactive (Web) Flow

Connectors such as Box, Google Drive, and Dropbox use the OAuth2 interactive (or web) flow.

 

OAuth2 Client Credentials Flow

Connections such as Syncplicity and Google Workspace uses the OAuth2 client credentials flow.

 

SharePoint

SharePoint (all versions, CSOM) uses a custom username/password authentication model.


OAuth2 Interactive (Web) Flow

You will need the following information when creating a connection to Network File System, Box, Dropbox, and Dropbox for Business:

  • A name for the connection

  • The account User ID (such as jsmith@company.com)

  • The password for the User ID.

Create Connections

Creating a connection in the DryvIQ Platform user interface is easy! Simply add a connection, select your platform, and enter the requested information. DryvIQ will securely validate your credentials and connect to your source content. 

Network File Share (NFS)

The NFS connector in DryvIQ has specific permission-related requirements beyond that of the connector Identity. Additional configuration may be needed to allow DryvIQ to use of the NFS Connector. 

Prepare a DryvIQ Manager Service account 

When a DryvIQ Job runs, it is the DryvIQ Manager Service that is connecting to and accessing the content on the NFS platform.  Therefore, the DryvIQ Manager Service needs to be running as a domain account that has the proper permissions to access the content that will be managed by DryvIQ.  

Review the DryvIQ Manager/Server Installation documentation to learn about Configuring DryvIQ and pay particular attention to the Configure Windows Service section.

For proper job function, the account requires Read, Write, Update and Delete privileges.

 

SQL Server (Optional)

SQL Server (Optional)

You can optionally create the database before running the installer:

  1. Log into SQL Server Management Studio.

  2. Create a new database.

    • Set the name appropriately, ie. DryvIQV4.

    • Do not select an owner.

    • Set the recovery mode to simple.

    • Add the Windows Service Account User to the database.

      • Security > Logins > {Windows Service Account User} > properties > Server Roles > dbcreator or sysadmin

      • Security > Logins > {Windows Service Account User} > properties > User Mapping > DryvIQV4 > db_owner

*Please see the following documentation: DryvIQ Platform | Infrastructure & Hardware Considerations

Prepare Source environment  

  • Create a Windows domain user account that will be used for the migration and grant main admin privileges to that user on the file server.

  • Ensure the account used to create the NFS Connector has all necessary permissions to edit, copy, delete, and create files and folders.

  • If using IP, ensure that the IP is static and will not change.

Create an NFS Connection

  1. Select Connections > Add connection.

  2. Select Network File Share as the platform on the Add connection modal.

  3. Enter the connection information. Reference the table below for details about each field.

  4. Test the connection to ensure DryvIQ can connect using the information entered.

  5. Select Done.

 

 

Field

Description

Required

Field

Description

Required

Display as

Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists.

If you do not add a display name, the connection will automatically be assigned a default name. 

Optional

UNC Path

Enter the UNC path for the connector. The UNC path will be to a folder at least 1 level off the root of the server, for example: \\<server name>\<folder on server>

You can also use the server IP address, for example: \\<ipaddress>\<folder on server>

You can locate the information by going to Windows>Control Panel>System and Security>System.

Required

User Name

Enter the user name for the administrator account. You should leave this field blank if you are using integrated authentication.

This needs to be an account with authority to access the content you will to process.

*When creating a NFS connection with a UNC Path containing unicode characters (i.e. \\test\あああ), User Name and Password are REQUIRED.

Optional*

Password

Enter the password for the administrator account. You should leave this field blank if you are using integrated authentication.

*When creating a NFS connection with a UNC Path containing unicode characters (i.e. \\test\あああ), User Name and Password are REQUIRED

Optional*

Features and Limitations 

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Utilize the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.

  • The maximum length of any folder or file name is 32767

  • The maximum path length is 32767

  • No trailing spaces in folder names, file names, or file extensions

  • No trailing periods

  • Any non-printable ASCII characters will not be filtered by DryvIQ

  • Restricted characters in the file name: < > : " / \ | ? *

  • When creating a Connector, it must be one level down from the root. Example, C:/1st folder

Author Preservation | Windows Only

  • Author Preservation for Network File Share is only supported for Windows only.

  • The NFS account owner can be identified in Properties → Security → Advanced → Advanced Security Settings.

  • Verify the Windows environment has long path support enabled.

    • (Local Computer Policy → Computer Configuration → Administrative Templates → All Settings → Enable Win32 long paths).

    • Refer to Microsoft's Maximum Path Length Limitation documentation for more information. 

.net core supports long paths, however functions that retrieve permissions for individual files still use old Win32 system calls. Long path support with these functions is not enabled by default.
Without long path support enabled, you will see the exception ‘invalid parameter: name’ in the log file or in the application user-interface log tab when attempting to get permissions on files with long paths.

Permissions

When applying permissions to FS/NFS, DryvIQ sets read access permission to "Read and Execute" rather than just "Read."

NFS Connection Troubleshooting for Microsoft Windows

When DryvIQ is running on Microsoft Windows, there are some nuances that may affect creating an NFS connection.

Multiple NFS Connections

You cannot create multiple connections to the same location UNC path and multiple users when DryvIQ is running on Windows. The connection creation will fail for the second user because the DryvIQ application uses an underlying Windows mechanism that requires unique names for each connection. If a connection to the same location but different user is needed, a workaround is to use the domain name in the UNC path for one connection and the IP address in the UNC path for the second connection.

Failed Connection Tests after Correcting Username or Password

There is an underlying Microsoft Windows issue that can cause issues when creating NFS connections. If an attempt is made to create a new NFS connection using an invalid username/password. The connection test will fail, which is expected behavior. Immediately entering the correct username/password may still result in a failed connection test even though it should pass. To prevent this issue, wait about 15 seconds after entering the correct username/password before running the connection test. The extra time allows Windows time to clear out the incorrect credentials and recognize the correct ones that were provided.

NFS Connection Troubleshooting for Microsoft Windows

When DryvIQ is running on Microsoft Windows, there are some nuances that may affect creating an NFS connection.

Multiple NFS Connections

You cannot create multiple connections to the same location UNC path and multiple users when DryvIQ is running on Windows. The connection creation will fail for the second user because the DryvIQ application uses an underlying Windows mechanism that requires unique names for each connection. If a connection to the same location but different user is needed, a workaround is to use the domain name in the UNC path for one connection and the IP address in the UNC path for the second connection.

Failed Connection Tests after Correcting Username or Password

There is an underlying Microsoft Windows issue that can cause issues when creating NFS connections. If an attempt is made to create a new NFS connection using an invalid username/password. The connection test will fail, which is expected behavior. Immediately entering the correct username/password may still result in a failed connection test even though it should pass. To prevent this issue, wait about 15 seconds after entering the correct username/password before running the connection test. The extra time allows Windows time to clear out the incorrect credentials and recognize the correct ones that were provided.

Create Connection | REST API

{    "name": "\\\\{{Your Machine Name}}\\{{Your NFS Directory or Folder}}",    "platform": {          "id": "nfs"    }, "auth": {      "unc": "\\\\{{Your Machine Name}}\\{{Your NFS Directory or Folder}}"       } }

Dropbox for Business

The Dropbox connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files to your Dropbox account from cloud storage repositories and on-premise network file shares. The first step is to create the Dropbox connection by providing the connection information required for DryvIQ to connect to the server. The connector can be created using a standard Dropbox account or a Dropbox for Business account. However, when creating a connection using a Dropbox for Business account, you must use an Administrator account. Standard accounts will return an error from the Dropbox for Business platform. 

 

For more information on using a standard Dropbox account, please refer to the Dropbox connector page.

Create Connection | User Interface

  1. Select Connections > Add connection.

  2. Select Dropbox for Business as the platform on the Add connection modal.

  3. Enter the connection information. Reference the table below for details about each field.

  4. Select Sign in with Dropbox for Business.

  5. On the Dropbox API Request Authorization modal, enter the Email and Password required to log in to the account and select Sign In. Only an Administrator account can be used for Dropbox for Business. Standard accounts will return an error from the Dropbox for Business platform.

  6. Select Allow when prompted to authorize the connection.

  7. You will see a "Connection test succeeded" message on the Add connection modal. (If you don't see this message, repeat the sign in and authorization steps above.)

  8. Select Done to finish creating the connection. 

 

Add Connection Modal - Dropbox for Business

 

 

Field

Description

Required

Field

Description

Required

Display as

Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists.

If you do not add a display name, the connection will automatically be named, "Dropbox for Business." DryvIQ recommends that you edit the name to more readily identify the connection. 

Optional

Platform API client credentials

Required

Use the system default client credentials

Select this option to use the default DryvIQ client application.

 

Use custom client credentials

Select this option to use custom client credentials provided by your administrator. When selected, two additional fields will be available to enter the credentials.

 

Client ID

This field displays only when you select Use custom client credentials. This value will be provided by your administrator.

Required when using custom credentials

Client Secret

This field displays only when you select Use custom client credentials. This value will be provided by your administrator.

Required when using custom credentials

 

Dropbox API Request Authorization modal

 

 

Allow Access to Dropbox 

 

 

Connection Test Succeeded

 

Features and Limitations 

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Utilize the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.

Files and Folders

Below is list of Dropbox's supported and unsupported features as well as additional file/folder restrictions. 

Supported

Unsupported

Other Features/Limitations

Supported

Unsupported

Other Features/Limitations

Version preservation

File lock propagation

Invalid characters

< > \\ / : ? * \ | ~

Timestamp preservation

Mirror lock ownership

File size maximum: 50 GB or smaller
All file uploads must be smaller than the account storage space.

Author/Owner preservation

Restricted types

Path length maximum: n/a

Account map

Tags map

Segment path length: 255

Group map

 

Maximum number of files per folder: 10,000

Permission preservation

 

No trailing spaces after file extensions

User impersonation

 

 

Metadata map

 

 

 

Author Preservation

The Dropbox connector uses "per-request impersonation." This means DryvIQ makes requests to the platform on behalf of the account owner, not the administrator. Therefore, files created by other users will fail to upload unless the account owner mounts the shared parent folder into their Dropbox drive before uploading the file. (See How to join a shared folder  for more information.) Failed uploads will be logged with a message similar to the following example: "[PermissionFailure] The account 'Joe Smith' is not authorized to perform the requested operation."

Business Team Folders

Team folders transfer automatically with any transfer job; however, Team and Shared folders must first be mounted in Dropbox (Dropbox for Business API only surfaces mounted Team and Shared folders). If you include Job Filters | Filter Shared Content, Team Folders will not be transferred. The Dropbox for Business connector creates shared user folders by default.  To create shared folders in a Team Folder, the root Team Folder must be created in the Dropbox UI and selected as the root of the job. Shared folders that are created in a Team Folder support permission disinheritance.  Shared folders created in a user folder do not support disinheritance and will log a warning.

Character Sanitization

DryvIQ will sanitize file names that contain combined Unicode characters by replacing the characters with an underscore (_).

Dropbox Paper

DryvIQ does not support Dropbox paper. Dropbox Paper is a separate work space that stores Paper documents in your account on http://paper.dropbox.com . DryvIQ doesn't support have access to these documents as part of your Dropbox connection. 

Path Lengths

Dropbox does not impose restrictions for the total path length.

Segment path lengths are limited to 255 character. Segments are delimited by a forward slash (/). For example, <max 255 characters>/<max 255 characters>.

Versioning

The Dropbox platform treats content version history differently than other cloud platforms, with each native move and rename tracked as a new version. In order to only transfer true version history, enable the Scripting option on step 6 during job creation and copy the following JSON into the scripting box:

{ "transfer": { "versioning": { "preserve": "native", "select": "published" } } }

 

 

For more information about how to use Advanced Scripting, refer to the Advanced Scripting | Additional Configuration Options page.

 

Version Limits

While Dropbox allows you to store unlimited versions, the platform restricts version downloads to 100. This means only the most recent 100 versions for a given file will be transferred to the destination. Refer to the Dropbox API Documentation for more information.  You can also find additional information in the Dropbox Forum.

 

If you want to transfer just teams folders, you can use the Dropbox for Business Teams Folders connector to create a connection that will transfer only teams folders. 

 

Create Connection | REST API

Create a New Dropbox for Business Connection

The following GET will return a target URL. Use this URL to log in to the Dropbox for Business account to authenticate and create the connection. Make sure you connect using an Administrator account. 

GET {{url}}v1/connections/platforms/dfb/new

 

Create a New Dropbox for Business Connection Using Custom Credentials

Create a new connection using custom credentials with the example call below. Replace the name, client_id, and client_secret with information relevant to your connection. 

{ "name": "Dropbox for Business", "platform": { "id": "dfb" }, "auth": { "client_id": "{{clientID}}", "client_secret": "{{clientSecret}}" } }

 

Dropbox for Business with Single Sign-On (SSO)

Create a new connection using single sign-on with the example call below. You will need to obtain the applicable access token for your Dropbox for Business account.

{ "name": "Dropbox for Business", "platform": { "id": "dfb" }, "auth": { "access_token": "{{access_token}}" } }

 

Create Job | Dropbox for Business Account Admin Connection

Create a simple transfer job using the example call below. Replace the information with information relevant to your job and connectors. 

Note that the following are known issues when creating a job for a Dropbox for Business account using an Administrator account connection.

  • Connection-based Impersonation should be used due to a caching issue which may incorrect shared folder detection

  • Connection-based Impersonation is shown in the user-interface as "Run As...." option on the Locations step when creating a new job.

  • Path-based impersonation should not be used, first 'folder' is a user name such as "path": "/user@company.com/"

 

{ "name":"Simple Job", "kind": "transfer", "transfer": { "transfer_type": "copy", "source": { "connection": { "id": "{{DropboxForBusiness_Admin_ConnectionID}}" }, "impersonate_as": { "email": "user@company.com" }, "target": { "path": "/sourceFolder" } }, "destination": { "connection": { "id": "{{OneDriveForBusiness_connection_destinationID}}" }, "target": { "path": "/Documents/destinationFolder" } }, "simulation_mode": false }, "schedule": { "mode": "manual" }, "stop_policy": { "on_success": 5, "on_failure": 5, "on_execute": 25 }, "category": { "name": "Report Category {Name}" } }

Transferring Dropbox for Business Team Folders

  • Team folders will transfer automatically with any transfer job; however, Team and Shared folders must first be mounted in Dropbox (Dropbox for Business API only surfaces mounted Team and Shared folders)

  • If you include Job Filters | Filter Shared Content, Team Folders will not be transferred

  • The Dropbox for Business connector creates shared user folders by default.  To create shared folders in a Team Folder, the root Team Folder must be created in the Dropbox UI and selected as the root of the job.

  • Shared folders that are created in a Team Folder support permission disinheritance.  Shared folders created in a user folder do not support disinheritance and will log a warning.

 If you want to transfer just teams folders, you can use the Dropbox for Business Teams Folders connector to create a connection that will transfer only teams folders. 

Connection Pooling

When transferring data between a source and destination, there are a number of factors that can limit the transfer speed.  Most cloud providers have rate limitations that reduce the transfer rate, but if those limits are account based and it supports impersonation, DryvIQ can create a pool of accounts that issues commands in a round-robin format across all the accounts connected to the pool. Any modifications to the connection pool will used on the next job run. 

For example, if a connection pool has two accounts, all commands will be alternated between them. If a third account is added to the pool, the next run of the job will use all three accounts.

 

Connection pooling is not supported with My Computer and Network File System (NFS) connection.

 

User and Group Maps 

A user account or group map provides the ability to explicitly associate users and groups for the purposes of setting ownership and permissions on items transferred. These mappings can happen automatically using rules or explicitly using an exception.  Accounts or groups can be excluded by specifying an exclusion, and unmapped users can be defaulted to a known user.  For more information, see Permissions | Account Map / Group Map.

Here are a few things to consider when creating an account or group map: 

  • A source and destination connection are required and need to match the source and destination of the job that will be referencing the user or group map. 

  • A map can be created before or during the creation of the job. 

  • A map can be used across multiple jobs. 

  • Once updated, the updates will not be reapplied to content that has already been transferred. 

User and Group Map Import Templates

Please see Account Map / Group Map | CSV File Guidelines for map templates and sample downloads. You can use these samples to help you build you own mapping files.

User & Group Map Exceptions

A user or group map exception provides the ability to explicitly map a specific user from one platform to another. These are exceptions to the automatic account or group mapping policies specified. User account or group map exceptions can be defined during the creation of the map or can be imported from a comma-separated values (CSV) file. See Account Map / Group Map | Exceptions for more information.

You can import the mappings using a CSV file.

 

You can manually create a map by selecting the user on the source and the corresponding user on the destination.

 

User and Group Map Exclusions

A user or group map exclusion provides the ability to explicitly exclude an account or group from owner or permissions preservation. User account or group map exclusions can be defined during the creation of the map or can be imported from a comma-separated values (CSV) file. See Account Map / Group Map | Exclusions for more information.

Import the exclusions or manually create them.

Transfer Planner 

 At the start of a project, it is common to begin planning with questions like "How long should I expect this to take?" Transfer Planner allows you to outline the basic assumptions of any integration, primarily around the initial content copy at the beginning of a migration or first synchronization.  It uses basic assumptions to begin visualization of the process without requiring any setup of connections or jobs. 

The tool estimates and graphs a time line to complete the transfer based on the information entered in the Assumptions area. The timeline assumes a start date of today and uses the values in the Assumptions section to model the content transfer.  The window displays projected Total Transfer in dark blue and Daily Transfer Rate in light blue. Hovering the mouse pointer over the graph displays estimated transfer details for that day. The timeline recalculates if you change any of the values, making simple “what if?” scenario evaluations. If necessary, you can reset the timeline to display the default values for the transfer planner tool. 

Note that the Transfer Planner is primarily driven by the amount of data needing to be processed. DryvIQ has various tools for transferring versions of files (if the platform supports this feature), which can increase the size of your data set. It also has the ability to filter out specific files by their type or by other rules you set. At this stage, a rough estimate of total size is recommended as it can refined later using Simulation Mode.

Simulation Mode

Simulation mode allows you to create a job with all desired configuration options set and execute it as a dry-run. In this mode, no data transfers, no permissions are set, and no changes are made to either the source or the destination. This can be useful in answering several questions about your content prior to running any jobs against your content.

 

How much content do I have?

An important first step in any migration is to determine how much content you actually have since this can help determine how long a migration will take.

 

What kinds of content do I have?

Another important step in any migration is to determine what kinds of content you actually have. Many organizations have accumulated a lot of content, and some of that may not be useful on the destination platform. The results of a simulation mode job can help you determine if you should introduce any filter rules to narrow the scope of the job. An example would be if you should exclude executable files (.exe or .bat files) or exclude files older than 3 years old.

 

What kinds of issues should I expect to run into?

During the course of a migration, there are many things to consider and unknown issues that can arise, many of which will only present themselves once you start doing something with the source and destination. Running a job in simulation mode can help you identify some of those issues before you actually start transferring content. Examples can include:

  • Are my user mappings configured correctly?

  • Does the scope of the job capture everything I expected it to capture?

  • Do I have files that are too large for the destination platform?

  • Do I have permissions that are incompatible with the destination platform (i.e. ACL vs waterfall)?

  • Do I have files or folders that are too long or contain invalid characters that the destination platform will not accept?

Creating a Simulation Job

During the last stage of the job creation process, you have the option to enable simulation mode. When a job is in simulation mode, it can be run and scheduled like any other job, but no data will be transferred. 

 

 

Transitioning a Simulation Job to Transfer Content

After review, a simulation job can be transitioned to a live job that will begin to transfer your content to the destination platform.

 

Creating a Job

DryvIQ delivers a user-friendly, web-based experience optimized for PC, tablet, and mobile phone interfaces, so you can monitor and control your file transfers anywhere, from any device.

DryvIQ’s true bi-directional hybrid/sync capabilities enable organizations to leverage and preserve content across on-premises systems and any cloud service. Seamless to users, new files/file changes from either system are automatically reflected in the other.  

DryvIQ uses jobs to perform specific actions between the source and destination platforms. The most common type of jobs are copy and sync; please see Create New Job | Transfer Direction for more information. All jobs can be configured to run manually or on a defined schedule. This option will be presented as the last configuration step.

To create a job, select the Jobs option from the left menu and click on Create Job. DryvIQ will lead you through a wizard to select all the applicable options for your scenario.

 

The main job creation steps include:

  • Selecting a Job Type

  • Configuring Locations

  • Defining Transfer Policies

DryvIQ Migrate Version: 5.9.21
Release Date: August 7, 2026