Hi Don,
First off please ensure that you include bacula-users in your follow
ups.
On Wed, 2007-01-03 at 18:05 -0700, MacArthur, Don wrote:
> Thanks Richard! The offsite thing is exactly what I'm doing. I write
> to tape first to go offsite, and then write to file for
> speed/convenience when re
Thanks Alan. I went through the docs and it comes close...
It looks to me like cloning creates a separate, second, job. What I was
hoping to do was get the data onto two separate volumes with only one
job run on the client, to reduce the duration of loading the client with
the backup process.
On Wed, 3 Jan 2007, Don MacArthur wrote:
> I'm preparing to upgrade from 1.38.7. My current nightly process looks
> like this:
> 1. Backup to tape.
> 2. Backup to file.
> My question is, can I use a migration job to *copy* my backup jobs to
> new volumes - as opposed to *moving* them? If so, ca
On Wed, 2007-01-03 at 14:43 -0700, Don MacArthur wrote:
> I'm preparing to upgrade from 1.38.7. My current nightly process looks
> like this:
> 1. Backup to tape.
> 2. Backup to file.
>
> In looking at the current documentation on bacula.org, the migration job
> info says a migration *moves* the
I'm preparing to upgrade from 1.38.7. My current nightly process looks
like this:
1. Backup to tape.
2. Backup to file.
In looking at the current documentation on bacula.org, the migration job
info says a migration *moves* the data and pointer in the catalog to new
volumes.
Somewhere else (I t
