Hi Karl, Thanks for answering. synchronize <http://docs.ansible.com/ansible/latest/modules/synchronize_module.html> is the module in ansible wrapping rsync.
The systems I'm dealing with are configured (due to security policies) to not allow login through SSH to the root user. That precludes connecting as root with neither ssh nor rsync. Also, ideally I'd like keep permissions and users (and the ansible controller does not really share the same users as the target nodes), so I would need to store it to an archive. Because that archive might be later used to bootstrap other host. (but yes, I could do Running this through ansible would bring some advantages, one is the internal knowledge of facts and introspection (e.g. I would be running this backup only on hosts that meet some *learned* criteria) and abstractions (there're different systems with different OS levels and restrictions (some have sudo, others can only do su) and ansible knows about them and how to connect in the right way (most of the time). Thanks again Julian El vie., 6 abr. 2018 a las 14:57, Karl Auer (<ka...@2pisoftware.com>) escribió: > On Friday, April 6, 2018 at 10:30:12 PM UTC+10, Julian Santander wrote: > >> The objective is to obtain a back-up of a directory in the target machine >> (managed) and needs to be saved to the controller host (where ansible runs). >> > > Why use Ansible? Something like rsync would seem to be the right tool. > Though you might need to use Ansible to install rsync on the target system > :-) > > rsync has the advantage (since you say the backup is huge) of being able > to restart a failed transfer (look for "partial" in the man page) and of > being able to transfer only changed items if the backup is going to be a > regular event; this massively reduces the size and duration of backup > operations after the first. > > I'm not sure what "synchronize" is; if you mean rsync, then I suggest that > the benefits to be gained will more than offset the investment in figuring > out how to use it (though in my experience it is extremely simple to use). > > Because rsync can use ssh, any user on the local system can access any > user, privileged or otherwise, on the target system, provided the local > system user's public key is in the authorized_keys file for the relevant > user on the target system. > > Regards, K. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/f26caaeb-3f49-448b-9fca-44116e79d95f%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/f26caaeb-3f49-448b-9fca-44116e79d95f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAA1UrpmuuyBa_O6SrK%2BXY_EMM%2Bm4egGbogoJbGBvME-FasXOhA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
