Secure Copy 7.6.3 - User Guide

NOTE: Verifying the file copy is a time, I/O, and processor intensive activity because it compares the checksums of the source and target files. Selecting this option could considerably extend the time required to complete the data migration.

NOTE: Use the File Verification Report to show errors in the SHA512 checksum comparisons. See Running reports.

To verify the copy job

Click Jobs, and expand the job.

Click Performance.

Select Perform SHA512 checksum verification on copied files.

To include skipped files, select Include skipped files.

Enabling logging

You can set logging for an individual copy job. Two logging levels are available: Full and Errors only. Selecting Full automatically enables the Logging Status option where you can customize your logs by copying status.

To enable logging

Click Jobs, and expand the job.

Click Performance.

Select Enable logging.

Select the logging level, and logging status (when available).

Maximizing copy performance

By default, the number of files in a batch is 50, the size of the batch is 1 MB, the number of threads is 4, and the inter-packet gap is 0. The goal of adjusting these parameters is to maximize your network bandwidth. Other factors that prevent Secure Copy from using all the network bandwidth include slow disk speeds, disk fragmentation, and other activity on the network and file server.

To maximize the performance of a copy job

Click Jobs, and expand the job.

Click Performance.

Adjust the thread count, batch count, batch size, and/or interpacket gap.

Table 10. Performance options

Option

Description

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.