none
Workaround to get the correct LatestRecoveryPoint time stamp of a data source RRS feed

  • Question

  • I'm doing some reporting of the last Hyper-V recovery points with Microsoft Data Protection Manager 2012 R2 (Update Rollup 5 with KB3040326) build 4.2.1297.0 running on Windows Server 2012 R2.

    The first time within a PowerShell session when the LatestRecoveryPoint of a datasource is requisted the date timestamp is "Monday, January 1, 0001 12:00:00 AM". When I wait about a second and request the date again it gives the correct date, for example "Friday, March 13, 2015 10:06:05 PM".

    When running the below PowerShell code the LatestRecoveryPoint is invalid:

    $oDPM = Connect-DPMServer -DPMServerName $env:COMPUTERNAME;
    $oPGs = $oDPM.GetProtectionGroups();
    foreach ($oPG in $oPGs) {
    	$oPG.Name;
    	$oDSs = $oPG.GetDatasources() | Where-Object {$_.ObjectType -eq "Microsoft Hyper-V"};
    	foreach ($oDS in $oDSs) {
    		$oDS.Name;
    		$oDS.LatestRecoveryPoint;
    	}
    }
    I've added a additional loop to first retrieve the LatestRecoveryPoint and then loop again to get the actual LatestRecoveryPoint:
    $oDPM = Connect-DPMServer -DPMServerName $env:COMPUTERNAME;
    $oPGs = $oDPM.GetProtectionGroups();
    foreach ($oPG in $oPGs) {
    	$oPG.Name;
    	$oDSs = $oPG.GetDatasources() | Where-Object {$_.ObjectType -eq "Microsoft Hyper-V"};
    	foreach ($oDS in $oDSs) {
    		$oDS.LatestRecoveryPoint | Out-Null;
    	}
    	Start-Sleep -Milliseconds 1500;
    	foreach ($oDS in $oDSs) {
    		$oDS.Name;
    		$oDS.LatestRecoveryPoint;
    	}
    }

    Example output of the first one:
    Group 1
    Online\SERVER1
    Monday, January 1, 0001 12:00:00 AM
    Online\SERVER2
    Monday, January 1, 0001 12:00:00 AM
    Online\SERVER3
    Monday, January 1, 0001 12:00:00 AM
    Group 2
    Online\SERVER4
    Monday, January 1, 0001 12:00:00 AM
    Online\SERVER5
    Monday, January 1, 0001 12:00:00 AM
    Online\SERVER6
    Monday, January 1, 0001 12:00:00 AM

    Example output of the second one:
    Group 1
    Online\SERVER1
    Friday, March 13, 2015 9:32:21 PM
    Online\SERVER2
    Friday, March 13, 2015 9:37:38 PM
    Online\SERVER3
    Friday, March 13, 2015 9:34:39 PM
    Group 2
    Online\SERVER4
    Friday, March 13, 2015 10:02:19 PM
    Online\SERVER5
    Friday, March 13, 2015 11:05:25 PM
    Online\SERVER6
    Friday, March 13, 2015 10:59:19 PM

    Has anybody ran into the same issue and knows a solution for this (rather then the workaround)? Otherwise I might create a support case for this.

    Saturday, March 14, 2015 8:50 PM