On Friday 18 March 2005 21:09, Brennon Church wrote:
> Kern Sibbald wrote:
>
>
> <snip>
>
> > With version 1.37 as it currently stands, you can "clone" a job. That is
> > start up another job that will backup the same data (since the jobs run
> > separately, there may be minor differences). This means that you can do
> > your regular backup, and simultaneously run another job that makes
> > off-site storage to tapes, or sends directly to an off-site SD.
>
> It sounds like the clone functionality would be perfect for what I'm
> looking for. Any estimate on when 1.37 is expected to release?
May - June, but no guarantees.
>
> > The problem here is that with the currently released version 1.36.2, you
> > can backup to two different media types as Arno indicates below, but you
> > cannot do restores from two different media types without manually
> > editing the bsr file. At one time I posted a document on how to do so,
> > but it is not a recommended configuration. If all goes well version 1.37
> > will resolve this problem, but it is not yet a reality.
>
> Do you still have that document anywhere? If it hasn't changed much,
> perhaps I could still use it for my situation?
It is attached ...
>
> Thanks.
>
> --Brennon
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Bacula-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Best regards,
Kern
If you run a backup job with two different types of media, for
example, using a DLT for full saves and a DDS-4 for incremental,
you will have some difficulties doing restores because Bacula
doesn't yet know how to deal with multiple media types for a single
job name (multiple jobs run).
When you do a "restore" command, bacula will warn you that it
is not possible to do the restore:
Warning, the JobIds that you selected refer to more than one MediaType.
Restore is not possible. The MediaTypes used are:
File
Filea
The defined Storage resources are:
1: DDS-4
2: DLTDrive
3: File
4: Floppy
Select Storage resource (1-4): 3
where I have run the full save with MediaType File, then ran an
incremental backup with MediaType Filea.
If you select device 3, for example, Bacula will quite happily
continue mixing the two MediaTypes with less than satisfactory
results when the Storage daemon gets the job.
The solution is to continue and select the files to be restored.
In the example below, I simply restore everything (default):
You are now entering file selection mode where you add and
remove files to be restored. All files are initially added.
Enter "done" to leave this mode.
cwd is: /
$ done
Bootstrap records written to /home/kern/bacula/working/restore.bsr
The restore job will require the following Volumes:
test12
Test13
121 files selected to be restored.
Run Restore job
JobName: kernsrestore
Bootstrap: /home/kern/bacula/working/restore.bsr
Where: /tmp/bacula-restores
Replace: always
FileSet: Kerns Files
Client: Rufus
Storage: File
When: 2003-12-07 21:44:25
Priority: 10
OK to run? (yes/mod/no): no
then respond no to the request to run the job. At this point, you
must edit the bootstrap file (saved in /home/kern/bacula/working/restore.bsr
in the above example) into two or more distinct bootstrap files. Each should
have the records that pertain to a single MediaType. You generally should
know by looking at the Volume names.
In the above example, there were two volumes, and if I do a "list volumes",
one can see clearly that volume "test12" is MediaType "File" and "Test13" is
MediaType "Filea":
+---------+------------+-----------+----------+-----------+
| MediaId | VolumeName | VolStatus | VolBytes | MediaType |
+---------+------------+-----------+----------+-----------+
| 1 | test12 | Append | 1994210 | File |
| 2 | Test13 | Append | 53898 | Filea |
+---------+------------+-----------+----------+-----------+
where I have truncated a number of columns for display purposes.
In my example, the bootstrap file looks like:
restore.bsr
---------------
Volume="test12"
VolSessionId=1
VolSessionTime=1070829472
VolFile=0
VolBlock=197-1994406
FileIndex=1-58
FileIndex=61-106
FileIndex=109-110
FileIndex=112-116
FileIndex=119-120
Count=113
Volume="Test13"
VolSessionId=2
VolSessionTime=1070829596
VolFile=0
VolBlock=576-54095
FileIndex=1-8
Count=8
and it is quite easy to separate it into two files as:
restore1.bsr
--------------
Volume="test12"
VolSessionId=1
VolSessionTime=1070829472
VolFile=0
VolBlock=197-1994406
FileIndex=1-58
FileIndex=61-106
FileIndex=109-110
FileIndex=112-116
FileIndex=119-120
Count=113
restore2.bsr
----------------
Volume="Test13"
VolSessionId=2
VolSessionTime=1070829596
VolFile=0
VolBlock=576-54095
FileIndex=1-8
Count=8
Finally, start two jobs, one after the other and specify the appropriate
bsr filename and an appropriate storage resource that can read the
MediaType corresponding to the bootstrap file being restored.
