Our Source File Servers currently do not have deduplication active in Windows, however, deduplication has been activated on the target filestore servers where we are copying the data to.
Will Secure Copy keep re-copying files that have been deduplicated on the target file servers or will Secure Copy recognize that the link left in place is for that file and so not re-copy it on subsequent sync tasks?
Data Deduplication optimizes data by using a post-processing model. All data is written unoptimized to the disk and then optimized later by Data Deduplication. If the source has no deduplication, the migrated data would not matter to the target and will be migrated in a non-dedup state.
So data will be migrated from source to target, and then later on processed by the dedup services, and then compressed accordingly.
Note: On target make sure there's enough space for the data pre-dedup, and then the post-migration Deduplication service will work and shrink the data volume.
Secure Copy version 7.1 and later is Data Deduplication aware and has improved handling by ignoring the (SVI) System Volume Information folder.
After the first job run, if the Deduplication service has completed deduping the data, it will create reparse points (file attribute) of the file, and the file's chunks will be stored in Chunk Store (terminology of Microsoft deduplication service).
So after the re-run of the job, the migrated files should be overwritten, since they do not exist on target, but only the reparse points exist.
Secure copy currently does not migrate Reparse Point (L) attribute which has been confirmed in a test.
© ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center