A common cause of drive performance problems is using too many tape drives and
not having a media server and disk subsystem that can push data fast enough to
the tape drives.
Start off by using only one tape drive and ensure the buffer setting are 256K.
use "iostat -xdnz 1" to examine the drive
Quick Answer from memory:
This applies to 5.1 and below but I cannot vouch for 6.0+
bpexpdate -m "MEDIAID" -ret 4 -force
I also recall a "-just_media" option
Jonathan Marianu
Sent from AT&T Blackberry 8820
___
Veritas-bu maillist - Veritas-bu@mailman.
Two things...
1. NBU will not reduce the retention period of a media. That is to
say that the expiration date of a media (data portion, not the
physical useful life span) will never be made to be a date which is
closer in time to today.
2. NBU will not change the retention level. That is t
Hi all,
In our NBU 6.0 environment, we have a number of tapes (about 60) that
we want to change the retention level of. From retention level 12 to
retention level 4.
I've already written a solid script (on Solaris) that recalculates the
expiry (via retention level) for each of the images o
David
When you get a chance can you send me whatever information you have on
the host name change process, thanks.
Daniel Jimenez
Data Protection Team
From: Jimenez, Daniel
Sent: Wednesday, November 28, 2007 9:18 AM
To: Clooney, David; WEAVER, Simon (external); Ed Wilts
Cc: veritas-b
An LTO-3 drive needs to run at least 23MB/sec native and preferably over
80MB native (before compression). We're having difficulties consistently
getting over 30 - and frequently get a lot lower - from our Solaris master
server to our tape drives with NetBackup 6.0MP5. Our media servers aren't
gr
All, in a class the instructor recommended setting it at 129 for
Windows.
Regards
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, November 29, 2007 1:56 PM
To: [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu
Subject:
Justin,
I believe the default is 32k. We try to get as many of our clients to 512k
as possible. I don't have any definitive numbers for you other than "it's
noticeably faster" and also that "switch cpu usage dropped noticeably".
Our network is most certainly different than yours so YMMV.
I would
I assume you did the nbpushdata -modify_5x_hosts command?
If you go into Devices>Media Servers, does it show all servers and the
proper version?
To me it sounds like you might have a name resolution problem. Things were
probably working fine before, but I've found that NBU 6.x (6.5 for me) and
pb
Hi, I have NBU 5.1 MP6 on a Windows server. I have a brick level
mailbox to restore and before I shoot this thing off, I want to ensure I
have the right settings.
What should be checked under the Microsoft Exchange Tab in Backup,
Archive, and Restore when selecting the option to restore marked
check to ensure that the storage unit that you are trying to duplicate to is
set as the same type as the media that you show in scratch.
Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee 37421
423-296-8200
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
That's a good question, I have not played with Vaulting in awhile. For
duplication via in-line tape copy it should be the same as a regular
backup, I guess it depends on what kind of duplication you are doing? Disk
-> Tape? Tape->Tape, Vaulting?
On Thu, 29 Nov 2007, ZIMMER, RANDY K [AG/1000] w
Guys i have just upgraded my master server to nbu 6.0mp4 running on
solaris 9.
I have 3 media servers which are SSO and back themselves up.
All connected via fibre to shared drives.
Master server and 2 of the media servers backup fine and at good speeds
but one media server now runs like a dog.
I guess my question would be is a Duplication treated the same way as a regular
backup? When a backup starts it looks to see if it has available media in the
pool it is writing to, if there is none it looks for a scratch tape, if it
finds one it assigns it to the appropriate pool. Are duplicat
I had no frozen tapes.
Thanks,
Randy K. Zimmer
Sr. Unix System Administrator
Office: 314-694-3109
Cell: 314-960-0500
[EMAIL PROTECTED]
-Original Message-
From: Justin Piszcz [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 29, 2007 8:57 AM
To: ZIMMER, RANDY K [AG/1000]
Cc: verit
Scratch aren't necessary scratch if they are frozen, run bpmedialist and
check for frozen tapes first.
On Thu, 29 Nov 2007, ZIMMER, RANDY K [AG/1000] wrote:
> All,
>
> My duplication process has been failing lately on code 96 ( could not
> allocate new media). What's weird is I show that I have
The default is either 16 KiB or 32 KiB, I was wondering if anyone tested
various sizes such as 64,128,256,512,1024 KiB and how that had an impact
on performnace? I believe in the tuning doc they recommend you set it to
128 KiB..
Justin.
___
Veritas-b
All,
My duplication process has been failing lately on code 96 ( could not
allocate new media). What's weird is I show that I have "scratch" tapes
in the robot so shouldn't it assign a tape to the appropriate volume
pool and start the duplication? Any information would be greatly
appreciated.
T
If your firmware is up to date on the i2K, you can use the tool in the robot
firmware to show the drive usage.
It is run from the ADIC java gui for the library.
Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee 37421
423-296-8200
-Original Message-
From: [EMAIL PROTECTED]
[m
Hello Abhishek,
Try this,
Stoping netbackup deamons on master server and power off-on your tape changer
(all drives must be empty) , later take online Netbackup.
Regards
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Abhishek Dhingra1
Sent: 29 Ka
Another option would be to analyse the bptm logs on the media server
doing the writing to ascertain whether you are supply enough or too
little data.
Dave
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 28 November 2007 23
21 matches
Mail list logo
