Rsync Command in Linux with Examples

Articles & guides
, ,
1
Read the full article: rsync Command in Linux with Examples

The rsync command is one of the most popular and powerful tools in Linux for synchronizing files and directories between different locations. It is widely used for backups, remote file transfers, and directory syncing, offering robust features like incremental file transfers, compression, and file permission preservation. In this article, we’ll explore the basics of rsync, along with… continue reading.
2

Thanks for the post @hydn

I’m curious if you’ve ever used Rsync or Rclone to migrate data from an old server to a new one. If you have, what commands did you use?

I’m asking because I’ve noticed that Rclone or Rsync sometimes don’t set the file permissions properly. Additionally, I believe that we shouldn’t sync all files between the servers, such as /proc or /dev.

What are your thoughts on this?

1 Like
3

Yes thats true and i think the best would be to use the dd for the backup and that works very well. You can easily back enormous amount of data and you can have no broken links.

Let me know if that works,
Gaurav

1 Like
4

I’ve used “dd” before, but I’ve encountered some issues. What commands do you use for server migration between two different servers? Do you migrate all files from the old server, or do you exclude some?

Thanks in advance.

5

I mainly use rsync, timeshift, clone for the server migration. If you have to migrate all the files from the one server to the another. Basically, i dont do that.

What i do and what is suggested is to 1. create a root node 2. After creating a root node and then mount the directive to the server. In this way the root node is only having a minimal install and for that a 2.5 HDD disk should be done as the faster booting time.

In case of the mount drives, RAID5-SATA should be done. This will allow the read and drive on the mount drives slow as compared to the booting time but that will not affect the root node. So building a distributed computing as compared to the monolithic system.

Following that connect another drive and after that set a time shift from one drive to another as a cron job. This will allow the complete system back up and at the same time, mounted drives will be safe incase the crash goes on.

Those who keep the data on the root node need to be worrying about the moving of the files and i dont recommend that.

Let me know if you need more information,
Gaurav

6

Thanks for the reply!

I totally agree with you. However, sometimes, some servers don’t have that separation and they keep their data on the root node. Additionally, the servers must be migrated from one provider to another. In that case, moving the hard drive is not possible either. I was wondering if there is a way to do migration in such cases.