Shulou(Shulou.com)06/03 Report--

Advantages and disadvantages of rsync

Advantages:

1. Advantages can be used for incremental backup, support socket, several (support push and pull, all with reference to the client)

two。 Remote shell peers can also encrypt (ssh) transmission, socket, need to encrypt transmission, can use × × service or ipsec service.

3. Most of them use intranet for backup.

Disadvantages:

1. When there are a large number of small files, it takes a long time to compare. Sometimes, during synchronization, the rsync process may stop or die. If there are a large number of small files, you can transfer them directly using a compressed package.

two。 When synchronizing large files, there will be interruptions. Files are hidden before synchronization is completed. You can resume files by parameters such as-- partail.

3. One-time remote copy can use scp, a large number of small files to achieve a package in the copy.

Wrong way of thinking:

Not familiar with the process and skilled in the steps

Understanding of rsync principle

Learn to read the log, rsync command output, log file / var/logrsyncd.log.

Common troubleshooting process

1. Check whether the password file name, synchronization directory file and configuration file match

two。 Check password permission 600?

3. Check whether the synchronization directory corresponds to the user and the configuration file one by one.

4. Most of them can.

Check the rsync log / varlog/rsyncd.log (same as in the configuration file).

Matters needing attention.

Today, there was a problem when I was doing a business case. A very important directory on the client server needs to be backed up, but there are soft connections in other directories, such as the / etc/ directory for backup. There are some soft links in this directory. Rc.local = = > rc.d/rc.local files. Files that appear under the backup server during unpackaged push backups display errors, (flashing red.) This situation indicates that the soft connection is invalid. Cannot be used.

Do a search for this and ask your colleagues. There are two kinds of answers in the end.

1. When pushing the backup, use the tar-h parameter to package it. This method is to package it in the original client server, and then push it to the backup server. In the packaging process, there will be no packet loss or link home file loss. The packaged package can be packaged and backed up together with the source files. Then push it. However, if the data to be backed up is very large, it will take up a lot of resources in the push process after each backup. This is a solution.

two。 Another solution is to push the files as a whole for the first time on the client and server, and then use the rsync incremental push method to push the files in turn. Then the files pushed are just added files at a time. Do not incrementally promote backup of duplicate files. Then arrive at the backup server and then package, backup and archive it. Including regular deletion. Deal with it. However, this method does not fully adapt to all files, soft connection files can not be fully adapted. If the soft connection is in a directory and the source file is in another directory, the situation just mentioned will occur during a real-time push backup. One solution is to change to chroot=yes. Chroot=yes in the chroot=no entry in the / etc/rsyncd.conf configuration file on the client server. This method is a way to cross the sea all over the sky. If the same path source file for the backup soft connection also exists in the backup file. For example, each soft connection under the / etc/ directory. After the backup can still be used, when their own backup server will be very dangerous. Other users can view the data at will in the backup server. When the / etc/ source file in the backup server is removed, the soft connection file of the backup server will become invalid. So it is a way to cross the sea all over the sky.

Summary:

When using rsync for incremental push backup, as long as the soft connection is not pushed, or the soft connection is tar-h for package push backup. The former is suitable for incremental push backups without soft connections. The latter is suitable for the backup of important system files.

The above is a summary of your own information and consultation with others, if there are any deficiencies, please help correct. Thank you for your hard work。

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.