Restore jobs - Veritas Backup Exec

This is a discussion on Restore jobs - Veritas Backup Exec ; I'm able to do backups, but experiencing problems restoring. The restore jobs will start restoring some of the data, but then it will just stop. The 1st of 2 processors in the server will go up to 100% utilization and ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Restore jobs

  1. Restore jobs


    I'm able to do backups, but experiencing problems restoring. The restore jobs will start restoring some of the data, but then it will just stop. The 1st of 2 processors in the server will go up to 100% utilization and the server will continue to function as normal. I tried stopping the job without success, then stopping Backup Exec with Bestop and get the message Besrvr is waiting for job to complete. It will also fail to unload Ndmpd.nlm. This module also seem to be using a large percentage of the processor thread.
    The only way to clear the 100% processor utilization on the 1st processor is to restart the server.

    I'm using version 9.10 Revision 1067 of Backup Exec. Server - Dell PE 2650 2GB RAM Dual Zeon 2.6 Ghz Netware 6 SP5.

  2. Re: Restore jobs

    Clive
    > I'm using version 9.10 Revision 1067 of Backup Exec


    Firstly, update this to the latest build, 1156, from the support
    website. If that doesn't resolve, post back with some more details about
    the restore (overwriting existing files, restoring trustees, amount of
    data, etc...)

    BTW - BE isn't MP aware, so it'll only ever use the 1st processor.

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

    * Please post replies via the newsgroup *

  3. Re: Restore jobs

    I will try that and let you know what happens.

    "Michael" wrote in message
    news:MPG.1d35fc9536d5e9d29897ba@news.support.verit as.com...
    > Clive
    >> I'm using version 9.10 Revision 1067 of Backup Exec

    >
    > Firstly, update this to the latest build, 1156, from the support
    > website. If that doesn't resolve, post back with some more details about
    > the restore (overwriting existing files, restoring trustees, amount of
    > data, etc...)
    >
    > BTW - BE isn't MP aware, so it'll only ever use the 1st processor.
    >
    > Michael
    > --
    > "If it jams, force it. If it breaks, you probably
    > needed a new one anyway"
    >
    > * Please post replies via the newsgroup *




  4. Re: Restore jobs

    Updated Backup Exec 9.1 to build 1156. Still experiencing the same problem. Chose to restore a folder with about 800+ MB of data, redirected to a different location. Backup restored about 300+ MB of restore job before stopping. Also tried renaming folder on server and restoring original folder without redirection. Tried running jobs from our monthend tape as well as our weekend tape. Tried resetting tape drive.

  5. Re: Restore jobs

    Clive
    > Updated Backup Exec 9.1 to build 1156.
    > Still experiencing the same problem.
    > Chose to restore a folder with about 800+ MB of data,
    > redirected to a different location. Backup restored
    > about 300+ MB of restore job before stopping. Also
    > tried renaming folder on server and restoring original
    > folder without redirection. Tried running jobs from
    > our monthend tape as well as our weekend tape.
    > Tried resetting tape drive.


    What's the TSAFS.NLM version & date?

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

    * Please post replies via the newsgroup *

  6. Re: Restore jobs

    In article ,
    Michael wrote:
    > BTW - BE isn't MP aware, so it'll only ever use the 1st processor.


    And toward that end, if hyperthreading is enabled, any task NetWare
    might offload to the second physical processor could well end up on the
    second logical processor, which is physical processor 1. Best to
    disable hyperthreading.

    -Barry.




+ Reply to Thread