Am 07.10.2015 06:53, schrieb Sven Gehr:
> Hi@all,
>
> for a long time I have problems with my tape backup and I can not solve it. I
> have configure my tape backup as described in the manual.
>
> /etc/bareos/bareos-sd.conf
> ...
> Device {
> Name = LTO4-Drive
> Drive Index = 0
> Media Type = LTO-4
> Archive Device = /dev/nst0
> Spool Directory = /var/bareos-spool
> Maximum Spool Size = 20G
> LabelMedia = yes;mit Label versehen
> Random Access = No;
> AutomaticMount = yes;
> RemovableMedia = yes;
> AlwaysOpen = no;
> }
> ...
>
> /etc/bareos/bareos-dir.conf
> ...
> JobDefs
> Name = "DefaultJob"
> Type = Backup(Backup/Restore)
> Level = Full
> Client = kvm01-fd
> Schedule = "WeeklyCycle"
> Storage = Tape
> Messages = Standard
> Pool = Full
> Full Backup Pool = Full
> Priority = 10
> Write Bootstrap = "/var/lib/bareos/%c.bsr"
> Max Start Delay = 22h
> }
> ...
> Job {
> Name = "kvm01"
> JobDefs = "DefaultJob"
> Client = kvm01-fd
> FileSet = "Linux All"
> }
>
>
> Job {
> Name = "tux"
> JobDefs = "DefaultJob"
> Client = tux-fd
> FileSet = "Linux All"
> }
>
> Job {
> Name = "kolab"
> JobDefs = "DefaultJob"
> Client = kolab-fd
> FileSet = "Linux All"
> }
>
> Job {
> Name = "wints"
> JobDefs = "DefaultJob"
> Client = wints-fd
> FileSet = "Windows All Drives"
> }
>
> Job {
> Name = "BackupCatalog"
> JobDefs = "DefaultJob"
> Level = Full
> FileSet="Catalog"
> Schedule = "WeeklyCycleAfterBackup"
> RunBeforeJob = "/usr/lib/bareos/scripts/make_catalog_backup.pl MyCatalog"
> RunAfterJob = "/usr/lib/bareos/scripts/delete_catalog_backup"
> RunAfterJob = "/bin/mt -f /dev/st0 eject"
> Write Bootstrap = "|/usr/bin/bsmtp -h kolab.local.lan -f
> [email protected] -s \"Bootstrap for Job %j\" [email protected]"
> Priority = 11
> }
> ...
> chedule {
> Name = "WeeklyCycle"
> Run = Level=Full Pool=MondayPool Monday at 23:05
> Run = Level=Full Pool=TuesdayPool Tuesday at 23:05
> Run = Level=Full Pool=WednesdayPool Wednesday at 23:05
> Run = Level=Full Pool=ThursdayPool Thursday at 23:05
> Run = Level=Full Pool=WeeklyPool Friday at 23:05
> }
>
> Schedule {
> Name = "WeeklyCycleAfterBackup"
> Run = Level=Full Pool=MondayPool Monday at 23:15
> Run = Level=Full Pool=TuesdayPool Tuesday at 23:15
> Run = Level=Full Pool=WednesdayPool Wednesday at 23:15
> Run = Level=Full Pool=ThursdayPool Thursday at 23:15
> Run = Level=Full Pool=WeeklyPool Friday at 23:15
> }
> ...
> Storage {
> Name = Tape
> Address = kvm01
> Password = "$#edv_bareos"
> Device = LTO4-Drive
> Media Type = LTO-4
> Autochanger = No
> }
> ...
> Pool {
> Name = Full
> Pool Type = Backup
> }
>
> Pool {
> Name = MondayPool
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 6h
> Maximum Volume Jobs = 2
> }
>
> Pool {
> Name = TuesdayPool
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 6h
> Maximum Volume Jobs = 2
> }
>
> Pool {
> Name = WednesdayPool
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 6h
> Maximum Volume Jobs = 2
> }
>
> Pool {
> Name = ThursdayPool
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 6h
> Maximum Volume Jobs = 2
> }
>
> Pool {
> Name = WeeklyPool
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 12h
> Maximum Volume Jobs = 2
> }
>
>
> The memory required for the jobs:
>
> Connecting to Client kvm01-fd at kvm01:9102
> 2000 OK estimate files=531,604 bytes=34,121,732,750
>
> Connecting to Client tux-fd at tux:9102
> 2000 OK estimate files=395,193 bytes=456,593,391,123
>
> Connecting to Client kolab-fd at kolab:9102
> 2000 OK estimate files=74,737 bytes=8,962,480,879
>
> Connecting to Client wints-fd at wints:9102
> 2000 OK estimate files=129,275 bytes=26,324,111,342
>
> The jobs kvm01 and tux run correctly with status "ok". Then I get the
> following messages:
Job 1 ....
> ---
> Bareos: Intervention needed for kolab.2015-10-06_23.05.00_28:
> 07-Okt 04:48 kvm01-sd JobId 1960: Job kolab.2015-10-06_23.05.00_28 is
> waiting. Cannot find any appendable volumes.
> Please use the "label" command to create a new Volume for:
> Storage: "LTO4-Drive" (/dev/nst0)
> Pool: TuesdayPool
> Media type: LTO-4
> ---
Job 2 ....
> Bareos: Intervention needed for wints.2015-10-06_23.05.00_29
> 07-Okt 06:00 kvm01-sd JobId 1961: Job wints.2015-10-06_23.05.00_29 is
> waiting. Cannot find any appendable volumes.
> Please use the "label" command to create a new Volume for:
> Storage: "LTO4-Drive" (/dev/nst0)
> Pool: TuesdayPool
> Media type: LTO-4
> ---
and you configured:
Maximum Volume Jobs = 2
congratulations, it does what you asked for.
> Why bareos writes not on the same tape? The space is sufficient!
>
> with best
> sven
>
--
Mit freundlichen Grüßen
Philipp Storz [email protected]
Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92
http://www.bareos.com Fax: +49 221 63 06 93-10
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, M. Außendorf,
J. Steffens, P. Storz, M. v. Wieringen
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
