Scheduled jobs get stuck "loading media" - Veritas Backup Exec

This is a discussion on Scheduled jobs get stuck "loading media" - Veritas Backup Exec ; BackupExec NT, V 8.5 Backup jobs scheduled to run at night always get stuck on "loading media". Veritas' Knowledge Base says it's creating a volume, but 84 hours later, and the backup hasn't even started yet. Here is a quote ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Scheduled jobs get stuck "loading media"

  1. Scheduled jobs get stuck "loading media"

    BackupExec NT, V 8.5

    Backup jobs scheduled to run at night always get stuck on "loading media".
    Veritas' Knowledge Base says it's creating a volume, but 84 hours later, and
    the backup hasn't even started yet.

    Here is a quote from their techdoc:

    " The larger the files are that are contained in the OFO backup operation
    and the larger the drive that is being backed up, the longer this initial
    "loading" time will be.

    Is there some way that the OFO can be configured to minimize the amount of
    time required to set up this "static volume" that they refer to? The only
    solution we've been able to find is to turn off OFO.

    Thanks.


    Rob Pelletier



  2. Re: Scheduled jobs get stuck "loading media"

    Rob, I recently dealt with this message.

    In my case the tape capacity was smaller that the files I wanted to backup.
    If this is your case you can put another tape into the machine and it should
    continue to run.

    HTH,
    Danny Ayo

    "Rob Pelletier" wrote in message
    news:3d986171@hronntp01....
    > BackupExec NT, V 8.5
    >
    > Backup jobs scheduled to run at night always get stuck on "loading media".
    > Veritas' Knowledge Base says it's creating a volume, but 84 hours later,

    and
    > the backup hasn't even started yet.
    >
    > Here is a quote from their techdoc:
    >
    > " The larger the files are that are contained in the OFO backup operation
    > and the larger the drive that is being backed up, the longer this initial
    > "loading" time will be.
    >
    > Is there some way that the OFO can be configured to minimize the amount of
    > time required to set up this "static volume" that they refer to? The only
    > solution we've been able to find is to turn off OFO.
    >
    > Thanks.
    >
    >
    > Rob Pelletier
    >
    >




  3. Re: Scheduled jobs get stuck "loading media"

    The tape hasn't even mounted yet. I'm not sure I understand how the
    software even knows the tape is too small, when it hasn't even started
    putting data on it yet...

    Also, in a past run-in with the same problem, I merely disabled Open File
    Option and the back worked fine. This is not an acceptable solution, but it
    got us going. Tape must be large enough, though, as it's been working fine
    ever since.

    Thanks for your reply.


    Rob Pelletier
    London, Ontario




    "Danny Ayo" wrote in message
    news:3d9876bf$1@hronntp01....
    > Rob, I recently dealt with this message.
    >
    > In my case the tape capacity was smaller that the files I wanted to

    backup.
    > If this is your case you can put another tape into the machine and it

    should
    > continue to run.
    >
    > HTH,
    > Danny Ayo
    >
    > "Rob Pelletier" wrote in message
    > news:3d986171@hronntp01....
    > > BackupExec NT, V 8.5
    > >
    > > Backup jobs scheduled to run at night always get stuck on "loading

    media".
    > > Veritas' Knowledge Base says it's creating a volume, but 84 hours later,

    > and
    > > the backup hasn't even started yet.
    > >
    > > Here is a quote from their techdoc:
    > >
    > > " The larger the files are that are contained in the OFO backup

    operation
    > > and the larger the drive that is being backed up, the longer this

    initial
    > > "loading" time will be.
    > >
    > > Is there some way that the OFO can be configured to minimize the amount

    of
    > > time required to set up this "static volume" that they refer to? The

    only
    > > solution we've been able to find is to turn off OFO.
    > >
    > > Thanks.
    > >
    > >
    > > Rob Pelletier
    > >
    > >

    >
    >




+ Reply to Thread