I've chosen Bacula (v.5.0.2) to do backups of our office worker's data.
The Director and Storage Daemon run on a Debian based root server (the
SERVER) rented from a major german hosting company.
All the precious data and therefore Bacula's File Daemon (the
CLIENT) resides on a Debian based Samba server that's located on site and connected to the internet via ADSL (~768Kbit up) behind a SOHO router (it's a non-profit organization that's cronically short on money).
CLIENT's internet connection is being disconnected by the ISP every 24 hours and its IP does change every now and then.
I've managed to set up the basic infrastructure and successfully tested backing up and restoring files. But, now that it is time to define the automated jobs, I am facing a problem that I just can't get my head around:
Assume that I want to have a job per office worker and need to backup his Samba share which weighs around
10GB. The backup level does not matter as Bacula needs to do a Full Backup to start from.
But this initial Full Backup won't make it across the office's wire before a forced disconnect renders the job useless.
Is there any way to partition the initial workload into smaller pices other then setting up multiple jobs (and file sets)?
Or better, is it possible to somehow pause and restart a running job to overcome the inevitable connection loss?
Anything else I didn't think of that might help?