WAN and Fiber backupjob setup, but how? 1

[geirendre]

Hi
I'm new in this job that includes maintaining a Server running BE8.6
backing up both external servers via WAN and local servers via FC-AL fiber-loop.
But I can't find anywhere how it's defined that a backupjob
for a local server should use the fiber-loop, while a remote
backupjob should use the ethernet (to get out on the WAN).
My (our) problem is that sometimes, (or always, I'm not sure
to be honest,) the local backup jobs use the ethernet (LAN)
insted of the FC-AL to send the data.
This saturates our LAN with backuptraffic and retransmissions
and all the problems that follows with such things.
I can't find anything in the BE docs about defining what medium
the job should use.
Can anybody help a newbie out on this?

Thanks.

 

[geirendre]

Realy nobody that knows???
Any hints or suggestions?

 

[steveot]

Well your not really giving us much to work with.
A few things (Backup Exec 8.6) is no loger supported. It EOL was a few years back. It doesnt support Windows 2003 server, SQL 2005, etc.

The media server will only backup over fiber if the fiber resource is presented lccally to the media server. Meaning you have a drive on media server out to a san resource. If you want true SAN backups at your location then (ssuming you have a fiber attached library) then you need a full copy of backup exec on each server with SSO license option. Example (FileServerA, FileServerB, SQLServerA). Installed a Full copy of Backup Exec on each. Setup jobs on each server. They would share the fiber attached library that is presented to all three servers. With Backup Exec add the CASO option so you dont have to logon to 3 console everyday to monitor the jobs.

 

[geirendre]

Thanks for responding steveot
Yes I know it have been EOL a long time, but our management
is planning a sentralised backupsolution in a year or two
and don't want to upgrade something they think works OK.

So BE needs to run on each server we want to backup.
Today we have a dedicated BE-server (only runs BE8.6 nothing else).

Somebody suggested that we could "share" the drives on the other
server to the BE-server, so it would see them as "local" drives, through the SAN.
They should then apair as drive F: G: H: etc. on our dedicated BackUpserver,
and then the BEserver could access them over the fiber-loop.
Does this make any sence?
(not to me ;-) )

 

[steveot]

Yes that would work. You would create local drives on media server to point to SAN resources.

Example you have FileServerA that has a D: drive that is a SAN drive to some storage space on the sane. On the media server you could present this as Q: drive. Then backup the Q: drive which is now local to media server.
Then it would be a fiber backup. Anything in BEWS once you select remote selection its going to be a network backup.
Backup Exec will not backup shares or mapped drive. So dont get confused that you create a share or map a drive Q: to fileservera D: drive. Backup Exec will not backup mapped drive. In my statement above im referring to zoning out the san volumes.