IDisaster Recovery failure on one job but not others(Error 111) - Veritas Backup Exec

This is a discussion on IDisaster Recovery failure on one job but not others(Error 111) - Veritas Backup Exec ; I am getting a failure on one of five backup jobs that we run each night that is : Error loading machine specific Intelligent Disaster Recovery information. Error: 111 The file name is too long. The fix for this on ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: IDisaster Recovery failure on one job but not others(Error 111)

  1. IDisaster Recovery failure on one job but not others(Error 111)

    I am getting a failure on one of five backup jobs that we run each night
    that is :

    Error loading machine specific Intelligent Disaster Recovery information.
    Error: 111
    The file name is too long.

    The fix for this on veritas site says that the IDR path in options is in UNC
    format not local drives, every time I correct the path and go back in, it
    converts back to a UNC path?!? Any ideas?

    What is more puzzling though is that the other four jobs run correctly with
    no IDR error?!? (Suggesting that the path is OK)

    Does anyone have any ideas on how to fix this, or have you come accross a
    similar problem before?

    Any help would be appreciated.

    Regards,
    Steve



  2. Re: IDisaster Recovery failure on one job but not others(Error 111)

    It's alright now, I have delete the dr file for the one giving me a problem,
    and the new one was created successfully, without any errors! (Just letting
    you know in case anyone else has this problem!)


    "Steve" wrote in message
    news:3b5ebd94$1@hronntp01....
    > I am getting a failure on one of five backup jobs that we run each night
    > that is :
    >
    > Error loading machine specific Intelligent Disaster Recovery information.
    > Error: 111
    > The file name is too long.
    >
    > The fix for this on veritas site says that the IDR path in options is in

    UNC
    > format not local drives, every time I correct the path and go back in, it
    > converts back to a UNC path?!? Any ideas?
    >
    > What is more puzzling though is that the other four jobs run correctly

    with
    > no IDR error?!? (Suggesting that the path is OK)
    >
    > Does anyone have any ideas on how to fix this, or have you come accross a
    > similar problem before?
    >
    > Any help would be appreciated.
    >
    > Regards,
    > Steve
    >
    >




+ Reply to Thread