If you're running NB 3.2, see
http://seer.support.veritas.com/docs/180017.htm.
For NB 3.4, see http://seer.support.veritas.com/docs/233254.htm.
Here's the Registry settings related to OTM sent to me by Veritas Support:
OTM Settings
Open Transaction Manager Registry Settings
These are located in HKEY_LOCAL_MACHINE - Software - Veritas - Netbackup -
CurrentVersion - Config:
· OTM_USE (if this is not present the default setting is YES and Open
Transaction Manager is enabled)
· Applicable Settings: "NO" = disabled "YES" = enabled
· OTM_Cache_File
· If this is not present the cache file defaults to c:\temp
If this is specified it must be specified down with the full path down to
the FILENAME Data type of Reg_SZ (eg. e:\temp\otm.tmp where otm.tmp is a 0
byte file)
· OTM_Cache_Size_Init
· NetBackup Properties Specifies the initial size of the cache file (in
megabytes). If a specific value is not set, NetBackup sets it to 10
megabytes. If the value is set to 0, NetBackup sets it to 10% of the used
disk space. (Patch 326 or higher should be used for the Initial Cache Size =
0 setting)
· OTM_Cache_Size_Max
· 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.
· OTM_Current
· Applicable settings are:
"YES" = Individual Drive Snapshots
Specifies that Open Transaction Manager take a snapshot of each drive and
back it up before proceeding to the next drive. For example, assume that
drives C and D are being backed up. Here, Open Transaction Manager:
1. Takes a snapshot of drive C, backs it up, and discards the snapshot.
2. Takes a snapshot of drive D, backs it up, and discards the snapshot.
Open Transaction Manager is enabled on only one drive at a time, depending
on which one is being backed up. This mode is useful when it is not
necessary to maintain relationships between files on the different drives.
"NO" = Global Drive Snapshots:
Specifies that Open Transaction Manager take a snapshot that includes all
drives that are part of the backup and then back up the drives. For example,
assume that drives C and D are being backed up. Here, Open Transaction
Manager:
1. Takes a snapshot of C and D.
2. Backs up C and then backs up D.
3. Discards the snapshot.
Open Transaction Manager remains enabled on both the C and the D drives for
the entire duration of the backup. This mode is useful when it is necessary
to maintain the relationships between files on the different drives.
"ALL_AVAILABLE"
Specifies that Open Transaction Manager be enabled on all drives, regardless
of which ones are being backed up. If backing up clients in a class that is
using "Allow Multiple Data Streams", this setting ensures that all the
backups can use Open Transaction Manager. For example, assume the following:
* A client has four drives: C, D, E, and F.
* The class file list contains directives that split the client backup into
two
streams, each of which is an independent backup. Drives C and D are in one
backup and drives E and F are in the other backup.
* The server attempts to start both backups at the same time.
If Individual drive snapshots or Global drive snapshots are selected, the
following occurs:
1. The drive C and D backup starts.
2. NetBackup enables Open Transaction Manager for drives C and D.
3. The drive E and F backup starts. However, NetBackup cannot enable open
transaction management for drives E and F.
When open transaction management is active, another enable attempt
succeeds only if the set of drives are the same as the active set. In this
example, the sets are different.
4. The drive E and F backup continues, but without Open Transaction
Manager.
If "Use all available drives" is selected, the following occurs:
1. The drive C and D backup starts.
2. NetBackup enables Open Transaction Manager for all drives (even
though E and F are not part of the current backup).
3. The drive E and F backup starts.
4. NetBackup enables transaction management for all drives. This attempt
succeeds because the set of drives is the same as the one that is already
using Open Transaction Manager.
5. Both backups use Open Transaction Manager.
· OTM_Exclude:
· The Exclude tab allows you to create and modify the exclude lists on
Microsoft Windows clients. An exclude list names files and folders that you
want to exclude from automatic backups. The Files/Directories box shows the
lists for clients that were selected when the dialog box was opend. If
multiple clients were selected, a scroll bar is present at the bottom of the
list box. Move the bar to display the list for the desired client (only one
list at a time can be modified).
* To add a file or directory to the list that is being displayed, click Add
List
Item.
* To modify a file or directory entry, select it in the list, click Edit
List Item,
and make the change.
* To Delete a file or directory entry, select it in the list and click the
Delete
key.
· OTM_Quiescent_Timeout:
· Busy File Timeout
Specifies the duration (in seconds) of the quiet period that
must occur so the snap can be taken.
. The default is 60 seconds. This a 60 second time period in which the
quiescent_wait must occur.
· OTM_Quiescent_Wait:
· Busy File Wait
Specifies how many seconds to wait for a quiet period to
occur. If this time expires, the backup proceeds but without backing up the
file. The quiet period is a period
of time during which no writes are being performed on the
drives or volumes to be backed up
The default is 5 seconds.
· OTM_Error_Control (Controls how OTM reacts when it encounters an error.)
The default is abort.
· The applicable values are listed below. Data type is Reg_Dword
0 = Abort on Error
1 = Disable OTM
2 = Retry OTM
Regards,
Ken Young
SC Design Systems
South Campus IT
Texas Instruments Inc.
(214) 480-7686
-----Original Message-----
From: Robinson, Gina [mailto:Gina.Robinson AT trw DOT com]
Sent: Tuesday, October 02, 2001 11:12 AM
To: Gopalakrishna_Reddy AT satyam-infoway DOT com;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] system call failed (11)
Are you backing NT or 2000 clients? If so, you need to change the registry
on the client to let OTM determine the amount of cache needed. After you
make the change with regedt32, the client must be rebooted for the changes
to take effect.
regedt32:
hkey_local_machine\software\Veritas\Netbackup\Current Version\Config
OTM_Cache_size_max = 0 (was 64 or 250 depending of OS)
Regards,
Gina Robinson
Unix System Administrator
TRW S&EG e-Enterprise
-----Original Message-----
From: Gopalakrishna_Reddy AT satyam-infoway DOT com
[mailto:Gopalakrishna_Reddy AT satyam-infoway DOT com]
Sent: Monday, October 01, 2001 8:17 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] system call failed (11)
Hi,
The backups for many of my files are failing due to the above reason.
What
could be the problem ? How to resolve this?
Regards
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
