On 9/25/17 9:52 AM, Douglas K. Rand wrote:
> On 09/25/17 09:38, Jon SCHEWE wrote:
>> On 9/25/17 8:58 AM, Douglas K. Rand wrote:
>>> On 09/25/17 08:25, Jon SCHEWE wrote:
>>>> On 9/14/17 9:38 AM, Douglas K. Rand wrote:
>>>>> On 09/14/17 09:11, Jon SCHEWE wrote:
>>>>>> I've got the always incremental backup strategy working. It backs
>>>>>> up to
>>>>>> the pool AI-Incremental and then the consolidate job goes to
>>>>>> AI-Consolidate.
>>>>>>
>>>>>> Now I would like to add virtual full backup for offsite. Below is
>>>>>> what I
>>>>>> have for configuration. I'm unsure about the setting of the pool in
>>>>>> the
>>>>>> virtual full job defs and the next pool for the virtual full.
>>>>>
>>>>> Yes, you want the name of your consolidated pool in the job defs for
>>>>> your offsite jobs. I also set Full Backup Pool and Incremental
>>>>> Backup
>>>>> Pool, along with Next Pool.
>>>>>
>>>>> The Next Pool is, I believe, the key for the virtual full jobs to
>>>>> work, that is where the virtual job is written. I think, but am not
>>>>> sure, that setting the Full and Incremental pools tells the virtual
>>>>> job where to get the source backups.
>>>>>
>>>>> Here is my setup for doing virtual full backups to tape from my
>>>>> on-disk always incrementals. We also have a host named gemini, so
>>>>> I'll include that as samples. (I wonder if using star names is the
>>>>> most popular naming scheme with computer geeks.)
>>>>>
>>>>> Note that our pool names don't follow the samples in the docs:
>>>>> * "consolidated" instead of "AI-Consolidated"
>>>>> * "always-incr" instead of "AI-Incremental"
>>>>>
>>>>>
>>>>> job {
>>>>> name = "gemini-offsite"
>>>>> client = "gemini"
>>>>> job defs = "ai-offsite"
>>>>> }
>>>>>
>>>>> job defs {
>>>>> name = "ai-offsite"
>>>>> type = backup
>>>>> level = virtual full
>>>>> schedule = "offsite"
>>>>> # Gotta turn "virtual full" jobs into Archive jobs so we don't
>>>>> try
>>>>> to use
>>>>> # the backup for the next "virtual full" job.
>>>>> run script {
>>>>> console = "update jobid=%i jobtype=A"
>>>>> runs when = After
>>>>> runs on client = No
>>>>> }
>>>>> file set = "standard"
>>>>> accurate = yes
>>>>> messages = "standard"
>>>>> write bootstrap = "/var/db/bareos/bootstrap/%c.bsr"
>>>>> pool = "consolidated"
>>>>> full backup pool = "consolidated"
>>>>> incremental backup pool = "always-incr"
>>>>> spool data = yes
>>>>> spool attributes = yes
>>>>> next pool = "offsite"
>>>>> }
>>>>>
>>>>> pool {
>>>>> # No "Label Format" disables automatic volume labeling
>>>>> name = offsite
>>>>> pool type = Backup # Sigh, case sensitive
>>>>> storage = lto6-1
>>>>> file retention = 30 days
>>>>> job retention = 90 days
>>>>> volume retention = 90 days
>>>>> maximum volume bytes = 2500 GB
>>>>> volume use duration = 48 hours
>>>>> recycle oldest volume = yes
>>>>> }
>>>>>
>>>>> storage {
>>>>> name = lto6-1
>>>>> address = bareos-sd.meridian-enviro.com
>>>>> password = "******"
>>>>> device = lto6-1
>>>>> maximum concurrent jobs = 1
>>>>> media type = "lto-6"
>>>>> }
>>>>>
>>>>> Hope this helps. When you get it working I think you'll really like
>>>>> the setup.
>>>>>
>>>> That didn't work. My offsite ran last night and wrote to the
>>>> Consolidated pool rather than the offsite Pool. Here's my job defs:
>>>> JobDefs {
>>>> Name = "OffsiteJob"
>>>> Type = Backup
>>>> Level = VirtualFull
>>>> Client = gemini-fd
>>>> FileSet = "SelfTest" # selftest
>>>> fileset (#13)
>>>> Schedule = "OffsiteSchedule"
>>>> Storage = Offsite
>>>> Messages = Standard
>>>> Pool = AI-Consolidated
>>>> Incremental Backup Pool = AI-Incremental
>>>> Next Pool = Offsite
>>>> Virtual Full Backup Pool = Offsite
>>>> Priority = 10
>>>> Accurate = yes
>>>> Write Bootstrap = "/mnt/bareos-file/bootstrap/%c.bsr"
>>>>
>>>> RunScript {
>>>> RunsOnClient = no
>>>> RunsWhen = Before
>>>> FailJobOnError = yes
>>>> Command = "/etc/bareos/check-offsite-backup-disk.sh"
>>>> }
>>>> RunScript {
>>>> console = "update jobid=%i jobtype=A"
>>>> RunsOnClient = no
>>>> RunsOnFailure = No
>>>> RunsWhen = After
>>>> FailJobOnError = yes
>>>> }
>>>>
>>>> }
>>>>
>>>> And the jobs that ran:
>>>> Job {
>>>> Name = "offsite-andromeda"
>>>> JobDefs = "OffsiteJob"
>>>> Client = "andromeda-fd"
>>>> FileSet = "andromeda"
>>>> }
>>>> Job {
>>>> Name = "offsite-gemini-fd"
>>>> JobDefs = "OffsiteJob"
>>>> Client = "gemini-fd"
>>>> FileSet = "gemini-all"
>>>> }
>>>>
>>>> It seems that the jobs ran at level "Full" rather than "Virtual Full"
>>>
>>> I'm not using the "Virtual Full Backup Pool" directive. Not sure if
>>> that is affecting things, mostly because I don't know what it does and
>>> the manual doesn't seem to say either. But I think that "Next Pool",
>>> which you have, is the key for setting the destination on Virtual Full
>>> backups.
>>>
>>> What is your Offsite pool and storage defined as?
>>>
>>> I'm not setting Storage in the Job Def, I do it in the Pool instead.
>>> Again, I'm not sure that matters.
>>>
>>> In short, I don't see what is causing the problem from what you
>>> posted. Sorry.
>>>
>>>
>> When you run your backups and look at the messages, what does the level
>> say? Mine are saying "Backup Level: Full". I would have expected
>> "Virtual Full".
>>
>> Pool {
>> Name = Offsite
>> Pool Type = Backup
>> Recycle = yes # Bareos can automatically
>> recycle
>> Volumes
>> Next Pool = Offsite
>> AutoPrune = yes # Prune expired volumes
>> Volume Retention = 60 days # How long should the Full Backups
>> be kept? (#06)
>> Maximum Volume Bytes = 50G # Limit Volume size to something
>> reasonable
>> Maximum Volumes = 100 # Limit number of Volumes in Pool
>> Label Format = "Offsite-" # Volumes will be labeled
>> "Full-<volume-id>"
>> Storage = Offsite
>> Action On Purge = Truncate
>> }
>> Storage {
>> Name = Offsite
>> Address = gemini # N.B. Use a fully qualified name
>> here
>> (do not use "localhost" here).
>> Password = "XXXXXXX"
>> Device = OffsiteStorage
>> Media Type = File
>> }
>
> Yes, my Backup Level is Virtual Full:
>
> Build OS: amd64-portbld-freebsd11.1 freebsd
> 11.1-RELEASE-p1
> JobId: 36416
> Job: gemini-offsite.2017-09-23_11.48.02_37
> Backup Level: Virtual Full
> Client: "gemini" 15.2.2 (16Nov15)
> amd64-portbld-freebsd10.2,freebsd,10.2-RELEASE-p14
> FileSet: "standard" 2016-10-25 19:20:00
> Pool: "offsite" (From Job's NextPool resource)
> Catalog: "catalog" (From Client resource)
> Storage: "lto6-1" (From Storage from Job's NextPool
> resource)
> Scheduled time: 23-Sep-2017 11:48:02
> Start time: 22-Sep-2017 21:12:42
> End time: 22-Sep-2017 21:12:57
> Elapsed time: 15 secs
> Priority: 10
> SD Files Written: 245,633
> SD Bytes Written: 2,778,402,119 (2.778 GB)
> Rate: 185226.8 KB/s
> Volume name(s): ND0014
> Volume Session Id: 34
> Volume Session Time: 1506185271
> Last Volume Bytes: 591,369,763,219 (591.3 GB)
> SD Errors: 0
> SD termination status: OK
> Accurate: yes
> Termination: Backup OK
>
>
> And I don't see anything from your Pool settings that jump out at me.
>
> Do you get the appropriate devices at the start of the job? In my log
> I have:
>
Well, my most recently job that was kicked off manually seems to have
worked. I do see the appropriate devices in there now. I guess I will
need to see what happens with the future jobs.
Thank you for the configuration help and log entries.
--
Research Scientist
Raytheon BBN Technologies
5775 Wayzata Blvd, Ste 630
Saint Louis Park, MN, 55416
Office: 952-545-5720
--
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.
