Why You Should Run a Simulation
We strongly recommend running a Simulation job as it enables you to do a “mock run” and see what the data transfer would be like, without transferring any actual data. At the end of the simulation run, you can look at reports that tell you what files would have transferred, how many bytes of data would have transferred, and what files, if any, would be deleted. Simulation can be used in situations such as:
- Anticipate and troubleshoot many issues such as insufficient permissions, unprovisioned target users, or inadequate bandwidth. All of these factors can influence job performance and overall migration time. Catching migration issues early will ensure that your data migration is successful and on time.
- Understanding exactly where your data will be migrated to on the target.
- Identifying which files and how many bytes of data would have transferred, and which files, if any, would be omitted or filtered.
- Simulations are highly recommended for Account Mapping jobs, permissions changes, and any other jobs where Target Paths may be changed or renamed.
- Assessing how many files and bytes will transfer during synchronization runs. You can also identify the files that will transfer during the sync so you can evaluate whether you want to do the sync run at all.
- For jobs where Mirror Deletions is turned on, Simulation will list the files that will be deleted from the target when the job is run.
- Determining an estimated time to complete the run, and any bottlenecks that may limit the speed of your transfer. Simulation can also sometimes be useful for evaluating drive and network connectivity problems.
Current Results Status and Error Messages
When your Simulation job completes, select “Current Results” to view a report of the files tagged for transfer: This will list all files, folders, and directories that would be involved in the data transfer. If you click on any result, a menu will appear providing more in depth information.
This is also useful for account mapping, where you can view which accounts your files will go to. You can also click the magnifying glass to filter your results further. Additional information on filters is available at Job History Filters.
Select the Export button at the bottom of the screen to generate an .xlsx file of your simulation report. If you do not use any filters, it will export every result in your simulation. If you wanted to only export filtered results, please filter first and then Export.
Filtering the On-screen Simulation Log
Navigate to the ‘All Statuses’ menu on the right side.
The menu will list all file statuses that have been logged to date for all files in the run. Not all status messages are errors, many are informational only. In most cases, CFP is reporting errors that are generated from the source or target. Some statuses in this menu may include:
- read-errors: due to issues such as permissions, file open/EBUSY or source connectivity. For Windows sources in particular, that means you can frequently just do a web search for the errors and find Microsoft documentation that explains the issue or, if you have access to the server, you can try to directly access the affected file for folder and open or download it. You will frequently get the same error.
- write-errors: due to issues such as file exceeding target account limits
- filtered: files that are not transferred to the target. These include system files, such as desktop.ini and thumbs.db files, or temp files such as ~$doc.docx. In many cases, these files may cause undesirable results if downloaded onto another computer from the cloud provider, or they may be prohibited altogether by the cloud provider. Files will also be filtered if there is an explicit exclude filter set up for them in Advanced Options, or if they are skipped in the spreadsheet of an account mapping job.
- match-exists: an up-to-date copy of the file is already on the target, so the file was not transferred
- success: file transferred successfully
- partial-success: the file or folder transferred successfully and completely, but some of the associated metadata did not transfer. A common source of this error is if a folder transfers, but one or more of the associated sharees did not transfer. For example, if you are migrating a folder to Dropbox and one of the designated sharees has not confirmed their invitation to Dropbox, they cannot be attached as a sharee to that folder.
- source-missing: the vast majority of source-missing files are ones that simply were found on the target but not on the source. In most cases, these files are listed for informational purposes only – CFP is just telling you there are additional files on the target that are not on the source during this specific job run. Source-missing files that have a Message of “Not found” are generally files that have been deleted from the source while the job was in progress, and if so, the files and associated errors will not be reported on subsequent runs unless the file is re-added to the source.
- size-exceeded: file is larger than the target service supports.
- target-account-missing: the affected file or folder had a source owner that was not mapped to a target account. The affected item did not transfer because you did not specify where you wanted it to go on the target. This error is only present in account mapping jobs.
Filtering with the Magnifying Glass
When you select the magnifying glass, a menu will pop open allowing you to search and filter even further. You can specify if you want matching results filtered by Source or Target, or General for either.
Enter your expected target directory in the “contains” field.
SOURCE/TARGET: Search for a full path or path fragment, on source or target.
SOURCE/TARGET EXTENSION: Search for all instances of a particular file extension in your job. Enter the extension without a leading period. For example, to search for all docx files, enter docx.
SOURCE/TARGET CATEGORY: Select a type of file.
OWNER: search for the account name of the data’s owner. Available for account mapping jobs only.
TYPE: This is one of the more popular fields. It has two options: ‘Type is directory’ returns all paths ending in directories, and ‘Type is not directory’ returns all files. So if you want to list only files in your transfer report, select ‘Type is not directory.’
BYTES, TRANSFER START DATE, MODIFIED DATE: These fields can help you narrow down the transfer report to files of a specific size or date range.
MESSAGE: This is another popular field that enables you to identify all errors in your job. See ‘Identifying All Types of Errors in a Job’ below for additional information.
How To See What Your Data Will Look Like On The Target
How To Check Permissions
Export the “Current Results” report. You’ll see tabs on the bottom for Source and Target Collaborators, both external and internal in the spreadsheet. This will only be available in jobs that are migrating permissions.
How To Check That Target Paths Are Correct
Export the “Current Results”, and view the “Translated File Name” column on the far right of the exported spreadsheet to see the precise path for your data on the target.