[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 415
  • Last Modified:

Backupexec v10 r2 backup path on blade with sas

Would like to know the backup path, for a group of blades take to a tape drive connected to the blade chassis through sas. It also has a network cable, which I am assuming is for management.

Please advice how data from the blades will travel to the tape drive ibm ts3100.

Thanks.
0
Toshky
Asked:
Toshky
  • 2
  • 2
1 Solution
 
andyalderSaggar makers bottom knockerCommented:
What blades/enclosure are you using?
0
 
ToshkyAuthor Commented:
IBM Blade Center H series using H22 blades
0
 
andyalderSaggar makers bottom knockerCommented:
SAS CIOv are added to blades, SAS connectivity module is added to bay 3 and the tape connected to that. http://www.redbooks.ibm.com/abstracts/tips0701.html does not mention tape though. (http://publib.boulder.ibm.com/infocenter/bladectr/documentation/index.jsp?topic=/com.ibm.bladecenter.hs22.doc/dw1iv_r_tape_alert_flags.html mentions tape though so may be supported)

As far as Backup Exec is concerned it's quite expensive, you need BE server license for each blade that connects to the library, Shared Storage Option for each to stop them fighting over who owns the library, and generally Central Admin Server Option as well to manage it.  You may be able to partition the library into multiple logical libraries instead.

Generally cheaper to have an external server as a backup server, install an agent on each blade and possibly add extra LAN connectivity to the blades/enclosure.
0
 
ToshkyAuthor Commented:
Made me understand the concepts...thanks..
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now