Viktor Radnai wrote:
> Hi Paul,
>
> Did you specify the ThecusCameraFile storage device in bacula-sd.conf
> as well? Did you restart the storage daemon so it would pick up the
> new config? If the answer to both questions is yes, could you please
> send us the storage definition from both bacula-dir.conf and
> bacula-sd.conf?
>
> Cheers,
> Vik
>
>   
Hi Vik,

The answer to both questions is yes (I think) :-)
Here is the relevant section from bacula-dir.conf:

Client {
    Name = thecus_camera
    Address = pluto
    FDPort = 9102
    Catalog = MyCatalog
    Password = "xxx"          # password for FileDaemon
    File Retention = 6 months
    Job Retention = 6 months
    AutoPrune = yes
}

Storage {
    Name = ThecusCameraFile
    Address = pluto.waldo.home
    SDPort = 9103
    Password = "xxx"
    Device = ThecusCameraStorage
    Media Type = File
}

Pool {
    Name = ThecusCameraFullPool
    Pool Type = Backup
    #Storage = PlutoFile
    Recycle = yes
    Maximum Volume Jobs = 1
    Volume Retention = 6 months
    Accept Any Volume = yes
    Label Format = "ThecusCameraFull-"
}

Pool {
    Name = ThecusCameraDiffPool
    Pool Type = Backup
    Recycle = yes
    Volume Retention = 1 month
    Accept Any Volume = yes
    Maximum Volume Jobs = 1
    Label Format = "ThecusCameraDiff-"
    Maximum Volumes = 7
}

Pool {
    Name = ThecusCameraIncPool
    Pool Type = Backup
    Recycle = yes
    Volume Retention = 1 week
    Accept Any Volume = yes
    Maximum Volume Jobs = 1
    Label Format = "ThecusCameraInc-"
    Maximum Volumes = 7
}

# List of files to be backed up
FileSet {
    Name = "ThecusCameraFileSet"
    Include {
        File = "/mounts/for_backup/camera"
        Options {
            Compression=GZIP2
            signature = SHA1
            verify = pins1
        }
    }
    Exclude {
        File = /proc
        File = /tmp
        File = /.journal
        File = /.fsck
    }
}

JobDefs {
    Name = "ThecusCameraTemplate"
    Type = Backup
    Level = Incremental
    Write Bootstrap =
"/var/backups/client_backups/thecus/camera/thecus_camera.bsr"
    Schedule = "WeeklyCycle"
    Messages = Standard

    FileSet="ThecusCameraFileSet"
    Pool = "Default"
    Full Backup Pool = ThecusCameraFullPool
    Incremental Backup Pool = ThecusCameraIncPool
    Differential Backup Pool = ThecusCameraDiffPool
    Run Before Job = "/bin/mount /mounts/for_backup/camera"
    Run After Job = "/bin/umount /mounts/for_backup/camera"
    Run After Failed Job = "/bin/umount /mounts/for_backup/camera"
    Priority = 10
    Spool Data = no
    Client = thecus_camera
    Storage = ThecusCameraFile
}

Job {
    Name = "ThecusCamera"
    JobDefs = "ThecusCameraTemplate"
    Type = Backup
}

Job {
    Name = "ThecusCameraRestoreFiles"
    #JobDefs = "RestoreFilesTemplate"
    Storage = "ThecusCameraFile"
    Type = Restore
    Client=pluto
    FileSet="Full Set"
    Pool = Default
    Messages = Standard
    Where = /tmp/bacula-restores
}

Job {
    Name = "ThecusCameraVerify"
    JobDefs = "ThecusCameraTemplate"
    Type = Verify
    Level = DiskToCatalog
}


*****End of bacula-dir.conf***********

And here is the relevant section of bacula-sd.conf:

Device {
    Name = ThecusCameraStorage
    Media Type = File
    Archive Device = "/var/backups/client_backups/thecus/camera"
    LabelMedia = yes;
    Random Access = Yes;
    AutomaticMount = yes;
    RemovableMedia = no;
    AlwaysOpen = no;
}


*****End of bacula-sd.conf***********


The backup works just fine, so I'm not sure why the restore does not,
using the same Storage parameter.  Thanks for your help!

Paul


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to