If you have a Technet or MSDN account you can download System Center 2012 R2 Preview
This Community Technology Preview (“CTP2”) enables System Center customers to jointly evaluate System Center 2012 and Windows Server 2012 Release Candidate. CTP2 includes updates and enhancements to the following System Center 2012 components:
- Virtual Machine Manager
- Improved Support for Network Virtualization
- Extend the VMM console with Add-ins
- Support for Windows Standards-Based Storage Management Service, thin provisioning of logical units and discovery of SAS storage
- Ability to convert VHD to VHDX, use VHDX as base Operating System image
- Configuration Manager
- Support for Windows 8
- Support for Mac OS clients
- Support for Linux and Unix servers
- Data Protection Manager
- Improved backup performance of Hyper-V over CSV 2.0
- Protection for Hyper-V over remote SMB share
- Protection for Windows Server 2012 de-duplicated volumes
- Uninterrupted protection for VM live migration
- App Controller
- Service Provider Foundation API to create and operate Virtual Machines
- Support for Azure VM; migrate VHDs from VMM to Windows Azure, manage from on-premise System Center
- Operations Manager
- Support for IIS 8
- Monitoring of WCF, MVC and .NET NT services
- Azure SDK support
- Additional support for Integration Packs, including 3rd party
- Manage VMM self-service User Roles
- Manage multiple VMM ‘stamps’ (scale units), aggregate results from multiple stamps
- Integration with App Controller to consume Hosted clouds
- Service Manager
- Apply price sheets to VMM clouds
- Create chargeback reports
- Pivot by cost center, VMM clouds, Pricesheets
- Server App-V
- Support for applications that create scheduled tasks during packaging
- Create virtual application packages from applications installed remotely on native server
You can get the System Center 2012 Service Pack 1 CTP2 Downloads here:
There are some cases you might need to migrate your protection data to a new disk. DPM is shipped with a Powershell script (MigrateDatasourceDataFromDPM.ps1) that allows you to migrate your protection data to new storage.
First get a list of disks attached to your DPM server:
Start the DPM Management Shell
PS> get-dpmdisk –dpmservername WARD-DPM01
Name Status NtDiskIdty Total Capaci Unallocated Space Type
—- —— ——– ———— ———— —-
VMware Vir… Healthy 1 150 GB 28 GB Basic #0
VMware Vir… Healthy 2 250 GB 100 GB Basic #1
Read the disk order in to a variable ($disk)
PS > $disk = Get-DPMDisk -DPMServername ward-dpm01
Now you can use the script MigrateDatasourceDataFromDPM.ps1. First find the disk number of the source disk, these numbers are not displayed when you use the get-dpmdisk command. Do not get fooled by the NTdiskID, you do not need those. You just need to count the disks listed starting with 0 (see red numbers in example). Now find the number for the destination disk using the same trick.
In the example below we like to migrate the data from disk 2 to disk 1
PS > ./MigrateDatasourceDataFromDPM.ps1 -DPMServerName ward-dpm01 -Source $disk -Destination $disk
More options and examples can be found on Technet
How to Uninstall a Protection Agent
Remove DPM agent from the DPM agent console
Removing a Protected Computer
Remove-ProductionServer.ps1 -DPMServername [DPMServerName] -PSName [ProtectedComputerName]
The following alert became inactive at 27-9-2011 3:15:52.
Data source type:
Data source: System Protection
Description: Last 1 recovery points not created.
DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 521, WSB Error Code: 0x807800A1).
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
Some noncritical volumes are included in the system state backup image when you use the "-allCritical" switch in Windows Server 2008 R2 or in Windows 7 only for non SP1 systems. SP1 includes this hotfix.
Windows 2008 R2
DCOM was unable to communicate with the computer <servername> using any of the configured protocols.
Windows 2003 R2
A DPM agent failed to communicate with the DPM service on <servername>because of a communication error. Make sure that <servername> is remotely accessible from the computer running the DPM agent. If a firewall is enabled on <servername>, make sure that it is not blocking requests from the computer running the DPM agent (Error code: 0x800706ba, full name: <servername>).
DPM Server Warning
The DPM protection agent on <servername> could not be contacted. Subsequent protection activities for this computer may fail if the connection is not established. The attempted contact failed for the following reason: (ID 3122)
The protection agent operation on <servername> failed because the service did not respond. (ID 316 Details: Internal error code: 0x8099090E)
On the Workgroup Server
SetDpmServer.exe –dpmservername <servername> -isnondomainserver –username <dpmuseraccount> –productionserverdnssuffix <fqdn>
On the DPM Server
Attach-NonDomainServer.ps1 –dpmservername <servername> –PSName <servername> –UserName <dpmuseraccount>
Don’t forget to set Password never Expires on the DPM User account
This error normally occurs due to one of the following two possible causes:
- Not enough disk space is available on the protected machine to store a backup of the system state files
- The Windows Server Backup feature is not installed on the protected machine (Windows 2008 or Windows 2008 R2)
Simply install the Windows Server Backup feature on to the protected machine from Server Manager. Installation of this feature doesn’t normally require a reboot.
If the protected machine doesn’t have enough disk space to store a backup of the system state files (you’ll need 10-12Gb free on the system drive by default to store these files) you’ll need to create some space on the system drive, or add another disk to the machine and modify the PSDataSourceConfig.xml file to allow DPM to use the new location.
The PSDataSourceConfig.xml file is normally located at %SystemDrive%\Program Files\Microsoft Data Protection Manager\DPM\DataSources. Modify the <FilesToProtect> section of the xml file to point to the new drive added. Maybe that you may need to remove protection for the machine from the DPM 2010 console and then re-enable protection to get DPM to read the new location for backup files from the PSDataSourceConfig.xml file.
I get the following error in DPM Management console on a SQL2000 server that is protected with DPM 2010
Occurred since: 8/20/2011 4:01:13 AM
Description: Recovery point creation jobs for SQL Server 2000 database ?????? on ???? have been failing. The number of failed recovery point creation jobs = 3.
If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for SQL Server 2000 database ???? since the last backup. All incremental backup jobs will fail until an express full backup runs. (ID 30140 Details: Internal error code: 0x80990D11)
Recommended action: If you see this failure as part of a backup job, then in the Protection task area, select the SQL Server database and click Create recovery point. Choose express full backup. Alternately, you can wait for the next scheduled express full backup to run.
If this failure occurs as part of a recovery job, then try to recover from another point in time.
Review the Application Event Viewer logs on the computer running SQL Server for more details.
Ensure that this database is not already protected by another backup application.
Create a recovery point…
Resolution: To dismiss the alert, click below
DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for SQL Server 2005 database database <name database> since the last backup. All incremental backup jobs will fail until an express full backup runs. (ID 30140 Details: Internal error code: 0x80990D11)
Resolution: It seemed that the problem was that there were also backups performed straight from the SQL Management Studio. Stopping these backups resolved the issue. See also http://support.microsoft.com/kb/970642
System Center Operations Manager 2012 provides the monitoring component of cloud and datacenter solutions, to help you manage your datacenter and cloud environments by:
- Delivering flexible and cost effective enterprise-class monitoring and diagnostics while reducing the total cost of ownership by leveraging commodity hardware, with standard configurations to monitor heterogeneous environments.
- Helping to ensure the availability of business-critical applications and services through market-leading .NET application performance monitoring and diagnostics plus JEE application health monitoring.
- Providing a comprehensive view of datacenters, and private and public clouds.
- Predictable performance and availability of critical applications
- End-to-end views of application health and topology
- Establishment of application service-level delivery (SLAs)
- Precise identification of application errors
- Flexible and cost-effective infrastructure monitoring
- In-depth monitoring, diagnostics, and reporting for heterogeneous environments
- Integrated network device monitoring and alerts
- Simplified management infrastructure
- Comprehensive monitoring for your datacenter and cloud—on your terms
- Integrated physical, virtual, and cloud management
- Common console across datacenter and clouds
- Rich reporting
Supported Operating Systems: Windows 7, Windows Server 2003 Service Pack 2, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2, Windows XP Service Pack 3
- Other Software:
- Any server role
- .NET 3.5 or 4.0
- Management Server, Reporting Server, Web Console, Gateway Server
- Windows Server 2008 R2 (64 bit)
- Operational & Data Warehouse
- SQL 2008 SP1 and above
- SQL Collation – SQL_Latin1_General_CP1_CI_AS
- Windows Server 2003 SP2 and above
- Windows Server 2008 SP2 and above
- Windows Server 2008 R2
- Windows XP Professional SP3 and above
- Windows Vista SP2 and above
- Windows 7
Supported Hardware Configuration:
- Operations Manager Operations database: 4 GB of RAM or higher, 50 GB of available hard disk space
- Management server: 2 GB of RAM or more, 20 GB of available hard disk space
- Operations console: 2 GB of RAM or more, 20 GB of available hard disk space
- Reporting data warehouse: 4 GB of RAM or more, 100 GB of available hard disk space
- Reporting server: 2 GB or more, 20 GB of available hard disk space
- gateway server: 2 GB of RAM or more, 20 GB of available hard disk space
- Web console server: 2 GB of RAM or more, 20 GB of available hard disk space
- Audit database: 4 GB of RAM or more, 100 GB of available hard disk space
- Management server with audit collector: 2 GB of RAM or more, 50 GB of available hard disk space
- Management server with Agentless Exception Monitoring file share: 2 GB of RAM or more, 30 GB of available hard disk space
- Agent: Please refer to the recommended hardware requirement required by the operating system.
- Any server role
Download the beta HERE
When you check the event log of de server you see a event 517.
Event ID: 5
Task Category: None
Computer: computer name
The backup operation that started at time has failed with following error code ‘2155347997’ (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved