Validation Reports

Migration App enables users to generate validation reports that compare source and destination data, helping to identify discrepancies. This report provides a list of mismatched and missing files for a migration job, along with remarks for each discrepant file, making it easier to understand necessary actions.

Key Benefits:

• Helps users identify discrepancies between source and destination.
• Provides clear guidance on required corrective actions.

The validation report includes:

• Files present in the source but missing from the destination
• Files with different checksum or hash values between source and destination
• Files with size differences between source and destination

The report can only be generated after data has been migrated to the destination (Egnyte).

 

Create a Validation Report

To create a validation report:

1. Navigate to the Migration Dashboard and access a migration job. Click on the three-dots menu.
   
2. Click on Details.
   
3. Click on Migration Job Actions -> Validate.
   
4. Users can choose to validate folders (including empty folders) from source to destination when they Validate a project. Please note that validating folders can take significantly longer.
   
5. The validation process will begin for the selected migration job displaying the details of total files and folders processed.
   
6. Once the execution is complete, the discrepancies between the source and destination will be listed under Needs Attention.
   

Alternatively, the validation command can be configured to run automatically after the true-up process completes. This option is disabled by default. Select Yes to enable automatic validation, and select the checkbox to validate all folders, including empty folders.

 

Access Validation Report

1. Click on Download report.
   
2. Validation report will be available under the Migrations folder. The user can go to the Migration-<migration-id> folder and then look for the zipped file by the name cmmagent_reports_<migration-id>_v<agent-version>. They can then download the zipped file, unzip it, and access the validation report at the path:
   <migration-id>\status\ validation_<migration-id>_<timestamp>_v<agent-version>.csv
   
   
    

3. The validation report comprises of three columns as:

   • Filename
   • Path
   • Remarks
   • Migrationid

   The migration ID column provides guidance to the users on which migration job or true up should be run to ensure all files are migrated successfully.
   If there are no discrepancies between the source and destination, the report will be blank. 

    

Limitations

• When using Data Validation along with the Sanitize on-the-fly option, the validation report may not accurately reflect the status of the files. For a more accurate validation report, customers are advised to use the Sanitize on source option instead.
• When validation reports are executed, exclusion rules will be considered. However, files and folders excluded in the migration job will still appear as missing in the validation report instead of being omitted.
• Symbolic links are not supported in validation reports. This is a general limitation of the validation command itself and also applies to project-level validation. As a result, files or folders that are symbolic links will not be validated, and may appear as missing or unverified in validation reports.
• Project-level validation reports can indicate that files are missing from the destination. However, they do not provide detailed information about which specific migration job or true-up needs to be executed in order to complete the migration and ensure all files are transferred.