About XCP specifications for CIFS

[shirotan]

Unlike NFS, CIFS does not use Catalog, so I understand that performance will not improve significantly compared to Robocopy and others.
Of course, it has a Verify function compared to Robocopy etc., so I think it is a big advantage that you can check the integrity of the data.
However, depending on the amount of data to be migrated, I think that Verify will take a very long time in the case of the behavior that I am asking the following questions.

Please tell me about the behavior of each command option.
<CIFS>
copy:
I understand how the initial synchronization of source data works.
Is it the behavior of scanning, listing files, and then copying?
Or are you copying without SCAN?

sync:
Since it is necessary to compare the source data with the data copied in the initial synchronization, is it the behavior of scanning the source and destination storage, comparing the list of files, and then copying the data?

verify:
Verify does not use a catalog and needs to compare the source data with the data copied in sync.
Therefore, the behavior is such that the source and destination storage are SCANed, the list of files is compared, and the hash value of each file is also calculated and compared in order to confirm the actual data block of each file.
By the way, I understand that if you add the nodata option, the hash value of the file will not be calculated or compared.
Is it correct?

[Reverett]

Hello,

The copy command scans and copies the entire source directory structure to a destination SMB share.

There is further detail regarding this in section 3.6 of the below document

https://library.netapp.com/ecm/ecm_download_file/ECMLP2875795

[shirotan]

Hello 

Reverett

Thank you for your replay.

Copying with xcpd is a copy after scanning.
sync scans the source and destination at the same time and copies the diffs.
I found the verifiy -nodata was on P93.

I understand that verifiy scans sources and destinations, makes meta information comparisons, and then compares the data.

Does the data compare calculate the hash value of each file?
Or another way?

[Reverett · Accepted solution]

As for the sync command:

It scans for changes and modifications in the source and target shares in parallel, and
applies the appropriate actions (remove, modify, rename, and so on) to the target to make sure that the target is identical to the source.

Hope this helps answer your question for more information please see below:

https://library.netapp.com/ecm/ecm_download_file/ECMLP2875795

[Reverett]

For the verify -nodata you can see on page 99 on the below document

https://library.netapp.com/ecm/ecm_download_file/ECMLP2875795