Dobimigrate-5 12 2

DobiMigrate Online Help
5.12
Revision 3
Table of Contents
1. Introduction to Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2. Configure Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.1. File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2. Configure Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3. Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4. Email Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.5. File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.6. LDAP/AD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.7. Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2.8. Session Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.9. System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.10. Manage DobiMigrate License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.11. Manage Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3. Set up Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.1. Set up bandwidth throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.2. Configuring different time zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4. Discover File Server Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.1. Scan paths for the Discovery Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.2. Download the Discovery Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5. Manage Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.1. What is Reporting? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.2. How to Create Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.3. Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.4. File Deletion Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6. Set up a Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.1. Add a Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.2. Configure Migration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.3. Change Migration Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.4. User Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.5. Multiprotocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7. Manage Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.1. Running migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8. Monitor Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8.1. View Dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.2. Migrations Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.3. Iteration Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.4. Additional views for more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.5. Export Migration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.6. Scan Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
9. Switchover or Dry Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
9.1. Switchover Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

9.2. Manual Dry Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
9.3. Automatic Dry Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
9.4. Manual Switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
9.5. Automatic Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
9.6. Errors during switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
9.7. Closing a Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9.8. Exported Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
10. Finish a Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
10.1. Migrate Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
11. Verify/repair a Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
12. Run a WORM Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
13. Migration Rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
13.1. Rollback Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
13.2. Rollback and Switchover Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
13.3. Rollback Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
14. Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
14.1. Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
14.2. Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
14.3. Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
14.4. Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
14.5. File Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
14.6. Events & Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
14.7. Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
DobiMigrate Online Help 5.12
1. Introduction to Online Help

Welcome to the online help for DobiMigrate.
We aim to keep this help and other support information up to date with the latest state of our
software. To accomplish this we also publish updates on the Datadobi Support Portal,
available to registered users.
Comments and suggestions for future improvements of this information are greatly
appreciated. Please post your suggestions or ideas on the forums of the Datadobi Support
Portal.
The structure of the Online Help follows the steps that are needed to perform a migration with
the DobiMigrate software. These steps are:
• Configure the DobiMigrate Settings and environment to prepare for a migration. This
involves the configuration of the File servers, Global Settings, and (optionally) items
such as SID Maps, Email Home, LDAP/AD, Users.
• Set up Throttling (optionally) if specific load or bandwidth requirements need to be

respected.
• Manage Migrations to configure migration options, interact with running migrations,

and manually start an iteration.
• Set up Discovery (optionally) to get more insight into the data that is stored on the file
server.
• Set up the Migration and initiate migration activities.
• Monitor Migrations to watch the progress and report to the stakeholders.
• Finish Migrations which involves planning and executing a switchover, creating Shares
and Exports on the destination file servers, and Exporting migration information.
Before you start with the configuration of the DobiMigrate settings and
 environment, make sure that the DobiMigrate Core software and the proxies
have been installed as described in the DobiMigrate Installation Guide.
2. Configure Settings
The Configuration module contains the following tabs that allow you to:
• File Servers: add a new file server and view, edit, remove configured file servers, and
configure a schedule
• Email Home: configure SMTP, migration and health reports

• LDAP/AD: configure LDAP/AD
• Users: add, edit and remove users
• User Mapping: view uploaded SID/UID/GID mapping files
• Filesystem: add disk space to DobiMigrate and configure a dropzone
• System: restart the DobiMigrate Core, configure HTTPS and upload DobiMigrate
software
• Global Settings: configure settings for the DobiMigrate instance, usage display,
migrations and discovery
• License: view DobiMigrate license key information and request and upload a new
license key
A specific section is available on Configuring different time zones in case you plan to do

migrations in different time zones.
2.1. File Server

The Configuration > File Server tab allows you to configure new file servers and view, edit and
delete configured file servers.
For more information on each of these operations, see the respective topics below.
2.1.1. Add a File Server
To add a new file server, go to the Configuration module and click on the File Servers tab.

Click the Add… button to open the Add New File Server dialog. Select the server type and
click Next to specify the credentials for accessing the file server via the management API.
DobiMigrate supports the following types of file server:
• Cohesity DataPlatform
• Dell EMC Isilon
• Dell EMC PowerStore
• Dell EMC Unity
• Dell EMC VNX / Celerra
• Hitachi NAS Platform (HNAS)
• NetApp Data ONTAP
• Nutanix Files
• Pure FlashBlade
• Other NAS
NetApp Data ONTAP covers both Data ONTAP 7-mode and Clustered Data
 ONTAP.
For VNX/Celerra you need to provide the user name and credentials of the
 admin account.
DobiMigrate integrates with the listed server types, for other server types, use Other NAS.
Integrated file servers
For integrated file servers, you need to specify the IP address (or DNS name) of the file
server’s management interface and the username and password that have been configured
for management access. Click Next when done. When you have specified the right credentials
for accessing the file server via the management API, a window with the file server details is
displayed:
The server details are retrieved via the management API and cannot be changed. In this dialog
you can only enter the DobiMigrate display name of the file server and configure a
schedule via the Configure button (see Configure Schedule). When done click Next.
DobiMigrate automatically starts a discovery of the sub file servers on the file server and
displays the results in the following dialog:
Depending on the file server type, the discovered sub file servers will be either:
• Storage Virtual Machines (SVMs) for NetApp Clustered Data ONTAP
• vFilers for NetApp Data ONTAP 7-Mode
• Access Zones for Isilon
• CIFS/NFS Server for VNX/Celerra
• Virtual Servers (EVSs) for HNAS
• NFS for generic NFS servers
• SMB for generic SMB servers
• NAS servers
The Validate configuration… button performs a number of checks on both file server’s

configuration to ensure they can be reliably migrated to, or from.
The next step is to select the parameters to set up a connection with the DobiMigrate proxies.
Select the parameters
You can set up and test the connection between the DobiMigrate proxies and the file server. To
do so, select the IP addresses of the sub file server to which the proxies should connect. The
list of available interfaces is collected via the management API and you have the option to
manually add more interfaces as described below.
To set up a sub file server via DobiMigrate, select an available IP address from the
address popup for the respective sub file server.
By default, the list displays the available addresses that have been collected from the file
server. Alternatively, you can add other server addresses by selecting the option Manage IP
addresses… from the popup. This will open the following window where you can add specific
server addresses via the Add… button. Once added, select the new server address and
click OK so DobiMigrate can use it.
In the case of SMB, you also need to add the SMB credentials by selecting Manage
credentials… from the popup.
In the New SMB credentials dialog, enter the domain and user name for the account that will
be used to access the data with the SMB protocol. Make sure that the user account is part of
the local backup operators group, and the local administrator’s group, on the file server.
Once you have specified account credentials, DobiMigrate will also make these available as an
option to choose from when setting up the other file servers.
When you have deployed SMB and/or NFS proxies prior to the setup of the file server, these
proxies are listed in the proxies table. Select one or more proxies and click the Test
connection button to validate if the selected proxies can connect to the configured sub file
servers using the given credentials. A separate dialog shows the Connection test result. When
all is OK, close the dialog and click OK to finish the setup of the file server.
In case no proxies are displayed, they probably have not been set up yet. You can complete the
setup ignoring this screen and come back to it later by editing the settings of the file
server after you have set up the proxies as described in the DobiMigrate Installation Guide. See
Edit/view a File Server.
For Isilon versions older than 7.2, NFS support is only available for the
 System access zone. For Isilon access zones, you can specify the pool of IP
addresses to which the proxies can connect.
Isilon recommends using Static SmartConnect zones for SMB, and

 Dynamic SmartConnect zones for NFS.
Manage Migration Shares and Exports
Once the SMB parameters have been set up, the next step is to setup the shares DobiMigrate
will be using for the migration. This can be done via the SMB Migration Shares tab.
DobiMigrate shows the set of directories on the server to which access is required.
DobiMigrate allows the user to select which share should be used to access the file system
path in the leftmost column. The options are:
• Automatic: DobiMigrate will automatically create a new migration share with a new,
unique name and will provide full access to the user with the credentials as provided in
the previous step. Click on Validate to check which operations DobiMigrate will perform
to configure the share(s).
• Manual: DobiMigrate will use an existing share on the file server without making any
modification to it.
• None: DobiMigrate will not use this path in the migration process.
Click Next to create the shares as selected.
The final screen of the file server setup allows you to manage the migration exports and how
these should be accessed. DobiMigrate shows the set of filesystem paths on the server to
which access is required. Access options are:
• Automatic: DobiMigrate will update the existing export or create a new one and allow
full access to the assigned NFS proxies for this file server. Click on Validate to check
which operations DobiMigrate will perform to configure the export(s).
• Manual: DobiMigrate will use the existing export without making any modification to it.
The user needs to give full access to the assigned NFS proxies manually.
Click OK when you have made your selection. DobiMigrate will ask confirmation for
creating/modifying the shares and exports. Click Finish to finalize the setup of the file servers
and the migration shares and exports. For more information on viewing or updating the
created file server, see Edit/view a File Server.
Other NAS
In this case, you need to enter a name for the file server and specify the IP address (or DNS
name) for data access via the NFS and/or SMB protocol.
In case you have deployed DobiMigrate proxies prior to the setup of the file server, these are
listed in the proxies table. Select one or more proxies and click the Test… button to validate
whether the selected proxies can connect to the selected interfaces using the credentials as
provided. A separate dialog shows the Connection test result. When all is OK, close the dialog
and click Next to manage the SMB migration shares and/or the NFS migration exports.
In case no proxies are displayed, they probably have not been set up. For
 more information on their setup, see the DobiMigrate Installation Guide.
In the next dialog you can select the SMB shares that DobiMigrate can access to migrate data,
options are:
• Manual: DobiMigrate will use the share on the file server without making any
modification to it.
Click Next and select the NFS exports that DobiMigrate can access to migrate data. Options
are:
• Manual: DobiMigrate will use the export on the file server without making any
modification to it.
Click OK and the file server is added to the list with configured file servers.
2.1.2. Edit/view a File Server
Go to Configuration > File Servers and select the file server that you want to edit/view from
the list. Click the Edit button. This opens the file server edit dialog on the General tab. The
information shown depends on the type of file server. The dialog allows you to change the
information as given during configuration as described in Add a File Server.
Integrated file servers
For integrated file servers, you can change the IP address or DNS name and the
username and the password that have been set up for management access.
On the Overview tab, you can change the name of the file server as it will be displayed in the
DobiMigrate GUI. Depending on the file server type, this tab shows:
• Name: the name of the system as provided when it was added to DobiMigrate.
• Type: (NetApp only) indicates if this is a virtual or physical file server.
• Model (Number): the model (number) of the hardware.
• System ID/System GUID/Serial number: unique identifier of the system.
• Version: version of the OS running on the file server.
• Schedule: click on Configure to configure a schedule (see Configure Schedule).
• Total raw capacity: (Isilon and Unity) the capacity used by the file server.
• Filename Encoding: (Isilon only) the encoding that has been set on the file server.
Typically this would be UTF-8.
• Nodes: not for all file server types. Information differs per type of file server.
You can confirm changes at any time and close the edit dialog by clicking OK.
On the tab with the discovered sub file servers, you can change and test the connection
between the DobiMigrate proxies and the access points of the file server. For more
information, see Add a File Server.
Other NAS
On the General tab of generic file servers you can view and edit the connection details for the
SMB share and/or NFS exports as described in Add a File Server. In the Name field you can
change the name that was given when the file server was added to DobiMigrate.
View/update migration shares and exports
The shares and exports on the file server that DobiMigrate can access to migrate data are
shown on the SMB Migration Shares tab and the NFS Migration Exports tab respectively. For
more information on the management of shares and exports, see Add a File Server.
View file server details
To view the configuration details of a file server, go to Configuration > File Servers. The
overview shows all (sub) file servers with their configuration settings. To view detailed
information of an individual (sub) file server, select it from the overview and then click on
the Details button under the table. For example, select vfiler1 to view its details:
For all types of file servers, the following tabs are available:
• The tab Migration shares shows the created migration shares.
• The tab Migration exports shows the created migration exports.
For the integrated file servers, the information depends on the file server type.
2.1.3. Planning report
When migrating from an existing NAS system to a new NAS system, you would try to get
information about the soon-to-be replaced system in a planning report to ensure a seamless
migration. This step helps you to:
• dimension the file system
• plan the migration, including file-system dimensioning and tuning, share and export
mapping, performance tuning, and so on
• prepare for file-system incompatibilities
• plot the migration strategy
You can use the Planning report provided in DobiMigrate to get a complete overview of the
scope, the risks associated with the migration projects, and determine the paths that will be
migrated to the new system.
The Planning report is a downloadable csv report and contains detailed information for sub file
servers. You can download the report for one sub file server, or for multiple servers.
In DobiMigrate, you can download the Planning Report in the Discovery tab > .
To download the planning report
1. In DobiMigrate, click the Discovery tab. If it is not enabled, you can:
a. Click the Configuration tab.
b. Click the Global Settings tab.
c. In Instance Settings, click the Edit button to edit the Early Access Features
options.
d. In Early Access Features, select Enabled, and then click Save.
e. Log out and log back in. The Discovery tab should now be displayed on the page.
2.
Select one or more file servers, and click .
If you download the planning report without scanning one or more file
 servers on the Jobs tab, all detailed column counts will be empty.
3. Verify the details and click Download.
• File Server: The file server for which the info is shown
• Path: The path for which the info is shown
• Shared: A boolean value that indicates whether the path, or a parent path, is shared by
at least one share on this path or a parent path
• Exported: A boolean value that indicates whether an export exists for this path or a
parent path
• Replicated: Gives a summary value of how this path acts as a replication source:
◦ NO: The path is not replicated
◦ YES: The path is replicated
◦ PARENT: The path is replicated as part of a replication job of one of its parents
◦ PARTIAL: This means that either:
▪ Filters were applied and not all of the paths content is replicated
▪ The path itself is not replicated, but one of its child paths is
◦ EXCLUDED: The path is not replicated, but has a parent that is replicated. The path
was explicitly excluded from that replication
• Quota origin: Describes the origin of the value in the Capacity Quota column:
◦ NONE: No quota info is available
◦ DISCOVERY: The quota information is reported by the DobiMigrate discovery

process. Said otherwise, this value means 'as reported by the file server'
◦ CHILDREN: The quota information is provided by aggregating the values of the

child paths. Due to this, this information might be partial if the quota is not known
for all children
• Capacity Quota: The limit on the capacity that can be stored in this path or any child
path.
Please note:
◦ In case of Quota origin = NONE: This value will be empty
◦ In case of Quota origin = DISCOVERY: This value might be an approximation of

the real used quota
◦ In case of Quota origin = CHILDREN: This value may be partial, if the quota is not
known for all children
• Capacity Origin: Describes the origin of the value in the Used Capacity and Approximate
Item Count columns. This can be:
◦ NONE: No capacity info is available
◦ DISCOVERY: The capacity information is reported by the DobiMigrate discovery

process. This value means 'as reported by the file server'
◦ CHILDREN: The capacity information is provided by aggregating the values of the

child paths. Due to this, this information might be partial if the capacity is not
known for all children
• Used Capacity: As reported by the file server. This is the capacity used by this path, in
bytes.
Please note:
◦ In case of Capacity Origin = NONE: This value will be empty
◦ In case of Capacity Origin = DISCOVERY: This value may be an approximation of

the real used capacity
◦ In case of Capacity Origin = CHILDREN: This value may be partial, if the capacity
is not known for all children
• Approximate Item Count: Number of items stored in this path and any sub paths, as
reported by the file server
Please note:
◦ In case of Capacity Origin = NONE: This value will be empty
◦ In case of Capacity Origin = DISCOVERY: This value may be an approximation of

the real used capacity
◦ In case of Capacity Origin = CHILDREN: This value may be partial, if the capacity
is not known for all children
• Shares: This is a list of all the shares for this path
• Number of Shares: The number of shares on this path
• Number of Child Shares: The number of shares on any child path
• Number of Parent Shares: The number of shares on any parent path
• Exports: This is a list of all the exports, and any NFS aliases for this path
• Number of Exports: The number of exports on this path
• Number of Child Exports: The number of exports on any child path
• Number of Parent Exports: The number of exports on any parent path
• Replicated Paths: Displays all replication jobs which replicate this path (fully or
partially), based on the Replicated value. If this value is:
◦ NO: Replicated Paths will be empty, as no replication is present
◦ YES: Replicated Paths will contain the Path itself. If a nested replication structure
is present, multiple paths may be shown
◦ PARENT: Replicated Paths will contain all the parents that are replicating this path
◦ PARTIAL:
▪ Replicated Paths:
▪ Can contain the Path itself if filters were applied
▪ Can contain parents if this path is replicated partially by replication

jobs higher up the tree
• Replicated Targets: A list of target paths the Path is replicated to. The format is a
semicolon-separated list of items with one of two forms:
◦ '<host>:<target path>' when this path is replicated completely
◦ '<host>:<target path> (partial)' when the path is replicated partially

• Scan Status: The status of the scan. For example, Complete. The values are:
◦ NONE: The file server is not configured for discovery
◦ SCANNING: The scan is in progress
◦ SCANNING_FAILED: The scan failed and therefore, could not be completed
◦ CALCULATING: The scan has finished and DobiMigrate is calculating the various
numbers for this report
◦ COMPLETE: The scan is complete and the scan statistics are up-to-date. If the
path includes children, then the scan status of Complete implies that the scan is
complete for the associated child paths as well
◦ INCOMPLETE: For a path with child paths, this status indicates that the scan is
not complete for one or more child paths
◦ PAUSED_BY_USER: The scan is paused by a user
◦ PAUSED_BECAUSE_SWITCHOVER:The scan is paused because a switchover is in

progress
◦ ABORTED_BY_USER: The scan is aborted by a user
◦ ABORTED_BECAUSE_LICENSE_EXPIRED: The scan is aborted because the license

is no longer valid
◦ ABORTED_BECAUSE_LICENSE_FOREIGN: The scan is aborted because the

license is for another instance of DobiMigrate
◦ ABORTED_BECAUSE_NOT_ENOUGH_FREE_SPACE_TO_RUN: The scan is aborted

because the core does not have enough local disk space to store the scan results
• Scan Time: The time taken for the scan. This includes the date, time, and the duration of
the scan
• Scan Errors: The count of errors found while scanning the path and sub-paths
• Scanned Capacity: The capacity as reported by the scan
• Scanned Item Count: The count of items that were scanned
• Scanned files: The count of files that were scanned
• Scanned file-system columns: The following columns display the count of the systems
in a file server:
◦ Scanned directories
◦ Scanned symlinks
◦ Scanned sockets
◦ Scanned block devices
◦ Scanned character devices
◦ Scanned pipes
◦ Scanned mountpoints
◦ Scanned items with no type: Items that have no type
◦ Other scanned items: Items with a type that does not fall in any of the preceding
categories
You can view the details in a histogram by importing the .csv file into
 Microsoft Excel.
• File-size columns: The following columns display the size of items for the various
systems in a file server:
◦ Total size of files
◦ Total size of directories
◦ Total size of symlinks
◦ Total size of sockets
◦ Total size of block devices
◦ Total size of character devices
◦ Total size of pipes
◦ Total size of mountpoints
◦ Total size of items with no type
◦ Total size of other items

• Creation-date count columns: The following columns display the count of items based
on the creation date and time stamps:
◦ Items with creation time in the future
◦ Items created in the past week
◦ Items created between 1 week and 1 month ago
◦ Items created between 1 and 3 months ago
◦ Items created between 3 and 6 months ago
◦ Items created between 6 months and 1 year ago
◦ Items created between 1 and 2 years ago
◦ Items created between 2 and 3 years ago
◦ Items created more than 3 years ago

• Creation-date size columns: The following columns display the total size of items based
◦ Size of items with creation time in the future
◦ Size of items created in the past week
◦ Size of items created between 1 week and 1 month ago
◦ Size of items created between 1 and 3 months ago
◦ Size of items created between 3 and 6 months ago
◦ Size of items created between 6 months and 1 year ago
◦ Size of items created between 1 and 2 years ago
◦ Size of items created between 2 and 3 years ago
◦ Size of items created more than 3 years ago

• Modified-date count columns: The following columns display the count of items based
on the modified date and time stamps:
◦ Items with modification time in the future
◦ Items modified in the past week
◦ Items modified between 1 week and 1 month ago
◦ Items modified between 1 and 3 months ago
◦ Items modified between 3 and 6 months ago
◦ Items modified between 6 months and 1 year ago
◦ Items modified between 1 and 2 years ago
◦ Items modified between 2 and 3 years ago

◦ Items modified more than 3 years ago

• Modified-date size columns:The following columns display the total size of items based
◦ Size of items with modification time in the future
◦ Size of items modified in the past week
◦ Size of items modified between 1 week and 1 month ago
◦ Size of items modified between 1 and 3 months ago
◦ Size of items modified between 3 and 6 months ago
◦ Size of items modified between 6 months and 1 year ago
◦ Size of items modified between 1 and 2 years ago
◦ Size of items modified between 2 and 3 years ago
◦ Size of items modified more than 3 years ago

• Access-date count columns: The following columns display the count of items based
on the access date and time stamps:
◦ Items with access time in the future
◦ Items accessed in the past week
◦ Items accessed between 1 week and 1 month ago
◦ Items accessed between 1 and 3 months ago
◦ Items accessed between 3 and 6 months ago
◦ Items accessed between 6 months and 1 year ago
◦ Items accessed between 1 and 2 years ago
◦ Items accessed between 2 and 3 years ago
◦ Items accessed more than 3 years ago

• Access-date size columns: The following columns display the total size of items based
on the access date and time stamps:
◦ Size of items with access time in the future
◦ Size of items accessed in the past week
◦ Size of items accessed between 1 week and 1 month ago
◦ Size of items accessed between 1 and 3 months ago
◦ Size of items accessed between 3 and 6 months ago
◦ Size of items accessed between 6 months and 1 year ago

◦ Size of items accessed between 1 and 2 years ago
◦ Size of items accessed between 2 and 3 years ago
◦ Size of items accessed more than 3 years ago

• File-size count columns: The following columns display the count of items based on the
file size:
◦ Files with size 0
◦ Files smaller than 8 KB
◦ Files between 8 and 64 KB
◦ Files between 64 KB and 1 MB
◦ Files between 1 and 10 MB
◦ Files between 10 and 100 MB
◦ Files larger than 100 MB

• File-size total columns: The following columns display the total size of items based on
the file size:
◦ Total size of files smaller than 8 KB
◦ Total size of files between 8 and 64 KB
◦ Total size of files between 64 KB and 1 MB
◦ Total size of files between 1 and 10 MB
◦ Total size of files between 10 and 100 MB
◦ Total size of files larger than 100 MB

• Longest file-system columns: The following columns display the details of file systems
with the longest information:
◦ Longest File Names
◦ Longest Dir Names
◦ Longest Full File Paths
◦ Longest Full Directory Paths
The Longest Full File Paths column includes the names of all the parent
directories, for example,
 "/ifs/data/and/so/on/until/you/have/a/very/long/full/path.txt". However, the

Longest File Names column includes only the file name, for example,
"path.txt".
• Full Paths of Biggest Files: The complete path information of the directories that
contains the biggest files.
• Full Paths of Directories With Most Files: The complete path information of the
directory that contains the most number of files.
Many systems have top-level exports or shares for administrative purposes, e.g. on an Isilon
/ifs might be shared for the backup system. In this case, all paths will report Shared: YES in
the report.
To know if the path is effectively shared, besides the top-level share, you can check if (number
of shares > 0) OR (number of parent shares - 1 > 0).
For example: if /ifs and /ifs/home/user/ are both shared, you might see a line in the report for
/ifs/home/user/my/replicated/dir:
• shared:yes
• number of parent shares: 2
• number of shares: 0
In this case, one of the parent shares is ifs, so we subtract 1 from this number. The number of
parent shares becomes 1, which indicates there is indeed another parent level share present.
2.1.4. Scan paths for the planning report
Using the Dashboard in the Discovery tab, you can view the file-system item count and size
provided by the file server in a GUI format. This information is displayed by DobiMigrate on the
Discovery tab.
However, before you can add a file server as part of the Planning report, you must first scan
the paths, by starting a discovery job for this path.
To start a discovery job
b. In Instance Settings, select Early Access Features.
c. Select Enabled, click Save.
d. Log out and log back in. The Discovery tab should now be displayed on the page.
2. Click the Configuration tab.
3. Select one or more file servers, and click Start.

2.1.5. Remove a File Server
You can remove a file server if it is no longer needed or used.
To remove a file server
1. In DobiMigrate, click the Configurations tab.
2. Select the file server from the list on the File Servers tab.
3. Click the Remove button in the bottom right corner.
Deleting a server will also delete any migrations or reports that use the
 server.
2.2. Configure Schedule

The Configure Schedule window opens with a calendar week view. The typical approach when
scheduling DobiMigrate is to indicate the business hours during which DobiMigrate needs to
run with different network and server load limitations or restrictions compared to the loads
outside business hours. In the Timezone field you can select the time zone associated with
the defined business hours. This can be the local time zone, the time zone of the application or
any other time zone of your preference.
By default, DobiMigrate is configured to run outside business hours with 64 threads for
scanning and 64 threads for operations. Examples of operations are: copy or delete files,
create symlinks, create or delete directories, transfer metadata or security settings. The
scanning operations serve two purposes:
1. To scan the file systems on the file server to discover changes that need to be inspected
and processed.
2. To scan the metadata of the files residing on the file systems for the generation of
reports that provide insights into the type of data on these systems.
A thread in the context of DobiMigrate refers to the number of concurrent access connections
that are made to a file server in order to manipulate data in parallel.
If you do not want DobiMigrate to interact with a file server from 9:00 to 17:00 during the
weekdays, then draw a block from 9:00 to 17:00 on Monday and use the Copy to
weekdays button to get the following week view.
When the schedule configuration is done, click on OK.
2.3. Global Settings

Go to the Configuration module and click on the Global Settings tab to configure the following
settings:
2.3.1. Instance Settings
To configure settings for all users, go to Global Settings > Instance Settings > Edit:
Name: This is the name that will be displayed as the title of your web page or tab when you log
in to this DobiMigrate instance. Changing the name can be handy if you have multiple
instances running and want to distinguish between them.
Session Timeout: Enable this to terminate a session (user logged out) when a session (logged
in user) has been inactive for a set amount of time.
User Lockout Threshold: Set a number value here to determine the number of consecutive
failed login attempts a user can make before being locked out.
If a user account has been locked, you can unlock it via Configuration >
 Users.
See also, Configure Session Management.
2.3.2. Configuration Backup Settings
The Configuration backup is an automated backup of the complete DobiMigrate configuration,

including the configuration of the core, its associated file servers, proxies and migrations.
This backup does not contain detailed states of those migrations, such as
scan files, error lists or chain of custody records. It is not possible to look at
 older scan results or do a selective retry on previous errors when a backup is

restored. This means that if you need a full Chain of Custody, DobiMigrate
will have to revalidate all the data that was already migrated.
Keeping a backup of the DobiMigrate configuration is highly recommended, as it will allow you
to restore the DobiMigrate core easier and faster in the event of, for example:
• Filesystem corruptions and/or loss of DobiMigrate core
• Manual errors: such as accidentally removing a file server and deleting all associated
migrations
• Reverting to a previous version of DobiMigrate : in case your environment is affected

by a DobiMigrate update.
DobiMigrate allows you to define a custom schedule that is used to trigger the configuration
backup on a regular basis.
These backups are saved as .zip files and can be encrypted if required. They can be stored in
any location on the filesystem of the machine running DobiMigrate. You can choose to backup
to an NFS mount, for example. This way the configuration backup archives can even be stored
automatically on an external system, safeguarding against the loss of the machine running the
DobiMigrate core.
To change the settings of the configuration backup, click on the Edit button, change the
values, and click the Save button.
Backup location: specifies the place on the core where the backups will be stored.
Schedule: Defines the moments when the backup of the configuration will be made. A backup
will be created every day at midnight by default, but this can be changed. It is possible to
define a custom backup schedule.
Password: Encrypts the backup with password protection, if needed.
Remove old backups: allows you to indicate if you would like to remove old backups:
• If this option is checked, old backups will be removed and only the most recent will be
kept. The number of backups to keep can be specified.
• If the option is unchecked, all backups will be kept and the number of backups to keep
is not relevant.
Number of backups to keep: Specifies the number of backups that are kept. Older backups are
automatically cleaned up.
It is also possible to immediately Take backup now and/or Disable the automated triggering
of the configuration backup.
2.3.3. Reporting Display Settings
Maximum File List Length: This allows you to define the maximum number of files to display
in the table list under the usage graphs. With this setting you can limit the length of the table
and, consequently, the time it takes for DobiMigrate to display the table. This is useful when,
for example, a user is browsing the content of a server and opens up a directory with
thousands of files. The default value is set to 2000.
2.3.4. Migration Settings
Iteration Schedule: You can define iteration schedules that can later be applied to individual
migrations. This is useful since often the schedule you want to use is the same for quite a few
migrations. Templates are defined here that apply to migrations afterwards.
Minimum age: with this setting you can define how old the files on the source server need to
be before they are taken into account for the next iteration. With this setting you can avoid that
DobiMigrate will migrate data that is updated constantly during the steady state process. Note
that during dry run and switchover activities, all data will be migrated regardless of this setting.
The modification timestamp of the file is used to check for file updates. This timestamp is
compared with the DobiMigrate server time (UTC) to calculate the file age which will then be
compared with the minimum age setting to decide whether the file needs to be migrated or
not.
To ensure a proper working of the minimum age setting, you need to make
 sure that NTP is set up on all involved systems.
For the example below, with the start of the next iteration DobiMigrate will:
• migrate File A: because its age since the last update is higher than the minimum age
setting.
• Not migrate File B: because its metadata has been updated more recently than defined
by the minimum age setting.
• migrate the metadata changes made to Directory C: because its age is older than the
minimum age setting.
Digest algorithm: allows you to specify which algorithm should be used to check the integrity
of copied data during a migration. This global setting defines the default that will be used
when setting up migrations. The digest algorithm is used by DobiMigrate during the migration
process internally, and during the creation of a Chain of Custody. You are able, however, to
deviate from this globally defined default by selecting a different algorithm when you set up an
individual migration.
Max number of concurrent scans: This setting, with a default value of 256, dictates the
number of scans that can be run at any point in time by the DobiMigrate core. For migration
projects with a lot of migrations running in parallel, you may want to increase this number.
This will have an impact on the memory requirements for the DobiMigrate core instance.
Please inquire with Datadobi for guidance.
2.3.5. File Server Settings (N2N Migrations)
This section will be displayed only for N2N migrations.
Discovery Schedule: this setting defines how frequently DobiMigrate will check the file server
to rediscover system settings and information.
Share/Export Operation Timeout: The timeout to use when retrieving or modifying SMB
shares and NFS exports.
2.3.6. Object Storage Settings (O2O Migrations)
This section will be displayed only for O2O migrations.
Discovery Schedule: this setting defines how frequently DobiMigrate will check the file server
to rediscover system settings and information.
2.3.7. Login Banner
The user can define a text message that will display on the login screen.
2.4. Email Home

To configure email home settings go to Configuration > Email Home. On this tab you can
configure the SMTP mail server, the sender and receiver addresses and frequency of health
and migration reports.
2.4.1. SMTP Configuration
In the SMTP Configuration panel you can configure the mail server through which
DobiMigrate has to send health reports, the credentials and the sender’s address.
By default, SMTP is disabled. Click the Enable button to open the configuration form. If SMTP
is already enabled and configured, you can edit the existing settings, by clicking the
Edit button.
You can configure the following settings:
• SMTP host: host name of the SMTP server to use (for example: mail.yourdomain.com).
• Use Secure Sockets Layer (SSL): select this option if the SMTP server accepts
connections using Secure Socket Layer/Transport Layer Security (SSL/TLS).
• Authentication: the type of authentication to use with the SMTP server. Possible values
are None and User & password. In case a user and password are required, the following
two fields need to be filled in:
◦ SMTP user: user name to be used for authentication with the SMTP server.
◦ SMTP password: password to be used for authentication with the SMTP server.
• From address: the email address from which to send the health reports.
Once all settings have been configured click on the Save button in the panel.
You can use the Test button to verify the given settings. DobiMigrate will try to connect to the
given SMTP server with the specified authentication settings and will show the result.
A notification appears at the top of the screen mentioning that the
 configuration has changed. Click the Save button next to it to keep all

changes.
2.4.2. Health & Migration reports
A health report gives a view of the overall condition of the migration environment, and
migration reports give a detailed view of running migrations.
In the DobiMigrate Health Reports panel you can configure the receiver’s address and the
frequency of the health reports.
The Migration reports panel allows you to configure the same settings for the migration
reports.
If the reports setting are disabled, click the Enable button to open the configuration form. If
already enabled and configured, you can edit the existing settings, by clicking the Edit button.
• To addresses: the email address to send the health reports to. Separate multiple
addresses with commas.
• Frequency: specifies whether a health report should be sent daily, weekly or monthly.
Once all settings have been configured click on the Save button in the panel.
You can use the Test button to send a test email using the given configuration. Note that
SMTP needs to be configured as well as described in the section above.
A notification appears at the top of the screen mentioning that the
 configuration has changed. Click the Save button next to it to keep all

changes.
2.4.3. Alerts
• To addresses: the email addresses to send the alerts to. Separate multiple addresses
with commas.
• Frequency: specifies whether an alert should be sent daily, weekly or monthly.
2.5. File System

On the Configuration > Filesystem tab you can configure:
• Filesystem roots that define the locations where DobiMigrate keeps its system files,
project data, and where you add more capacity if needed.
• Dropzones that define where DobiMigrate will drop large file exports. The Chain of
Custody files, for example, will also be dropped in these locations.
2.5.1. Add a DobiMigrate Filesystem Root
For a typical DobiMigrate installation one root location will be assigned during the installation
for DobiMigrate to keep all its information. The default path is: /mnt/data/DobiMigrate/ for
.OVA based deployments. However, when DobiMigrate is deployed in large environments, it is
highly recommended to either provision enough capacity for the default root location or to add
extra paths for DobiMigrate to use. Extra capacity can be added by adding more disks and
once created and configured at the operation system level, configure them in DobiMigrate.
More information on adding extra capacity is described in the DobiMigrate Installation Guide.
• To add a path to DobiMigrate, go to the Configuration module and click on

the Filesystem tab. Click on the Add button in the bottom right corner of the Filesystem
Roots panel.
• A window appears that allows you to select a path. Note that you can only select a
directory for which DobiMigrate has the UNIX file system permissions read, write,
and execute.
• Once you have made a selection, click on the Select button. In the window that appears
next, the Results option has been selected by default. Keep this setting and click
on Save to save the path settings.
• The new path is added after a restart of DobiMigrate.
The Clear and Disconnect button should only be used when asked by Datadobi support as it

could cause loss of project data and impact ongoing activities in DobiMigrate.
It is strongly advised to only apply these changes under guidance of

 Datadobi support.
2.5.2. Configure a dropzone
A dropzone allows you to quickly store and retrieve large exported lists with information
related to discovery or migration activities. This approach is recommended when you want to
export and keep large amounts of information such as a list of all files that were migrated to
the destination file server. Since these files can be gigabytes in size, it is best to save them in a
dropzone and then retrieve them by connecting to the dropzone on the DobiMigrate instance
using tools as scp or WinSCP.
The configured dropzones are shown in the Dropzones panel. To configure a new dropzone,

click on the Add button under the table and select the location. Use the Remove button to
delete dropzones that are no longer needed.
2.6. LDAP/AD
2.6.1. Configure LDAP/AD
Instead of the default user management embedded in DobiMigrate you can also use LDAP/AD
to manage user access to DobiMigrate. Make sure that you configure the LDAP server
accordingly.
In DobiMigrate, go to the Configuration module and click on the LDAP/AD tab. By default,

LDAP/AD is disabled. Click the Enable button to open the LDAP configuration form.
• Server address: the host name of the LDAP server. For example: ldap.yourdomain.com.
• Server port: the port number on which the LDAP server can be reached. The options are:
◦ Default: the default LDAP port is taken and the Custom server port field is greyed
out. Typically this is port 389 or 636 when using SSL/TLS.
◦ Custom: a custom port can be given in the Custom server port field.

• Custom server port: the port number on which the LDAP server can be reached. You
can only enter a value here if Custom is selected in the Server port field.
• Use SSL: select this option to use Secure Socket Layer/Transport Layer Security
(SSL/TLS) when connecting to the server.
• Bind DN: the distinguished name (DN) to use when binding to the LDAP server. The DN
needs read-only rights on the server. For
example: DN=read_only,OU=people,DC=yourcompany,DC=com. Not needed when
anonymous binding is used.
• Bind password: the password to use in combination with the Bind DN when binding to
the LDAP server. Not needed when anonymous binding is used.
• Base DN: the base distinguished name under which to find user accounts. For example:
OU=people,DC=yourcompany,DC=com.
• User group DN: the group containing the accounts which will get DobiMigrate user
rights. For example: CN=DobiMigrate-users,OU=groups,DC=yourcompany,DC=com.
• Expert group DN: the group containing accounts which will get DobiMigrate expert
rights. For example: CN=DobiMigrate-experts,OU=groups,DC=yourcompany,DC=com.
• Admin group DN: the group containing accounts which will get DobiMigrate admin
rights. For example: CN=DobiMigrate-admins,OU=group,DC=yourcompany,DC=com.
• Server type: the type of LDAP server that will be used. Options are: Active Directory
, OpenLDAP or custom. When Active Directory or OpenLDAP are selected, the fields UID
attribute and Group member attributes will be greyed out. When custom is selected,
you need to enter values in these fields.
• UID attribute: the attribute used on the LDAP server to contain unique user IDs.
Typically uid on OpenLDAP or sAMAccountName on Active Directory.
• Bind method: options are anonymous binding or binding with a

DN/password combination. This depends on your local LDAP configuration.
• Group member attribute: the attribute used on the LDAP server to indicate group
membership. The member attribute is commonly used for this purpose.
 The fields marked with a red star are mandatory.
Once all settings have been configured, you can use the Test button to validate the
configuration. DobiMigrate will try to connect to the configured LDAP server and retrieve the
specified Groups.
2.7. Users
2.7.1. Add a user
To add a new user, click on the Add button in the bottom right corner of the screen.
A dialog box appears in which you can enter the following details:
• Name: the name of the user.
• Role: the role assigned to the user. Options are:
◦ User: gives users a read-only right to view and export information. Users with this
role can consult some of the settings of DobiMigrate but cannot change them.
◦ Expert: in addition to viewing reports and exporting information, the expert role
allows users to manage all aspects of a migration (manage file servers, set up
discovery, set up & manage migrations, manage proxies, create shares and
exports, manage global settings and SID Maps)
◦ Administrator: gives users full rights to DobiMigrate. Specific settings are only
reserved to the administrator such as DobiMigrate application settings. For
example: upgrade DobiMigrate, change licenses, set up Email home or LDAP/AD,
set up secure server, enable logging, manage users and configure DobiMigrate
capacity and dropzones.
• Password: the user password.
• Verification: the user password.
Click on Save to save the user configuration. A user account is activated as soon as it has
been created.
 Contact Datadobi for a password reset.
2.7.2. Remove a user
To remove a user, select the user that you want to remove in the list and click on the
Remove button in the bottom right corner of the screen.
2.7.3. Edit a user
To edit a user, select the user that you want to edit in the list and click on the Edit button in the
bottom right corner of the screen. The edit option is mainly used to either change the role of
the user or its password.
2.8. Session Management

Session management is a security feature giving administrators greater control over user’s
accounts, enabling them to:
• Block users after a number of failed login attempts
• Store information about failed login attempts
• Terminate an active user
• Unblock a known blocked user
2.8.1. Configure Session Management
To configure Session Management for an individual user, go to Configuration > Users. From
here you can select Local Account, External Account, and Show sessions.
Once you select a user, from the bottom of the page you can:
• Add
• Remove
• Edit
• Unlock user
• Terminate Session
See also, Instance Settings, under Configuration > File Server > Global
 Settings.
2.9. System
The Configuration > System tab allows you to restart the DobiMigrate core server, to configure
HTTPS settings, upload DobiMigrate software and to configure logging.
2.9.1. Restart server
In some cases DobiMigrate might ask you to restart the DobiMigrate core server. To do this,
click on the Restart Server button in the top panel of the System tab. You will be disconnected
from DobiMigrate. After the restart you need to refresh your browser before you log in.
2.9.2. Configure HTTPS
DobiMigrate by default uses standard HTTP (port 80) to provide access to its web GUI. If
required, it is possible to configure DobiMigrate to use HTTPS (port 443) instead.
To set up HTTPS for a web server such as DobiMigrate, you need:
• A pair of public and private keys.
• An SSL certificate that links the URL of DobiMigrate’s web server to a specific public

key.
DobiMigrate can generate a key pair and certificate itself but it also accepts them from a
certificate authority like VeriSign, Thawte, GeoTrust and others.
Depending on the kind of certificate that you want to use, you can:
• Generate a certificate: DobiMigrate generates a public/private key pair and a matching

self-signed certificate. This configuration cannot be used to authenticate the web server
but will be used for encryption of the network traffic only. Note that most web browsers
will display threatening security warnings when you use DobiMigrate with this
configuration.
◦ To configure DobiMigrate with a generated certificate, click the Generate

certificate button in the HTTPS Configuration panel.
A dialog box appears showing the certificate that DobiMigrate has generated. The owner
should match the name of the host on which DobiMigrate is running.

Click the Restart button to restart DobiMigrate using this new certificate.
After the restart, connections to the DobiMigrate web GUI will automatically use HTTPS. The
web browser will probably display a warning that the site’s certificate is untrusted. You can
ignore this warning and go to the web GUI using an encrypted connection to DobiMigrate.
Using this configuration, an attacker can still redirect your connection to

 another website and mimic DobiMigrate to capture your login credentials.
• Upload a certificate: For optimal security it is best to obtain a public/private key pair and
a matching certificate (in PEM format) issued by a certificate authority. The host name
in the certificate must match the URL at which DobiMigrate is installed. Please refer to
the certificate authority of your choice for detailed instructions.
• To configure DobiMigrate to use an authorized certificate, click the Upload

certificate button in the HTTP Configuration panel.
A dialog box appears in which you need to copy your key pair and certificate (including the
BEGIN and END lines) to the appropriate fields.
Click Ok to continue.
The next dialog box shows the certificate that you have uploaded. The owner should match
the name of the host on which DobiMigrate is running.
Click the Restart button to restart DobiMigrate with this new certificate.
After the restart, connections to the DobiMigrate web GUI will automatically use HTTPS. You
will now have an encrypted connection to the authenticated DobiMigrate web server. Attackers
will no longer be able to intrude your data traffic or redirect your connection to a fake server
without a security notification from your web browser.
Upgrading DobiMigrate
To upgrade to a new version of the DobiMigrate software:
1. Click the Upload button in the Update DobiMigrate Software box.
Before you proceed with the upload, ensure the /tmp directory has
 enough space to store the upgrade image.
A file browser dialog is displayed.
2. Select the upgrade image which has the extension_tar.gz.gpg_.

When the file has been uploaded, click the Upload button to upgrade to the new version.
DobiMigrate will automatically restart so you can log in using the new version. The
upgrade itself might take up to five minutes.
Should proxies fail to upgrade automatically, they can be upgraded manually by taking
the following steps:
Proxy
a. Copy the DobiMigrate proxy RPM to the Linux machine running the proxy.
b. Upgrade the installed RPM using rpm -U <proxy rpm>
2.10. Manage DobiMigrate License
2.10.1. Request a license key
DobiMigrate prompts you to retrieve and upload a license key in the following cases:
• when you log in for the first time after initial installation
• when the current license key is no longer valid or corrupt
Follow the steps below to obtain and upload the license key.
1. Navigate to Configuration > License and click Request License… .
2. In the Request license key dialog, copy the text in the Encoded License Request field
and send it to support@datadobi.com to obtain a new license file.
Do not restart DobiMigrate while waiting for the license key. If needed,
 you can close the UI.
3. If you want to request a license key for specific source or destination servers, click
Advanced….
4. Select the source or destination file servers for which you want to request a license and
click Save.
 Licensing a server is only needed if instructed by Datadobi.

5. When you have received the license key, go to the Configuration module and open
the License tab. Click on the Upload license key button at the bottom of the screen.
6. Select the license key file and upload it.
The File Servers tab in the Configuration module shows green check marks for the licensed
file servers. You can now start migrations for these servers.
2.10.2. View license information
The License tab in the Configuration module shows the following information on the current
license key:
• Expiration date: The date that the license expires.
• Customer: The name of the organization to which the license has been issued.
• License ID: Unique identifier for the license.
• DobiMigrate instance ID: A unique identifier for the DobiMigrate instance on which this
license key can be used.
• Migration capacity: The capacity that has been used for migration against the total
licensed migration capacity. Click on the Details button to see more information on the
capacity usage.
• Custom fields: Are fields that are added by DataDobi when creating the license.
The table shows the following information:
• Cluster name: The name of the cluster as configured in DobiMigrate.
• Cluster ID: The list of clusters on which DobiMigrate can be used. These clusters are
identified through their unique Cluster IDs or GUIDs.
• Capacity: The amount of capacity that has been purchased as part of the software
license.
• Modules: The licensed modules per cluster.
2.11. Manage Proxies

Proxies are installed and subscribed to the DobiMigrate Core during initial installation as
described in the DobiMigrate Installation Guide. Once this has been done, you can allocate
them to the source and destination storage systems. You have the flexibility to deploy one
proxy against multiple storage servers, many to one storage server and any other
combination; as long as the proxies are connected to both the source and destination system.
The Proxies module allows you to manage the installed proxies as described in the following
sections.
2.11.1. View proxy configuration and restart proxies
The Dashboard tab allows you to:
• View detailed information on the installed proxies and check whether the proxies are
online.
• Remove proxies that are no longer needed by selecting them and clicking the
Remove button at the bottom right of the page. A warning message appears to show to
which file servers the proxies are connected.
2.11.2. Proxy Schedule
To schedule each proxy individually, go to the Schedule tab and select the proxy. Click on
the Edit button to open the scheduler.
Add the time slots and the associated bandwidth using the buttons at the right. Click OK to
save the schedule. The schedule is shown in the overview from where you can copy it to
another proxy using the Copy schedule button at the bottom right of the page.
2.11.3. Assign proxies
You can assign one or more proxies to one or more file servers, either through the file server
configuration during setup (or when editing these settings), or using the Proxies module via
the Assign tab and the File Servers button at the top.
You can also assign proxies to a specific access zone. Access zones are for
 Isilon; however, other integrated file servers have similar concepts and are
also supported.
1. Select one or more file servers and click the Edit button to assign one or more proxies to
it:
The offline proxies are displayed as well.

2. Click the Test button to check if the connection succeeded.
3. Click OK to close the dialog if the connection is successful. If not, click Cancel and fix
the issues shown in the test results dialog.
When the proxy is used to migrate data between the source and destination
 file server, make sure to have it assigned to both these servers.
You can see which file servers are assigned to one or more proxies using the Proxies tab
under the Assign module.
The Edit button allows you to connect or disconnect one or more proxies to or from one or
more file servers.
2.11.4. View proxy performance
The Performance tab shows the statistics of all proxies per bandwidth or per scanned, copied
and deleted operations. You can zoom in and out using the Zoom buttons in the top right
corner.
3. Set up Throttling
Throttling can be set up for:
• Load by defining the number of concurrent connections that are allowed against the
source and destination file server. With the Configure Schedule setting, you can define
the amount of load during and outside business hours
• Throughput or bandwidth at proxy level. For each individual proxy, you can define a time
schedule with restrictions on bandwidth usage based on a week schedule. For more
information on how to set up bandwidth throttling see below.
In addition you can vary the allocation of the number of proxies that you assign to a source
and destination file server. This allows you to create a bigger pipeline between your source and
destination file servers, especially when the data to be migrated are mostly large files (>1MB).
In case your migration is scheduled to run for an extended time, also consider the minimal
age setting and the iteration schedule length. The minimal age avoids that files that are
changed frequently are re-migrated with each iteration (e.g. mailbox PST files). These files
should only be migrated as part of the switchover windows to maximize the efficiency of
network usage.
The iteration schedule determines how frequently source and destination server are scanned
for changes. If you have run a usage report prior to your migration setup, you can select those
paths that have few ongoing changes to increase the iteration schedule and those paths that
are used very actively to be scanned more often in relation to the total planned time for the
migration and switchover.
Both these settings can be configured in Configure Migration Options.
3.1. Set up bandwidth throttling

To set up bandwidth throttling, go to the Proxies module and select the Schedule tab. This
view lists all available proxies, the time zone they operate in and their weekly schedules.
If needed, you can change the default regimes that are available by clicking on the
configuration button next to the (colored) predefined bandwidths at the top right corner.
The Edit bandwidth categories window opens with color-coded fields representing bandwidth
speed limitations expressed in Mbit per second. There are six predefined regimes which you
can change to your needs.
When done, select a proxy for which you want to apply restrictions and click on the Edit
button below the list. The week schedule for the selected proxy is displayed. First you specify
the time zone of the proxy so that its bandwidth restrictions are aligned with the local business
activities. Next you can draw a slot, specify the regime for that slot and optionally use the
button on the right hand side to duplicate the slot across the week schedule. Throughout the
day and week, you can create multiple slots, each with their specific regime.
When done, confirm the schedule with the OK button. You can reuse a defined schedule
across multiple proxies by selecting the proxy and clicking the Copy schedule button under
the list. The Copy schedule dialog lists the proxies to which you can copy the schedule. Make
your selection and confirm with the OK button.
At any point in time, you can check whether a certain proxy is subject to a bandwidth
restriction through the Proxies Dashboard.
3.2. Configuring different time zones

Time zones are useful to configure in case a migration involves file servers that are spread
over different time zones.
If all your migrations take place in the same time zone as the time zone in which the
DobiMigrate core server is running, then no specific time zone settings are required.
A time zone can be configured at two levels in the DobiMigrate environment:
• Proxy level
• File server level

3.2.1. Proxy level
It is best to align the proxies with the time zone in which they operate. This would normally be
the same location as where the source and target file servers reside.
The reason for this is that the bandwidth restrictions need to align with local business context
and operations.
For example, if you are migrating infrastructure based in one location, but you are monitoring
and managing the project from elsewhere, then you set the time zone of the proxies. If a
customer does not want any migration activities to occur during the busiest part of the
working day, for example between 9:00 AM to 6:00 PM, then you just draw a slot in the proxy
schedule of the local proxy and set its regime to 0Mbit/s bandwidth speed.
If you are also migrating from infrastructure in a local data center, facing the same bandwidth
restrictions during local business hours, you select the select Copy Schedule and select those
proxies. Once this is done, you can then change their time zone via the Edit button.
3.2.2. File server level
The same approach as for proxies needs to be taken when you want to configure the
maximum load (expressed by the maximum amount of concurrent threads) against your
source and target file server. You can configure the time zone and business hours for which
load restrictions apply via Configure Schedule.
4. Discover File Server Information

When migrating from an existing NAS system to a new NAS system, you would try to get
information about the soon-to-be replaced system in a planning report to ensure a seamless
migration. This step helps you to:
• dimension the file system
• plan the migration, including file-system dimensioning and tuning, share and export
mapping, performance tuning, and so on
• prepare for file-system incompatibilities
• plot the migration strategy
You can use the Discovery module provided in DobiMigrate to get a complete overview of the
file server, any issues related to the file server (through the scan status of the job), and
determine the paths of the file server that can be migrated to the new system.
The Discovery module is still in a beta phase and can be used more for
 exploratory purposes.
4.1. Scan paths for the Discovery Spreadsheet

Using the Dashboard in the Discovery tab, you can view the file-system item count and size
provided by the file server in a GUI format.
However, before you can add a file server as part of the Planning report, you must first scan
the paths, by starting a discovery job for this path.
To start a discovery job
b. Click the Global Settings tab.
c. In Instance Settings, click the Edit button to edit the Early Access Features
options.
d. In Early Access Features, select Enabled, and then click Save.
e. Log out and log back in. The Discovery tab should now be displayed on the page.
2. Click the Jobs tab.
3. Select one or more file servers, and click Start.

4.2. Download the Discovery Spreadsheet

You can download the server information in a spreadsheet format.
To download the Discovery Spreadsheet
2.
Select one or more file servers, and click .
3. Confirm the Report type and Report format, and click Download.
5. Manage Reporting
5.1. What is Reporting?

Reporting gives insights into the various file-types stored on the file server. There are two
types of reports:
Web Reports
• These allow you to interactively drill down through the user interface – this is a fixed
report configuration only.
DB Reports
• A flexible definition is determined by a combination of set criteria. Each file found is

assigned a category and the results are then visible in the user interface and exported to
a database.
• Information is selected from the full directory tree only (not the sub-trees).
5.2. How to Create Reports
5.2.1. Configure a scan
To configure a scan, go to Reporting > Configuration > Scans, and click on the Add button:
1. Select the path and protocol to use – this effects the reported owner, such as name or
SID for SMB owner or group, numerical UID and GID for NFS owner or group:
2. If the protocol is SMB, select the Scan mode to include or exclude ownership
information.
Getting ownership information over SMB will reduce the throughput of

 the scan – excluding it, if it’s not needed, will speed up the scan job.
3. Schedule to run the scan job manually or at predefined start times. The scan job will
then crawl the complete directory tree and store the results to be used as input for any
subsequent report jobs. You can manually start, pause, stop, and otherwise monitor the
scan job’s progress by going to Reporting > Jobs.
5.2.2. Configure a report job
To configure a report job, go to Reporting > Configuration > Reports, and click on the
Add button.
In the Configure a report popup, give a name to the report:

An optional ID mapping file can be used to map raw SIDs or UIDs to a user
 name.
5.2.3. Configure the report definition
1. Go to Reporting > Configuration > Reports, select a report, and click on Edit.
2. In the Configure a report popup, click on Edit.
3. Select either a Web report or a DB report. Web reports have a fixed definition.
4. To configure a DB report, select the DB report tab, select the classification, and click on
the edit symbol:
You can select an output directory where the report will be written as a
 SQLite3 database file and multiple CSV file lists (one per category).
You are then presented with a number of classification options. A classification consists of a
number of criteria, and each one assigns a file to a category. In the example below, we’ll chose
file size:
This classification can then be further defined within certain parameters. In this case you
would edit the file sizes. For example:
The available classification criteria are:
• user (owner) of the file
• file path
• file type
• file size
• creation time
• modification time
• change time
• last access time
5.3. Running a Report

A report is recalculated automatically whenever one of its input scan jobs is updated. It is also
possible to force a report to be recalculated - to do this go to Reporting > Jobs > Reports >
Run.
When DobiMigrate runs a report, it will go through the scan results assigned to it, and these
files will be classified according to the report job definition.
5.3.1. Consult a DB report
You can look up the report job by going to either Reporting > Jobs > Reports, and clicking on
the magnifying glass, or, going directly to Reporting > DB reports and selecting the report from
the Report list.
The columns on the left of the DB reports table correspond to the classification criteria used in
the report definition. The next column shows the input scan path, and the remaining columns
show how many files, directories, symlinks or other file-types are included in that category.
The final column shows how many bytes are present in the files in the category.
Selecting a row and pressing the List files button gives the complete list of files matching the
categories represented by the row.
5.3.2. Export a Web Report
To export a web report, go to the Web reports tab. Select a report from the drop-down list in
the upper left corner and apply the required filtering. In the view below, the filter was set to
display all files of all users.
Click the Download button in the bottom left corner to open a dialog in which you can specify
the metadata to be exported.
Select the metadata you want to export and click Export, this will generate a CSV file
containing Path, Creation time, Owner (end user) and Size (in bytes) for the filtered list across
the two file servers. In this case, the list will contain 1,959,927 files.
Optionally, you can first inspect the list before you export it. To do this, select the button next
to the download button. This opens the file list on a separate tab.
5.3.3. Export a Database Report
DobiMigrate allows you to generate a database report containing the results of one or more
scanned paths. To configure a database report, go to the Configuration tab and click on
the Add button in the Reports tile. In the dialog that appears you can define the following
report information:
• Report name.
• An (optional) ID mapping file to upload a CSV file which contains one column with a UID
or SID value and a second column containing the mapping string for the UID or SID.
• A selection of the scanned paths to include in the report.
• The definition of the report. Options are:
◦ Web report: to show the discovered information directly on the Web reports tab.

◦ DB report: to configure a database report that can be exported and viewed

outside DobiMigrate.
After selecting DB report, you can define the output directory to save the report to and the data
classes to be included in the report. Additionally, you can import an existing DB report
definition (using the Upload button) or export it to a .json file for future import (using
the Download button).
You can choose predefined file types by adding, removing or renaming them (respectively by
using the + and - buttons and double clicking them). You can further define a classification by
selecting it and clicking on the cog icon.
Click OK when done. The report is added to the reports list and the data is exported in a DB file
to the output directory, from where it can be imported in a database reporting tool.
All reports, both web and database, are listed on the Jobs tab from where
 you can select a report and (re)run it.
5.4. File Deletion Jobs
5.4.1. What is a File Deletion job?
A file deletion job is an optional function that is licensed separately. If present, it is possible to
then start a deletion job for all the files in a DB report row.
5.4.2. How to start a File Deletion Job
To start a file deletion job, go to the DB reports tab, select a row, and press the Delete files…
button:
A dialog box will appear where you can enter:
• (optional) a description for the delete job; not used by DobiMigrate. It can be used to
record additional information about the job.
• an output directory where the results of the deletion job will be saved.
• (optional) delete jobs can create a tombstone file for every file that was deleted.
Tombstone files are written to the same directory as the delete file, and will have the
same name with an additional, configurable, extension.
The content of the tombstone file is also configurable and can, for instance, contain a
message explaining to the user why a file was deleted, and how to retrieve it from backup.
All the information about a deletion job (parameters, status, ok and error file
 lists) are also exported as a SQLite3 database and accompanying CSV file
lists.
The deletion job is started by approving the dialog. You can follow its progress by going
to Reporting > Jobs > Deletes. From here you can manually pause, resume, or stop delete
jobs.
Details about the job can be seen by clicking on the magnifying glass. The details screen will
show the deletion job’s parameters and status, along with full lists of all the files that have
been deleted, and any errors that may have occurred.
If a file needed to be deleted, but was already removed from the file server before DobiMigrate
could delete it, this would not be considered an error. In this case the file would be reported
as Not found in the Deleted & Not Found file list (instead of the Errors file list).
6. Set up a Migration
6.1. Add a Migration

DobiMigrate allows you to set up a migration by manually adding migration paths, or by using
bulk import to quickly add multiple migrations using a common set of migration options.
6.1.1. Add a Migration manually
1. Go to the Migrations module and click on the New migration button at the bottom right

to open the Select source path(s) window.
2. First select the source file server from the drop down at the top (see screenshot, below),
and then select the paths to be migrated.
3. Select the path(s) that you want to include in the migration. You can migrate at the root
level or at any subdirectory level.
DobiMigrate will prevent you from selecting migration paths that are a

subset or superset of paths that have already been set up for
 migration. If you are confronted with nested shares or exports, select

the path that is at the root of these shares or exports to cover for these
scenarios.
4. Once you have made your selection, click Next to go to the Select destination

path dialog. Here you can select the destination file server and location and create
additional directories to serve as the root level for the migration data.
When you have selected the migration paths, a dialog opens listing the select migration
paths and corresponding security information and migration-types.
5. Verify that the Protocol is filled in correctly. In case there are multiple options, you can
select the correct protocol using the drop-down in this column. The following values are
possible:
◦ NFS: NFS-only migration.
◦ SMB: SMB-only migration.
◦ Multiprotocol: Copy data over NFS and metadata using both NFS and SMB.
◦ SMB + symlinks over NFS: Copy files and directories over SMB. For symbolic
links, use NFS to create them and then apply SMB metadata.
When you select this option for the protocol, you can no longer select "Normal
symbolic link handling" for the "Symbolic links" option, only the following options
are possible:
▪ Create over NFS
▪ Apply metadata over NFS and SMB
▪ Create and apply metadata over NFS
◦ NetApp Mixed to Isilon: DobiMigrate will choose the most appropriate copy
protocol, NFS or SMB, for the data and metadata of each individual file or
directory.
A specific license is required to perform multiprotocol
 migrations (options Multiprotocol, Multiprotocol to SMB and

NetApp Mixed to Isilon).
6. Click Next when all of the values are correct.
DobiMigrate may then present an error message or warning at this
 time. If this is the case, follow up with the necessary actions as

described by the message. To continue to click Next.
DobiMigrate will present an overview of the migration options:
Make sure the relevant migration options are selected, then click Next. Read Configure
Migration Options for more information about all of the different choices.
7. DobiMigrate automatically performs a number of prechecks.

Review the Precheck results and assess whether, for example:
◦ The right permissions have been given to DobiMigrate to perform the migrations
from the source to the destination location.
◦ The destination locations are empty or not.
◦ Enough free capacity is available to perform this migration.
◦ The required ACL Policy settings have been set.
After review of the results, you can change the migration settings if needed or click Finish to
start the migration process.
In case a pre-check fails it is strongly advised to review the information

provided in the detail section and to fix the issue before continuing the
 migration setup. Cancel the migration setup, resolve the issue and start the
setup of the migration again. When in doubt, contact Datadobi because a
failed pre-check could lead to an incomplete or incorrect migration result.
6.1.2. Use bulk import to add multiple migration paths
The bulk import feature allows you to create multiple migrations by uploading a CSV or Excel
file. Templates for these files can be downloaded from the migration wizard as detailed in the
following steps.
There are two types of bulk import templates:
• Full Import: Allows you to import migrations for multiple file server pairs. In this case
you need to specify the source and destination server for each of the migration paths.
• Paths Only Import Allows you to import migration paths for one specific file server pair.
In this case, specify only the source and destination paths in the template. You will be
asked to choose the source and destination file servers, after uploading.
To add multiple migration paths in one go, via bulk import, take the following steps:
1. Go to the Migrations module and click on the New migration button at the bottom right

to open the Select source path(s) window.
2.
If you have not done so already, download the applicable template using the
button.
3. Add the migration path definitions to the template. The templates contain a description
of the data that is needed and how it should be filled in.
4. Upload the completed template using the Import button. From here you can browse to
the correct file.
If you are uploading the paths only import template verify that the
 correct source and destination file servers are selected in the

dropdowns at the top of the wizard.
DobiMigrate will process the import, perform some prechecks, and display the results
as a summary of imported migrations, including security mappings and protocols used.
Incorrect imports will be flagged and will need to be corrected in order to continue.
5. Proceed with the migration setup as usual as described in step 6 in the section Add a
Migration manually.
6.2. Configure Migration Options
6.2.1. General Options
• Iteration schedule: allows you to define when migration iterations will run. By default
the migration will start an iteration at midnight, but there are lots of different values to
choose from:
◦ Other…: allows you to define a custom iteration schedule.
◦ Use default: refers to the default schedule as defined in global settings. The value
for the default global iteration schedule setting can be changed
under Configuration > Global Settings > Migration Settings.
◦ Manual: In this mode you have to manually start the next process iteration in the
detail screen of the respective processes. Once started it will execute the process
for the migration path and pause it again before starting the next process step or
iteration.
◦ Presets: Predefined schedules are sets of starting times, for example every 6

hours would be 0:00, 6:00, 12:00 and 18:00.
• Start first iteration: allows you to bypass the Iteration schedule and start the first
iteration immediately.
• Minimum age: defines the minimum amount of time a file needs to be unmodified
before it will be taken into account for the next iteration. With this setting you can avoid
that DobiMigrate will migrate data that is updated constantly during the steady state
process. The globally defined default is set to 1 hour and can be changed
in Configuration > Global Settings, Migration Settings.
During dry run and switchover activities, all data will be migrated
 regardless of this setting.
• Root directory handling: allows you to determine how DobiMigrate should copy the
security (permission bits or ACL) of the root folder of the migration to the destination.
The possibilities are:
◦ Copy security: will ensure DobiMigrate copies the security as is defined on the
source. This is the default setting.
◦ Don’t copy security: will instruct DobiMigrate not to copy any security settings
from the source. Choose this option in cases where it is not possible to read the
source root directory permissions or to apply these permissions to the destination
root directory. This is, for example, the case when you cannot grant DobiMigrate
the permissions to do these actions.
◦ Convert inherited security to explicit: copies the security as is but the

inherited flag is stripped from each ACE (if present). When the root folder of the
migration on the source has an ACL containing ACEs that are inherited from its
parent folder, the normal copy option will copy this over to the destination as is.
This results in a situation where the root folder on the destination has an ACL
containing ACEs that are marked as being inherited from its parent while the ACL
of the parent folder does not contain these ACEs. If you then change the ACL of
the parent folder on the destination and allow changes to propagate to child
folders, the ACE inheritance algorithm will delete the inherited ACEs on the
migration root folder. It removes them because they are not present in the parent
ACL.
◦ Consolidate root folder: allows you to migrate directories from several source
paths into one destination path. DobiMigrate has built-in detection mechanisms
for consolidation scenarios and will warn you to apply consolidation where
needed.
When using this option, be aware that:
▪ the root security of any of the consolidated source paths is not copied, as it
is impossible to determine which exact source security settings to use on
the destination path.
▪ files directly in the source root folder will not be migrated. Only directories in
the root folder are migrated.
▪ if the consolidated source folders also contain sub-folders with the same
name, a blocking error message will be shown. In this case, you should use
the Consolidate sub folders option.
◦ Consolidate sub folders: allows you to run the consolidation for the root folder
and its 1st level sub-folders. The consolidation of the 1st level sub-folders is
executed in the same way as the consolidation of root folders, which is described
in the previous bullet.
• Excluded path/file patterns: directories or files matching these patterns will be

excluded completely from the migration. This means that the excluded files or
directories will not be migrated from the source file server. Also, files or directories will
not be deleted if they already exist on the destination file server.
• Skipped path/file patterns: directories or files matching these patterns will be skipped
during iterations that are not part of a dry run or switchover. This can be used to avoid
recopying files that will change often during the migration lifecycle.
Excluded/Skipped patterns uses file globbing when following these rules:

◦ The * character matches zero or more characters in a single name component of

the full path.
◦ The ** characters match zero or more characters in multiple successive name

components.
◦ The ? character matches exactly one character in a name component.
◦ The \ character can be used to escape other characters that would otherwise
have a special meaning. For example: \\ matches the backslash character and \{
matches the left brace character.
◦ One or more characters between square brackets [ ], match a single character in a

name component. For example: [xyz] matches the characters x, y or z.
◦ The hyphen – indicates a range of characters; [a-z] specifies all characters from a
to z (inclusive). A combination is also possible: [abce-g] matches a, b, c, e, f, or g.
If the ! character follows the left bracket, then it is used for negation: [!x-z]
matches any character except x, y and z.
◦ The characters *, ? and \ match their actual characters. The – character matches
its actual character if it follows the left bracket or the ! after the left bracket.
◦ The { } characters include a group of sub patterns separated by the , character;

the group matches if any sub pattern in the group matches. Nested groups are
not allowed.
◦ Leading periods/dots are interpreted as regular characters. For example: the

name .exe matches the * pattern.
◦ All other characters match their actual character.
◦ Examples:
▪ /departments/{hr,mgmt} will
exclude /departments/hr and /departments/mgmt
▪ /invoices/201[0-4] will exclude /invoices/2010 to /invoices/2014 but not,

for example /invoices/2015
▪ /home/**/iTunes will exclude all the directories named iTunes, anywhere

under the /home directory
/invoices/20\{12*,13*,140[1-9],141[0-1]} will
exclude /invoices/20120301,/invoices/20140901, /invoices/20141101 but
not /invoices/20141201 or /invoices/20150101
◦ You can enter multiple patterns in a text box via the Edit button on separate lines.
◦ You must specify each pattern in a separate line otherwise none of the patterns
on the same line will work. Press the Enter key after every pattern.
DobiMigrate will use a default set of exclude patterns depending on the
 source and destination file server types. The default patterns exclude the
system files and directories that should typically not be migrated.
• Allowed operations: gives you the possibility to restrict the operations that are allowed
during this migration. Note that this refers to operations being carried out on the
destination. As part of the migration process, DobiMigrate may delete directories/files
from the destination that are not on the source as part of the process to match the
destination with the source. DobiMigrate will never delete or update anything on the
source.
◦ All operations allowed: is the default value for this migration option. Allowing all
operations without restrictions is the required value to be able to perform a
regular full migration.
◦ No deletes: allows you to ensure no directories nor files will be deleted from the
destination at all during this migration process even when the directory/file no
longer exist on the source. The updates and/or additions that are made to
directories/files on the source will continue to be made/reflected on the
destination by DobiMigrate.
◦ No deletes or updates: allows you to ensure no directories nor files will be deleted
nor updated from the destination at all during this migration process. The updates
that are made to directories/files on the source will not be made/reflected on the
destination. This option can be useful when there is existing data on the
destination that may not be modified by the migration.
Preserve access times on source: allows you to preserve the access time of the source files
when migrating the data to the destination file server.
 This will impact performance and may require write-access on the source.
In addition to the general migration options, protocol-specific options and advanced options
are available for the data of the selected migration paths as described in the sections below.
6.2.2. General SMB Options
The following options can be set for SMB migrations:

• Follow junctions: By default, DobiMigrate will skip junctions when these are discovered.
◦ When a junction is skipped by DobiMigrate, it will be flagged as skipped with the

message Junction point skipped, but that is not een issue.
◦ When this option is enabled, DobiMigrate will not ignore the junction and migrate
all the content it refers to as if it was a directory with that content.
• Copy owner: This will copy the owner of the Security Descriptor. When not set, it will be
left blank on the data on the destination file server.
• Override owner: This owner will be used for all the migrated files and directories.
• Copy group owner: This will copy the group owner of the Security Descriptor. When not
set, it will be left blank on the data on the destination file server.
• Override group: This group will be used for all the migrated files and directories.
• Copy discretionary access control list (DACL): A DACL identifies the trustees that are
allowed or denied access to files or directories.
• Copy system access control list (SACL): A SACL contains access control entries (ACEs)
that specify the types of access attempts that generate audit reports. Each ACE
identifies a trustee, a set of access rights, and a set of flags that indicate whether the
system generates audit messages for failed access attempts, successful access
attempts, or both.
This controls whether it will be copied to the destination or not. Not all file
 servers support SACLs (for instance: Isilon stores them but doesn’t use
them).
6.2.3. General NFS Options

• Copy owner: copy the owner ID
• Copy group: copy the group ID
• Copy permissions: copy the POSIX permissions bits
• Copy access control list (ACL): copy the POSIX ACL (NFSv3 only) or NFSv4 ACL if
present. For NFSv3 to NFSv4 migrations, DobiMigrate will convert POSIX ACLs to NFSv4
ACLs automatically.
6.2.4. Advanced General Options
• Type: determines the migration workflow. This option is only available when setting up a
new migration.
The possible values are:
◦ Migrate: a regular migration.
◦ Rollback: this type can only be enabled for migrations that have been finished and
for which a rollback needs to be done. For more information, see Migration
Rollback.
◦ WORM: this type applies to migrations that include WORM data. For more
information, see Run a WORM Migration.
• Chain of custody: specifies for which set of data you would like to generate a Chain of
Custody (CoC) entry in the Chain of Custody File (CoCf). You can choose between the
following:
◦ Full (default): to generate a CoC for all of the data. This means that a CoC will be
generated for pre-existing data on the destination in addition to generating a CoC
for the data that is migrated during this process. The pre-existing data will be
validated by comparing it with the source.
In addition to providing a full chain of custody at the end of the migration, this
option also adds a safety net by trying to detect inadvertent destination
modifications made by users before a switchover is completed. When such
modifications are detected, DobiMigrate flags the modified items as "Modified on
destination" and will not synchronize them with their corresponding source items
during subsequent iterations. =
NOTE: If your destination contains a lot of pre-existing data, validation of that data
will impact the performance of the migration process.
◦ Migrated data: to limit the generation of a CoC to the data that is copied during
this migration process. This means that the data that already exists on the
destination will not be included in the CoCf of this migration.
In addition, the safety net provided by the Full migration option will not be used.
Thus, inadvertent destination modifications made by users will be overwritten
when DobiMigrate synchronizes the modified items with their corresponding
source items.
◦ None: if you don’t wish to keep a CoC for this migration at all. Additionally, files
that are modified on the destination before a switchover, will be overwritten
because there is no CoC.
• Advanced Integrity Protection: allows you to enable or disable the Advanced Integrity
Protection (AIP) setting. Enabling this setting ensures that DobiMigrate generates a
timely warning when the data on the destination is externally modified.
It is recommended that you disable this setting only in exceptional circumstances. For
example, if you keep seeing false positives for AIP and cannot track down the root cause
for them.
• Digest algorithm: allows you to choose the hashing algorithm used to compute the
digest value, to verify the migrated data and potentially generated a CoC. The default
option indicates that the digest algorithm specified in Configuration > Global Settings >
Migration Settings will be used. You can choose to use a different algorithm for this
specific migration by selecting a different value in the dropdown list. Note that when you
change this value during a running migration, your final CoC will contain a mix of
different digest algorithms.
• Source read-back verification: causes DobiMigrate to read back the data from the
source a second time, after it has been copied, to verify that the source potentially did
not supply any corrupt data. This option is disabled by default. Note that enabling this
extra verification, will impact the performance of the migration process.
6.2.5. Advanced SMB Options
For SMB migrations the following advanced options are available:
• SID map: to specify SID mapping from source to destination. This option is described in
more detail in section User Mapping.
• Clean invalid security descriptors: DobiMigrate will clean up any invalid security
descriptors found on the source platform before copying them to the destination.
• Replace "Creator Owner" and "Creator Group" in effective ACEs. These are two well-
known SIDs that can be used in inheritable ACEs. Some file servers are tolerant to them
appearing in effective (inherited) ACEs; others will refuse to do that. When this option is
enabled, DobiMigrate will replace these SIDs in effective ACEs by the actual owner and
group SIDs of the file.
• Alternate Data Streams:
◦ Copy: copies alternate data streams and report errors on failure.
◦ Copy, ignore errors: tries to copy alternate data streams, but does not report
errors when it fails.
◦ Don’t copy: skips alternate data streams.

• SMB file attributes to copy (Hidden, Not content indexed, Read only, System, and
Temporary).
6.2.6. Advanced NFS Options
• UID map: Here you can specify UID mapping to be used between source and
destination. This option is described in more detail in section User Mapping.
• GID map: Here you can specify GID mapping to be used between source and
destination(i will . This option is described in more detail in section User Mapping.
• Override permissions: allows you override the value of each individual POSIX
permission. Click on the edit symbol on the right to configure the copying of NFS
permissions. For each permission you can select to either copy it from source to
destination, or allow or deny the permission on the destination regardless of the value
on the source.
◦ Copy symlink permissions: allows you to copy symlink permissions.
◦ Copy FIFO (named pipe) files: allows you to copy FIFO (named pipe) files. A FIFO
file is a special file used for exchanging data between processes executing on the
same Unix host.
◦ Copy Unix domain socket files: allows you to copy domain socket files. A Unix
domain socket file is a special file used for exchanging data between processes
executing on the same Unix host.
◦ Copy FIFO (named pipe) ACLs: allows you to copy FIFO (named pipe) ACLs. A
FIFO ACL lists all of the FIFO’s access control entries.
◦ Copy Unix domain socket file ACLs: allows you to copy Unix domain socket file
ACLs. A Unix domain socket file lists all of the access control entries for the unix
domain.
If you do not explicitly select to copy these types of items, they

 will excluded from the migration.
6.2.7. Advanced Multiprotocol Options
• Invalid SMB Filenames: select the behavior for when a file or directory can’t reliably
access over SMB because of, for example, invalid characters in file names, or multiple
file names with different casing for example.
◦ Generate errors to report an error.
◦ Migrate files using NFS only, generate error for directories to report an error for
directories, fall back to an NFS only copy for files (SMB security descriptors and
alternate data streams will not be copied).
◦ Migrate files and directories using NFS only to fall back to an NFS only copy for
files and directories (and the complete subtrees below them). SMB security
descriptors and alternate data streams will not be copied.
• Symbolic links: determines which protocol is used to create symbolic links.
◦ Normal symbolic link handling: symbolic links are handled the same way as files
or directories.
◦ Create over NFS, apply metadata over NFS and SMB: all symbolic links are
created using the NFS protocol. Metadata is copied using both the NFS and SMB
protocol.
◦ Create and apply metadata over NFS: all symbolic links are only copied using the
NFS protocol.
6.3. Change Migration Protocol

You can change the migration protocol if you have selected the incorrect protocol during a
migration setup.
 If you change the protocol, DobiMigrate will recopy the metadata.
To change the migration protocol
1. In the Running tab, under Migrations, select an item, and click Options.
2. Select Change Protocol…. The Migrations wizard is shown at the Selected Migrations
Shares and Exports page.
If you are changing the protocol for an Isilon target, DobiMigrate

checks the chmod (007) on files with existing ACLs Isilon ACL policy
 to ensure it is allowed to fully recopy metadata; if not, it is flagged as
an error in the Precheck results page.
3. Select the correct protocol, and click Next.
4. Specify the Migration Options as needed, and click Next.
5. Review the Precheck results, and click Start.
6.4. User Mapping

During the setup of a migration you can upload SID, UID and/or GID mapping files. Depending
on the chosen source and destination file servers, the following upload buttons become
available:
• If both source and destination have SMB configured then the SID Map upload button
will become available.
• If both source and destination have NFS configured then the UID Map and GID
Map upload buttons will become available.
6.4.1. SID Maps
In a Windows NTFS file system, all file access permissions and auditing controls are
associated with Security Identifiers (SIDs). A SID is a variable-length bit string which is
guaranteed to be unique worldwide. The relationship between a SID and a domain\account or
domain\group name is contained in the data structures maintained by a Domain Controller or
the Security Accounts Manager of a local machine. DobiMigrate provides an easy way of
(re)assigning files and permissions to a new account or group. This can be done by uploading
a SID map during the setup of a migration. At that time DobiMigrate validates its content
for syntax and the ability to resolve the imported user accounts.
The following mapping types are allowed:
1. [S-1-5-21-2694190442-3250320402-2687946070-1111]:[S-1-5-21-4248949456-
2451647171-897633524-17198]
2. [S-1-5-21-2694190442-3250320402-2687946070-1111]:CORP.COM\Administrator
In the first example above, a SID has been replaced with another, absolute SID. In the second
example, the SID will be replaced with the user Administrator that is part of the corp.com
domain. In the third example, the SID will be replaced with the user Administrator from the
domain in which the respective proxy is running.
SIDs that are no longer valid can be removed by specifying the REVOKED as
 the destination value.
6.4.2. UID/GID Maps
UID stands for User Identifier, GID stands for Group Identifier. Both are numbers identifying
each user/group on systems with NFS exports (typically UNIX systems). There is a 1:1
mapping between the user name and the UID, and between the group name and GID. The UID
and GID are unique.
The following mapping types are allowed:
1. Admin_source:Admin_destination
2. 100:Admin
3. 100-103:500
◦ In the first example above, files with owner or group Admin_source on the source
will be transferred to the destination with owner/group Admin_destination.
◦ In the second example, files with owner or group 100, will be transferred to the
destination with owner/group Admin.
◦ In the third example, files with owner or group 100, 101, 102 and 103 will be
transferred to the destination with owner/group 500.
UID/GID name mapping is only available for NetApp 7mode, CDOT and
Isilon. VNX and Unity only support UID/GID number mapping.
 Thus, Admin_source:Admin_destination will not work on Unity,
whereas100:101 will work.
6.4.3. View user mapping details
To view the details of uploaded mapping files, go to Configuration > User Mapping. The
screen below shows the details of a file that has been uploaded for a specific migration. At the
top, summary information is shown such as the File name, the number of Entries and the
number of Blank lines, Rejected lines, Source or Destination user account errors.
Select a user mapping and click on the Details button to open the window below with more
details.
In the Rejected lines table, DobiMigrate lists the Line number and the Content that does not

meet the syntax rules and is therefore rejected. The User account errors table shows the user
mapping entries where an imported user account could not be resolved into SID by the
proxies. The File Server indicates for which file server the mapping could not be done,
the User account details the domain and user account that could not be mapped and the
Error provides more context on the kind of error.
The User mapping table shows the user mapping pairs that have been imported. These
mappings will be applied when you set up migrations using this user mapping.
DobiMigrate will not validate whether these user mappings exist, it will use
them as is. So it is critical that they apply in your environment and that
 their mapping is correct. DobiMigrate only resolves the provided SMB
usernames to SIDs.
In case you want to use SID mappings, it is important that their syntax is correct and that the
user accounts exist for the mappings to use. DobiMigrate will only proceed with setting up a
migration when there are no rejected lines and user account errors. In case of errors, first
review and resolve the errors in your mapping file. Go back to the migration options and delete
the current user mapping. Then upload the updated mapping again for validation by
DobiMigrate.
6.4.4. Applying user mappings in migrations
Note that it is also possible to assign an owner SID and/or a group owner SID when you set up
a new migration. In these fields in the Migration options window, you can specify only the SID
values (e.g. [S-1-5-21-2694190442-3250320402-2687946070-1111]). This setting will be
applied independently from any SID maps that are set up at the migration level. Whenever a
SID value has been entered for one of these fields, the old SID values will be ignored and
replaced with the new ones for all the data in your migration.
6.5. Multiprotocol
Multiprotocol is a licensed feature in DobiMigrate, and is not available by

 default.
6.5.1. What is a Multiprotocol Migration?
There are two different types of file system security models: NTFS (ACLs) and Unix (Posix
mode bits), and in most cases a file system will use either one of these.
It’s also possible, however, for a file system to use both NTFS and Unix security settings.
Depending on the access protocol, one of two security settings is used: NTFS security for
objects accessed over SMB, and POSIX mode bits for objects accessed over NFSv3.
For both sets of security settings to be transferred, a multiprotocol migration needs to be

made, that is, a migration using a combination of both protocols to migrate security
information.
6.5.2. Challenges
Multiprotocol migrations can present difficulties when migrating between different file server
product families because there are no industry standards governing security. This can lead to
confusion, because while both SMB and NFSv3 are standard protocols, the simultaneous
multiprotocol access of file system objects using both of them is not.
As a result, any vendor that provides a multiprotocol function has created a proprietary
method of maintaining security as it relates to the storage of permissions and the resulting
evaluation and enforcement of access control.
Directory and filename differences
Characters
• NFS is case-sensitive and SMB is not.
• The following characters are not permitted in SMB filenames: \ / : * < > |
Trying to retrieve a file named with invalid characters will result in an error.
• An SMB path can’t end on a . or a <space>.
Encoding
SMB uses UTF-16 encoding for its filenames while NFS uses the encoding supplied by the
client. It’s therefore quite possible that a file can have a different name, based on whether it’s
viewed through NFS or SMB.
Special File types
There are special file types that are only available on NFS, such as sockets and pipes.
6.5.3. Multiprotocol and DobiMigrate
How to configure a multiprotocol migration
1. Once you’re logged in to DobiMigrate, go to the Migrations module, and click on New
Migration.
2. Select the source and destination file servers, and the destination path.
3. In the Selected Migrations, Shares and Exports popup, select Multiprotocol in the
Protocol column:
7. Manage Migrations
DobiMigrate provides several options to manage migrations.
7.1. Running migrations

To see when the next iteration will run for a migration path, go to the Migrations module and
click on Running.
In this example, the scheduling column shows that:
• The paths /vol/vol_unix/ErrorDir, /vol/vol_unix/Small, and

/vol/vol_unix/Test are running which means that a new iteration is being
executed.
• For the path /vol/vol_ntfs the next iteration will start within 6 hours and 56
minutes.
• The migration for /vol/vol0 will only start after manual intervention.
• The path /vol/vol_unix/Big is paused by the user.
The orange color indicates the paths that are waiting for an action to proceed.
Irrespective of the configured iteration schedule setting, you can start a new iteration
immediately by selecting the migration path and clicking the Start button under the table. For
more information, see Manually start a migration iteration.
Use the Pause and Resume button to manually pause and resume the iteration of a migration
path.
Use the Options to configure the migration options or to change the migration protocol.
 If you change the protocol, DobiMigrate will recopy the metadata.
Click the magnifying glass to view more details of the iterations for a migration path.
7.1.1. Manually start a migration iteration
You can start the next iteration or a special iteration of a migration path by selecting the path
from the list and clicking the Start button under the table. The start iteration wizard will first
ask you to specify which type of iteration you would like to start:
• Incremental: The goal of an incremental iteration is to detect if any changes were made
on the source since the previous iteration and if there are any, apply them to the
destination.
a. Select the Incremental iteration type and then click Next.
You can then specify the type of incremental iteration:
▪ Normal: Applies all source changes that occurred since the previous
iteration to the destination. This option allows you to manually trigger the
same type of iteration that is triggered automatically based on a defined
schedule.
▪ Force metadata copy: Recopies all metadata from source to destination for
all items in the migration, even if it has not changed. The actions of a
normal iteration, as described in the previous bullet are also applied.
▪ Force overwrite of external modifications on destination: Overwrites the

files that have been modified on the destination before a migration has
been switched over. If this option is not selected, externally modified files on
the destination server will not be overwritten to maintain the integrity of the
information.
• Retry items with errors (xx): allows you to run an incremental iteration limited to a
subset of items that gave errors during the migration, instead of a normal iteration that
runs for all items. The number between the parentheses is the total number of errors in
this migration.
a. Select the Retry items with errors (xx errors) iteration type and then click Next.
DobiMigrate will then display a list of all the items that gave errors (limited to a
max. of 5000), with the possibility to narrow the list of items down by filtering on a
particular string or via the filter button that allows you to filter different criteria
such as on a certain category of errors.
b. Select one or more of the errors, and click Next. You can also specify a filter to
display a subset of the errors.
When you filter the errors, the whole set of errors is filtered even
 though only the first 5000 are shown.
c. Confirm you want to retry the selected errors, and click Next. The iteration will
then be started and all the selected errors will be retried.
All the errors will be retried. However, not all data will be
recopied. For example, if the command that failed was a
metadata copy then only that metadata copy will be redone, and
 the data will be kept. Another example is if the command was to

create a directory or delete a file, then that will be retried. In
addition, this option will not overwrite files that have been
marked as ‘modified on destination’.
• Verification: A verification iteration compares content and metadata of all items in order
to check that they are consistent and that there is no data corruption.
a. Select the Verification interation type, and click Next.
b. Specify whether you would like to verify:
▪ All which will verify that there is no data corruption nor metadata
inconsistencies.
▪ Only content which will only verify that there is no data corruption.
▪ Only metadata which will only verify that there are no inconsistencies in the
metadata.
Not all file servers store metadata the same way. If you
migrate between different file server types, it is very likely
that the verification of metadata will report errors. The
 metadata is not exactly the same, but that does not

necessarily mean that the migration has errors. In this
case, you can avoid these types of errors by selecting to
verify ‘only content’.
When an option has been selected and the migration iteration has started by clicking Next, you
can view the results in the Iteration details window (see Iteration Details View).
8. Monitor Migrations
You can monitor the progress of a migration from different views and at different levels:
• High level: via the Dashboard
• Migration path level: via the Iterations view
• Process level: via the Activity view

8.1. View Dashboards

The dashboard or grid view allows you to monitor the progress of all migrations. This allows
you to monitor a large set of servers and migrations, for example. The color of the tiles will let
you check, at a glance, if all is ok or if an intervention is needed.
You can control what’s displayed in the dashboard by selecting a predefined filter from
the Group by dropdown list and/or entering details in the Filter field.
8.1.1. Tile color coding
Green indicates that the migration is running without issues and that no action is required.
Yellow/orange indicates that an action or decision is required by the user. Examples are:
• The user needs to start the next process step or iteration for a migration that is running
in manual mode. The process tile containing a manual migration will be orange when it
is in waiting mode. A process can also be in waiting mode because the user has defined
specific iteration schedules.
• Not all migration paths have been set up for a specific source/destination file server
pair.
• Not all shares or exports found on the source file server have been created on the
destination file server.
Red indicates that there are issues that need to be resolved in order to successfully complete
the migration. Examples are:
• Errors that pop up during the execution of a process step and that are out of control of
DobiMigrate.
• You try to complete switchover windows for shares and exports that do not exist on the
destination environment or for which no explicit decision was taken to migrate them.
8.1.2. Shares & Exports
In the Shares & Exports module, you can view interactive tiles under Dashboard, and use
the Filter field to select source and/or destination names.
You can select either Shares or Exports from the tiles in the Dashboard, or select their

individual tabs.
Once Shares or Exports is selected, you can select a source/destination file server pair and,
using the buttons at the bottom of screen:
• Rescan: rescan the fileserver’s metadata and recalculate the destination status
• Modify source access: change source shares and exports to read-only or export scripts
to change the source access.
• Restore source access.

• Mark as Unresolved: mark the selected settings as unresolved. This tell DobiMigrate

that you’ll take care of it yourself and it should no longer go reported as unresolved.
• Mark as Resolved: mark the selected settings as resolved.
• Fix…: fix missing shares or exports on the destination server.
8.2. Migrations Dashboard

The Migrations dashboard shows all process steps of the scheduled migration paths.
Whenever a migration path has been processed in a process step, it will move to the next step
automatically unless the user explicitly has chosen to run it in manual mode.
The rows are groups of migrations as selected in the Group by dropdown list. Clicking on a tile
will show all migrations from the grouping in the selected state.
Click on a tile to view its details.
When no migration paths are processed in a specific process step, then the
 view can be empty.
While the dashboard provides an overview, the four stages of migrations can be viewed under
the following tabs:
For each running process, progress details are displayed in the dashboard on tiles, and each
tile gives an overview of the following information:
• Planning: a complete overview of the migration paths, and the current migration status
for each of those paths.
• First Scan: the migration paths for which the first scan is running.
• First Copy: the migration paths for which the first copy is running.
• Steady State: the migration paths for which scans are executed on a scheduled basis.
Any (meta)data differences between source and destination are then migrated. A
migration path will remain in this state until it is scheduled for switchover.
• Finished: the migration paths that are successfully switched over.
• Post Finish: the migration paths for which additional actions are being executed, such
as verify content, for example.
8.2.1. Planning
This view provides a clear overview of the migration of the different directories during a large-
scale migration. It shows the different migration paths that have been defined, what the status
of their migration is, and provides the necessary insight to ensure that all of the directories
have been migrated successfully and that none have been missed.
As you can see, DobiMigrate will retrieve and present the sibling directories on each of the
levels for the defined migration paths.
The key feature of this view is the Show coverage option that you can select by clicking in the
button at the to left of the screen. By turning this option on, the view is supplemented with a
visual indication of the completeness of a migration per path. We call this path coverage, and
it is displayed in the status column on this view.
When Show coverage is selected, which is the default, DobiMigrate will use the status column
to provide path coverage information. Each row of the planning table will display one of the
following path coverage values:
• migrate: a migration has been defined for this directory. The directory and all its
contents will be migrated to the destination server.
• missing: a migration has not been defined for this directory.
• excluded: this directory has been marked as excluded from the coverage report, and will
not be migrated.
You can use the Exclude from coverage report shortcut menu (right-
 click option) to exclude directories and files from the coverage report.
• incomplete: the contents of this directory will only be migrated partially. One or more
migrations exist for child directories of this directory, but not for all child content.
• complete: all child directories of this directory are either part of a migration or have been
marked as excluded.
You can filter this view on paths by clicking on the button at the top left of the screen and
selecting the root(s) whose paths you would like to see, or by using the filter wizard by clicking
on its button in the top right of the screen.
8.2.2. Running
This includes first scan, first copy, and steady state. You can choose what to display through
the View and Group by dropdown lists.
8.2.3. Finished
This shows the paths that have been switched over. Choose what’s displayed through
the Group by and Paths dropdown lists.
8.2.4. Post Finished
This includes further actions that may be required such as verification, fixing and metadata for
example. Choose what to display through the View, Group by, and Paths dropdown lists.
8.2.5. Statistics
This presents a visual overview of how the source data is structured and how it might impact
migration speeds. The view is updated after each iteration to allow for any changes that may
have occurred since the previous iteration.
For further details within each tab, hover over individual columns for tooltips, for example:
You can also access the tabs by clicking on an active tile under its corresponding column.
8.3. Iteration Details View

You can open this view by navigating to Migrations > Running, and then clicking on the
magnifying glass icon of a running migration path.
This view is called the Iterations Details View. It allows you to monitor running migrations
closely by presenting all of the iteration’s details, and allows you take any actions needed
during the running of the migration.
The source and destination paths of this migration are presented at the very top of this view
together with the following action buttons:
• Statistics: takes you to a view of the statistics and histograms that you can consult
regarding this migration.
• Pause: pauses the this migration if it is currently running.
• Resume: re-starts the running of this migration if it was paused.
• Start: allows you to manually start a new iteration for this migration, see Manually start
a migration iteration for more details.
In addition to the normal incremental and verification iterations, you

also get the option to Retry items with errors (xx errors). As previously
 described, this allows you to run an iteration of this migration limited

to the items with errors, which can save significantly on time when the
number of items with errors is limited and the migration is rather large.
• Options: allows you to view/edit the options of this running migration, see Configure
Migration Options for more details.
The iterations details view consists of the following five main parts that are explained in the
sections hereafter:
• Summary is the table at the top of this view and presents a summary of the most recent
iterations for this migration, including the First Scan and First copy iterations.
• Iteration details, directly underneath the Summary on the left, presents the main
characteristics of the iteration that is selected in the Summary, including histograms
that present the migration data graphically.
• Scan details, underneath the Iteration details on the left, displays the activity that
happened for the selected iteration of the migration during source and destination scan.
• Command details, underneath the Iteration details in the middle, displays the activity
during the copy phase of the selected iteration.
• Error details, underneath the Iteration details on the right, aggregates the errors from
the Scan and Command details, and provides error categorization.
8.3.1. Summary table

The Summary table contains the following information:
• Status: indicates the current status of the iteration. The possible values are:
◦ Success when the iteration has completed successfully,
◦ Running (when the migration is ongoing) or
◦ Failed (when an error occurred that blocked the progress of the iteration).

• Type: specifies the type of the iteration.
This field is filled in with a '-' during normal incremental iterations.
The other possible values are:
◦ Dry Run
◦ Switchover
◦ First Scan
◦ First Copy
◦ Recopy metadata
◦ Verify content
◦ Verify metadata
◦ Verify all
◦ Copy WORM
◦ Verify WORM
◦ Verify WORM metadata

• Start: the start time of the iteration. DobiMigrate uses the same timezone that is
specified for the browser in which it is running.
• End: is the end time of the iteration.
• Duration: is the length of the iteration.
• To Do: is the number of operations to be done.
• Done: is the number of operations completed.
• To Copy: the total amount of capacity to be copied from source to destination (may

include verification depending on the validation options).
• Capacity copied: is the amount of data that has already been copied (may include
verification depending on the validation options).
• Capacity deleted: is the amount of data that has been deleted.
• Skipped: the number of operations skipped. These are the items that were part of the
iteration that did not meet the set minimum age criteria for that iteration. If for instance
the minimum age has been set to 1 day and DobiMigrate comes across a file that was
stored 3 hours ago, then it will be skipped in this iteration.
• Capacity Skipped: the amount of data that is not copied based on the minimum age
setting.
• Errors: the number of errors that occurred during this iteration, and in between
parentheses the number of errors that are recurring.
A recurring error is an error that already occurred during the previous

iteration(s), and typically needs investigation. The other errors that
 appear for the first time in this iteration have a high chance of being
automatically resolved in the next iteration.
Some types of errors block the iteration. When this is the case, the
 status of the iteration is set to Failure and the error message is

displayed in the Iteration details table.
You can view additional details of these errors by looking at the Error Details table.
You can select a specific iteration by clicking on one of the rows in this table. The Iteration
details view underneath this table will then present details of this selected iteration.
8.3.2. Iteration Details table
The table underneath the Summary is the Iteration Details table. This table displays the details
of the iteration that is selected in the Summary.
The left side of the Iteration details lists basic statistics. The type of statistics that is shown
here depend on the status of the iteration. The statistics are described in more detail further
on in this paragraph. The right side of this view presents a number of Histograms, which give
you a graphical representation of the migration. The four histograms, which you can cycle
through using the arrows on each side of the displayed histogram are: Directory size, File
modification time, Directory depth, and File size, see Scan Statistics for more information.
As long as the status of the selected iteration is Running, the following statistics are displayed:
• Status: this is the status of the iteration. This status matches the one displayed in the
Summary for this iteration, but gives more detail when it is running by presenting sub-
steps, the total number of sub-steps, and the current sub-step number. This can give
you an idea of how the iteration is going.
When you click on the icon next to this status, the Activity view is opened which shows
the details of the current activity. See Activity view.
• Start: the time this iteration was started.
• Duration: the exact duration that the iteration has been running up till now.
• Throughput: the actual number of items scanned per second. An item can be a file,
directory, symlink, or metadata.
• Bandwidth: an approximation of the amount of network bandwidth being used by this

iteration.
• Progress (throughput): the percentage of items that have been processed out of the
total amount.
• ETA (throughput): the estimated time of completion based on the number of items
processed so far and the current throughput.
• Progress (bandwidth): the percentage of capacity copied out of the total amount.
• ETA (bandwidth): the estimated time of completion based on the capacity processed so
far and the current bandwidth.
When the selected iteration is completed with Success, the following information is displayed:
• Status, start and stop time of the iteration. These are the same values as displayed in
the Summary above.
When you click on the icon next to this status, the Chain of custody results is opened
which shows the chain of custody data related to this iteration. See Chain of custody
results.
• Duration: the exact value for the total duration of the iteration..
• Source Scan Duration: the total time DobiMigrate took to scan the path on the source
file server.
• Destination Scan Duration: the total time DobiMigrate to scan the path on the
• Command Duration: the total time DobiMigrate took to execute the operations.
An iteration’s status is set to Failure when one or more blocking errors occurred while it was
running. The following information is displayed:
• Status: the status of the selected iteration, as displayed in the Summary.
When you click on the icon next to this status, the Chain of Custody results view is
opened which shows the chain of custody data related to this iteration. See Chain of
custody results.
• Failure reason: presents the blocking error that caused the iteration to fail.
• start and stop time of the iteration. These are the same values as displayed in the
Summary above.
• Duration: the exact value for the total duration of the iteration is shown here instead of
the rounded value in the Summary.
• Source Scan Duration: the total time DobiMigrate took to scan the path on the source
file server.
• Destination Scan Duration: the total time DobiMigrate to scan the path on the
• Command Duration: the total time DobiMigrate took to execute the operations.
In case of very large files or directories containing large amounts of files, it
 might take some minutes before the statistics are refreshed. DobiMigrate
waits for these operations to complete before updating the statistics.
8.3.3. Scan Details table

The Scan Details table presents a summary of what has been discovered during the scanning
phase of the selected iteration. It lists the number of items found on the source as well as on
the destination. This information gives you an idea of what the migration entails, which types
of items that will be processed, and the progress of the migration.
This table presents the following types of items:
• Files: the number of files that have been discovered
• Directories: the number of directories that have been discovered
• Other: the number of other items (symbolic links, junctions, sockets, pipes..) that have
been discovered
• Exclusions: The number of items that matched the exclude pattern of this migration
 When a directory is excluded, its content is not scanned.
• Errors: the number of items that caused an error during the scanning phase of this
iteration.
You can view a complete listing of the scan results by clicking on the small icon next to either
the Source heading or Destination heading to get the complete listing of either the Source or
Destination scan results respectively. Note that the icon is only available when there are
results for the selected iteration.
You can also retry specific errors in the Destination Scan Results table by selecting the error,
clicking the Details button and then clicking the Remigrate button.
8.3.4. Command Details table
The Command Details table presents a summary of the activity during the running operation
phase. It lists which commands have been executed and how many times they have been
executed during this iteration.
The columns of this table are:
• Type: the type of command (Copy/Verify File, Copy/Verify Dir,….)
• To Do: number of commands to be done, per type
• Done: number of commands done, per type
• Errors: number of errors, per command type
You can view a complete listing of the commands that need to be performed and that have
been performed by clicking on the small icon next to either the To do heading or Done heading
respectively. The icon is only available when relevant.
Note that for an iteration of the type Verification, this table is replaced with the Verification
Details table.
8.3.5. Error Details table

The Error Details table aggregates and displays the number of errors encountered during
source scan, destination scan, and the execution of the commands.
The most common errors have been classified in the following categories:
• Permission denied: The DobiMigrate proxy shown has not been given the permission to
perform the operation.
• Out of space: The destination file server does not have enough capacity to accept the
file.
• Not found: The file is not found on the source file server. This can happen when the file
was deleted between the scan operation and the subsequent copy process.
• In use: The file on the source file server has been locked and is not available to
DobiMigrate to read it for a copy operation.
• Timed out: The operation timed out because the DobiMigrate Core did not get a timely
response from the DobiMigrate proxy.
• Modified on destination: DobiMigrate works in iterations to transfer changes on the

source to the destination, including copying, deleting, overwriting data, and so on.
Normally, when a migration is running, you would make the destination read-only to
ensure that there are no chances of data loss before a switchover. With the introduction
of CoC, an additional safety mechanism is included, namely, destination-modification
detection. With destination-modification detection, every time DobiMigrate detects
external destination changes it triggers a "Modified on destination" error. The only
exception is when destination data was deleted, where data will be recopied without a
warning or an error.
The destination-modification detection option is included as a safety
 net and will work only if CoC is enabled. It is still not recommended
writing to the destination during a migration.
Destination-modified detection uses the change timestamp, maintained by the file

server. This information is read-only and is incremented by the file server every time an
item is changed, for example, when a file is written to, a directory has an item added or
deleted, and so on. DobiMigrate records the change timestamp every time it copies a
new item or updates an already migrated item. If content was changed on the
destination, then the change timestamp will not match the recorded change time value.
This indicates to DobiMigrate that the item was externally modified. Normally, this
would also mean that those changes would be overwritten with the changes on the
source. To prevent this issue, DobiMigrate triggers a Modified on destination error. Any
item with a Modified on destination error will no longer be changed by DobiMigrate and
will not be kept in sync with its corresponding source item.
What can you do in case you encounter a modified on destination error? Examine the
cause for external changes on the destination. What caused the change timestamp to
be incremented? Who made the change? Was it a process or a person? Some of the
more obscure reasons for the change are: file changes by a virus checker, attribute
changes by a backup software, quota setting on a destination filesystem, and so on.
Verify that the changes are valuable or not. If they are, make sure you take a backup
before you continue.
To resume source to destination syncing for items that have the "Modified on
destination" error, you can:
◦ Delete destination items
◦ Run a selective retry
◦ Run a new migration iteration with the force overwrite option
With this option, DobiMigrate will resume keeping destination items in sync with
the source, and any changes done on the destination will be overwritten.
• Network issue: A network issue occurred during the operation.
• Other: None of the known categories apply. In this case, you can find out more about the
error by viewing the complete listing.
You can view a complete listing of the items with errors by clicking on the small icon next to
one of the column headers. The icon is only available when relevant.
8.3.6. Verification Details table

The Verification Details table: lists the results of the chosen verification option for the selected
iteration. This table is only presented when viewing the details of a verification iteration. In this
case it replaces the Command Details table, which is less relevant during a verification
iteration as the commands will always be a type of verification.
• OK: No issues found during verification.
• Failed: The verification itself failed; the item could not be read because of permission
issues, network not available, or other reasons.
• Not verified: The item has not been verified. This column should always be empty. Any
value in this column indicates an issue.
• To be copied: The content of the item has been modified on the source file server and
will be (re)copied to the destination file server during the next iteration.
• To update metadata: The metadata of the item has been modified on the source file
server and will be (re)copied to the destination file server during the next iteration.
• To be deleted: The item is no longer available on the source file server and will be
deleted on the destination file server during the next iteration.
• Content mismatch: The timestamps of the items are the same but either the size or the
content is different between the source and destination file server. This has to be
investigated in more detail and will not be fixed automatically during the next iteration.
• Metadata mismatch: The timestamps on the metadata between the source and
destination file server indicate that the source metadata has been copied to the
destination file server, but there is still a mismatch between the actual metadata. This
has to be investigated in more detail and will not be fixed automatically during the next
iteration.
Not all file servers store metadata the same way. If you migrate
between different file server types, it is very likely that the verification
 of metadata will report errors. The metadata is not exactly the same,
but that does not necessarily mean that the migration has errors.
• Modified on target: The item has been modified on the destination file server. This may
indicate that there were changes on the destination. This has to be investigated in more
detail and will not be fixed automatically during the next iteration.
The validation is done hierarchically; if some criteria are not met for an item,
 the validation will stop.
8.4. Additional views for more information

On top of the information that is immediately visible in the Iteration Details View, DobiMigrate
allows you to click through to additional, even more detailed information on the a migration.
You can access the additional information by clicking on the small icons you may find next to
the Status in the Iteration Details table or by clicking on one of the small icons in the headers
of the Scan Details, Command Details, Error Details, and Verification Details tables. It is in the
description of those tables that you will find when/which additional detailed information is
available.
8.4.1. Activity view
The additional Activity view displays detailed information on all the activity of the iteration.
You can access this view by clicking on the small icon next to the status, when the iteration is
running in the Iteration Details table.
This additional view shows the details of which commands are being executed for this running
iteration. DobiMigrate presents a list of each and every command it is executing and specifies
whether it is on the source or destination, through which proxy, with which protocol, etc.
You can specify which columns are included in this view with the icon at the
 far right of the header row.
This view shows a maximum of 1000 entries, sorted on age. You can export the complete
overview of activity, for this iteration, using the export button at the bottom left of the screen.
Occasionally it might look as if nothing is happening, the most common causes are:
• the migration is moving from scan activity to command activity (solution: wait), or;
• the proxies are not running (solution: start up the relevant proxies).
8.4.2. Chain of custody results
The Chain of custody results of a migration iteration can be consulted as soon as it has

stopped running, in other words when its status is success or failure, by clicking on the small
icon next to the status in the Iteration Details table.
Key to a Chain of Custody is proving the integrity of an item throughout its lifetime. This can be
proven through the use of content digests. A content digest is calculated for every individual
item encountered during the migration and logged in a Chain of Custody record along with its
identifiers. A second content digest is calculated immediately after migrating the item, and
compared with the first to prove the integrity of the item after migration.
The three most useful columns in this view are:
• Path: which helps you identify the item whose integrity is evaluated.
• Status: in other words, the result of the integrity evaluation. The possible values are:
◦ In sync: which means that the item is the same on source and destination
◦ Excluded: due to exclusions defined in this migration’s options. See Configure

Migration Options for more information.
◦ Modified on destination: indicates the files on the destination have been modified
by users before a migration has been switched over. Files marked with this flag
will not be synchronized with the source because updated files will be overwritten
by the content in the source.
◦ Retained: which means that the item would have been deleted to be in sync with
the source, but was retained due to the no deletes option defined in the
migration’s options.
◦ Out of sync: which means that a change on the source was not propagated to the
destination, see further details in Info.
◦ Unknown: in this case you should have a look at the details in Info.
• Info: which gives additional information in case the status is Excluded, Out of sync or
Unknown.
You can export the Chain of custody results, for this iteration, using the export button at the
bottom left of the screen.
8.4.3. View Additional Details
Each of the information tables at the bottom of the Iteration Details View (Scan Details,
Command Details, Error Details, and Verification Details) provides links in the headers, given
there is data in the columns, to get additional information as the tables on the main Iteration
Details View only provide a summary.
The additional information is provided by DobiMigrate to allow you to follow up the activity of
the iteration in very fine grained detail. This is typically useful during trouble-shooting.
You can specify which columns are included in these additional information
views with the icon at the far right of the header row, and you can export the
 complete overview of activity, for this iteration, using the export button at the
bottom left of the screen.
8.5. Export Migration Issues

Migration issues can be grouped and exported at two levels: at the file server level or at the
migration path level. In both cases, go to the Migrations module.
8.5.1. Export Issues at File Server Level
To export a list of issues, locate your migration(s) under their corresponding tab (Planning,
Running, or Finished), select them, and click on the error button in the bottom left corner:
This opens an export dialog with the following options to select from:
• Filter: select a filter to export all failures or a subcategory based on the definition of
exception categories (see below).
• Destination: you can download the list to your desktop via a browser or put the exported
file in DobiMigrate’s dropzone.
When you select Based on the Exception Category, an extra table is shown allowing you to
make a more granular selection for the records to be exported.
Select which categories you want to export, confirm the Destination and press the
Export button.
For large files, it is advised to use the dropzone otherwise your browser could
be locked for a while when the information is collected and downloaded.
 Depending on the amount of entries you have selected, the files size can be
GBs or TBs.
8.5.2. Exported Information
The following fields are exported into a .csv file:
• Source: Name of the source file server.
• Source Path: The migration path on the source file server.

• Destination: Name of the destination file server.
• Destination Path: The migration path on the destination file server.
• File server: Name of the file server for which the records are exported.
• Path: The path for which an operation was performed in DobiMigrate.
• Security: The security protocol used to perform the operation.
• Operation: The operation performed for the respective path. The values for Operation
can be:
◦ SCAN (S): Scan of the file, folder or symlink
◦ COPY FILE (CF): Copy of the file
◦ COPY DIRECTORY (CD): Copy of the directory
◦ COPY SYMLINK (CL): Copy of the symlink
◦ COPY FILE METADATA (CFM): Copy of the metadata of the file (for instance a
change in the file attributes)
◦ COPY DIRECTORY METADATA (CDM): Copy of the metadata of the directory (for
instance a change in the directory attributes)
◦ COPY SYMLINK METADATA (CSM): Copy of the metadata of the symlink (for

instance a change in the symlink attributes)
◦ DELETE FILE (DF): Deletion of the file on the destination file server
◦ DELETE DIRECTORY (DD): Deletion of the folder on the destination file server
◦ DELETE SYMLINK (DL): Deletion of the symlink on the destination file server

• Category: The outcome of the operation:
◦ OK: Operation is successful.
◦ Permission Denied: The respective DobiMigrate proxy is not given the permission
to perform the operation.
◦ Out of Space: The destination file server does not have enough capacity to accept
the file.
◦ Not Found: The file is not found on the source file server. This can happen when
the file was deleted between the scan operation and the subsequent copy
process.
◦ In Use: The file on the source file server has been locked and is not available to
DobiMigrate to read it for a copy operation.
◦ Timed Out: The operation timed out because DobiMigrate Core did not get a
timely response from the DobiMigrate proxy.
◦ Other: In case none of the known categories apply, the exception field will
contain more details.
• Exception: The exception message that came with the processing of this path. This
message provides extra context to help root cause and resolve the issue.
• Stack Trace: For an exception, the stack trace can be used to determine where the error
occurred within DobiMigrate.
8.6. Scan Statistics
The statistics page gives you a visual overview of how the source data is structured and how it
might impact migration speeds. The view is updated after each iteration to allow for any
changes that may have occurred since the previous iteration.
There are five different histograms used to display specific data information:
• File size: This groups the files into different size categories and shows the number of
files in each category. It also shows the total capacity in each category.
• Directory size: This groups the directories based on the number of files they contain.
The numbers of files per group are also shown.
• File modification time: This groups the files based on when they were last modified.
• Directory depth: This groups the directories based on the number of subdirectories they
contain, and shows the number of directories per group.
• File type categories: This categorizes files per file type and also shows the number of
files per file type, along with their total capacity.
You can also get an overview of the ten largest files and directories:
Scan statistics also appear under Migrations > Running (Histogram with a
 carousel interface).
9. Switchover or Dry Run

When a migration path runs in steady state, it is time to plan for the switchover or a dry run. A
dry run is used to estimate how long a switchover will take. During the switchover, users and
applications cannot use the source or destination file servers. That’s why you typically do
them during service windows. You need to plan them carefully and know how long it will take.
At the end of the switchover, users and applications are redirected to the new environment.
The most critical aspect when planning the switchovers is to know their duration so you can
tune and optimize the scope of each service window.
A switchover includes the following high level steps:
• Users and applications are prevented from writing or changing data on the source file
server by modifying the access rights. If needed, read-only access is still permitted.
• DobiMigrate performs a final compare between the data on the source file server and
the destination file server to capture any changes that happened since the previous
iteration. It will then copy the delta changes to the destination so that the data on source
and destination file server are in sync.
• Users and applications are given access to their data on the destination file server so
that they can continue with their work and operations on the new environment.
To minimize or avoid any impact to the user or application, you basically need to minimize the
time they do not have access to their data. DobiMigrate makes this possible in different ways:
• Due to its iterative approach, DobiMigrate continually tracks and migrates changes
since the time a migration path has been added up to the point when the switchover has
been completed. By default it will run fully automated following a predefined iteration
schedule. This approach helps to reduce the amount of data to be migrated during the
execution of the switchover window, thus minimizing downtime for the user or
application.
The project team always has the option to control this process
 manually if needed.
• DobiMigrate has been optimized to perform delta scans and migrations very effectively
which considerably reduces the switchover windows.
• DobiMigrate allows performing dry runs. The recorded timings can be used to tune the
switchover planning by fitting the maximum amount of migration paths to be switched
over in a given service window. This information also tells how long the users and the
application teams will not be able to change their data during the switchover.
• DobiMigrate does not allow you to change the protocol during a switchover. You can
change the protocol only during the iterations before a switchover.
9.1. Switchover Groups

To be able to perform a dry run or a switchover, you need to define a switchover group first. A
switchover group is a selection of migrations – more than one – that’s switched over at the
same time. Switchovers can be done manually or automatically.
Manual switchovers are suitable for smaller, once-off migrations, and allow for more real-time
adjustment.
Choose an automatic switchover for larger, recurring migrations that can be scheduled in
advance – settings can be saved for use again in the future.
9.2. Manual Dry Run

Setting up a dry run is the same as creating a slot for a switchover, but it needs to be marked
as a dry run, and have migration paths assigned to it.
To start a dry run, take the following steps.
1. Go to the Current event tab in the Switchover module, and click on Start new event (if

an event is currently running, click on Close Event).
2. Select Dry run from the Type dropdown list.
3. Select a switchover group from the Group dropdown list. If you need to define a

switchover group, choose Other in the dropdown. Then click OK.
When you click OK, the following view is shown:
The tiles indicate the following:

• Summary – number of dry runs scheduled for execution
• Shortlist – need to be executed
• Scheduled – are executed
• Copy Completed – were completed
9.3. Automatic Dry Run

DobiMigrate will automatically execute the dry runs at the scheduled time. At the start time of
a scheduled window, the Current window tile in the Switchover view becomes active and
accessible.
When a dry run is executed, the following happens:
• All the processes not directly contributing to the switchover/dry run are paused
automatically to provide maximum CPU & network support to the scheduled operation.
• For each of the migration paths that are part of the dry run window, a final delta
(comparison) is run, calculating the delta and executing the delta.
• When all the migration paths have been processed, the dry run window closes
automatically, disabling the current window tile.
• All paused processes related to this schedule will resume again.
• When the allocated time has passed, the dry run window is closed regardless of the
execution state of the migration path. The paths that are not finished will not have ETA
calculations available for planning purposes. In case the paths were executed prior to
the scheduled time, the window automatically closes and the end time of the slot is set
to the closing time.
The sequence of execution follows the prioritization as defined in the
 planning window. If needed, you can change this sequence during execution
of the dry run.
The amount of migration paths that will be executed in parallel is based on
 the value as defined in the field Parallelism when creating the dry run

window.
 The switchover ETA for a group is the average of the last three dry runs.
As the dry run progresses, the colors might change indicating bottlenecks,
 delays or issues. Click on the respective tile to get more information on the
risks or issues that occur.
In case you want to change the order in which the migration path will be executed, click on
the Shortlist tile, select the respective migration paths and use the navigation buttons (Top,
Up, Down & Bottom) to move them in the list.
9.4. Manual Switchover

To start a manual switchover, take the following steps.
1. In the Switchover module, select the Current event tab and click on Start new event…
2. Select Switchover from the Type dropdown list in the Start new event right

now dialogue box.
In the Group dropdown list, you can select a switchover group now, or select migrations
during the switchover.
3. Click OK.
The switchover tiles will display the current switchover.

9.5. Automatic Switchover

To plan an automatic switchover, define switchover groups in advance – you can then work
with these groups and plan dry runs.
To define switchover groups in advance, take the following steps.
1. Select the Pending groups tab in the Switchover module, and click on the + Add button

at the bottom of the panel on the left.
2. Enter details in the Create new switchover group dialogue box and click OK.
The group is then created and automatically selected.
3. Click the Add or Edit buttons the Migrations panel.

4. Select the migrations that will be part of this group in the Add/Edit migrations for
group dialogue, and click OK.
You can then plan switchovers or dry runs by clicking on the Add/Edit symbol under
the Upcoming events panel.
9.6. Errors during switchover

Errors that occur during switchover are shown in the Switchover module on the Copy
Completed tile of the Current event window.
Click on the error icon (with the exclamation mark) to view the error details:
After you have fixed errors, you can reschedule the switchover and retry the items with errors.
1. Select the path you want to reschedule in the current event window and click the
Reschedule.. button at the bottom.
2. Select Retry items with errors (x errors) and click Next
If you select Back to shortlist and schedule, force overwrite of

external destination modifications, the selected iteration will be
 moved back to shortlist and scheduled automatically. In addition, any

external destination modifications will be overwritten when the
destination is synchronized with the source.
3. Select the items with errors you would like to retry and click Next.
4. Select one of the following retry types, and click Next:

◦ Normal: Copies over all source changes that occurred since the previous iteration
to the destination.
◦ Force data and metadata copy: Recopies all data and metadata from the source
to the destination for all items in the migration even if the information has not
changed.
◦ Force metadata copy: Recopies all metadata from source to destination for all the
items in the migration even if the information has not changed.
◦ Force overwrite of external modifications on destination: Overwrites the files

that have been modified on the destination before a migration has been switched
over. If this option is not selected, externally modified files on the destination
server will not be overwritten to maintain the integrity of the information.
5. Finish by clicking Apply to retry your selection.
6. Verify that all errors have been resolved after rescheduled iteration has finished.
In order to complete the switchover, all errors should have been resolved or
 accepted.
9.7. Closing a Switchover

When closing a current window, DobiMigrate automatically generates reports that can be used
to investigate any potential problems with a previous migration.
A Closed Window report is generated whenever the current scheduled window is closed. If the
closed window is in the Finish decision state, then a Final report is also created. These reports
are stored in the dropzone of DobiMigrate. (Note that if there is more than one dropzone
associated with your installed DobiMigrate then it will download the reports to the dropzone
with the most available space.)
To close a window, go to the Scheduling dashboard, click on the Windows tile and click on

the Close window button.
A dialog opens that shows the migration path(s) in the current window and their decision
state:
When clicking OK then a Closed Window report and a Final report will be generated in the
dropzone of DobiMigrate.
If a non-finished decision is made when closing the current window, as shown in the example
below, then only the Closed Window report will be generated in the dropzone:
9.8. Exported Information

In the dropzone, the generated reports, for multiple migrations, look like:
A Closed Window report is a gzipped .tar file named ClosedWindowdatetimestamp.tar.gz

containing 3 files:
• a .csv file with information on all the scheduled windows for the given migration
• a .csv file with a summary of the source and destination file servers
• an .HTML file with the above information in readable format (see example below)
A Final report is a zipped .csv file (comma delimited) named sourceserver

_destinationserver_sourcepath_destinationpathFinalReportdate_timestamp.csv.gz.
The .csv file has information for each item migrated (file, directory, link) including source and
destination paths, mtime, ctime, size for files, and, if any, errors associated with the items
migrated.
For example:
10. Finish a Migration
10.1. Migrate Configuration Settings

When a migration has been defined, DobiMigrate will compare the configuration settings on
the source and destination file servers and will show discrepancies in the Shares &
Exports view. Depending on the specific file server types involved, the configuration settings
that can be migrated include:
• SMB shares
• NFS exports
In the example below, the Exports tile is red which indicates that a migration has been defined
for this source/destination file server pair, but there are issues with some (or all) configuration
settings. In this case there is one issue:
When you click on the Exports tile, a more detailed view on the discovered settings is opened.
The Destination status column shows the status of the share/export on the destination

server:
• No migration: migration still has to be set up.
• Share/export not found on destination: migration has been defined but no

corresponding share/export is found on the destination file server.
• Resolved: the share or export was flagged as resolved.

• OK (read-only): an export or share configuration has been created on the destination file
server but user(s) and group(s) have been granted read-only access.
• OK (switched over): an export or share configuration has been created on the

destination file server and all rights have been inherited from the source file server.
• Multiple destination paths: the source path maps to multiple destination paths (for
example on a case-insensitive file system).
• Cannot determine destination path: the destination path cannot be determined.
• Unsupported destination type: the destination does not support the creation/transfer of
share or export settings.
• Error determining destination path: there was a problem determining the destination
path. For example, scanning of the destination file system failed.
• Excluded path: the path was flagged as excluded.
• Destination path does not exist: the destination path does not exist.
• Unsupported source type: the source does not support transferring of share settings.
• Wrong destination path: there is already a share, but pointing to a different path.
• Share/export not available on destination: SMB/NFS disabled/not configured on

destination.
• Existing share/export: Share/export already exists on destination, but no action has

been taken yet.
To see all shares/exports including the Resolved ones, select the

 checkbox Show resolved settings under the table.
The Compatibility column shows if there are issues with the transfer of the share/export
definition from the source to the destination platform. The color of the exclamation mark in
the Action column indicates whether it is a warning (yellow) or an issue that needs to be
resolved (red).
Possible values in the Compatibility column are:
• Share/export not available on destination: SMB/NFS disabled/not configured on the

destination.
• OK: There are no issues for converting the source share/export to the destination file
server.
• Unsupported destination type: The destination does not support the creation/transfer

of share or export settings.
• Conversion issues: There are minor issues converting the share/export to the

destination file server but conversion is possible (mostly not 100% correct because the
destination does not support all features from the source). To investigate the issues,
click on the yellow exclamation icon.
• Conversion errors: There are known errors converting the share/export to the

destination filer. The current share/export definition cannot be converted to the
destination. To investigate the errors, click on the red exclamation icon.
• Unsupported source type: The source does not support transfer of the share settings.
Click on the Action icon to open a popup window that lists all compatibility issues.
10.1.1. Create Shares
In case there are configuration settings with an issue (Not found on destination), select the
setting from the list and click the Fix button.
The window below shows an SMB share that is missing on the destination fileserver.
There are multiple options for the creation of the destination shares:
• Keep the same name as the source shares. In this case, click the Create button. This will
create the shares on the destination file server and DobiMigrate will check their
availability. When OK, the status for these shares is flagged green with the message OK.
• Add a prefix to the selected shares. To do this, enter the prefix string in the text field next
to the Set prefix button and when done, click Set prefix. This will add the prefix to the
destination share names. In case you have set the wrong prefix, use the Revert button
to reset the names to match the source share names. When done, click the
Create button to create the shares on the destination file server.
• Change the name of the destination shares one by one by editing the Destination
Share field. When done, click the Create button to create the shares on the destination
file server.
When clicking the Create button, a dialog asks to confirm the share name and the matching
destination path. Click OK to create the shares/exports on the destination file server. When
done, the status of the shares/exports is updated.
Click Close to go back to the overview window which shows an updated overall status. If
needed, select the checkbox Show resolved settings to display the newly created share.
10.1.2. Create Exports
In case there are configuration settings with an issue (Not found on destination), select the
setting from the list and click the Fix button.
The window below shows which exports that are missing on the destination file server.
When clicking the Create button, a dialog asks to confirm the creation of the export and which
access rights these should be granted:
When clicking OK, the selected export will be created on the destination file server. When done,
the export status is updated to OK (read-only). Click Close to go back to the overview window
which shows an updated overall status. If needed, select the checkbox Show resolved
settings to display the newly created exports.
10.1.3. Modify Source Access
The Source Status column, which only displays a value for a defined migration, indicates the
access level to the share/export on the source file server. It’s good to do this during a
switchover to ensure that nobody makes changes to the source data while a switchover is
taking place.
The following values exist:
• Original: this is the access level as it has been set for the share/export prior to any
manipulations done by DobiMigrate.
• Read-only: this value is shown after the share/export has been set to read only via
DobiMigrate.
• Unsupported: indicates that DobiMigrate cannot set access to this source to Read only.
To change the access to the source shares/exports, select the share/export and click
the Modify source access button. In the dialog that opens you can select the shares/exports
for which that you want to change the access. Select the option Set shares access rights to
derived read-only if you want DobiMigrate to put the selected shares/exports to read only.
10.1.4. View Share Details
When you select a share and click the Show details button, extra information is displayed in
the bottom frames.
The left frame provides settings information for the selected configuration on the source file
server. For a share, it shows the user(s) and group(s) that have access to that share together
with their permissions. This information is collected from the source file server when you open
the Settings window. The frame on the right lists the details of the share that has been created
by DobiMigrate on the destination file server:
The settings that generate warnings/errors with the conversion from source
 to destination are highlighted in orange/red respectively. When hovering over

the warning/error, a tooltip is shown with more information.
• Share Name: the name of the share as given at the time of creation by DobiMigrate or
the name that was given by the person who created the share outside the DobiMigrate
environment.
• Description: the description given with the share name. It shows Created by

DobiMigrate when it was generated from within the DobiMigrate environment.
• Shared directory: The directory path that is shared.
• Home Directory Provisioning: these are the home directory settings that were applied
when creating these shares. DobiMigrate uses the default settings of the destination file
server. Possible values for Isilon are: Path variables will NOT be expanded, Path
variables will be expanded, Directories will NOT be automatically created, and
Directories will be automatically created. For more information on these settings, please
consult the Isilon online help.
• Users and Groups: the list of user(s) and group(s) that have been given read-only
access to the share.
In case the project team has decided not to migrate a specific migration path
by excluding it from the scope, the matching share(s) are also excluded
 automatically in the Settings view. The shares are labeled green with the
text Excluded path.
It is not mandatory to create shares within the DobiMigrate environment.
 Whenever shares have been created directly of the file server, these will show
up in the file server list.
10.1.5. View Export Details
When you select an export and click the Show details button, extra information is displayed in
the bottom frames.
The left frame provides settings information for the selected export on the source file server.
For an export, it shows the clients that have access to that export together with
their permissions. The frame on the right lists the details for the export that has been created
by DobiMigrate on the destination file server. Please note that the type of configuration
settings that can be migrated and their detailed representation will vary according to the
source and destination file server types.
Shares and exports are always given read-only access when they are created before the
actual switchover. This is to avoid that users or groups start to write or manipulate data on the
new shares or exports while they still have full access to the data on the old environment. This
could lead to confusion about which shares and exports should be used during the migration
project. The read-only access has been put in place to allow users and groups to validate
whether they can access their data on the destination file server before a switchover is
finalized. One of the final steps of the switchover is to transfer all rights from the source file
server to the destination file server.
The creation of shares can be done at any point during the migration process as soon as the
matching destination migration path is known. Whenever shares/exports are added to the
source file server during the migration project, the shares/exports are shown when the
settings window is opened.
In case you have created shares/exports on the destination file server incorrectly, you will have
to contact the file server administrator to have these shares/exports removed.
The Rescan button under the overview pane instructs DobiMigrate to rescan the settings that
can be migrated on the source file server. Use the Mark as Resolved, Mark as
Unresolved buttons to explicitly flag an issue or pending decision as resolved in case the issue
does not apply, or to revert from that decision. This allows the project team to clear any
irrelevant pending decisions and issues.
In case the project team has decided not to migrate a specific migration path
 by excluding it from the scope, the matching configuration settings are also
excluded automatically in the Settings view.
11. Verify/repair a Migration

You can view the details of a finished migration by clicking the Finished tile on the
Scheduling dashboard. In case you are not sure that the migration has finished correctly or
when there are issues with accessing data on the destination system, you can verify and try to
repair the migration as described below.
Select the migrations that you want to verify/repair and click on the Actions button under the
overview table. This opens a dialog from where you can select one of the following options:
• Recreate: to recreates this migration, restarting in first scan. You have the ability to
change the migration options before the migration is recreated.
• To steady state: to put the selected paths back to steady state. The selected paths will
appear in the Steady State tile and can be rescheduled from there for migration.
DobiMigrate will overwrite any changes made to files on the

destination. To ensure that changes made to files on the destination
 are not overwritten or deleted, set Allowed Operations to No deletes or
updates for one or more of the selected migration paths.
• Repair metadata: to forces a copy of metadata for content that is present on both
source and destination. New content or updates to the content will not be migrated, and
content only present on the destination will not be deleted.
• Copy new content: to only copy new content from source to destination. Updates to
content on the source will not be migrated, updates to content on the destination will
not be overwritten and new content on the destination will not be deleted.
• Verification: to verify the consistency between the source content and the destination
content and report inconsistencies, if there are any.
Go to the Post Finish tile to view the results of the verification and repair actions, for example:
• If there are failures they will show up in the Finished and/or Post Finish tile and in the
Issues tile (summary).
• If no blocking errors are found, the error will be part of the Finished tile.
• To view the iteration details, click on the magnifying icon
• To view the error details, click on the red icon with the exclamation mark
12. Run a WORM Migration
 A separate license is required for a WORM migration.
Setting up a migration with WORM data is similar to setting up a normal migration, except that
the migration type WORM has to be selected when adding a migration path. See Add a
Migration.
After setting up a WORM migration, the Type column for this migration path will show WORM.
For example:
WORM and non-WORM data cannot be combined in a single migration, and

 would need to be migrated separately.
All migration states, including switchover, are the same as for a normal migration and the MD5
checksum calculations are also performed to ensure integrity of all migrated data and
metadata. Note however that during the migration iterations of a WORM migration, the
retention period and the commit state are not transferred to the destination.
When a WORM migration has been set up, the Scheduling dashboard contains an additional
tile called *WORM State which shows the state of a WORM migration after switcho
When a WORM migration has been switched over, only the data and some part of the
metadata in the WORM volume(s) have been copied to the destination; not the retention period
and the commit state. To do the actual Copy WORM operation, click on the WORM state tile in
the Scheduling dashboard, select the paths that are WORM state waiting for manual
start and click the Start button:
In the dialog that opens, you can select one of the following options:
• Copy WORM and commit to copy the WORM information and do the commit
immediately.
• Copy WORM and NO commit to copy the WORM information and do the commit later.
• WORM commit to commit the WORM information that is already copied.
In case there are issues with the WORM state of the data, you can select Verify WORM
metadata or Verify WORM.
To view the progress and the results of the Copy WORM operation, click on the magnifying
glass to view the iteration details. When there are issues, you can view these by clicking on the
error icon next to the iteration number as shown below:
To view a report of the performed operations, click on the export button next to the
Status column.
 Resolving the issues is the same as for regular migrations.
When there are no issues and the Copy WORM has been done, you can finish the WORM
migration by selecting the path(s) and clicking the Finish button. The WORM migration will
move to the Finished state and will be visible on the Finished tile in the
Scheduling dashboard.
In case you are not sure that the migration has finished correctly or when there are issues with
accessing data on the destination system, you can restart the migration. Open the
Finished tile in the Scheduling dashboard, select the migration path(s) and then click
the Restart button. This allows you to either:
• Move the selected paths back to steady state. The selected paths appear in the Steady
State tile.
• Move the selected paths back to WORM state. The selected paths appear in the WORM
state tile.
• Restart the migration of the selected paths from the beginning. The selected paths
appear in the First Scan tile.
13. Migration Rollback

Normally after switchover, users will start to read from and write to the new destination file
system. However, if there are issues after a switchover with the new destination file system
(for example, permission issues or a DNS misconfiguration) it might be necessary to revert to
the old file system again. In this case, all modifications that were done on the destination file
system since the switchover must first be propagated to the old filesystem before this
reversion can happen. This is called rollback.
Rollback as implemented in the current version of DobiMigrate has the following limitations:
• Deletes are not propagated. To avoid modifying the source during a switchover, deletes
are not propagated. For example, if someone accidently deleted files on the destination
after the switchover, the only remaining copy at the source should not be deleted.
• Share management is not supported. The original share configuration must be restored
manually.
• No automatic reversal of the SID mapping. If the original migration used SID mapping,
you need to create the opposite SID map manually and assign that to the rollback
migration.
• A migration must be defined to migrate in the opposite direction. If the original migration
was from FilerA to FilerB, a migration from FilerB to FilerA must exist.
13.1. Rollback Prerequisites

• The migration to roll back must be Finished. This is shown in the Scheduling dashboard
on the Finished tab.
• End users should not have access to the original source when you perform a rollback.
13.2. Rollback and Switchover Recommendations

The following table provides some recommendations on user permissions to ensure a smooth
migration-rollback and switchover.
Action Recommendations
Initiate rollback Ensure original source is still read-only so that users no longer
have access to it. The target you are rolling back from, can still
be in read-write mode at this point until the rollback switchover.
Initiate rollback Ensure source and target are marked as read-only. This is the
switchover last incremental copy and users should not have access to
either side during rollback switchover.
Complete rollback Original source can be marked as read-write; however, target

switchover should remain read-only. End users can be directed to the
original source to continue their work.
13.3. Rollback Procedure

1. In the Finished tab, select the migration to roll back, and click the Rollback button.
The Rollback migration wizard dialog is displayed, summarizing the rollback that will be
performed.
2. Click Next. The wizard checks the prerequisites and runs pre-checks to verify that
everything is in place to run the migration rollback.
Once these pre-checks are completed, DobiMigrate displays a summary of the paths
and shares that will be used for the rollback.
3. Click Next. The Rollback migration options page displays the migration options.
By default, the Rollback migration wizard displays the same options as the original
migration wizard.
4. Click Next. The Precheck Results page is displayed. This is the final step where
DobiMigrate will run additional pre-checks based on the displayed paths and options.
5. Click Finish. The rollback migration will be performed. It will run as a normal migration
and the details will be displayed on the Iteration details screen.
Once the rollback migration is in "steady state", it must be switched over. For
 more information, see Switchover or Dry Run.
14. Tools
The following tabs are available:
• Performance
• Activity
• Logging
• Console
• File Browser
• Events & Alerts
• Sessions
14.1. Performance
This tab provides performance information for a chosen source - destination file server pair.
The slider at the bottom allows you to define the time period for which you want to see the
data.
The information displayed can be:
• Bandwidth
• Throughput
• Scanned items per second
14.2. Activity
The Activity view shows the ongoing migration activity (if any) for all of the entered migrations.
In the screenshot below you can see an example of different migrations that are in the copy
phase:
The Blocked state for the Commit Directory is not an issue. It simply means
 that these directories are waiting until all files are copied, after which the
directory commit will be done.
14.3. Logging
This tab shows the logging for the different components in DobiMigrate. This can be a very
handy tool to debug issues.
The left-hand side of the window shows the items that can be selected for logging with their
logging level. You can search for specific items or reload the last-used logging configuration
by clicking the reload button next to the search field.
Logging should be configured under guidance of Datadobi support. Do not
 change the logging levels or other settings as this may seriously impact
performance.
Logging details are cumulative, with each subsequent level building on the previous one.
Logging settings are hierarchical. When a particular logger is ‘not set’ the level of detail setting
of its parent will apply.
• Not set: for this item no logging has been configured.
• Off: for this item logging has been disabled.
• Fatal: for this item only fatal errors are logged.
• Error: for this item all errors are logged.
• Warn: for this item all warnings are logged.
• Info: for this item only informational details are logged.
• Debug: for this item only information that might be relevant for debugging is logged.
• Trace: for this item all traceable information is logged.
• All: for this item all events are logged.
14.3.1. View logging information
At the right side of the window, a snapshot of the current logging information is shown (last
1000 lines). This includes:
• Time: the time at which the logged event occurred.
• Level: the logging level indicated by an icon with the following color coding:
◦ red = error/fatals
◦ yellow = warning
◦ green = info
◦ no color = debug/trace
• Class: the internal DobiMigrate class that generated this log message.
• Message: a message generated by DobiMigrate describing the log event.
To pause and resume the current logging information, click on the Pause button above the
logging overview table.
To download the log files, click on the download button above the logging overview table. A
dialog appears allowing you to select the logging information to include in the log files:
• Source: from where should the logging details be retrieved, options are:
◦ DobiMigrate: download the log files from DobiMigrate itself. If there are proxies
configured, there will be additional options.
◦ All proxies: to download the log files for all configured proxies.
◦ Per proxy: to download the log files for that specific proxy.
• Type: the different type of log files available. The content of the drop-down list depends
on the selected source.
• Destination: the location to save the log files to. The log files can be downloaded
directly within the web browser or they can be downloaded to an existing dropzone. The
download will be a ZIP file containing one or more TXT files with all logging details.
14.4. Console
This allows Datadobi support to execute commands in order to troubleshoot reported issues.
It is also possible Datadobi will ask you to execute certain commands and send back the
output, as part of an ongoing issue investigation.
This tool is to be used by Datadobi only, or in cooperation with Datadobi as
 part of an investigation, as described above. It is not to be used without

Datadobi supervision.
14.5. File Browser

Via the File Browser you can view the details for a certain file or directory over SMB or NFS.
You can choose the file server, and then drill down to the file or directory in question.
This tool is useful to, e.g. root cause permission differences on source and target during a
migration, as you can check how DobiMigrate sees the permissions via SMB or NFS on the
source and on the destination file server.
14.6. Events & Alerts

Events are anything significant that may occur that warrant a user’s attention and, potentially,
user action. These events can then be set to issue Alerts that notify the user.
Alerts are communicated through a red indication marker in the GUI, or by email (SMTP), and
these emails can be configured to send out alerts of varying levels of severity or detail.
14.6.1. Configure Events & Alerts
You can configure alerts through both the Configuration and Tools modules, where the user
can chose from an extensive list of possible event-types and decide whether or not to be
notified through an alert.
Configuration module
1. Go to the Configuration module and select the Email Home tab.
You should first configure the SMTP host in the SMTP Configuration
 panel at the top of the page.
2. Enter the email address and frequency in the Alerts panel:

The email address field can hold a comma-separated list of addresses.
There isn’t one email per event - each email includes all events that may have occurred during
the set time frame. So for example if the frequency is set to 'Every 15 minutes', DobiMigrate
will check every 15 minutes if any events have occurred, and then bundle all events into a
single email alert if needed.
Tools module
The Events & Alerts tab in the Tools module allows you to view the events and alerts of a
given DobiMigrate instance.
You can select either All events & alerts or Unresolved alerts. You can also filter by type,
source, or details:
You can configure the Events & Alerts by clicking on the cog wheel symbol on the right. From
here you can select the event or alert-types you would like to receive:
You can then view the details of an event or alert by clicking on its corresponding icon in the
column on the left.
14.7. Sessions
The Sessions tab displays the open SMB connections to a certain file server. In the example
below, 2 active connections are present, both of them originating from DobiMigrate:
During a switchover, this tab is useful to check if there are any open SMB connections to the
file servers that can impact the switchover. If so, it is possible to end these open Sessions by
clicking on the Disconnect button.

Dobimigrate-5 12 2

Uploaded by

Copyright:

Available Formats

You might also like

Dobimigrate-5 12 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dobimigrate-5 12 2

Uploaded by

Copyright:

Available Formats

DobiMigrate Online Help

2.1. File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.2. Configure Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.3. Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.4. Email Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.5. File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.8. Session Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.9. System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.10. Manage DobiMigrate License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.11. Manage Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.1. Set up bandwidth throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2. Configuring different time zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4. Discover File Server Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.1. Scan paths for the Discovery Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.2. Download the Discovery Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.1. What is Reporting? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.2. How to Create Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.3. Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.4. File Deletion Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

6.1. Add a Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

6.2. Configure Migration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

6.3. Change Migration Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

6.4. User Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

7.1. Running migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

8.1. View Dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

8.2. Migrations Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

8.3. Iteration Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

8.4. Additional views for more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

8.5. Export Migration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

8.6. Scan Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

9. Switchover or Dry Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

9.1. Switchover Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

1. Introduction to Online Help

• Set up Throttling (optionally) if specific load or bandwidth requirements need to be

• Manage Migrations to configure migration options, interact with running migrations,

• Set up the Migration and initiate migration activities.

• Monitor Migrations to watch the progress and report to the stakeholders.

• Email Home: configure SMTP, migration and health reports

• LDAP/AD: configure LDAP/AD

• Users: add, edit and remove users

• User Mapping: view uploaded SID/UID/GID mapping files

• Filesystem: add disk space to DobiMigrate and configure a dropzone

A specific section is available on Configuring different time zones in case you plan to do

2.1. File Server

2.1.1. Add a File Server

To add a new file server, go to the Configuration module and click on the File Servers tab.

• Dell EMC Isilon

• Dell EMC PowerStore

• Dell EMC Unity

• Dell EMC VNX / Celerra

• Hitachi NAS Platform (HNAS)

• NetApp Data ONTAP

Integrated file servers

• Storage Virtual Machines (SVMs) for NetApp Clustered Data ONTAP

• vFilers for NetApp Data ONTAP 7-Mode

• Access Zones for Isilon

• CIFS/NFS Server for VNX/Celerra

• Virtual Servers (EVSs) for HNAS