If it turns out that you cannot get the cache sized properly because your 
systems don't have the resources (which was my case) you can disable OTM by 
making a change in the Registry. You can follow this sequence:

Regedit
  Hkey_local_Machines
    Software
      Veritas
        Netbackup
          Current Version
            Config

Find entry for OTM_Use and edit value from YES to NO

Regards,
Dennis

Quote: "Time is not a test of the truth"
Translation: Just because you've always done it that way, doesn't make it right

Dennis F. Dwyer
Enterprise Storage Manager
Tampa Electric Company

(813) 225-5181  - Voice
(813) 275-3599  - FAX

Visit our corporate website at www.tecoenergy.com

>>> Charles R Somogyi <charles.somogyi AT bms DOT com> 08/06/01 04:02PM >>>
Mario:

When we saw these errors for our NT clients, it was always
associated with an OTM error. If this is the case at your site,
try adding this param to the registry on the client; you may be
running out of OTM cache space. This happens alot if a system is
very busy during backup.

I know the desrcription says that OTM continues but Veritas has
come back and said that it does not work correctly, so, try
increasing the cache size. (double it if need be)

OTM_Cache_Size_Max = <value>

?  Specifies the maximum cache size (in megabytes) of the cache
file. If the cache file reaches this size and more cache is
required, Open Transaction Manager is turned off and the backup
continues. However, relationships between the backed up files can
be lost because the snapshot is not used. The default maximum
cache size is 50 megabytes. This can also be set this to 0 and
NetBackup will dynamically allocate space.

Charlie Somogyi
BMS
Princeton, NJ


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