> Thank you for the response Oliver. I, reluctantly, changed the Jumbo
> Frame
> size from 9048 to 4088 on both servers and Backup Exec now works normally.
> Strange that BE would be sensitive at the physical layer. It's as if
> Veritas
> didn't take advantage of a networking API or something during development.
> Stacey
could be. You should contact them though, and identify the issue. It could
be a bug, or they may not have considered using the application in this
environment. They may wish to create a hotfix for you.
Good luck!
Oliver
>
> "Oliver O'Boyle" wrote:
>
>> Probably an unsupported frame size in the Backup Exec application. I
>> would
>> make sure BE can actually use this config before I go any further...
>>
>> Oliver
>>
>> "5tac3" <(E-Mail Removed)> wrote in message
>> news:6DAAE50D-563A-476A-BF90-(E-Mail Removed)...
>> >I have two W2K3 SP1 Std. Ed. servers both with Intel Pro/1000 MT server
>> > adapters. One has E2K3 SP1 Std Ed. with Backup Exec 9.1 SP4a and a
>> > DDS4
>> > tape
>> > backup unit. The other is a DC and a file server with the Remote
>> > Agent.
>> > Before I upped the frame size of both NICS to 9014 bytes on the two
>> > servers,
>> > Backup Exec downloaded and backed up the data from the file server/DC
>> > with
>> > the Remote Agent on it just fine. However, after I upped the frame
>> > size
>> > from
>> > the usual default size (1518 bytes) to 9014 bytes Backup Exec hasn't
>> > been
>> > able to see the file server/DC with the Remote Agent. Both servers can
>> > ping
>> > each other successfully and swap files using UNC and IP successfully.
>> > The
>> > topology is a flat single subnet network. Both servers are plugged
>> > into
>> > an
>> > SMC 8505T switch which supports said frame size. I tried to reinstall
>> > the
>> > Remote Agent by pushing it up from the server that has Backup Exec on
>> > it
>> > but
>> > it can't find the file server/DC. Any ideas?
>> > Stacey
>>
>>
>>
|