Even on 3.4, there should be a registry setting you can disable OTM
with. Look under Hkey_Local_Machine/software/veritas/netbackup/current
version for a key called OTM_USE, you can set it to no. You'd have to
set it to be off, then use the reporting in the gui to see what files
were missed and decide if they were essential. 
What 4.5 has that is nice is that you can set it through the client
config on the admin console to use individual drive snapshots and retry
on error per client. This has helped me avoid a lot of problems. There
might be a setting in the registry to do this also, I just don't know
what it is. 
Bob Grabbe
Dominos Pizza LLC
grabbeb AT dominos DOT com


>>> "Nash, Ebon" <Ebon_Nash AT compuware DOT com> 2/20/03 10:54:38 AM >>>
I would recommend either increasing the size of the system drive, which
is
most likely your C: drive.  If that is not possible, I believe there is
a
way to tell NetBackup to write OTM files to a different location
(anything
other than c:).  I believe their web site has information on how to do
this.
One other thing you can try is disabling OTM to see if that fixes the
problem.  That should be documented on Veritas' web site as well.


Ebon Nash
Compuware Corp.

-----Original Message-----
From: Weber, Philip [mailto:Philip.Weber AT egg DOT com] 
Sent: Thursday, February 20, 2003 6:17 AM
To: veritas-bu AT mailman.eng.auburn DOT edu 
Subject: [Veritas-bu] NT OTM Questions


Dear all,

We are experiencing system problems with a large NT4 fileserver (500
Gb
storage, 2 * P3 Xeon 550, 512 Gb RAM), the system has been found
hanging the
last three mornings & had to be cold restarted.  We are running
Netbackup
3.4 patch level 3 on the Solaris servers & patch level 1 on the NT
clients.

Fingers are being pointed at OTM (because yesterday when the problem
occurred the winnt system drive was found to have filled up, & an old
OTM
cache file was found on it).

I have seen on this list that other people have had issues with OTM.  I
know
it is a pain to configure and doesn't seem to work very well, can it
cause
system problems?

I have also seen that people have turned OTM off.  What are the effects
of
this - I would assume that all open files would therefore not be backed
up
and we would get lots of 1 return codes.

When OTM is working correctly I does it create cache files & delete
after
use?  Can it create multiple?  Why would it leave them lying around?

Any help appreciated ... thanks, Phil

Phil Weber
Egg Distributed Hosts - UNIX Systems Engineer
Phone: 01384 26 4136
Mobile: 


-----Original Message-----
From: Liddle, Stuart [mailto:liddles AT amgen DOT com] 
Sent: 19 February 2003 22:48
To: veritas-bu AT mailman.eng.auburn DOT edu 
Subject: [Veritas-bu] Catalog backup question (NetBackup Datacenter
3.4
UNIX)


I need a way to find out how much data is actually being written to
our
catalog tape.  I used the following:

bpbackupdb -v

and looked at the /usr/openv/netbackup/logs/admin/log.<date> file

It did not have the total number of bytes written to the tape anywhere
in
the output.  I'd like to know how close I'm getting to filling my
catalog
tape.

Is there an easy way to determine this information, or do I have to
just
guess that since the data in the 

/usr/openv/netbackup/db 

directory is mostly text that it will get at least a 2:1 compression
(probably closer to 4:1) and use that as a guide for how much will fit
on my
DLT7000 tapes?  Since the hardware compression will get about 70GB of
compressed data on a tape, what's the realistic amount to expect that
will
fit on the tape?  Would I have to worry if my db directory is about
50GB?
100GB?

thanks,

--stuart
_________________________
Stuart W. Liddle
Amgen Corp.
liddles AT amgen DOT com 


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 


This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
carries out investment business on behalf of Egg and is regulated
by the Financial Services Authority.  
Registered in England and Wales. Registered offices: 1 Waterhouse
Square,
138-142 Holborn, London EC1N 2NA.
If you are not the intended recipient of this e-mail and have
received it in error, please notify the sender by replying with
'received in error' as the subject and then delete it from your
mailbox.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 



The contents of this e-mail are intended for the named addressee only.
It
contains information that may be confidential. Unless you are the
named
addressee or an authorized designee, you may not copy or use it, or
disclose
it to anyone else. If you received it in error please notify us
immediately
and then destroy it. 

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu