• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 938
  • Last Modified:

Data Protection Manager 2012

Hi, we are currently using Symantec BackupExec 2010 and 2012 to backup about two dozen application (Exchange 2007, Oracle, SQL, etc) and file servers and a few Windows 7 systems. The majority of the servers are running various versions of 2008 and there is one 2003 server. We own System Center 2012 and I'm trying to get it up and running and I'm having some issues. Currently I have DPM installed on a 2008 R2 virtualized server. I would like the storage location to be on two NAS systems. I have no physical connection to the NAS ... currently with the BUE software they backup over the network. Do I have to create a physical connection to the NAS(s) ... i've read some postings about fibre channel or iscsi, but the servers (Dell PowerEdgeR710) nor the NAS (Thecus N8900) have these external connectors. In the DPM software when I click on "Add" to add a storage device, it comes up blank.  Questions:

Can DPM Administrator Console (looks like this is where I tell the system what servers are to be backed up and what folders, etc) work on a virtualized computer?

How do I get the DPM to see the NAS so I can use its storage space?

Am I better off sticking with BUE?

Thanks :-)
0
OGDITAdmin
Asked:
OGDITAdmin
  • 2
1 Solution
 
BembiCEOCommented:
1.) Yes, DPM can run on a virtual machine. Just be aware, that DMP may produce heavy network traffic. But as virtual machines have usually a virtual 10 GB network device, should be not the problem.

2.) DPM uses disk or tapes as bakup devices and creates partitions for each protection group / protection element. You can either give DPM a physical disk, i.e. by the virtualisation hoste or you can use iSCSI as well as Fibre Channel connections. Even you can mix the devices. But in a way, DPM has to be able to see them.

I run DPM with virtual assigned disks via the virtualisation host, local disk exposed via Microsoft iSCSI target as well as a tape device, exposed by Starwind tape to iSCSI software.
On the DPM the iSCSI Initiator is configured to grab the devices vis iSCSI together.
The DPM sees than like local disks.

The Microsoft iSCSI target jsut creates a virtual disc (vhd) on a local accessable device and exposes it as iSCSI device.
The Solarwind software (free) uses a local tape device on a physical machine and exposes it as sSCSI device.

So, if at least one machine can access the NAS as a disc and can create a vhd on it, you can expose it via iSCSI to DPM. If DPM can access the device directy and acces sit as disc, you can unse it directly.
0
 
OGDITAdminAuthor Commented:
Hi Bembi, I'm assuming the iSCSI is an actual physical connection between the Host and the NAS or is it some kind of virtual thing using the LAN ... sorry, no knowledge of the iSCSI ... although I had tons of experience with the old SCSI back in the day.
0
 
BembiCEOCommented:
iScsi is a bit different.
There a two parts.
The iSCSI target, which can be either a device, which exposes itsself as a iSCSI device, or you can create a kind of virtual iSCSI devices via Microsoft iSCSI target software, which you can download from Microsoft. The last one just exposes a virtual disc, which is created on the exposing machine on a device, where the local machine can create vhds local device. The device is exposed via a IQN Name.
Tee iScsi initiator is a built in feature of microsoft server. You just have to activate it and then you can grab the iSCSI device by the IQN name. It shows up on this machine like a local disk.
If your NAS supports iSCSI, you just need the IQN name, which is configured on the NAS. If it doesn't support iSCSI, you can use the MS iSCSI target software to expore it from a machine, which can see the NAS device as a disc.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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