Take a look at the following TechNote for a really good write-up on
this subject...
http://support.veritas.com/docs/280398
Also this one for 6.0:
http://support.veritas.com/docs/280067
-Tim
On Dec 16, 2005, at 5:53 PM, Geyer, Gregory wrote:
> John,
>
> GREAT INFORMATION!
>
> Now, to investigate whether MAX_STAGING_JOBS is per DSSU or altogether
> (ie, if DSSU#1 kicks off first and grabs all the jobs, what does
> DSSU#2
> do?)
>
> Thanks again, the list rocks.
>
> G.
>
> -----Original Message-----
> From: Nardello, John [mailto:john.nardello AT wamu DOT net]
> Sent: Friday, December 16, 2005 4:26 PM
> To: Geyer, Gregory
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] 5.1 MP4
>
>> From the MP4 readme:
>
> Etrack Incident = ET313352
>
> Description:
> Disk staging only submits one duplication job at a time so it
> was unable
> to make use of idle tape drives.
>
> Additional Notes:
> Up to four bpduplicate jobs are submitted at a time. The
> duplication jobs
> contain images grouped into jobs of 25 Gigabytes. By creating
> files named
> MAX_STAGING_JOBS and STAGING_JOB_KB_LIMIT in the NetBackup
> directory on the
> master server, these defaults can be adjusted as needed. For
> the
> STAGING_JOB_KB_LIMIT, the value is in kilobytes and the
> default is 26214400
> (25 gigabytes). A smaller value causes more jobs to be
> submitted, but
> there will only be MAX_STAGING_JOBS running at a time.
>
> "It's not a bug, it's a feature."
>
> I've also seen those bid files present under 5.1 MP3a so it's nothing
> new anyway. I haven't seen hundreds either so I'm pretty sure NB is
> cleaning up after itself at some point.
>
> - John Nardello
> "Your backups are only as good as your restores."
>
>
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Geyer,
> Gregory
> Sent: Friday, December 16, 2005 3:14 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] 5.1 MP4
>
>
> We've upgraded to 5.1 MP4 and are now experiencing issues with Disk
> staging. We've got a ticket open but interested to see if anyone else
> has experience these issues:
> The disk staging process now automatically takes 4 tape drives per DSSU
> when going off to tape. This is a problem if you have 6 DSSUs and only
> 15 tape drives, not to mention those drives are needed for other media
> servers.
> It is now also creating these files on the DSSU media servers in
> /usr/openv/netbackup:
> root@<hostname>:/usr/openv/netbackup# ll bid*
> -rw-rw-rw- 1 root root 1984 Dec 15 13:20
> bid_file_bladestore_oracle0
> -rw-rw-rw- 1 root root 530 Dec 16 13:08
> bid_file_bladestore_oracle_1_15240
> -rw-rw-rw- 1 root root 1219 Dec 16 13:08
> bid_file_bladestore_oracle_2_15240
> -rw-rw-rw- 1 root root 18 Dec 16 13:08
> bid_file_bladestore_oracle_3_15240
> -rw-rw-rw- 1 root root 293 Jul 1 2004
> bid_file_bladestore_staging_1TB0
> -rw-rw-rw- 1 root root 4375 Dec 15 10:04
> bid_file_bladestore_unix0
> <SNIP>
> In the files are a listing of images to get backed up.
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
|
