A good new from Mike Jacquet :
Meanwhile don't install SP1 beta, because there is no upgrade way from Beta SP1 to RTM SP1...
General Availability is targeted for early January.
- Upgrade from Sp1 Beta is only supported for TAP customers who installed RC.
- Non-TAP customers will only be able to upgrade from DPM 2012 RTM (+ qfe's) to DPM 2012 SP1 RTM.
- There is no upgrade path from BETA Sp1 to RTM Sp1, you must reinstall DPM 2012 RTM, then upgrade to SP1 RTM.
Technet content will be updated to include new supported workloads in SP1 of Exchange 2013 and Sharepoint 2013.
Hi Guys,
I use these Powershell scripts to remove datasources from Protection Group:
(Data are retained for recovery purpose when using "-KeepDiskData" parameter. If you don't use "-KeepDiskData", Replica and Recovery points will be deleted)
1- CleanUp your DPM Server - Delete All Protection Groups
Connect-DpmServer $env:COMPUTERNAME
$PgList = @()
$PgList = Get-ProtectionGroup -DPMServerName $env:computername
foreach($Pg in $PgList){
write-host ""
Write-host "# ProtectionGroup Name " -ForegroundColor red -Nonewline
Write-host $Pg.FriendlyName -ForegroundColor green
$mpg = Get-ModifiableProtectionGroup $Pg
$dsList = @()
$dsList = Get-DataSource -ProtectionGroup $Pg
foreach($ds in $dsList){
write-host ("Remove data source ",$ds.Name)
Remove-ChildDataSource -ProtectionGroup $mpg -ChildDataSource $ds -keepDiskData
}
Set-ProtectionGroup $mpg
}
Disconnect-DpmServer $env:COMPUTERNAME
2- Delete a Protection Goup
Connect-DpmServer $env:COMPUTERNAME
$StringSearch="YourStringSearch"
$PgList = @()
$pgList = Get-ProtectionGroup -DPMServerName $env:computername
where {($_.friendlyname) -match $StringSearch}
foreach($Pg in $PgList){
write-host ""
Write-host "# ProtectionGroup Name " -ForegroundColor red -Nonewline
Write-host $Pg.FriendlyName -ForegroundColor green
$mpg = Get-ModifiableProtectionGroup $Pg
$dsList = @()
$dsList = Get-DataSource -ProtectionGroup $Pg
foreach($ds in $dsList){
write-host ("Remove data source ",$ds.Name)
Remove-ChildDataSource -ProtectionGroup $mpg -ChildDataSource $ds -keepDiskData
}
Set-ProtectionGroup $mpg
}
Disconnect-DpmServer $env:COMPUTERNAME
Feel free to customize/use it.
When you try to protect W8 clients with DPM 2010 or DPM 2012 (RU3), you get some error messages :
DPM is unable to continue protection for because the change tracking information is corrupt (ID 30156 Details: The system cannot find the file specified (0x80070002))
Cannot perform creation of a recovery point on a replica which is pending manual replica creation (ID: 31207)
Cannot perform creation of a recovery point on a replica which is inconsistent (ID: 31209)
# DPM 2012 workaround
On the protected W8 clients :
- Located the dpmfilter.inf file and right-click and choose install.
- Open an administrative command prompt and run: fltmc load dpmfilter
(dpmfilter.inf => C:\Program Files\Microsoft Data Protection Manager\DPM\bin)
# DPM 2010 workaround
On the protected W8 clients :
- browse to the registry path : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0.
- Create a DWORD registry value named ForceFixup and set it to1.
Or
- Located the dpmfilter.inf file and right-click and choose install.
- Open an administrative command prompt and run: fltmc load dpmfilter
As soon as you apply a workaround, you may have to perform a consistency check and your W8 protections will be fine.
This hotfix rollup resolves the following issues:
# When a Microsoft SharePoint site collection name contains a space, SharePoint item-level recovery fails in System Center Data Protection Manager 2010.
For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 2755678 - SharePoint item-level recovery fails when the site collection name contains a space in System Center Data Protection Manager 2010. (http://support.microsoft.com/kb/2755678/ )
# After you rename a SharePoint site in System Center Data Protection Manager 2010, you cannot restore the site.
For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 2763004 - System Center Data Protection Manager 2010 is unable to restore SharePoint after renaming a site. (http://support.microsoft.com/kb/2763004/ )
# In System Center Data Protection Manager 2010, the SharePoint Recovery Point Status report displays incorrect data.
For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 2763010 - System Center Data Protection Manager 2010 SharePoint Recovery Point Status Report shows stale data .(http://support.microsoft.com/kb/2763010/ )
Download the Rollup Package 7 for System Center Data Protection Manager 2010
Hi all,
DPM 2012 RU3 has introduced a spelling mistake in SQL Store Procedure leading to dysfonction of Sharepoint Catalog task: http://social.technet.microsoft.com/Forums/en-ZA/dataprotectionmanager/thread/e0e70be6-7249-438d-b43c-a0456f7c1338
The store procedure prc_PRM_SharePointRecoverableObject_Update should be modified.
Open Microsoft SQL Manager Studio :
Go to DPMDB / Programmability / Stored Procedures
### before ###
USE [DPMDB]
GO
/****** Object: StoredProcedure [dbo].[prc_PRM_SharePointRecoverableObject_Update] Script Date: 11/04/2012 09:53:37 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[prc_PRM_SharePointRecoverableObject_Update]
(
@Caption nvarchar(40),
@ComponentType nvarchar(16),
@RecoverableObjectId BIGINT
)
AS
DECLARE @error INT,
@rowCount INT
SET @error = 0
SET NOCOUNT ON
UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption
UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption,
ComponentType = @ComponentType
WHERE RecoverableObjectId = @RecoverableObjectId
SELECT @error = dbo.udf_DPS_CheckRowCount(1)
SET NOCOUNT OFF
RETURN @error
### After ###
USE [DPMDB]
GO
/****** Object: StoredProcedure [dbo].[prc_PRM_SharePointRecoverableObject_Update] Script Date: 11/04/2012 09:53:37 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[prc_PRM_SharePointRecoverableObject_Update]
(
@Caption nvarchar(40),
@ComponentType nvarchar(16),
@RecoverableObjectId BIGINT
)
AS
DECLARE @error INT,
@rowCount INT
SET @error = 0
SET NOCOUNT ON
-- UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption
UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption,
ComponentType = @ComponentType
WHERE RecoverableObjectId = @RecoverableObjectId
SELECT @error = dbo.udf_DPS_CheckRowCount(1)
SET NOCOUNT OFF
RETURN @error
This bug will most likely fixed in the SP1.
Hi Guys,
This link provided all builds number for DPM 2010 and DPM 2012, it must be Bookmarked :)
List of DPM build numbers
If you want to know which build version is your DPM, open DPM shell and type:
$dpmversion = ((get-process | where {$_.name -eq "msdpm" }).fileversion)
$dpmversion
Or from your DPM console, click on the Information button :
DPM 2010
DPM 2012
List of issues that are fixed in Update Rollup 3 for System Center 2012 - Mostly for SharePoint, feel free to apply or wait for SP1 - :
Update Rollup 3 for System Center Data Protection Manager 2012 (KB2751230)
UR3 have been released via Microsoft Update.
For more information and to download: http://support.microsoft.com/kb/2756127/en-us
Issue 1
After you upgrade System Center Data Protection Manager 2010 to System Center Data Protection Manager 2012, the tape management report does not display overdue tapes.
Issue 2
System Center Data Protection Manager 2012 Client Protection does not scale to the limits that are expected.
Issue 3
When you try to specify a client computer name in the DPMServerName attribute by using Windows PowerShell, Windows PowerShell crashes.
Issue 4
When the name of a Microsoft SharePoint site collection contains a space, and you perform a SharePoint item-level recovery operation in System Center Data Protection Manager 2012, the operation fails.
Issue 5
After you rename a SharePoint site in System Center Data Protection Manager 2012, you cannot restore the site.
Issue 6
The SharePoint Recovery Point Status Report displays incorrect data in System Center Data Protection Manager 2012.
Issue 7
A bare metal recovery fails in certain situations.
