DPM 2010 Data Protection Manager Error ID: 316
or DPMRA Event id 85
On the protected server running the DPM agent
SetDpmServer.exe -dpmServerName YOURDPMSERVER -isNonDomainServer –updatePassword
On the DPM server
Update-NonDomainServerInfo –PSName YOURPROTECTEDDPMSERVER –dpmServerName YOURDPMSERVER
I’ve used System Center Data Protection Manager (DPM) since the 2007 beta, primarily for SharePoint and SQL backups & Exchange Backups. At a customer they have one DPM server which backs up to disk and additionally to a HP MSL2024 Tape Library for long term protection. The runs Windows Server 2008 R2 with DPM 2010 since its release.
After updating de DPM Server with SP1 for Windows 2008 R2 en updated the drivers. I had some issues with DPM. What I found was that although DPM installed correctly it couldn’t see all the tape drives in the VTL. All the tape drives were visible in Device Manager and none were showing errors. I use the RECOMMENDED * HP StorageWorks Tape Drivers for Windows
In the DPM console under Management -> Libraries, the library was listed, but Total Drives was 0, rather than the expected 2. The DPM console showed the following error:
I followed the instructions to remap the drives here: http://technet.microsoft.com/en-us/library/bb795782.aspx. The DPMLA.xml file produced by the tool was correct, showing the correct SCSI IDs, serial numbers etc. but DPM still couldn’t see the drives.
I found the solution to the problem on the DPM forum here: http://social.technet.microsoft.com/Forums/en-US/dpmtapebackuprecovery/thread/1d599443-7bf6-437a-bf12-52847fa7c8e5/ What I did is update the tape drive driver to the Inbox LTO driver as described on the forum and below:
1) Open device manager
2) Locate the tape drive
3) Right-click and look at the properties.
3) Under the DRIVER tab, select UPDATE DRIVER
a) Select the Install from list or specific location (Advanvced) – next.
b) Select Don’t search. I will choose the driver to install. – next.
c) Uncheck the Show comtabile hardware checkbox.
d) Highlight LTO under the manufacturer.
e) Highlight the LTO tape drive under model – then next.
f) This should install the Microsoft ltotape.sys driver.
4) Rescan the tape library in the DPM console – try to take another backup.
After following the above steps, all the two tape drives were visible in the DPM console.
When using System Center Data Protection Manager 2007 or 2010 (DPM) to backup your production servers, you might encounter a situation where the recovery point volumes for your protected data source keep running out of space and the number of days that DPM has recovery points for exceeds the desired retention range. If you run vssadmin list shadows, or run diskshadow.exe followed by list shadows all command, you can see that there are more shadow copies than there should be based on the desired retention goal. Also, if you manually run the DPM Power Shell pruneshadowcopies2010.ps1 script, no recovery points are removed, but there are no errors.
So what’s going on here? Most likely this is happening because the NetBIOS name of the DPM server is longer than 15 characters.
To resolve the problem perform the following to truncate the name to the 15 character limit.
1) Using notepad, open C:\Program Files\Microsoft DPM\DPM\bin\pruneshadowcopiesDpm2010.ps1 (For DPM2010) or pruneshadowcopies.ps1 (For DPM 2007).
2) Locate the following entry:
$dpmservername = &"hostname"
3) Replace the &"hostname" with the truncated 15 character NetBIOS name of the DPM server. For example, if the DPM Server’s host name is "Long-DPM-server-name" then modify the entry as follows:
$dpmservername = "ward-dpm01.wardvissers.local"
4) Save the modified script.
5) Either run the script manually, or wait for it to run at midnight – then verify the shadow copies are being pruned as expected.
Now I have nice Green Protection Groups
Special Thanks to J.C. Hornbeck
The “Microsoft Virtualization for VMware Professionals” Jump Start is specially tailored for VMware and Microsoft virtualization technology pros. This cutting-edge course features expert instruction and real-world demonstrations of Hyper-V, many components of the System Center Suite, including VMM 2012, and a myriad of VDI solutions. This course is designed for Data Center Managers, IT Professionals, IT Decision Makers, Network Administrators, Storage/Infrastructure Administrators & Architects. Expert IT infrastructure consultant, Corey Hynes, and Microsoft Technical Evangelist, Symon Perriman, leveraged an engaging "team teaching" approach which makes the class as entertaining as it is educational
Virtualization Jump Start (01): Virtualization Overview
Virtualization Jump Start (02): Differentiating Microsoft & VMware
Virtualization Jump Start (03a): Hyper-V Deployment Options & Architecture | Part 1
Virtualization Jump Start (03b): Hyper-V Deployment Options & Architecture | Part 2
Virtualization Jump Start (04): High-Availability & Clustering
Virtualization Jump Start (05): System Center Suite Overview with focus on DPM
Virtualization Jump Start (06): Automation with Opalis, Service Manager & PowerShell
Virtualization Jump Start (07): System Center Virtual Machine Manager 2012
Virtualization Jump Start (08): Private Cloud Solutions, Architecture & VMM Self-Service Portal 2.0
Virtualization Jump Start (09): Virtual Desktop Infrastructure (VDI) Architecture | Part 1
Virtualization Jump Start (10): Virtual Desktop Infrastructure (VDI) Architecture | Part 2
Virtualization Jump Start (11): v-Alliance Solution Overview
Virtualization Jump Start (12): Application Delivery for VDI
Download all the Video’s:
Video: WMV | WMV (ZIP) | PSP
Audio: WMA | MP3
Now only finding some spare time to watch’s these video’s
With this feature, you can achieve better tape utilization by co-locating data from multiple protection groups with similar retention range. This feature is disabled by default. You can use following PowerShell commands to enable and disable tape co-location.
Enable Tape co-location:
Set-DPMGlobalProperty -DpmServer <DPM Server Name> -OptimizeTapeUsage $true
After data co-location has been enabled, DPM will check for the following conditions before allocating a tape:
- The expiry date of the current dataset should fall in between the following dates:
Upper bound: furthest expiry date among all the datasets on the tape – (furthest expiry date among all the datasets on the tape – current date) * TapeExpiryTolerance
Lower Bound: furthest expiry date among all the datasets on the tape + (furthest expiry date among all the datasets on the tape – current date) * TapeExpiryTolerance.
- Current time should be less than first backup time of the dataset on the media + TapeWritePeriodRatio * RetentionRangeOfFirstDataset.
A dataset will be collocated only if both the above conditions are true.
When you add the value to the registry, set the DWORD to be the actual percentage in decimal. The Default is 17 percent if that value is not present. Most likely you need to increase that value to a higher percentage and in some cases you need to set it to 100 in order for tape co-location to work as desired.
TapeWritePeriodRatio – Indicates the number of days for which data can be written on to a tape as a fraction between 0 and 1. The default value is 0.15 – meaning by default, we will write to the same tape for 15% of the retension range period specified for each PG.
TapeWritePeriodRatio is not a registry. It is a global property for the DPM which needs to be set using DPM CLI command. Here is the command to set it:
Set-DPMGlobalProperty –DPMServerName <dpm server name> -TapeWritePeriodRatio <fraction>
EXAMPLE, to set the write period ratio to 50%, use the following command.
Set-DPMGlobalProperty –DPMServerName MY-DPMSEREVR -TapeWritePeriodRatio .50
Jonathan has created a nice script. This script checks witch updates are missing from Hyper-V hosts and SCVMM Server.
Updates are regularly released for SCVMM Server, Hosts, and the Admin Console. These updates must be applied to all Hosts no matter how many you have. Updates are also released for technologies SCVMM leverages:
- Failover Cluster
As well as components SCVMM cannot function without:
The difficulty is in making sure all systems are fully updated. This is a time-consuming task.
WSUS takes care of this for me…
Not necessarily. There are certain Hotfixes that need to be downloaded manually, but for the most part Windows Update is the key. WSUS is Microsoft’s solution to distributing Windows Updates within an enterprise, and this pulls from Windows Update as well. Unfortunately, rules in WSUS are sometimes set up such that all updates required do not find their way to SCVMM systems. So, there are layers of complexity in keeping systems up to date.
Prevent problems with VMMUpdate
With this script you now or that your Hyper-V hosts & SCVMM Server are up to date.
To download the latest follow the link HERE
The management pack monitors the health status of System Center Data Protection Manager 2010 and its components. It alerts the admin on critical health state and it provides certain break fix tasks to take corrective actions.
The following alerts are new in this release of the DPM 2010 Management Pack:
- Backup metadata enumeration failed
- Agent ownership required
- Replica allocated and initial replication scheduled
- Share path changed
- Duplicate disks detected
- VHD parent locator fix-up failed
- Virtual machine metadata enumeration failed
- VHD parent locator fix-up canceled
- SharePoint Item Level Catalog failed
- Backup without writer metadata
- Customer Feedback opt-in
- Backup SLA failed
- Hyper-V Recovery Success
- Global DPMDB Database Not Accessible alert notification
- StagingAreaRestore in-progress
- StagingAreaRestore success
- StagingAreaRestore partial success
- StagingAreaRestore failure
- Auto Instance Protection failed
- DPM Online Recovery Point creation failures
- DPM Online Cache volume is missing
- Partial Backup success
- Library devices were disabled
You can download the System Center Data Protection Manager 2010 Monitoring Management Pack HERE
Vizioncore, a wholly owned subsidiary of Quest have released a free Management Pack for System Center Operations Manager 2007 R2 which enables the monitoring of VMware virtual infrastructures. Now, before I get into the features and capabilities of what the MP gives you, it’s important to point out that this is the first free MP to deliver these capabilities, and may stir things up a little over at both Veeam and Bridgeways, who both have established MP’s for OpsMgr to enable monitoring of VMware environments. It’s important to say, both Veeam and Bridgeways offer trails of their solutions, so it would be important to compare the different MP’s for yourselves, however looking at a high level, one of the key elements that Veeam seems to have today, is that it’s PRO-enabled, thus provides more automated, dynamic and agile responses within the environment based on changing conditions. That’s not to say both Bridgeways and Vizioncore won’t evolve their technologies in the future, and bring in PRO capabilities, however today, you would have to classify it as a differentiator for Veeam. One you have to pay for however.
So, what are the key features of the Vizioncore MP?
- Essential alerts from the virtual infrastructure to reduce mean time to resolution (MTTR) of problems
- Integration to System Center Operations Manager to centralize and consolidate monitoring efforts
- Low cost and simple to use while allowing administrators to work in their familiar System Center Operations Manager views
- Native management pack delivers alert and event management as well as trending inside the SCOM console
- Agentless architecture for simple deployment and low overhead
- Performance monitoring & availability event monitoring for fast resolution in the virtual environment
- Out-of-the-box reports for host and guest metrics provides flexibility and clear communication between stakeholders
There’s even more features here…
What’s nice from my perspective, is the growth of the ecosystem around the Microsoft virtualisation platform, from Partners that have, in the past, been quite VMware focused. That’s more Vizioncore than Quest, but still, it’s moving in the right direction.
If you’re interested, you can get all the info, and download the MP, from here.
Ik kreeg een error toen ik een computer aan System Center Essentials 2010 wou toevoegen.
Oplossing: Dit was gelukkig iets simpels. Ik had van desbetreffende host per ongeluk dns record verwijderd.