2012/2/5 Jan Lentfer <Jan.Lentfer AT web DOT de>:
> Am 05.02.2012 11:26, schrieb Jan Lentfer:
>> Currently I have a setup where I use 3 file pools for Incr, Diff and
>> Full. I use copy jobs to copy the incr jobs to one tape drive (DLT) and
>> the full and diff jobs to another tape drive (LTO-1).
>>
>> Now I thought about doing Virtual Full Backups from the file pools to a
>> 3rd drive every 2nd month or so with a retention of 5 years to establish
>> a long term archive.
>>
>> Of course the NextPool is already configured in the File Pool
>> Definitions for the Copy jobs.
>>
>> Is there a possibility to run Virtual Fulls from the File Pools to
>> another Pool? E.g. is it possible to set the NextPool in the Virtual
>> Full's job definition or on the schedule definition?
>
> I think I have solved/worked around this using a "Dummy" Pool like this:
>
> Pool {
> Name = "ArchivePool"
> Pool Type = Backup
> Storage = "DLT-Tape II"
> Recycle = yes # Bacula can automatically
> recycle Volumes
> AutoPrune = yes # Prune expired volumes
> Recycle Oldest Volume = yes # Use oldest Volume
> Volume Retention = 5 Years #
> Label Format = "Archive-"
> # Maximum Volumes = 15 # 10 Volumes
> }
> Pool {
> Name = "ArchiveDummyPool"
> Pool Type = Backup
> Storage = FileStorageDev7"
> Recycle = yes # Bacula can automatically
> recycle Volumes
> AutoPrune = yes # Prune expired volumes
> Recycle Oldest Volume = yes # Use oldest Volume
> Volume Retention = 1 week
> NextPool= ArchivePool
> Label Format = "Dummy-"
> # Maximum Volumes = 15 # 10 Volumes
> }
>
> The Dummy pool has a File Storage device that points to the same
> directory the file volumes are stored in.
>
> And then I use this "archive" job:
> Job {
> Name = "Archive_epia"
> Enabled = Yes
> JobDefs = "DefaultJob"
> Level=VirtualFull
> Pool=ArchiveDummyPool
> Client = "epia-fd"
> FileSet = "epia-fs"
> Write Bootstrap = "/home/bacula/file-dev/epia.bsr"
> }
>
> Now I just have to figure out how to prevent restore from taking the
> ArchivePool into account for "standard" restores (because that would be
> slow)
>
> Jan
Hi,
What do you think about to use one more file device for full backup?
It will resolve problem with slow restore and it enable to use
schedule "Virtual Full" backup. I prepared two screens which show
proposed solution. That solution will give you possibility fast backup
to file devices (and fast restore) and schedule that kind of backup.
Example configuration:
Pool {
Name = "Pool 1"
...
Storage = "File device 1"
Next Pool = "Pool 2"
}
Pool {
Name = "Pool 2"
...
Storage = "File device 2"
Next Pool = "Pool 1"
}
Pool {
Name = "Pool 3"
...
Storage = "File device 3"
}
Job {
Name = Docs
Type = Backup
Level = Incremental
Pool = "Pool 3"
Client = darkstar-fd
FileSet = "Docs FileSet"
Messages = "Some messages"
}
run job=Docs level=Full pool="Pool 1" storage="File device 1"
run job=Docs level=Incremental pool="Pool 3" storage="File device 3"
...
run job=Docs level=Incremental pool="Pool 3" storage="File device 3"
run job=Docs level=VirtualFull pool="Pool 1" storage="File device 1"
run job=Docs level=Incremental pool="Pool 3" storage="File device 3"
...
run job=Docs level=Incremental pool="Pool 3" storage="File device 3"
run job=Docs level=VirtualFull pool="Pool 2" storage="File device 2"
etc.
I hope I helped.
Best regards.
gani
--
"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus
virtual-full-1.png
Description: PNG image
virtual-full-2.png
Description: PNG image
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
| 
