To use Secure Copy®, a user must hold administrative rights. These rights are required for the installation and use of the product. Additionally, users must have administrative rights on any servers or workstations that are involved in the copy process.
Secure Copy® needs to be installed on only one machine, which does not need to be the source machine or the target machine. Ideally, install Secure Copy on the source machine, which is most probably retired after the migration is done. The only time it is not recommended is when the source machine is too old to be quick enough or reliable enough for the copy process to be successful.
NOTE: Secure Copy streams RPC commands to the source and target machines as part of the copy process. Having the Secure Copy on a third machine causes numerous network connections to open and thus consume additional resources, which causes a minor latency between Secure Copy and the source and target machines. |
NOTE: For the resume option, Secure Copy will generate more read requests against the storage. Thus, starting copy from scratch for very large volumes is recommended as an approach. |
NOTE: While some RAM is consumed at the source and target machines; however, the majority of the RAM is consumed on the machine running Secure Copy to build copy jobs. In the process of building copy jobs, Secure Copy generates lists of files that are portioned out among the available threads and batches. Maximizing the available RAM on the machine running Secure Copy allows it to perform tasks without caching to disk because of lack of memory. |
To see what is new in Secure Copy®, refer to the What’s New in Secure Copy 7.6.3 document or the Secure Copy 7.6.3 Release Notes.
During the licensing process, you can import log files, scheduled jobs, and the jobs database from the previous version of Secure Copy. See Licensing Secure Copy.
The installation process involves installing Quest® Secure Copy® and activating your license.
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center