SCP for file transfer in Linux CLI - Step-by-Step Execution

Concept Flow - SCP for file transfer

Start SCP command

↓

Check source file exists

↓

Establish SSH connection

↓

Transfer file data

↓

Write file on destination

↓

Close connection

↓

End with success or error

This flow shows how SCP checks the source, connects securely, transfers the file, and finishes.

Execution Sample

Linux CLI

scp /home/user/file.txt user@remote:/home/user/

This command copies file.txt from local to remote user's home directory.

Execution Table

Step	Action	Evaluation	Result
1	Start SCP command	scp /home/user/file.txt user@remote:/home/user/	Command initiated
2	Check source file	/home/user/file.txt exists?	Yes, file found
3	Establish SSH connection	Connect to user@remote	Connection successful
4	Transfer file data	Send file.txt bytes	Data sent successfully
5	Write file on destination	Write to /home/user/file.txt	File written successfully
6	Close connection	End SSH session	Connection closed
7	End	Transfer complete	Success

💡 Transfer ends after file is written and connection closes successfully

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
source_file	/home/user/file.txt	Exists	Data read	Transfer complete
ssh_connection	None	None	Established	Closed
transfer_status	Not started	Not started	In progress	Success

Key Moments - 3 Insights

What happens if the source file does not exist?

SCP stops at Step 2 with an error because it cannot find the file to send.

Why is SSH connection important in SCP?

At Step 3, SCP uses SSH to securely connect and transfer files safely.

When does SCP close the connection?

After the file is fully transferred and written (Step 6), SCP closes the SSH connection.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the file data actually sent?

A Step 5

B Step 2

C Step 4

D Step 6

💡 Hint

Check the 'Action' column for when data transfer happens.

At which step does SCP check if the source file exists?

A Step 2

B Step 1

C Step 3

D Step 5

💡 Hint

Look for the step mentioning source file check.

If the SSH connection fails, which step would SCP not reach?

A Step 3

B Step 4

C Step 6

D Step 7

💡 Hint

Without connection, data transfer cannot start.

Concept Snapshot

scp [source] [user@host:destination]

- Copies files securely over SSH
- Checks source file before transfer
- Establishes SSH connection
- Transfers file data
- Writes file on remote
- Closes connection after transfer

Full Transcript

SCP is a command to copy files securely between computers using SSH. First, it checks if the source file exists locally. Then, it connects to the remote computer using SSH. After connection, it sends the file data over the secure channel. The remote side writes the file to the destination path. Finally, SCP closes the connection and ends with success or error. This process ensures safe and reliable file transfer.

Practice

1. What does the scp command do in Linux?

easy

A. Changes file permissions

B. Compresses files into a zip archive

C. Securely copies files between local and remote machines

D. Displays the contents of a file

Solution

1. Step 1: Understand the purpose of scp

   The scp command is designed to securely transfer files between computers over a network.

2. Step 2: Compare with other options

   Options A, B, and C describe different commands: permission changes, compression, viewing files, which are unrelated to scp.

3. Final Answer:

   Securely copies files between local and remote machines -> Option C

4. Quick Check:

   scp = Secure copy [OK]

Hint: Remember: scp = secure copy files remotely [OK]

Common Mistakes:

• Confusing scp with compression commands
• Thinking scp changes file permissions
• Assuming scp only works locally

2. Which of the following is the correct syntax to copy a file file.txt from your local machine to a remote server server.com under user alice in the directory /home/alice/?

easy

A. scp file.txt [e-mail]:/home/alice/

B. scp [e-mail]:/home/alice/ file.txt

C. scp /home/alice/file.txt [e-mail]:

D. scp file.txt /home/alice/[e-mail]

Solution

1. Step 1: Identify source and destination in scp syntax

   The syntax is scp source destination. Here, file.txt is local source, and [e-mail]:/home/alice/ is remote destination.

2. Step 2: Check each option

   scp file.txt [e-mail]:/home/alice/ correctly places local file first and remote path second. scp [e-mail]:/home/alice/ file.txt reverses source and destination. scp /home/alice/file.txt [e-mail]: uses remote path as source incorrectly. scp file.txt /home/alice/[e-mail] has wrong path format.

3. Final Answer:

   scp file.txt [e-mail]:/home/alice/ -> Option A

4. Quick Check:

   scp source destination = scp file.txt [e-mail]:/home/alice/ [OK]

Hint: Local file first, remote user@host:path second [OK]

Common Mistakes:

• Swapping source and destination
• Missing colon after remote host
• Incorrect path order

3. What will be the output or result of this command?
scp -r [e-mail]:/var/logs ./backup_logs
Assuming you have access and the remote directory exists.

medium

A. Copies the remote /var/logs directory recursively to local ./backup_logs folder

B. Copies only files inside /var/logs but not subdirectories

C. Throws an error because -r cannot be used with remote paths

D. Deletes the local ./backup_logs directory

Solution

1. Step 1: Understand the -r option in scp

   The -r flag means recursive copy, so it copies directories and their contents.

2. Step 2: Analyze the command effect

   The command copies the remote directory /var/logs from user alice on server.com to the local folder ./backup_logs. This is valid and copies all files and subfolders.

3. Final Answer:

   Copies the remote /var/logs directory recursively to local ./backup_logs folder -> Option A

4. Quick Check:

   scp -r remote:/path local copies folders recursively [OK]

Hint: Use -r to copy folders recursively from remote [OK]

Common Mistakes:

• Thinking -r only copies files, not folders
• Believing -r is invalid with remote paths
• Confusing copy direction

4. You run this command to copy a file from remote to local:
scp [e-mail]/home/alice/file.txt ./
But it fails with an error. What is the likely problem?

medium

A. scp cannot copy files from remote to local

B. Missing colon after the remote host before the path

C. Local path ./ is invalid

D. User alice does not have permission to copy files

Solution

1. Step 1: Check the remote path syntax

   Remote paths must be specified as user@host:/path with a colon after the host. The command misses the colon after server.com.

2. Step 2: Understand the error cause

   Without the colon, scp treats the whole string as a local path, causing failure.

3. Final Answer:

   Missing colon after the remote host before the path -> Option B

4. Quick Check:

   Remote path needs colon after host [OK]

Hint: Always put colon after remote host in scp paths [OK]

Common Mistakes:

• Omitting colon after remote host
• Assuming local path is wrong
• Thinking scp can't copy remote files

5. You want to copy multiple files file1.txt and file2.txt from your local machine to the remote directory /data/uploads on server example.com as user bob. Which command correctly does this in one line?

hard

A. scp file1.txt,[e-mail]:/data/uploads/ file2.txt

B. scp file1.txt file2.txt -r [e-mail]:/data/uploads/

C. scp [e-mail]:/data/uploads/ file1.txt file2.txt

D. scp file1.txt file2.txt [e-mail]:/data/uploads/

Solution

1. Step 1: Understand copying multiple files with scp

   scp supports copying multiple files by listing them before the destination path.

2. Step 2: Analyze each option

   scp file1.txt file2.txt [e-mail]:/data/uploads/ correctly lists both files followed by remote destination. scp file1.txt file2.txt -r [e-mail]:/data/uploads/ misplaces the -r flag after the sources, treating "-r" as a non-existent source file. scp [e-mail]:/data/uploads/ file1.txt file2.txt reverses source and destination. scp file1.txt,[e-mail]:/data/uploads/ file2.txt has invalid syntax with comma.

3. Final Answer:

   scp file1.txt file2.txt [e-mail]:/data/uploads/ -> Option D

4. Quick Check:

   List files then remote destination [OK]

Hint: List all files first, then remote destination [OK]

Common Mistakes:

• Misplacing the -r flag after source files
• Swapping source and destination
• Incorrect file list syntax