
© Infrant Technologies
4
Rsync in practice
Consider the topology illustrated in Figure A. In this scenario, a local ReadyNAS can maintain a
copy of all the data generated at one or more remote locations. For example, the local device can
reside at an off-site location, such as a home office or other facility, and back up the data stored
at a remote business site. Rsync can accomplish this goal in two different ways:
9 Each remote device can “push” its data to the local device.
9 The local device can “pull” data from each remote device.
If you choose the “push” solution, you need to create a backup job at each remote site. However,
this can add administrative overhead to your organization because you need to maintain separate
backup jobs residing at potentially different locations. Choosing the “pull” solution is more
efficient because, although you still need to create a backup job for each remote site, all the
backup jobs are maintained on the local device.
In general, you can think of each location as a separate network, either internal or external to
your organization. For the purpose of this guide, the ReadyNAS device hosting the backup jobs
is the local device and the ReadyNAS devices you want to back up via Rsync are the remote
devices.
Figure A: A ReadyNAS device can be either a local or a remote device.
Comentarios a estos manuales