General discussion

  • Creator
    Topic
  • #2296862

    Otman4 – veritas

    Locked

    by kn_abhilash ·

    In my Windows nt workstation following system event is logging

    Event Type: Information
    Event Source: Otman4
    Event Category: None
    Event ID: 4
    Date: 12/6/2003
    Time: 9:38:38 PM
    User: N/A
    Computer: STAR-FMDUBBING
    Description:
    The description for Event ID ( 4 ) in Source ( Otman4 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: .
    Data:
    0000: 00 00 18 00 01 00 66 00 ……f.
    0008: 00 00 00 00 04 00 00 60 …….`
    0010: 00 00 00 00 00 00 00 00 ……..
    0018: 00 00 00 00 00 00 00 00 ……..
    0020: 00 00 00 00 00 00 00 00 ……..
    0028: 00 00 00 00 00 a0 0f 00 …..?..
    0030: 00 40 1f 00 00 00 00 00 .@……
    0038: 00 00 00 00 0a 00 00 00 ……..

    In tis machine veritas OFO and Remote agent is running
    and i noticed taht this event is logged when remote backup is running on this mchine

    why it is happening , will it create any problem and whats the solution

All Comments

  • Author
    Replies
    • #2684824

      Reply To: Otman4 – veritas

      by jschein ·

      In reply to Otman4 – veritas

      Device: “Otman4” – Otman4.sys is the driver which is Open File Option (OFO). It is used to make the static volume OFO uses to protect open/changed files. If the file is missing or corrupt, this error could occur. To resolve this error OFO must be reinstalled.

      See Veritas TechNote ID: 239054 link.

    • #2670808

      Reply To: Otman4 – veritas

      by jarrettc ·

      In reply to Otman4 – veritas

      Are you receiving any errors in Veritas that indicate the the OFO failed to work?

      You may want to investigate the recommended size for the OFO Cache on that server (they have a formula for it somewhere in the Veritas Knowledge Base) and alter the OFO Cache size on that server accordingly. The OFO wizard is limited in its ability to alter this cache size so you may have to alter it in the registry.

      As the backup/recover admin at my last job we had major issues with the OFO due to cache sizes and the amount of open files that were being backed up and received many different otman4 errors.

Viewing 1 reply thread