Hello Adam,

Do you have any storage resource defined in the pool or schedule resources
defined for this job? The pool is not defined in your BackupCatalog job,
therefore I suppose it is spedified in the schedule resource for this job?

Best regards,
Ana

On Thu, Aug 20, 2015 at 12:18 AM, Adam Clark <a...@eryjus.com> wrote:

> Hello all,
>
>
>
> I have been using Bacula to back up several servers for about 2 months
> now.  I now would like to take the next step to FTP my backups off-site.
> However, I back up about 10GB each night and that is a bit too much data to
> move every night.  My backups are to the file system.
>
>
>
> To get around this, I have created a second storage device that puts a
> backup in a subfolder that I will not FTP.  The remaining backups are left
> to the original storage device.  By the way, I have pools Sun to Sat set
> up, plus a Perm pool.  These all work fine.
>
>
>
> So far, everything is working as I would expect…  except, the catalog
> backup is not going to the device (and therefore the volume mounted on that
> device) that I specify.  Let me try to elaborate:
>
>
>
> Server A backup kicks off at 22:00 and writes to storage Z
>
> Server B backup kicks off at 22:00 and writes to storage Z
>
> Server C backup kicks off at 22:00 and writes to storage Z
>
> Server D backup kicks off at 22:00 and writes to storage Y
>
> Catalog backup kicks off at 23:55 and is supposed to write to storage Z,
> but attempts to write to storage Y.
>
>
>
> Now, since the volume it is expecting does not reside in storage Z, it
> invalidates the volume to which it wanted to write (sets it to Error), and
> ultimately finds the correct volume on the correct storage.  However, it
> leaves me with a volume in error each night.
>
>
>
> I’m afraid that my only solution is to create a second pool set (Sun-Sat +
> Perm for this 1 server) in order to get the catalog to write to the correct
> storage device.  That is bit of complexity I did not want to take on if I
> could help it.
>
>
>
> Here is the catalog backup job in my bacula-dir.conf:
>
>
>
> Job {
>
> Name = "BackupCatalog"
>
> JobDefs = "DefaultJob"
>
> Level = Full
>
> Client = Bacula-Server
>
> FileSet="Catalog"
>
> Schedule = "FullCatalog"
>
> Storage = Backup-File
>
> RunBeforeJob = "/usr/libexec/bacula/make_catalog_backup.pl MyCatalog"
>
> RunAfterJob  = "/usr/libexec/bacula/delete_catalog_backup"
>
> Write Bootstrap = "/var/spool/bacula/%n.bsr"
>
> Priority = 11                                 # run after main backup
>
> }
>
>
>
> Notice I am explicit about the storage to which to write the catalog.
>
>
>
> Is there anything I might be missing before I set up another set of
> pools?
>
>
>
> Thanks in advance for your help!
>
>
>
>
>
>
>
> Thank you!
>
>
>
> Adam Clark
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to