Secure Copy 7.6.3 - User Guide

Thread count

Select the number of copy threads for an individual copy job

The number of threads is equivalent to the number of copy jobs that can be performed simultaneously. By increasing the thread count, you are adding more threads that copy batches of files. Each of the file threads deals with one batch of files at a time.

In normal operation, the default settings should be adequate. However, if you have a large number of small files and many batches, you might start by creating at least 10 threads, and then monitoring network card utilization.

IMPORTANT: Setting the thread count too high can result in poor performance. We recommend using a value less than 20 if using normal server hardware.

·         When moving a large number of small files, you can increase the number of threads towards the maximum number of 250 threads. With more threads per job, large numbers of files can be moved in the shortest period of time.

·         When moving larger files, using fewer threads is more effective because the threads are able to focus on moving a few large files, switching control between few threads in a fluid process rather than passing control to multiple threads, which would slow down the copy process.

Batch count

Select the maximum number of files in an individual copy job thread

Batch Count is a limiter based on the number of files a thread can process at a time. When a job is being processed, a single thread copies either the maximum number of files in the batch count or the maximum batch size, whichever is reached first. The minimum number of files is 25 and the maximum is 1000.

IMPORTANT: In most cases, the default values are optimal. Changing these values incorrectly can lead to performance degradation.

·         When processing a large number of small files, it is preferable to set the batch count to the highest level for efficiency.

·         When processing large files, the batch count can be set anywhere because the batch size limitation will be met before the batch count limit is met.

Batch size

Select the maximum number of bytes in an individual copy job thread.

Batch Size is a limiter based on the size of the files a thread can process at a time. When a job is being processed, a single thread copies either the maximum size of files or the maximum number of files, whichever is reached first. The minimum is 1MB and the maximum is 100MB.

IMPORTANT: In most cases, the default values are optimal. Changing these values incorrectly can lead to performance degradation.

·         When processing a large number of small files, it is preferable to set the batch size to the highest level for efficiency.

·         When processing large files, the batch size can be set anywhere because the batch size limitation will be met prior to meeting the limit of the batch count.

Inter-Packet Gap

Select the time span to wait between packets of data being copied.

The Inter-Packet Gap (IPG), which is also referred to as an Interframe Gap (IFG), slows down the copy process, which reduces the bandwidth usage over the network. As a file is copied, it is copied 64 kilobytes at a time. The Inter-Packet Gap is a time span in milliseconds (ms) to wait before sending the next 64 kilobytes.

NOTE: Due to factors, such as the volume of other traffic on the network, you may need to experiment with the time span to achieve a desired bandwidth.

Local groups

Migrates local groups from the source to the target.

Local users

Migrates local users from the source to the target.

Copy only local groups and users not files

Migrates only local groups and users accounts. Files are not migrated.

NOTE: Only local groups and users who already have permissions on the source data will be migrated.

Set password for migrated user accounts

Set a new password for the migrated user accounts. Type the new password in the box.

Target server

Migrates local groups and users from the source server to the target server that is indicated on the Copy Locations page.

Active directory

Migrates local groups and users from the source server to an Active Directory^® Organizational Unit (OU). Type a path using standard LDAP format in the box, or click Browse to browse for an OU.

Always perform the following action

To avoid conflicts, add a prefix or suffix to the migrated groups/users. Adding a prefix or suffix allows administrators to enforce a standard naming convention, or to differentiate the migrated groups and users from their already existing counterparts.

Use the existing group/user

If a local group/user name already exists on the target, Secure Copy applies those permissions to the migrated data.

Add members of the source group to existing group

Migrates the users of a group on the source server to the group with the same name on the target server.

Synchronize target members with source members

If a local group/user already exists on the target, the source local group/user overwrites the target.

Add the Prefix

Add the Suffix

In cases where there may be multiple local groups/users of the same name and manually renaming the local groups/users when prompted may be unfeasible, such as in the case of a scheduled job, you can have Secure Copy add a prefix or a suffix to the new local group/user name. This gives a uniform naming convention to the new local groups/users and prevents unnecessary user intervention.