Ofmcdm - failed to achieve server wip. Largest wip found = 1 seconds - Veritas Backup Exec

This is a discussion on Ofmcdm - failed to achieve server wip. Largest wip found = 1 seconds - Veritas Backup Exec ; Rodrigo > when i to backup my groupwise > system with the open files option. I wouldn't use OFO to back up GroupWise 6.x - it's not supported, and is exactly why Novell provide GWTSA.NLM If you use GWTSA.NLM, which ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Ofmcdm - failed to achieve server wip. Largest wip found = 1 seconds

  1. Re: Ofmcdm - failed to achieve server wip. Largest wip found = 1seconds

    Rodrigo
    > when i to backup my groupwise
    > system with the open files option.


    I wouldn't use OFO to back up GroupWise 6.x - it's not supported, and
    is exactly why Novell provide GWTSA.NLM
    If you use GWTSA.NLM, which enables you to backup GW6.x while in use,
    you will see a separate GroupWise System to backup - that's what you
    should select. You should then exclude the GW files on the server from
    the normal selections (e.g. if GW is on a MAIL volume, exclude that
    volume from the selections)

    > Ofmcdm - failed to achieve server wip. Largest wip found = 1 seconds
    > Ofmcdm - failed to achieve wip on pool mail. Largest wip found = 1 seconds.


    You could also check free space on your volumes (including purging if
    necessary)

    > NW 6.5 SP1


    BTW, hope that's SP1.1
    (http://support.novell.com/cgi-bin/se...i?/2967905.htm)

    > Backup Exec for NetWare 9.1 Build 1067.2


    Update to 1152.4 - not only does it have a host of fixes, the OFO
    modules are updated too.

    Michael
    --
    "If it jams, force it. If it breaks, you probably
    needed a new one anyway"

    * Please post replies via the newsgroup *

  2. Ofmcdm - failed to achieve server wip. Largest wip found = 1 seconds


    Hi all, im getting the following message, so often, when i to backup my groupwise
    system with the open files option.

    Ofmcdm - failed to achieve server wip. Largest wip found = 1 seconds
    Ofmcdm - failed to achieve wip on pool mail. Largest wip found = 1 seconds.

    And then my backup started with skipping all open files.

    This is my scenario

    NW 6.5 SP1
    Backup Exec for NetWare 9.1 Build 1067.2
    OFO NW option = 9.1.101d

    This is an urgent issue.

    Thks in advance

    Regards

    Rodrigo


  3. Re: Ofmcdm - failed to achieve server wip. Largest wip found = 1


    Ok, Michael. Two things ...
    1 - when you said that OFO its not supported, u said that cause we dont have
    much technical support or its because a kind of compatibility problem between
    GW and OFO.

    2 - Have u any explain or details about more OFO Sync problem ??? I will
    try to update my BE but i wish to know more details about my issue

    Thks for your time

    Regards

    Rodrigo

    Michael wrote:
    >Rodrigo
    >> when i to backup my groupwise
    >> system with the open files option.

    >
    >I wouldn't use OFO to back up GroupWise 6.x - it's not supported, and
    >is exactly why Novell provide GWTSA.NLM
    >If you use GWTSA.NLM, which enables you to backup GW6.x while in use,
    >you will see a separate GroupWise System to backup - that's what you
    >should select. You should then exclude the GW files on the server from
    >the normal selections (e.g. if GW is on a MAIL volume, exclude that
    >volume from the selections)
    >
    >> Ofmcdm - failed to achieve server wip. Largest wip found = 1 seconds
    >> Ofmcdm - failed to achieve wip on pool mail. Largest wip found = 1 seconds.

    >
    >You could also check free space on your volumes (including purging if
    >necessary)
    >
    >> NW 6.5 SP1

    >
    >BTW, hope that's SP1.1
    >(http://support.novell.com/cgi-bin/se...i?/2967905.htm)
    >
    >> Backup Exec for NetWare 9.1 Build 1067.2

    >
    >Update to 1152.4 - not only does it have a host of fixes, the OFO
    >modules are updated too.
    >
    >Michael
    >--
    >"If it jams, force it. If it breaks, you probably
    >needed a new one anyway"
    >
    >* Please post replies via the newsgroup *



  4. Re: Ofmcdm - failed to achieve server wip. Largest wip found = 1

    Rodrigo
    > 1 - when you said that OFO its not supported, u said that cause we dont have
    > much technical support or its because a kind of compatibility problem between
    > GW and OFO.


    GroupWise is basically a big constantly-in-use database. Every time you
    have an open file with OFO, you have to swap a copy of the file into the
    cache file/snapshot generated by OFO. Now, if your database is
    constantly in use, you end up adding files very frequently which reduces
    performance. Doing this, there is an increased opportunity for
    corruption. This is why it's not a supported operation and why Novell
    provided GWTSA.NLM to back up GW while open (if you look at the BE for
    Windows product, there are specialised agents for
    SQL/Exchange/Oracle/etc that don't use OFO...).

    > 2 - Have u any explain or details about more OFO Sync problem ??? I will
    > try to update my BE but i wish to know more details about my issue


    WIP = Write Inactivity Period. This is the amount of time that the disk
    must be "quiet" for (i.e. no disk writes) in order that OFO can
    synchronize the server. So basically your error is meaning that OFO
    cannot synchronize the server because the disk is being written to more
    frequently than your WIP is set to (seems like the longest period
    without a disk write is 1 second).

    Firstly, you *definitely* should update your BE build - these are the
    important TNs just for the OFO components:
    http://seer.support.veritas.com/docs/272222.htm
    http://seer.support.veritas.com/docs/273594.htm
    http://seer.support.veritas.com/docs/272357.htm
    http://seer.support.veritas.com/docs/272085.htm

    Secondly, if still a problem, look at the free & purgeable space on the
    volumes - see if there's some problem being caused there by insufficient
    disk space.

    If you still have a problem after this, post back, and I'll guide you
    through changing the settings (or open a call for VERITAS to do it).

    Michael
    --
    "If it jams, force it. If it breaks, you probably
    needed a new one anyway"

    * Please post replies via the newsgroup *

  5. Re: Ofmcdm - failed to achieve server wip. Largest wip found = 1


    OK, Michael thks for your quick answer. Give me a few days and i will write
    you about the results.

    Regards

    Rodrigo

    Michael wrote:
    >Rodrigo
    >> 1 - when you said that OFO its not supported, u said that cause we dont

    have
    >> much technical support or its because a kind of compatibility problem

    between
    >> GW and OFO.

    >
    >GroupWise is basically a big constantly-in-use database. Every time you


    >have an open file with OFO, you have to swap a copy of the file into the


    >cache file/snapshot generated by OFO. Now, if your database is
    >constantly in use, you end up adding files very frequently which reduces


    >performance. Doing this, there is an increased opportunity for
    >corruption. This is why it's not a supported operation and why Novell
    >provided GWTSA.NLM to back up GW while open (if you look at the BE for
    >Windows product, there are specialised agents for
    >SQL/Exchange/Oracle/etc that don't use OFO...).
    >
    >> 2 - Have u any explain or details about more OFO Sync problem ??? I will
    >> try to update my BE but i wish to know more details about my issue

    >
    >WIP = Write Inactivity Period. This is the amount of time that the disk


    >must be "quiet" for (i.e. no disk writes) in order that OFO can
    >synchronize the server. So basically your error is meaning that OFO
    >cannot synchronize the server because the disk is being written to more


    >frequently than your WIP is set to (seems like the longest period
    >without a disk write is 1 second).
    >
    >Firstly, you *definitely* should update your BE build - these are the
    >important TNs just for the OFO components:
    >http://seer.support.veritas.com/docs/272222.htm
    >http://seer.support.veritas.com/docs/273594.htm
    >http://seer.support.veritas.com/docs/272357.htm
    >http://seer.support.veritas.com/docs/272085.htm
    >
    >Secondly, if still a problem, look at the free & purgeable space on the


    >volumes - see if there's some problem being caused there by insufficient


    >disk space.
    >
    >If you still have a problem after this, post back, and I'll guide you
    >through changing the settings (or open a call for VERITAS to do it).
    >
    >Michael
    >--
    >"If it jams, force it. If it breaks, you probably
    >needed a new one anyway"
    >
    >* Please post replies via the newsgroup *



  6. Re: Ofmcdm - failed to achieve server wip. Largest wip found = 1

    Rodrigo
    > OK, Michael thks for your quick answer.


    No problem :-)

    > Give me a few days and i will write
    > you about the results.


    Ok, just fyi, my access will be a bit limited for the next 4 weeks.

    Michael
    --
    "If it jams, force it. If it breaks, you probably
    needed a new one anyway"

    * Please post replies via the newsgroup *

+ Reply to Thread