Registered users
Linkedin Twitter Facebook Google+
Close

In order to improve user's experience and to enable some functionalities by tracking the user accross the website, this website uses its own cookies and from third parties, like Google Analytics and other similar activity tracking software. Read the Privacy Policy
33HOPS, IT Consultants
33HOPS ::: Proveedores de Soluciones Informáticas :: Madrid :+34 91 663 6085Avda. Castilla la Mancha, 95 - local posterior - 28700 S.S. de los Reyes - MADRID33HOPS, Sistemas de Informacion y Redes, S.L.Info

<< Return to index

XSIBACKUP-PRO: the --host argument and process delegation.

The --host option is very popular among XSIBACKUP-PRO users, it allows to execute a backup job to any remote linked (--link-srv) server. This is very convenient when you want to create complex backup topologies that extend throughout a number of servers.

Nevertheless we have found that there's still some obscurity surrounding this command. Although from a user perspective, it may seem natural to believe that backupid=01 will launch backupId=02 when finished, this is not true.



When backupid=00 finishes, it will call backupid=01, that's clear, but backupid=01 will be executed in host 192.168.33.33. It will literally be a process running at host 192.168.33.33, thus when it finishes, it will look for a backup job named backupId=02 at the 192.168.33.33 host's crontab, and not the crontab from where it was originally launched.

Understanding how remote backups are executed and how the processes must be chained is vital to design more complex backup topologies

Daniel J. García Fidalgo
33HOPS
This page was las modified on 2018-08-14



Website Map
Resources & help
Index of Docs
33HOPS Forum

Fill in to download
The download link will be sent to your e-mail.
Name
Lastname
E-mail


            Read our Privacy Policy