-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReaR connects to rsync server over ssh even if configured to use the rsync protocol without ssh #2867
Comments
@oldunclez
For details and background information FYI: As a side note: |
Re Note 1 : that's real and is one of the many oddities I noticed (but not fixed) when working on PR #2831 , see #2831 (comment) (the 4th bullet point). Re Note 2 : you need to add the file to the rescue system using |
@pcahyna |
@oldunclez generally I have found that the rsync-over-ssh seems to be better supported and tested than rsyncd. See the third bullet point in #2831 (comment) that might affect you. Please check whether the solution for Note 2 works for you and if yes I will change the topic of the issue to cover only Note 1. |
@oldunclez I then consider note 2 solved and focus only on note 1. I think the only solution is to disable the reporting of disk space used and disk full entirely in the case of the rsync protocol. I think that it would not be reported correctly anyway, because the "path" in the case of the rsync protocol is actually a module name and one can't now which actual path on the server the module name refers to (it depends on the server configuration), so there is no way to construct the correct |
About the ssh connection we found a w/a adding these lines in local.conf
|
@fadamo wow, I have not thought about a possibility of such a workaround, thanks for sharing it! |
Thank you for all your reply. |
regarding etc/rear/local.conf and other config files
Regarding There is no such thing as "offical" scripts in ReaR Relax-and-Recover is intentionaly written entirely Things could be different when you use a ReaR software |
Stale issue message |
Not completed - I plan to work on this as time permits, but I have more urgent issues now. |
Stale issue message |
Stale issue message |
Stale issue message |
Stale issue message |
Stale issue message |
Stale issue message |
Stale issue message |
Stale issue message |
I am using the most fresh "Relax-and-Recover 2.7 / Git" to backup my "src vm" , and then recover it to "dst vm".
For non-interactive , when backup "src vm" , I set " --password-file" for rsync.
/etc/rear/local.conf is :
Note 1:
No matter what rsync transfer method is using :
For displaying the progress of rsync data tranfer , rear will ssh to rsync server to count how much data has been transfered.
( function "check_remote_du" , line 94 in file /usr/share/rear/backup/RSYNC/default/500_make_rsync_backup.sh ).
So if you want to make it works , you have to make sure "non-interactive SSH login for rsync@192.168.1.27" is accessable.
Otherwise, if you do not need the progress of the rsync transfer , maybe you could modify 500_make_rsync_backup.sh to the following :
Note 2:
Rear will pack "/etc/rear/local.conf" of the "src vm" into the the rescue iso.
When excuting "rear recover" on "dst vm" , rear will copy the backup files from rsync server to "dst vm" via rsync with "BACKUP_RSYNC_OPTIONS=( -az --password-file=/etc/rsync.pass )" .
But the "/etc/rsync.pass " will not be packed into rescue iso , so it does not exist in "dst vm",
You have to create it manually or remove it from BACKUP_RSYNC_OPTIONS .
Otherwise , rear recover will fail because of rsync fail with the non-existent "/etc/rsync.pass "
The text was updated successfully, but these errors were encountered: