Imaging a scenario in which DPM 2010 needs to share a Tape Library or a Virtual Tape library among 2 or more DPM servers.
Please Note that In order to have a shared tape library, the tape library must be in a storage area network (SAN) environment . After installation on DPM bits over the 2 DPM servers, there are additional steps required to successfully share both Tape Libraries.
The DPM Library Server is the server that has the medium changer enabled in this case SCDPMSVR01
The DPM Client Library Server is the server with the medium changer disabled, in this case SCDPMSVR02
DPM Library Server Device Manager
DPM Client Library Server Device Manager the Medium Changer must be disabled:
It is important to notice that during the installation of DPM 2010 using a local SQL Server Installation, we are asked the password of the account DPMR$%ComputerName%. This account will be granted the required permissions to generate Reports and this configuration will be changed afterwards.
This account is added to the group DPMDBReaders$%ComputerName% and SQLServerMSSQLUser$%ComputerName%$MSDPM2010 created during the installation.
Configuring the Tape Libraries
In order to share the Tape Libraries it is necessary that both DPM Servers are able to see the Libraries so you will need to do a Rescan on both DPM servers:
Once the rescan finishes you will likely see that the physical library is correctly mapped but the Virtual Tape Library is shown as a Stand-alone Drive:
To get the correct drive mapping we need to use the template LADriveMappingTemplate.xml typically located at C:\Program Files\Microsoft DPM\DPM\Config\LADriveMappingTemplate.xml
Next, stop the dpml service, (open an elevated command prompt and type net stop dpmla ) and create a new file and name it: DPMLA.xml , map the drives using the serial numbers, SCSIPort, SCSBus, SCSITargetID, SCSILun and DriveBayIndex.
Start the dpmla service (open an elevated command prompt and type net start dpmla ) you should now see the drive information correctly configured in DPM 2010 Administrator Console:
Now we are ready to start sharing the tape Library.
On the DPM Server that will host the DPM Library Server execute the following command from the Setup directory:
AddLibraryServerForDPM.exe –ShareLibraryWithDPM <DPMClientServerName>
On the DPM Client Library Server execute the following 3 commands from the Setup directory:
AddLibraryServerForDPM.exe –DpmServerWithLibrary <DPMLibraryServerName>
SetSharedDpmDatabase.exe –InstanceName <DPMLibraryServerName> \msdpm2010:
Set-DPMGlobalProperty –DPMServerName <DPMClientServerName> – LibraryRefreshInterval 5 ( where 5 represent the refresh interval in minutes, the minimum value is 5 ):
Configuring Reports for Shared Libraries
You will notice that if you run a report on the Client Library Server you will receive the following error on 2 reports, Tape Management & Tape Utilization
An error occurred during client rendering.
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DLS'. (rsErrorOpeningConnection)
Or
An error occurred during client rendering.
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'OnlineTapes'. (rsErrorExecutingCommand)
Named Pipes Provider: Could not open a connection to SQL Server [1326].
You will need to go to your Report Manager URL:
Go to Reports, go to DPMReports, then DPMReporterDataSource:
You will notice that the account configured to run this report is the local account DPM created during Setup; however this account will not be able to execute the tape related reports once you have Shared the Library:
You will have to change it to another account and add it to the proper DPM groups:
DPMDBReaders$DPMMACHINENAME
Please Note that you might receive the following error
An error occurred during client rendering.
An error has occurred during report processing. (rsProcessingAborted)
Cannot impersonate user for data source 'DLS'. (rsErrorImpersonatingUser)
Log on failed. (rsLogonFailed)
Logon failure: the user has not been granted the requested logon type at this computer. (Exception from HRESULT: 0x80070569)
Logon failure (0x80070569): The user has not been granted the requested logon type at this computer.
If this happens, you should add the user to the “ Allow logon locally” policy on the server.
Type Gpedit.msc go to Windows Settings, Security Settings, User Rights Assignment
You should now see all the reports without any issues:
Sample DPMLA.xml used in this post
<?xml version="1.0" encoding="utf-16" ?>
- <LAConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/2003/dls/LAConfig.xsd">
- <DriveReMapInfo IsMannuallyMapped=" true ">
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0e " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 1 " DriveBayIndex=" 0 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0f " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 2 " DriveBayIndex=" 1 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0g " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 3 " DriveBayIndex=" 2 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0h " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 4 " DriveBayIndex=" 3 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0i " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 5 " DriveBayIndex=" 4 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0j " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 6 " DriveBayIndex=" 5 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0k " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 7 " DriveBayIndex=" 6 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0l " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 8 " DriveBayIndex=" 7 " />
<Library SerialNumber=" 7c7u0Mfw0m " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0m " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 9 " DriveBayIndex=" 8 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
- <DriveLibraryAssociation>
<Drive SerialNumber=" 7c7u0Mfw0n " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 9 " DriveBayIndex=" 9 " />
<Library SerialNumber=" 7c7u0Mfw0d " SCSIPort=" 1 " SCSIBus=" 0 " SCSITargetId=" 8 " SCSILun=" 0 " />
</DriveLibraryAssociation>
</DriveReMapInfo>
</LAConfig>
Jesús Gutiérrez | Consultant - Microsoft Consulting Services
The App-V Team blog:
http://blogs.technet.com/appv/
The WSUS Support Team blog:
http://blogs.technet.com/sus/
The SCMDM Support Team blog:
http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog:
http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog:
http://blogs.technet.com/operationsmgr/
The SCVMM Team blog:
http://blogs.technet.com/scvmm/
The MED-V Team blog:
http://blogs.technet.com/medv/
The DPM Team blog:
http://blogs.technet.com/dpm/
The OOB Support Team blog:
http://blogs.technet.com/oob/
The Opalis Team blog:
http://blogs.technet.com/opalis
The Service Manager Team blog: http:
http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http:
http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http:
http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http:
http://blogs.technet.com/b/serverappv
