[Bacula-users] Feature request:

Hello,
I may implement this myself, after people have commented.
Thanks,
Graham.


Item n: Restore from volumes on multiple storage daemons

Origin: Graham Keeling (graham AT equiinet DOT com)

Date: 12 March 2009

Status: Proposing

What: The ability to restore from volumes held by multiple storage daemons
would be very useful.

Why: It is useful to be able to backup to any number of different storage
daemons. For example, your first storage daemon may run out of space, so you
switch to your second and carry on. Bacula will currently let you do this.
However, once you come to restore, bacula cannot cope when volumes on different
storage daemons are required.

Notes: The director knows that more than one storage daemon is needed, as
bconsole outputs something like the following table.

The job will require the following
   Volume(s)                 Storage(s)                SD Device(s)
===========================================================================
   
   backup-0001               Disk 1                    Disk 1.0                 
   backup-0002               Disk 2                    Disk 2.0             

However, the bootstrap file that it creates gets sent to the first storage
daemon only, which then stalls for a long time, 'waiting for a mount request'
for the volume that it doesn't have.
The bootstrap file contains no knowledge of the storage daemon.

I think that restoring from multiple storage daemons can be achieved as
follows:


Add 'Storage=' lines to the bootstrap file.

Currently, the director connects to the sd first, and then the fd.
Since we need to go through the storages one by one, it should connect to
the fd first.

The director then reads the bootstrap file, looking for the storages.
The existing mechanism for authorising and restoring from a bootstrap file
is then reused once for each storage, but the director sends only the
relevant section of the bootstrap file to the fd.
After each storage, the fd tells the director that it has finished. Once
the director finishes reading the bootstrap file, it tells the fd to end the
restore.
The fd then runs the 'run after' scripts.



With the idea above, the sd code is not changed.

The director migrate, vbackup, and verify code also suffer from the same
problem to do with reading from multiple storage daemons.
However, once the restore is fixed, I believe that it would be very simple
to update those parts too, as they do not need to contact a file daemon.


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users