Backup directly from SAN to Tape using backup exec 15?

Does this device support CIFS or iSCSI ? If yes, then BE should be able to back it up, however the data will not go directly from the device to the tape drive but rather from the device to the BE media server and then to tape.

Please see this blogs for options of using SAN with Backup Exec - note this is just conceptual and therefore covers multiple versions of Backup Exec

http://www.symantec.com/connect/blogs/lan-free-including-san-backup-configurations-backup-exec

...sounds like it might be a zoning issue and mapping LUNs would refer to FC or iSCSI. Check your zoning. If this is a LUN specifically for backups and it contains NO data, then make sure you configured it correctly in Windows.

Thanks!

Hi VJware,

This device supports CIFS.

- Only BE 15 can do or both BE 15 and BE 2010 can do?

- Why can't the backup server see the mapped LUN? Does it need LAN backup feature license?

Thank VJware so much.

If you make the server that use the LUN into a Backup Exec Server and attach the tape library to the back of the same server then this will achieve SAN based backups.

As this is a devcie that does not support NDMP unless it is also a VMware datastore as I don't think the device supports ADBO either this will be your only option

CIFS is not a SAN backup and in fact if using CIFS, this means it is configured as a NAS device and not a SAN device and then your use of the term MAP means attaching a windows drive letter to \\device\share and yes Backup Exec cannot backup via the mapped drive letter as the drive letter is a user level record and Backup Exec operates at a service level (so that it can run when no user is logged in) You can however configure to backup directly from \\device\share

Thank CraigV,

I mean Symantec cannot see the LUN which mapped from SAN to backup server.

Thank Colin,

i am using first case: SAN backup. SAN---------Server----------TAPE.

LUN is mapped to server.

Why this Symantec cannot see this LUN? How should i configure?

Thank Colin,

i am using first case: SAN backup. SAN---------Server----------TAPE.

LUN is mapped to server.

Why this Symantec cannot see this LUN? How should i configure?

LUN needs to be zoned or attached directly to Backup Exec server and not to another server

Tape Library also needs to be zoned or attached to Backup Exec srever

Data then moves across SAN from LUN to Backup Exec server and then back across SAN to tape library.

If LUN is attached/zoned to a different server (because the data inside the LUN is managed and owned by that server) then you will have to make this server into the Backup Exec server and attach the tape library to this server.

Please read the blog I linked ealier as it explains all the scenarios and it is possible you currently have a configuration that cannot do any of the SAN based scenarios - if this is the case then there is nothing we can do until you change your environmental configuration (which might involve investment in specific hardware or extra software )

Thank Colin very much,

Yes, i mean this LUN is mapped to Symantec BE server.