|
Article ID: 514
Last updated: 04 Dec, 2025
Transfers between a remote system and a host system within the NAS enclave—for example, between your local system and a PFE—must be carried out using the Secure Unattended Proxy (SUP). To use the SUP for Shift transfers to NAS systems, you must first download the SUP client, authorize one or more NAS hosts for SUP operations, and then authorize one or more NAS directories for writes. A brief summary of these steps is shown below. For a full overview, see Using the Secure Unattended Proxy. Downloading SUP to Enable Remote TransfersComplete the following steps to set up your system for remote transfers:
Performing Remote TransfersFor remote transfers, the shiftc syntax is similar to local transfers and transfers between two hosts within the enclave, except that you must prepend sup (the SUP client) to each shiftc command. Also, remote Shift transfers must always be initiated from the system that is external to the NAS enclave, but files may be transferred in either direction.
For example, the following enclave-to-enclave transfer copies file1 into the directory ~/data/run2 on lfe5:
If the above example were changed into a remote transfer, it would become:
In general, shiftc [args] becomes sup shiftc [args]. Note: For information about Shift options, including those used in the examples in this article, see Shift Command Options. File Transfer ExamplesThe examples in this section show you how to transfer files between your local system and a host within the enclave. The first example includes output; subsequent examples show only the command line.
Creating and Extracting Tar Files RemotelyYou can use Shift to transfer a directory and write it into a tar file it in one step, resulting in a portable tar file that can be read by either shiftc or tar. In the same step, we recommend that you also create a table-of-contents (.toc) file that lists the files contained in the archive along with their sizes and attributes. Because of their sequential nature, tar files cannot be efficiently updated in place. As a workaround, incremental tar files can be used, which are separate tar files that consist of files updated after the time the original or subsequent incremental updates were created. Creating Tar FilesThis example creates a tar file (dir1.tar) of the directory dir1 on your local system directly into your Lou home directory, along with a corresponding table of contents (dir1.tar.toc):
Note: If the dir1 directory is over 1 TB, it will be split into multiple tar files prefixed with dir1. Creating Incremental Tar FilesThe example in this section shows you how to create incremental tar files from your local system to your Lou home directory. Create an incremental tar file (dir1-2020.tar) of all files modified on or after January 1st, 2020 in the directory dir1 on your local system directly to your Lou home directory, along with a corresponding table of contents (dir1-2020.tar.toc):
Extracting Tar FilesThese examples show you how to extract tar files from your local system to your Lou home directory.
Also read
|