Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

BE2012 connecting to SAN via vray

Created: 02 Apr 2013 • Updated: 04 Apr 2013 | 9 comments
This issue has been solved. See solution.

Hi,

I've got an EMC VNX SAN, Cisco Nexus core and an IBM 3650 dedicated server for BE2012 with all roles installed. I've got a Dell PVT4000 with 2 x LTO4 drives directly attached via SAS. The 3650 has 9Tb internal storage which is going to be for dedupe and a small amount of D2D.

The server is connected to the Nexus via FCoE and the SAN is conencted to the Nexus via FC. The network is administered by a 3rd party.

We're using VMware 5.0, a 4 host cluster in location A and a 2 host cluster in location B. We have a vCentre server at each location. At the moment I've only done tests using location A.

 

I'm after some advise on how best to configure the network to get the most out of it. At present when I perform a backup it appears to transfer via the vCentre server and the transfer speeds are slow, even if backing up to the local disk on the BE server.  The BE server is dual FCoE teamed and my network admin has apparently coinfigured the Nexus correctly. I have configured a vlan for normal network access to our server vlan and that works fine.

This is the first time I've done this so feel free to keep it real basic :) and we'll move up from there.

Thank you in advance,

Stu

Operating Systems:

Comments 9 CommentsJump to latest comment

CraigV's picture

Hi Stu,

 

You're looking at SAN SSO, and probably CASO which ships with the Enterprise Server Option license for BE 2012. Start by checking the 2 links below:

http://www.symantec.com/business/support/index?pag...

http://www.emea.symantec.com/beguide/en/options/st...

From there you move onto configuring the job to use SAN Transport Mode...

http://www.symantec.com/business/support/index?pag...

Give them all a read and post back here...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Colin Weaver's picture

Not exactly sure how SSO helps with SAN transport backups, which are purely to do with the VMware Agent (AVVI) and do not require an SSO license to use. CraigV's 3rd link does explain SAN Transport however so is useful. 

As there are two sites involved I guess a CASO setup might be applicable.

CraigV's picture

You're absolutely right on the SAN SSO, thanks Colin for clarifying!

 

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Stu B's picture

Thank you CraigV for the links and Colin for the clarification.  At the present I'm not worried about the second site.

 

Some question's about it if I may..

 

  • Zone the LUN’s containing the VMFS datastore so the Backup Exec 2010 or Backup Exec 2012 server can see and access them.

With regards to the zoning, This needs to be done on the SAN itself? Does anyone have any experience on an  EMC SAN? I've spoken to EMC and they've told me to add the BE server as a host so that permission can be given for the required LUNs, I just want to confirm this is good and that I'm not going to break anything.

  • LUNs should show as "unknown volumes" in disk manager on BE server.

If I open up disk management in Server manager on the server I get a pop up saying that these disks need to be initialised, is this the right stage? At the moment I'm clicking cancel and they're unknown disks with a state of not initialised.  I'm very conscious of breaking the LUN's in some way. 

 

You may ask why I'm worried about the first point if I'm at the second stage.  If I've got the disk presented to the BE server than the zoning must be right.  Unfortunately I don't know where or what these disks are.  We do have an old SAN we use for testing and developement and they may be from this SAN but 8 disks are being presented but the old SAN has 7 luns and the new one has about 30.

 

Thank you for all your help, its much appreciated.

 

Stu

Stu B's picture

Just doing some more research, it appears that the zone is created on the network switch, with the WWN of the HBA added to the list which allows all the devices to communicate.  Once this is done the list of hosts on the EMC will be automatically updated.

Would this sound right?

Stu

Stu B's picture

Ok, so with help from EMC i've confirmed that the zoning on the switch is correct that that both SAN's can see the BE server. Tomorrow i'll be setting permission's on the SAN which will hopefully present the LUN's to the server.

Next step will be configuring them on the server. What stage should I stop at in terms of mounting the drives. At the moment they show as Unknown / Not Initialized, is that where they need to be? Or do I need to initilize them? MBT? GPT?

Regards

Stu

CraigV's picture

Hi,

 

NEVER initialize those drives. If you do, your VMs are overwritten giving you worse problems! Automount should be disabled...that should be in the last link I posted.

THanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Stu B's picture

Ok, so leaving them as unknown and uninitialised is all the BE requires?

Stu

CraigV's picture

Yes...with automount disabled no signature is written by Windows to the volume. This also means you should make note that people shouldn't try initializaing the disk...put in strict security or a logon message for instance!

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

SOLUTION