hello i have an old unraid server and i want to move data from the old one to the new one throw the network how to do that?

can any one help me plz

Several ways to do this. This is perhaps one of the simplest: link

 

 

rsync -avh /mnt/user/PlexData/ [email protected]:/mnt/user/PlexData/

 

 

did i do it right ?

 

 

as i want to move PlexData folder from server 1 to 2

its show that its moving but not time and speed how long will take ??

its show that its moving but not time and speed how long will take ??

Depends on the number of files. If past experience is any guide, plexdata could contain 100's of thousands of small files, so it may take days.

use the --progress switch in your rsync command will give you an idea of how many files are left to transfer

 

like this

 

rsync -avh --progress /mnt/user/PlexData/ [email protected]:/mnt/user/PlexData/

use the --progress switch in your rsync command will give you an idea of how many files are left to transfer

 

like this

 

rsync -avh --progress /mnt/user/PlexData/ [email protected]:/mnt/user/PlexData/

 

Keep in mind --progress still won't tell you time remaining. rsync is slow. Expect it to take a very long time. For reference I hooked an external hdd up to my raid server via USB and transferred ~650GB and it took a full 24 hours to do so. That was this past weekend.

thanks

Keep in mind --progress still won't tell you time remaining.

Yes, unfortunately!

 

rsync is slow

This is not correct.

The LAN might be slowing but most likely the unRAID writes on target side are limiting due to

parity calculation.

 

If doing such a massive transfer you should consider switching to "reconstruct write".

You can do a full parity build after the transfer is complete.

Finally you could do a second rsync run to compare source and destination just to be on the safe side.

rsync is slow

This is not correct.

The LAN might be slowing but most likely the unRAID writes on target side are limiting due to

parity calculation.

 

If doing such a massive transfer you should consider switching to "reconstruct write".

You can do a full parity build after the transfer is complete.

Finally you could do a second rsync run to compare source and destination just to be on the safe side.

 

Well, the example given was an external USB drive connected to the server. Probably USB2 and most likely slower than parity protected writes even without reconstruct write.

 

If we additionally assume that the drive contains tons of files rather than only fewer really large ones, the numbers/slowness make perfect sense. Nasty overhead for smaller files (same goes for regular copying of course)...

Exactly, file size is always a problem and not related to rsync.