Wednesday, February 01, 2012 9:25:48 AM
The problem is that sometimes the BMR backup "Bare Metal Recovery" is not working properly and fails with the message "Replica inconsistent" caused by "insufficient disk space". Cause: DPM 2010 does not calculate the size of BMR data source, but assumes 30 GB for all servers. Admins should change the value as per the size of BMR backups expected on their environments. Read more
|
Monday, January 23, 2012 9:20:00 AM
Friday, January 20, 2012 9:07:17 AM
This week Microsoft released the RC version of DPM2012. The RC was released as part of the Private Cloud Management Suit. This is Microsoft next step in offering a 'all-in-one' cloud solution, based on Windows Server 2008 R2 SP1 8 and System Center. During this web cast Microsoft launched their Private Cloud Management Suit. In this session you will see how all System Center products come to getter in one suit that allows to manage your private cloud. ![image image]() The Private Cloud Management Suit includes: System Center 2012 App Controller Provides a common self-service experience across private and public clouds that can help you empower application owners to easily build, configure, deploy, and manage new services. System Center 2012 Configuration Manager Provides comprehensive configuration management for the Microsoft platform that can help you empower users with the devices and applications they need to be productive while maintaining corporate compliance and control System Center 2012 Data Protection Manager provides unified data protection for Windows servers and clients that can help you deliver scalable, manageable, and cost-effective protection and restore scenarios from disk, tape, and off premise System Center 2012 Endpoint Protection Built on System Center Configuration Manager, provides industry-leading threat detection of malware and exploits as part of a unified infrastructure for managing client security and compliance that can help you simplify and improve endpoint protection System Center 2012 Operations Manager Provides deep application diagnostics and infrastructure monitoring that can help you ensure the predictable performance and availability of vital applications and offers a comprehensive view of your datacenter, private, and public clouds.
System Center 2012 Orchestrator Provides orchestration, integration, and automation of IT processes through the creation of run books that can help you to define and standardize best practices and improve operational efficiency. System Center 2012 Service Manager Provides flexible self-service experiences and standardized datacenter processes that can help you integrate people, workflows, and knowledge across enterprise infrastructure and applications.
System Center 2012 Virtual Machine Manager Provides virtual machine management and services deployment with support for multi-hypervisor environments that can help you deliver a flexible and cost effective private cloud environment. System Center 2012 Unified Installer Starting this release Microsoft introduced one installer for all System Center (Cloud) management products the System Center 2012 Unified Installer. With the Unified Installer it's possible to install all System Center products as once, without the need to install a single product multiple times. That way products can be installed quicker and less screens are needed to install them. ![image image]() You run the Unified Installer to deploy System Center 2012 components. After you select a System Center 2012 component to install, the Unified Installer prompts you for the prerequisites that the component requires. Then, the Unified Installer installs the component and its prerequisites. ![image image]() Licensing The licensing for the new System Center 2012 product suite will be fully renewed. The current System Center 2010 suite contains 110 licensing items. Where the new SC 2012 will only have 2 license types. , That is for the whole suite of SC products! License required only for endpoints being managed. No additional licenses are needed for management servers or SQL Server technology. Consistent licensing model across editions. Processor-based license, covering up to two processors for server management. User- or OSE-license for client management. All server management licenses (SMLs) include the same components and the ability to manage any workload. System Center 2012 SMLs will be released in two editions differentiated by virtualization rights only: Datacenter: Maximizes cloud capacity with unlimited virtualization for high density private clouds Standard: For lightly or non-virtualized private cloud workloads. ![image image]() Full details: Licensing & Pricing Datasheet Download The release candidate versions of all the Microsoft System center products are now available for download. Start here. More to read Download the Microsoft Private Cloud Whitepaper The Microsoft Private Cloud web site Using the System Center 2012 Unified Installer System Center 2012 Gets Generous Licensing Changes Licensing & Pricing Datasheet More to watch Transforming IT with Microsoft Private Cloud Video: Thought Leadership Series - Enabling Private Cloud
|
Monday, January 16, 2012 9:24:10 AM
DPM will use free tapes before it uses expired tapes. The thinking is that once you overwrite an expired tape, it can no longer be used for recovery, so DPM favors using free tapes first. DPM always pull tapes from the highest slot number first, so a free tape in slot 8 will be used before a free tape in slot 2. (DPM forum by Mike J) 
|
Monday, January 16, 2012 9:21:52 AM
My Conclusion FIT colleague Marcel van den Berg has created a posting to collect links to articles on disaster recovery and disaster recovery as a service. Read more 
|
Friday, January 13, 2012 8:21:47 AM
A TechNet post about everything you need to consider when sharing a tape library in DPM.
Read more 
|
Monday, December 05, 2011 6:31:00 AM
One of our customers ran in to the problem that the DPM Console Kept on crashing when selecting the recovery Tab in the DPM console. ![image image]() Error data Description:AppName: mmc AppVer: xxxxx ModName: mmc.exe ModVer: 6.1.7600.16385 StackHash: F36A6DFE Problem signature: Problem Event Name: DPMException Application Name: mmc Application Version: xxxxxxxx Module Name: mmc.exe Module Version: 6.1.7600.16385 Exception Name: System.ArgumentException Exception Point: System.ThrowHelper.ThrowArgumentException Other: F36A6DFE OS Version: 6.1.7601.2.1.0.272.7 Locale ID: 1033 Check for duplicate servers in database The error could be caused by duplicated names of Protected servers in Your DPM database. Best way to check this is by running a query against the DPMDB. ![image image]() The query: Select ServerName, Domainname from dbo.tbl_AM_Server returns an overview of all protected servers in the database. It could be that servers are duplicate in the database with their NETBIOS and their FQDN. If there are any duplicates you should stop protection for these servers and re-add them to DPM. This should resolve the issue with the crashing DPM console DPM log error and event log error below <FatalServiceError><__System><ID>19</ID><Seq>0</Seq><TimeCreated>11/28/2011 11:51:40 AM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>ArgumentException</ExceptionType><ExceptionMessage>An entry with the same key already exists.</ExceptionMessage><ExceptionDetails>System.ArgumentException: An entry with the same key already exists. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.TreeSet`1.Add(T item) at System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value) at Microsoft.Internal.EnterpriseStorage.Dls.UI.RecoveryPage.RecoveryBrowseTab.UpdateProductionServers(ICollection`1 productionServerList, TreeNode dataOnDiskAndTapeNode) at Microsoft.Internal.EnterpriseStorage.Dls.UI.RecoveryPage.RecoveryBrowseTab.RenderTreeView(Boolean firstTime) at Microsoft.Internal.EnterpriseStorage.Dls.UI.RecoveryPage.RecoveryBrowseTab.RenderView() at Microsoft.Internal.EnterpriseStorage.Dls.UI.CommonControls.FireOnceTimer.OnTimerTick(Object sender, EventArgs e) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</ExceptionDetails></FatalServiceError> The Event viewer shows the following error The following information was included with the event: An unexpected error caused a failure for process 'mmc'. Restart the DPM process 'mmc'. Problem Details: <FatalServiceError> <__System><ID>19</ID><Seq>0</Seq><TimeCreated>11/28/2011 11:51:40 AM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>ArgumentException</ExceptionType><ExceptionMessage>An entry with the same key already exists.</ExceptionMessage><ExceptionDetails>System.ArgumentException: An entry with the same key already exists. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.TreeSet`1.Add(T item) at System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value) at Microsoft.Internal.EnterpriseStorage.Dls.UI.RecoveryPage.RecoveryBrowseTab.UpdateProductionServers(ICollection`1 productionServerList, TreeNode dataOnDiskAndTapeNode) at Microsoft.Internal.EnterpriseStorage.Dls.UI.RecoveryPage.RecoveryBrowseTab.RenderTreeView(Boolean firstTime) at Microsoft.Internal.EnterpriseStorage.Dls.UI.RecoveryPage.RecoveryBrowseTab.RenderView() at Microsoft.Internal.EnterpriseStorage.Dls.UI.CommonControls.FireOnceTimer.OnTimerTick(Object sender, EventArgs e) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</ExceptionDetails></FatalServiceError>
|
Friday, December 02, 2011 7:45:17 AM
When enabling self service recovery for an Instance on a SQL Cluster you might run into the following error. ![image image]() The specified SQL instance . is invalid or cannot be found (ID 32608). If a SQL instance exists with the specified name, use Get-Datasource -ProductionServer <ProductionServer> -Inquire cmdlet to refresh the information. Then retry the Operation. Solution SQL instances of a Cluster need to be added in a special way. The convention is: FQDN of the Resource\SQLVirtualname\SQLInstance Example FQDN resource = (blackberry).c260.gp.wan SQLVirtualname= C265 Instance name - BLACKBERRY ![image image]() In the example above you need to specify the following SQL Server Instance: (Blackberry).c260.gp.wan\C265\BLACKBERRY ![image image]()
|
Friday, December 02, 2011 7:44:11 AM
During the deployment or the attaching of agents you might run in to the error below. Unable to connect to the Active Directory Domain Services database. Make sure that the DPM server is a member of a domain and that a domain controller is running. Also verify that there is network connectivity between the DPM server and the domain controller. ID: 7 Details: Unknown error (0x80005000) (0x80005000) There is a knowledge database article for a issue like this: http://support.microsoft.com/kb/978900 Resolution for Error ID: 7To resolve this error, change the Authenticated Users group so that it has read permissions for the organizational unit that the target server is a member of. To do this, follow these steps: - On the domain controller, open the Active Directory Users and Computers MMC.
- Right-click the organizational unit that contains the target server, and then click Properties.
- On the Security tab, add the Authenticated Users group and give them READ permissions.
- Redeploy the DPM protection agent to the protected server
Alternative cause to this issue The error code Unknown error (0x80005000) (0x80005000) points to another cause. In this case the issue was caused by a slash in the OU Name the The target machine to install the DPM agent on was in an OU named "DR/ test Servers." DPM doesn't understand special characters in active directory, so the / was what tripped it up. When you rename the OU, you should be y able to install the agent.
|
Friday, December 02, 2011 7:42:53 AM
The Bare Metal Recovery (BMR) option in DPM 2010 allows you to recover servers from an image file. BMR is actually an option build in to Windows 2008 (R2) which can be utilized by DPM 2010. By default the BMR will protect the "critical system data" According to the Microsoft definition -> critical data = System State and C drive and all other drivers that contain system data directories (Program files).
Check what is includes: - logon to the protected server
- Open the Windows Server Backup Feature
- Select Action - Backup ones
![image image]() Select Different options ![image image]() Select Custom ![image image]() C Click on Bare Metal Recover and check which other volumes are automatically selected. Modify Drives included Now you can choose to modify the BMR selection. This can be done by editing the file named Bmrbackup.cmd. To alter this configuration do this: On the protected server, open the C:\Program Files\Microsoft Data Protection Manager\DPM\bin\Bmrbackup.cmd file in notepad. ----------------------Modify the file below------------------------------------------------------------------- rem Start a wbadmin.exe to create a BMR backup start /WAIT %SystemRoot%\system32\wbadmin.exe start backup -allcritical -quiet -backuptarget:%1 ------------------------------------------------------------------------------------------------------------------------ --------------------------------To include the d-drive--------------------------------------------------------- rem Start a wbadmin.exe to create a BMR backup start /WAIT %SystemRoot%\system32\wbadmin.exe start backup -allcritical -include:D: -quiet -backuptarget:%1 --------------------------------------------------------------------------------------------------------------------------
--------------------------------To exclude the e-drive--------------------------------------------------------- rem Start a wbadmin.exe to create a BMR backup start /WAIT %SystemRoot%\system32\wbadmin.exe start backup -allcritical -exclude:E: -quiet -backuptarget:%1 --------------------------------------------------------------------------------------------------------------------------
Note: You also need to adjust the replica volume and recovery point volume sizes on the DPM server to account for the additional space required for the extra volume(s) being included in future BMR backups (Source http://robertanddpm.blogspot.com/2010/09/bmr-can-protect-more.html)
|