Re: [Veritas-bu] Retentions

2007-12-18 Thread David Chapa
Bingo, it will start from the utime of the originating backup and add
86,400*NrOfRetentionDays and add that to the originating utime to get to
the expiration.

I believe in the "old days" it was 28 days, but I believe Bobby is
right, 31 days is a month in NB.

I have it documented somewhere...if I can find it, I'll post it here.

Chapa

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bobby
Williams
Sent: Tuesday, December 18, 2007 4:02 AM
To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Retentions

I just checked a 3 month backup from last night (I don't have any 6
month).

It started @ 1197958489 (12/18/07 00:14:49)

It says that it expires @ 1205993689 (3/20/08 01:14:49)

A difference of 8035200 seconds; or 133920 minutes; or 2232 hours; or 93
days

I have seen it documented somewhere that a month in NB was 31 days just
to
make sure.

Use bpimagelist on a backup in your 6month retention policy to see the
backup time and the expiration time of the backup id. 




Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee  37421
423-296-8200

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave
Markham
Sent: Tuesday, December 18, 2007 5:07 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Retentions

Guys im being asked by management a bit of a stupid question but i don't
know for 100% so thought id check here.

If i have a retention set to 6 months i assume it is 6 months e.g from
02/01/07 to 02/07/07 and not 6 * 4 weeks or a certain number of days?

I know you can edit retentions but im just questioning the standard
ones.

Cheers
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

---
The information contained in this transmission may be 
confidential. Any disclosure, copying, or further 
distribution of confidential information is not permitted 
unless such privilege is explicitly granted in writing by 
Quantum Corporation. Furthermore, Quantum Corporation is not 
responsible for the proper and complete transmission of the 
substance of this communication or for any delay in its 
receipt.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Question: Backup what the symlink points to?

2007-05-02 Thread David Chapa
I think there used to be a way back in the early versions (1.6-1.7) but
I don't believe its there today...

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff
Lightner
Sent: Wednesday, May 02, 2007 9:04 AM
To: Justin Piszcz; NB List Mail
Subject: Re: [Veritas-bu] Question: Backup what the symlink points to?

GNU tar, find and cpio all have ways to "follow" symbolic links to get
the real files to which they point.  However I don't know of a way to
tell a NBU policy to use that option for the modified GNU tar it uses
for backups.  (You could do it at command line but then it would not be
a "netbackup" backup - just a tar.)  

The help for 5.1 MP4 says of symbolic links that it backs up the link
only and not the file to which it points.  It goes on to say to restore
the file to which the symbolic link restores you must actually restore
that file as well.




-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Justin
Piszcz
Sent: Wednesday, May 02, 2007 10:45 AM
To: NB List Mail
Subject: [Veritas-bu] Question: Backup what the symlink points to?

This concerns UNIX:

I need to look this up but was wondering if anyone knew off the top of 
their head how to make NetBackup backup what a symlink points to or if 
that is even possible?

I know about the cross-link option but that concerns mounts and 
filesystems, not sym-links.

Justin.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


The information contained in this transmission is 
confidential.  It is intended solely for the use of the 
individual(s) or organization(s) to whom it is addressed.  
Any disclosure, copying, or further distribution is not 
permitted unless such privilege is explicitly granted in 
writing by Quantum Corporation.  Furthermore, Quantum 
Corporation is not responsible for the proper and complete 
transmission of the substance of this communication or for
any delay in its receipt.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] LTO-2 LTO-3 mix

2007-04-25 Thread David Chapa
Two ways...buy the partitioning license for your i2K and have a separate
logical library for LTO2's and LTO3's

 

:-)

 

Or you can do it based on media type.

 

HCART2 Media (LTO2)

HCART3 Media (LTO3)

 

HCART2 Storage Units 

HCART3 Storage Units

 

NBU will only mount HCART2 media in an HCART2 storage unit and so on.

 

The media can reside in the same volume pool - that won't matter, what
matters is the media type and storage unit type.

 

david

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Spearman, David
Sent: Tuesday, April 24, 2007 1:17 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] LTO-2 LTO-3 mix

 

 

We will be getting an expansion cabinet to our scaler 2000 soon.
At the moment we have LTO-2 drives and tapes. When we add the expansion
cabinet we are also going to add 2 LTO-3 drives with a set of LTO-3
tapes. My question is how do I keep LTO-2 tapes going to LTO-2 drives
while the LTO-3 tapes go only to LTO-3 drives. I suspect a combination
of storage units and tape pools but now that we are at NBU6mp4 expired
tapes just return to the scratch pool which would make them available to
anything.

 

present setup

 

W2K3 master/media with sso/ndmp to scaler 2000 (5 tape drives
allowed)

W2K3 media server sso to scaler 2000 and DSSU (4 tape drives
allowed)

W2K3 san media server sso to scaler 2000 

 

David Spearman

County of Henrico

 

 



The information contained in this transmission is 
confidential.  It is intended solely for the use of the 
individual(s) or organization(s) to whom it is addressed.  
Any disclosure, copying, or further distribution is not 
permitted unless such privilege is explicitly granted in 
writing by Quantum Corporation.  Furthermore, Quantum 
Corporation is not responsible for the proper and complete 
transmission of the substance of this communication or for
any delay in its receipt.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Curious Log Entry

2007-04-24 Thread David Chapa
They could have killed the proc too...not that I've ever done that
before...





-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff
Lightner
Sent: Tuesday, April 24, 2007 10:23 AM
To: Steve Fogarty; Greenberg, Katherine (ISD, IT); Hudson, Steve;
WEAVER, Simon (external); Brooks, Jason;
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Curious Log Entry

Don't get me wrong.   As an early DOS user who refused to go to Windows
for years and a longtime UNIX/Linux admin I don't have much respect for
folks who can't do command line.   Having said that, however, I do think
there are times using a GUI makes sense.  For monitoring I like the
activity monitor and if one is careful one can actually kill what is
intended rather than everything.  As noted it is a pet peeve - not a
show stopper.

For stopping/starting drives and many other tasks the GUI is a royal
pain so I use command line or my own scripts based on command line for
such tasks.

-Original Message-
From: Steve Fogarty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 24, 2007 12:12 PM
To: 'Greenberg, Katherine (ISD, IT)'; 'Hudson, Steve'; Jeff Lightner;
'WEAVER, Simon (external)'; 'Brooks, Jason';
veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Curious Log Entry

Agreed.

Stay away from the GUI!

Steve 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Greenberg,
Katherine (ISD, IT)
Sent: Tuesday, April 24, 2007 12:31 PM
To: Hudson, Steve; Jeff Lightner; WEAVER, Simon (external); Brooks,
Jason;
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Curious Log Entry

Reason # 9 trillion to learn all the various syntax options of bpdbjobs
;) 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hudson,
Steve
Sent: Tuesday, April 24, 2007 11:03 AM
To: Jeff Lightner; WEAVER, Simon (external); Brooks, Jason;
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Curious Log Entry

I couldn't agree more We have inadvertently killed all jobs when
trying to kill only one. 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff
Lightner
Sent: Tuesday, April 24, 2007 10:47 AM
To: WEAVER, Simon (external); Brooks, Jason;
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Curious Log Entry

I've never seen a 150 that wasn't caused by someone actually canceling
the job (even when they initially don't fess up).

That brings up one of my pet peeves about the Java GUI.  The options for
"kill" selected job and "kill" all jobs are one above the other.  Often
once you highlight it the highlight goes away when you get the prompt to
OK the action.  Due to this I've seen a couple of times where people
here have killed all when they meant to kill one.

The kill all should be all the way at the end of the list and separated
by a bar so one has to consciously choose it.  Its warning prompt should
be significantly different than the one for killing a single job.   Hell
if it would just leave the original selection highlighted one would be
less likely to go ahead and hit OK.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of WEAVER,
Simon (external)
Sent: Tuesday, April 24, 2007 10:16 AM
To: 'Brooks, Jason'; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Curious Log Entry


Jason
Well its not automated :-)

If no one had access to the Master Server console, what about from the
end client??

Spooky :-)

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: [EMAIL PROTECTED]



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brooks,
Jason
Sent: 24 April 2007 14:49
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Curious Log Entry


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from
disclosure.
If you are not the intended recipient, please notify the sender
immediately, do not copy this message or any attachments and do not use
it for any purpose or disclose its content to any person, but delete
this message and any attachments from your system.

Astrium disclaims any and all liability if this email transmission was
virus corrupted, altered or falsified.
-
Astrium Limited, Registered in England and Wales No. 2449259 Registered
Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/v

Re: [Veritas-bu] Reporting scripts

2007-04-24 Thread David Chapa
This is probably the most attainable solution...

I think I have a script that does this...I'll have to track it down in
my archives.

You could also use bperror which will tell you all of the successfully
written backup jobs (grep for successfully wrote) with a backupID which
you can then use bpimmedia (long listing) and identify whether it was a
full, inc or c-inc backup, then extract from bpplist the file list or
bpflist

There are a variety of roads to get to where you want to be.

david

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darren
Dunham
Sent: Tuesday, April 17, 2007 8:55 AM
To: Veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Reporting scripts

> I know things like this have been discussed but I haven't found a way
to 
> get what I want from the command line.  It looks like I need a little 
> bit of output from bpdbjobs -all_columns, using the lastbackup column 
> definition in the bp.conf file, and part of the bpcatlist command.  I 
> have spent considerable time looking on the web and RTFM (several of 
> them).  Here is what I'm trying to get.  If you know of a command that

> gives all of this or have a script that will dig all this up, I would 
> greatly appreciate it.
> 
> Client name, file system or mount point, last successful full date,
last 
> successful incremental date.  I want something like:
> 
> client1,/,04/01/2007 19:20:00, 04/16/2007 20:00:03
> client1,/mnt/data,04/01/2007 19:38:00, 04/16/2007 21:33:00

I don't have anything that does exactly that, but it's close.  I can at
least tell you how I'm getting the data:

Use 'bppllist' to get the list of clients in active policies.

For each of those clients, get a list of images in the time frame of
interest (can limit to full at this stage if you want) with
'bpimagelist'.

For each of those images, use 'bpflist' to get the name of the first
file in the backup.  That's normally the filesystem or directory that is
being backed up.

Sort the ones with the same name by date and report the last one.

'bpdbjobs' would give you the filesystem mapping a bit more directly,
but then you're limited to what's in the jobs list.  If you kept that
and stored it in your own database, that would be easier to manipulate.
I went to the file data because it hangs around longer.

> I'm guessing this is why Aptare and Bocada are in business :-)

Seems to be.  :-)

-- 
Darren Dunham   [EMAIL PROTECTED]
Senior Technical Consultant TAOShttp://www.taos.com/
Got some Dr Pepper?   San Francisco, CA bay area
 < This line left intentionally blank to confuse you. >
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


The information contained in this transmission is 
confidential.  It is intended solely for the use of the 
individual(s) or organization(s) to whom it is addressed.  
Any disclosure, copying, or further distribution is not 
permitted unless such privilege is explicitly granted in 
writing by Quantum Corporation.  Furthermore, Quantum 
Corporation is not responsible for the proper and complete 
transmission of the substance of this communication or for
any delay in its receipt.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Storage Unit Strangeness

2007-04-24 Thread David Chapa
ACS/LS will use whatever it wants.

 

Are all 6 really active?   Is there another application using those
drives somewhere?  ACS/LS may have just left those in the drives...eh,
its been a long time since I rock and rolled with acs

 

What's with the fragment size and the mpx value?

 

:-)

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Greenberg, Katherine (ISD, IT)
Sent: Tuesday, April 24, 2007 9:41 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Storage Unit Strangeness

 

Have a support call open, but find you guys to have seen more than they
have sometimes ;) 

Solaris 9 
NBU 5.1 MP4 Media server 
NBU 5.1 MP6 Master 

The storage unit for media server (the only one for that media server)
is configured to use 3 drives, however the media server has 6 drives in
use...

Label: HOST_STU 
Media Type:Media Manager (2) 
Host Connection:   HOST 
Number of Drives:  3 
On Demand Only:no 
Density:   hcart2 (14) 
Robot Type/Number: ACS (1) / 0 
Max Fragment Size: 2048 
Max MPX/drive: 8 

isdsnh027 (root):/usr/openv/pack#> vmoprcmd 

PENDING REQUESTS 

  

  DRIVE STATUS 

Drv Type   Control  User  Label  RecMID  ExtMID  Ready   Wr.Enbl.
ReqId 
  0 hcart2   ACSroot   Yes   L94844  L94844   Yes Yes
2  
  1 hcart2   ACSroot   Yes   L92802  L92802   Yes Yes
1  
  2 hcart2   ACSroot   Yes   L01203  L01203   Yes Yes
5  
  3 hcart2   ACSroot   Yes   L96625  L96625   Yes Yes
4  
  4 hcart2   ACS- No   -
-   
  5 hcart2   ACS   Yes   L00222  L00222   Yes Yes
-   
  6 hcart2   ACSroot   Yes   L95981  L95981   Yes Yes
3  
  7 hcart2   ACS -No   -
-   
  8 hcart2   ACSroot   Yes   H05037  H05037   Yes Yes
1  
  9 hcart2   ACSroot   Yes   L94986  L94986   Yes Yes
2  
 10 hcart2   ACSroot   Yes   L95971  L95971   Yes Yes
0  
 11 hcart2   ACSroot   Yes   L95991  L95991   Yes Yes
3  

 ADDITIONAL DRIVE STATUS 

Drv DriveNameSharedAssignedComment

  0 HFD_STK3_0_10_06  Yes  HOST 
  1 HFD_STK3_0_10_08  Yes  HOST 
  2 HFD_STK3_0_10_10  Yes  HOST 
  3 HFD_STK3_0_10_11  Yes  HOST 
  4 HFD_STK3_0_10_12  Yes  -

  5 HFD_STK3_0_10_13  Yes  -

  6 HFD_STK3_0_10_14  Yes  HOST 
  7 HFD_STK3_0_10_16  Yes  -

  8 HFD_STK3_0_10_17  Yes  other

  9 HFD_STK3_0_10_18  Yes  other 
 10 HFD_STK3_0_10_07  Yes  HOST 
 11 HFD_STK3_0_10_09  Yes  other 

 

And no commentary on the MPX or Fragment size, I'm slowly digging them
out of their backward ways... 

Anyone seen this??? 

Kate Greenberg 
Enterprise Backup 
Infrastructure Solutions Department 
860.547.8155 
[EMAIL PROTECTED] 




*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution
is
strictly prohibited. If you are not the intended recipient, please
notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.

*



The information contained in this transmission is 
confidential.  It is intended solely for the use of the 
individual(s) or organization(s) to whom it is addressed.  
Any disclosure, copying, or further distribution is not 
permitted unless such privilege is explicitly granted in 
writing by Quantum Corporation.  Furthermore, Quantum 
Corporation is not responsible for the proper and complete 
transmission of the substance of this communication or for
any delay in its receipt.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] NDMP Duplication - 5.1

2006-08-28 Thread David Chapa








I
can’t get my hands on 5.1 documentation right
now…

 

Can
anyone confirm if I can duplicate NDMP images by a media server that
DIDN’T write it originally using the altreadhost
feature of bpduplicate.

 

Thanks

 

David

 

David A.
Chapa | Senior
Technologist of Advanced Solutions | Quantum Corporation | 720.272.8452 cell | http://www.quantum.com 




 
  
  
   


 


   
  
   
 




 

 

 






BEGIN:VCARD
VERSION:2.1
N:Chapa;David
FN:David Chapa
TEL;WORK;VOICE:720 249 5836
TEL;CELL;VOICE:720 272 8452
ADR;WORK:;Englewood;8560 Upland Dr;Englewood;Colorado;80112;UNITED STATES
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Englewood=0D=0A8560 Upland Dr=0D=0AEnglewood, Colorado 80112=0D=0AUNITED STA=
TES
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20060102T165913Z
END:VCARD
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


RE: [Veritas-bu] Does backup data *always* pass through the Master server?

2006-05-03 Thread David Chapa
There used to be a very nice functional overview in Appendix A of the
Troubleshooting Guide...but the docs have been reorganized since then.

But it should be there...

Kate is right - only meta data it sent back to the master server, the
functional overview shows you other process interaction between master
and media which is very helpful.

David Chapa

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greenberg,
Katherine A
Sent: Wednesday, May 03, 2006 6:40 AM
To: Richard Hellier; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Does backup data *always* pass through the
Master server?

No, only META DATA will go to the Master server. Are you using the
MUST_USE_LOCAL_DRIVE directive in bp.conf or setting the policy to only
use the STU for the specific media server?



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard
Hellier
Sent: Wednesday, May 03, 2006 8:31 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Does backup data *always* pass through the Master
server?


Hi -- a question on data 'routing' in NetBackup:

If a machine is a N/B media server and is backing itself up, does the
data 'short-circuit' straight from disks -> tape/whatever or does it
pass across to the master server and then back?

Thanks

Richard.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-
This e-mail may contain confidential or privileged information.  If
you think you have received this
e-mail in error, please advise the sender by reply
e-mail and then delete this e-mail immediately.  Thank you.  Aetna


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


RE: [Veritas-bu] Tuning Netbackup

2006-04-28 Thread David Chapa








You definitely want to look at the bptm
logs to see what is happening and how you should affect your buffers.  See attached document for tuning help.

 

David

 

 

PS. Well I attached the document but it
exceeded the 20K limit J (doug loves it when I do that) so if you’d like the document
let me know and I’ll send it 

 

 

-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ambrose, Monte
Sent: Friday, April 28, 2006 7:04 AM
To: nouresh LEGACY; veritas-bu
Subject: RE: [Veritas-bu] Tuning
Netbackup

 

Nouresh

 

Without analyzing output for buffer waits from your
bptm log - I have found that more buffers generally works better than bigger
buffers.  Try increasing the number of buffers and decrease the size a
little.

 

Perhaps

 

SIZE=65536

NUM=64

 

Or

 

SIZE=131072

 

NUM=32

 

You will notice that they all add up to the same total
but it can make a big difference.   I believe that the first option
above also matches the LTO3 hardware buffer size.

 

Monte













From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of nouresh LEGACY
Sent: Thursday, April 27, 2006
10:46 PM
To: veritas-bu
Subject: [Veritas-bu] Tuning
Netbackup



 

What major changes I'll have to do incase the OS is
Linux. 

The data transfer (throughput) rate is 14mb/sec.
cd /usr/openv/netbackup/logs/bptm
grep -i "KBytes/sec" log.*
transfer rate is 18632.911 Kbytes/sec

Let me explain u abt my setup:
NBU 5.1 MP3
HP StorageWorks MSL 6000
HP Ultrium LTO 3 cartridges

Changes made, but still struggling to get the speed.
/usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS = 256kb
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS = 16

After creating these files, backup was fired at the
speed of 18mb/sec.

Do i have to change any directives in
/etc/sysctl.conf

Cheers,
Nouresh








[Veritas-bu] robtest poll

2006-02-24 Thread David Chapa
Title: Message











Hello
everyone...I’m curious about a robtest command
that has been there as far back as I can remember (version 1.6).

 

Once
you are in robtest the command is “initrange”

 

How
many of you use initrange?  And if you do use it what do you use it for?  

 

Any
Symantec (Veritas) input is welcomed as well.

 

Thanks
very much,

David