Isn't it better to specify Pools in Job resource?
Job {
[skipped]
Full Backup Pool = db-full-pool
Differential Backup Pool = db-diff-pool
Incremental Backup Pool = db-inc-pool
}
On Mon, 10 Dec 2012 17:31:02 -0200
"Luis H. Forchesatto" wrote:
> Woah, that's exactly whath I need.
>
> I'm
You can also do that per Job OR JobDefs too, If you the same schedule for more
than 1 client this may be more appropriate for you:
Job or JobDefs {
Pool = "thisjob-inc-pool" # default 'level' pool *REQUIRED even if not used*
Full Backup Pool = "thisjob-full-pool"
Incremental Backup Pool = "t
Woah, that's exactly whath I need.
I'm reorganizing my backup system an I need to restructure the volume
usage, so the best solution is separating full and incremental backups.
Thanks Bill and Silas for teaching me how to do this =D
Now let's implement.
Good bye and thanks.
2012/12/10 Bill Arl
On 12/10/12 11:46, Bill Arlofski wrote:
> Hi Louis,
>
> Yes, you can do this withing a Schedule:
>
> An example is below, but it kind of funny.
heh Should have been "but it wrapped kind of funny"
--
Bill Arlofski
Reverse Polarity, LLC
On 12/10/12 11:19, Luis H. Forchesatto wrote:
> Its possible to separate full and incremental backups from the same client
> in separated volumes.
>
> The client has one full backup weekly and for the other 6 days it has an
> incremental backup. I would like to keep the full backup separated and a
On 12/10/2012 11:19 AM, Luis H. Forchesatto wrote:
Its possible to separate full and incremental backups from the same
client in separated volumes.
The client has one full backup weekly and for the other 6 days it has
an incremental backup. I would like to keep the full backup separated
and a
Its possible to separate full and incremental backups from the same client
in separated volumes.
The client has one full backup weekly and for the other 6 days it has an
incremental backup. I would like to keep the full backup separated and all
the incremental backups that is run during the week b
