Copy CP ?

jarimlim · 01-27-2019, 06:58 AM

Hello,

I am a beginner ... I would be glad if I get help.

On a CentOS V7.5 there are about 250 GB of data. The data should be transferred to a W2012 server in a shared directory. I have these directories mounted. I started the copying with "cp -ax / home / linux_directory / mnt / Windows_direktory". 170 GB were transferred, then the line broke off. Here are 2 questions:

- Do I have to delete the copied 170 GB and start copying again ??
or
- Is there a way to start copying from the break point? if yes how ??

Vielen Dank

wpeckham · 01-27-2019, 07:40 AM

Research rsync. Rsync or something that uses the rsync protocols may be your best answer.

jarimlim · 01-27-2019, 02:32 PM

thanks...but what would the command line look like?

many thanks

frankbell · 01-27-2019, 08:10 PM

Code:

rsync -a [/path/to/source] [/path/to/target]

See man rsync for more about the "-a" argument before you proceed. Don't just take my word for it.

jarimlim · 01-30-2019, 08:36 AM

many thanks solved

l0f4r0 · 01-30-2019, 09:06 AM

^ Good. Can you mark your thread as such please (see HOWTO in my sig)?

lleb · 01-30-2019, 12:26 PM

Quote:

Originally Posted by jarimlim

thanks...but what would the command line look like?

many thanks

rsync -aviS /path/to/files/to/send /path/of/destination

Code:

-a, --archive               archive mode; equals -rlptgoD (no -H,-A,-X)
-v, --verbose               increase verbosity
-S, --sparse                handle sparse files efficiently
-i, --itemize-changes       output a change-summary for all updates
     --out-format=FORMAT     output updates using the specified FORMAT
     --log-file=FILE         log what we're doing to the specified FILE
     --log-file-format=FMT   log updates using the specified FMT
     --password-file=FILE    read daemon-access password from FILE
     --list-only             list the files instead of copying them
     --bwlimit=KBPS          limit I/O bandwidth; KBytes per second
     --write-batch=FILE      write a batched update to FILE
     --only-write-batch=FILE like --write-batch but w/o updating dest
     --read-batch=FILE       read a batched update from FILE
     --protocol=NUM          force an older protocol version to be used
     --iconv=CONVERT_SPEC    request charset conversion of filenames
     --checksum-seed=NUM     set block/file checksum seed (advanced)

example:

Code:

 rsync -aviS /home/user/foo.txt user@server:/home/user/

This will send the file foo.txt to the SERVER (destination) server in the path /home/user/

Note the trailing / that will place all of your files from source without the top level directory of the source. Leave the / off of both source/destination to create directories and sub-directories during the rsync process.

wpeckham · 01-31-2019, 07:06 AM

Note that the server need not be specified if the two paths are mounted on the same host. (ie, a local clone/copy or transfer, or one involving a cifs, nfs, or sshfs mount)

I have found remote transfer reliable,even over slow network links. I have found local transfer very reliable. I have had issues at times with local transfer to a remote mounted volume: nfs, cifs, or sshfs is not always a happy camper. In addition, the extra levels of encryption and encapsulation impact performance.

ehartman · 01-31-2019, 07:42 AM

Quote:

Originally Posted by lleb

rsync -aviS /path/to/files/to/send /path/of/destination

I like the -H option too, to prevent hard linkes files from being copied twice (or more):

Code:

-H, --hard-links            preserve hard links

Note that -a does not preserve hardlinks, because finding multiply-linked files is expensive.
You must separately specify -H.

Note too that rsync can only detect hard links between files that are inside the transfer set.
If rsync updates a file that has extra hard-link connections to files outside the transfer,
that linkage will be broken.

(both notes from the manpage for rsync).