One remedy that does work (but not all the time) is an adjustment to one of
the OTM settings (refers to NT/200 clients only).
OTM (Open Transaction Manager) is a program used by NetBackup to back up
files, applications and databases that are open or active. OTM works by
taking snapshots of the data on drives containing files to be backed up.
NetBackup then backs up these files as they were at the time of the
snapshot. The snapshots are maintained/kept up to date by using a cache, due
to the fact that the status of a file may change during the course of a
backup.
When this error occurs, and it is associated to OTM, then the Max size of
the OTM cache file needs to be adjusted. This can be done as follows:
connect to client machine, and carryout the following steps:
Start => Run => regedit => HKEY_LOCAL_MACHINE => SOFTWARE => Veritas =>
NetBackup => CurrentVersion => Config
Once here double-click OTM_CACHE_SIZE_MAX, in window that appears, place dot
in Decimal, and delete the decimal value and replace it 0.
What this will do is set the max cache size to 0 MB, therefore when a
schedule is started it NetBackup will automatically determine a suitable
value.
OTM problems can also occur if there is not enough disk space on the
partition where NetBackup is installed. If this is the case then space needs
to be made available to enable the cache files to be created.
Alternatively you can set OTM use to No by going back into regedit and the
same location as above and setting the OTM_Use feature to NO
This will stop OTM completely which should resolve your problem.
Regards,
Steve.
-----Original Message-----
From: Suzanne Palmer [mailto:s.palmer AT umassp DOT edu]
Sent: 04 September 2003 21:28
To: Veritas-Bu
Subject: [Veritas-bu] OTM error and System Call Fail
Been wrestling with this for a while, and not getting any closer to a
solution. I've got a system where I'm getting a ton of error 11:
system call failed which is immediately preceeded by an OTM Error:
09/04/03 9:54:09 AM: [1284]: INF - tar message received from
dos_backup::V_OTM_CheckError
09/04/03 9:54:09 AM: [1284]: ERR - OTM Error:0xe0001005 (WIN32
-536866811: Unknown error)
09/04/03 9:54:12 AM: [1284]: INF - OTM Destroy - destroyed snapshot
09/04/03 9:54:12 AM: [1284]: INF - tar message received from
dos_backup::tfs_readdata
09/04/03 9:54:12 AM: [1284]: ERR - OTM Error while reading file:
E:\foobar\3argumentationwk12.htm
09/04/03 9:54:12 AM: [1284]: FIL - 0 140901 14435700 56 33216 root
root 5339 1060363332 1030730670 1060363332
/E/foobar/3argumentationwk12.htm
09/04/03 9:54:12 AM: [1284]: INF - tar message received from
tar_backup::backup_nextfile_state
09/04/03 9:54:12 AM: [1284]: FTL - Backup operation aborted!
09/04/03 9:54:12 AM: [1284]: INF - Client completed sending data for
backup
09/04/03 9:54:12 AM: [1284]: INF - EXIT STATUS 11: system call failed
My server is Datacenter 3.4 running on Solaris 8. My client is Win2k.
I did some research, and there's various suggestions about setting the
OTM to 0, but I don't see anywhere on the client gui to set that, and
if possible I'd rather only tinker with the single machine. Nor do I
see anywhere on the server gui...
If anyone knows how to set this, or alternately, what other steps
would address my problem above, I'd greatly appreciate it...
Thanks in advance,
-Suzanne
--
Suzanne Palmer - Unix System Administrator
University of Massachusetts President's Office
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
