Secure Copy 7.5 - User Guide

Using Secure Copy Setting copy options Running copy jobs Using the command line Managing licenses Running Update Utilities Troubleshooting PowerShell cmdlets

Copying recently modified files

By default, files where the last-modified date and time differs by less than 2 seconds are skipped in a copy job.

File-time granularity is 100 nanoseconds on NTFS and 2 seconds on FAT, so copying a file from NTFS to FAT causes file times to be rounded to a value that the FAT file system can manage. When both the source and destination volumes are NTFS, the file times are compared exactly. When either the source or destination volume is not an NTFS volume, Secure Copy considers file times to be identical if they are within 2 seconds of each other. Without this 2-second margin, Secure Copy might classify unmodified files as older or newer files, which would result in unnecessary copying of unchanged files.

Sometimes you may want to override this handling of file times. For example, you copy an NTFS tree to a FAT volume. Secure Copy rounds the file times. You then copy the FAT tree (with its rounded file times) to a local NTFS drive. Later, when you want to recreate the original tree exactly, you do not want to refresh the entire tree.

Click Jobs, and expand the job.
Click Other File Options.
Select Ignore NTFS/FAT time differences up to 2 seconds.

Using compression

NOTE: Compression is not performed by Secure Copy; it is performed by the operating system. The compression function is performed at the same time as the write function, which could extend the write time of the file and thus extend the duration of data migration.
Click Jobs, and expand the job.
Click Other File Options.

Never compress target files

Disregards any file or folder compression that may exist on the source or target. Copies all files and folders uncompressed. This option offers the greatest speed for the copy process, and is recommended if there is not a space requirement on the target.

Always compress target files

Select only in cases when space is a premium as it adds substantial overhead and time to the copy job. This option also adds to the fragmentation on the target volume. Use only if absolutely necessary.

Compress target files only if source is compressed

Select to compress the files and folders on the target if they are compressed on the source. This option provides consistency among the file systems on the source and target, but also adds to the time required to perform the process. Use only if necessary.

Copying ACL information

During a migration, you can choose to update access control lists (ACLs) with new security identifiers (SIDs) for the objects being migrated and to remove their SID history.

Click Jobs, and expand the job.
Click Other File Options.

Update ACLS which use SID history

Select to update ACLs that use SID history, and type a Lightweight Directory Access Protocol (LDAP) domain path.

During a migration, the SIDs of the objects being migrated are checked against the SID History specified in the LDAP domain path box. If the SIDs of the objects being migrated are on the list, the ACLs are updated with new SIDs for the migrated objects and their SID history is cleared.


Select to copy security information.

Remove Orphaned SIDs

Select to remove orphaned SIDS.

Map SIDs Using Quest Migration Manager for AD map file

If you created a map file using Quest™ Migration Manager, select the check box, and click Browse to locate the map file.

NOTE: If you select Translate only accounts found in the map file, the Leave source accounts permissions on target check box is cleared and vice versa. Both checkboxes cannot be selected at the same time.

Running pre and post migration tasks

You can choose to run a task either before or after a migration.

In the Jobs pane, expand the job.
Click Other File Options.

Run a Pre-Migration Task

Select to run a task before the migration begins. Click Browse to locate an executable (*.exe or *.cmd) or type the path into the box.

Run a Post-Migration Task

Select to run a task after the migration completes. Click Browse to locate an executable (*.exe or *.cmd) or type the path into the box.

If a fatal error occurs, cancel all tasks including the migration.

Select to cancel all pending tasks and the migration if a fatal error occurs during the execution of a task or the migration.