One correction to the Basic Disk Staging
as we found out is that there are no settable high water marks for Basic
Disk Staging. The hard-coded maximum is 98% of your basic storage
disk. It is my guess this is done so that you will want to purchase
the Shared Disk Option. You can still manually start the destaging
process; however, it is a real pain in the butt to keep on top of your
filling volumes.
Try to prevent the situation where
multiple jobs write to a storage unit at one time and fill it to capacity.
Once the storage unit is full, none of the jobs can complete and all the
jobs fail due to a disk full condition. To reduce the number of jobs that
are allowed to write to the storage unit, decrease the Maximum concurrent
jobs setting. For more information, see “Maximum concurrent jobs” on
page 231.
The high water mark does not apply
to storage units that are used for basic disk staging. For more information
about this type of staging, see “Basic disk staging” on page 244 of the
Veritas NetBackup 6.5 Administrators Guide for UNIX and Linux, Volume 1.
Mike
To:
|
"Clausen, Matt R [EQ]"
<Matthew.R.Clausen AT Embarq DOT com>
|
cc:
|
"'ssloh AT singnet.com DOT sg'"
<ssloh AT singnet.com DOT sg>, veritas-bu <veritas-bu AT mailman.eng.auburn DOT edu>
|
Subject:
|
Re: [Veritas-bu] Confusing disk staging
methods |
Nice definition, should be put in a FAQ :)
On Wed, 17 Dec 2008, Clausen, Matt R [EQ] wrote:
> Here are the basics:
>
> 1. Basic Disk Staging
>
> Backup to Disk First then a Destaging schedule duplicates the backup
image to tape media. Once the image is successfully destaged to tape, it
is then removed from the disk depending on how your low/high water marks
are set. You need enough disk space with this though to basically store
all your backups until the images can be successfully destaged.
>
> 2. Storage Lifecycle Policies
>
> Basically these define the backup/duplication relationships based
on the "level" of the SLP defined in the policy. The nice thing
about these is you define the schedule once and it handles it from there
backing up and duplicating based on the directives in the policy. The caveat
here is that you need Advanced Disk Staging units which means the Flexible
Disk Option (Read $$$$$$$$). This is basically Vault without the reporting/management
functionality.
>
> 3. Multiple Copies
>
> When a backup runs, it makes multiple copies based on what you tell
it. Think of it as multiple destinations for a backup at the time the policy
runs.
>
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of ssloh
> Sent: Wednesday, December 17, 2008 9:00 PM
> To: veritas-bu
> Subject: [Veritas-bu] Confusing disk staging methods
>
> Hi folks,
>
> Could help to elaborate what are the differences & scenarios apply
between
> 1. Basic Disk staging
> 2. Storage Lifecycle Policies
> 3. Multiple copies
>
> After reading the NBU guide getting more and more confusing.
>
> Thanks
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Mike_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|