Go Premium for a chance to win a PS4. Enter to Win

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

Backup - to - Disk -> SAN

Good morning.  I've been using BE for years but this is definatly a stumper.  This might be a long post, but I want to make sure I give all the information for troubleshooting.

------- Equipment --------
Windows 2003 Server w/SP2
  ** BE12 w/sp1 loaded **
  ** Windows Services for Unix 3.5 **

Sun StorageTek 2510 w/1.2TB
  ** 500GB Partition set aside for B2D **

SunFire 4550 Server
  ** NFS mount point for the SAN unit above **
 ---------------------------

Since my last powersurge and unable to recover my tapes, I've been tooling around with the idea of not only continuing to backup my servers to tapes, but also to have a 'hot' backup (redundency) on the SAN unit mentioned above.  For testing purposes I partitioned 500GBs on the SAN unit and NFS mounted it through the SunFire server (the SAN is a iSCSI device and the SunFire is it's 'host').  I then loaded Windows Services for Unix 3.5 and configured the Windows server as a NFS client.  I have been able to mount / unmount / copy and delete files off the SAN partition without a problem.  When mounting the drive in windows, it shows up as a shared drive ( Z:\ ).  Now here's the kicker.

Going into the Devices -> B2D wizard -> creating a new folder path , when I type in the path to the NFS mount (ex: \\10.0.0.1\b2d) I get a "Unable to create new backup folder.  Access denied".  The weird thing is that this NFS mount properties allows 'guests' with RWX permissions.  To verify the error, I disconnected the drive ( Z:\ ), reconnected and copied a file via windows explorer without any problems.  I've tried mapping the drive in the B2D wizard with and without the Z:\ drive mounted to windows.  I'm able to see all my physical hard drives in the wizard, but no network drives show up.  I'd really like to use my SAN unit as it was designed to be and not just a huge paperweight.  I've always been under the impression that BE can utilize SANs.  Any ideas or suggestions would be greatly appreciated.  Thanks...
0
D00Dness
Asked:
D00Dness
  • 3
  • 2
1 Solution
 
honmapogCommented:
First of all, if the SAN is an iSCSI device, can't you just load the iSCSI initiator on your Windows server and use iSCSI to access the drive. I believe it would make things a lot easier and performant than the SFU/NFS combination. iSCSI would make the volume a local volume and you shouldn't have any problems accessing it.

To avoid the access denied error, make sure that the Backup Exec service account has access to the NFS share.
0
 
D00DnessAuthor Commented:
Thanks for the reply.  I can do that but I've already setup the initiators / host on the SunFire (SUSE Linux).  I was going to use the remaining 1TB for my Linux users for NFS shares.  Not sure if I use the Windows box as the host, I can still share out the remaining TB for NFS shares.

0
 
honmapogCommented:
I assumed you could create two separate volumes on the SAN and have each of them used for a different iSCSI initiator. But I don't know the StorageTek, so I could be wrong.
0
 
D00DnessAuthor Commented:
Well since I only had 1 large volume on there, I decided to blow it away and go with your suggestion.  I dloaded the MS iSCSI Initiator software, created 2 volumes on the SAN and now I'm formatting the F: drive.  Lets hope this works!!
0
 
honmapogCommented:
One suggestion. When you create the B2D folder on the F: drive, make sure to enable the B2D option to "Allocate the maximum size for backup-to-disk files". This will reduce fragmentation.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

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