Ayaz.  This is WONDERFUL data.  I've thought a number of times about 
turning this into an automated method of making registry changes on all NT 
clients.

1. Create the veritas.reg file on the master
2. Create a bpstart_notify.update.bat file on the master.
    It would contain the following commands:

regedit /s c:\temp\veritas.reg
del c:\temp\veritas.reg
del <INSTALL_PATH>\bin\bpstart_notify.update.bat

    (regedit <file> will import that file into the registry.  The
    /s flag tells it to be silent, and not open the dialog box when
    it's done.)

3. Create a class called "update" with all your NT clients in it.
    If this were a UNIX server, you could do this easy by saying:
    cd /usr/openv/netbackup/db/class
    grep 'NT' */clients |cut -d: -f2 >update/clients
    Use the default settings for the class. You could put
    C:\config.sys as the file to be backed up, or some other file
    that you know will be there.  It actually doesn't matter what
    you put
4. Push the veritas.reg file to c:\temp and the bpstart_notify file
    to <INSTALL_PATH>\bin on each NT client.  To do this, you could
    either back it up to disk and restore it to every client.
5. Run the update class

And voila!  You've updated the registry on all your NT clients.

Did I leave anything out? Can you think of any goofs?

We might want to build in a sleep between the regedit and the deletes, but 
I don't an NT command to do that.

(I'm thinking about putting this in the FAQ.)

At 11:29 AM 11/28/00 -0600, Ayaz Mudarris wrote:
>On Tue, Nov 28, 2000 at 02:42:46PM +0100, Dave Pearson (EML) wrote:
> > < a good practise for OTM is to change the default config from
> > "fail backup if OTM fails" to "continue without OTM", so if the
> > OTM cache is full, the backup will still continue instead of
> > failing. >
> >
> > Any advice (apart from RTFM) on how to do this?
> >
>  Make a file called veritas.reg with the contents shown below,
>between START and END blocks.
>
>_START_
>Windows Registry Editor Version 5.00
>
>[HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config]
>"OTM_Current"="ALL"
>"OTM_Cache_Size_Init"=dword:00000000
>"OTM_Cache_Size_Max"=dword:00000000
>_END_
>
>And run it on your NT/2k boxes
>
>Here's what they mean:
>
>OTM_Cache_Size_Max      0  (auto adjusting)
>OTM_Cache_Size_Init     0 (auto adjusting)
>OTM_Current = "NO" (Default), "YES," or "ALL."
>YES = Good for "ALL_LOCAL_DRIVES" backups that do not require synchronization.
>NO = Good for "ALL_LOCAL_DRIVES" backups that require synchronization.
>ALL = Use for Multiple Data Stream backups.
>
>--
>Ayaz
>
>#!/a.k.a/jazz
>____________________________________________    _                       _
>                                Ayaz Mudarris   |_| C o l l e c t i v e |_|
>                 Consultant, Great Lakes Team    |_    technologies     _|
>                            ayaz AT colltech DOT com      []                 []
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

---
W. Curtis Preston, Principal Consultant at Collective Technologies
Email: curtis AT colltech DOT com                (Best way to contact me)
Work : 408 452 5555                       (Leave a message.)
Pager: 800 946 4646, pin#1436065        (If urgent.)

Tap into the Collective Intellect (TM): http://www.colltech.com
Backup & Restore resources:        http://www.backupcentral.com