So we had a failed iSCSI target on our production DPM server and as the NAS unit was a bit old decided to upgrade it.
New unit was installed and iSCSI Target was mounted and disk was added to DPM.
The old disk was still there with status “Missing”
All Protection Group members were also marked as “Volume Missing” Continue Reading
Because we planned to implement a new Hyper-V Cluster using Windows Server 2012R2 we had to move to SCVMM 2012 R2 but in order to do this one of the steps we needed to complete was Upgrading System Centre DPM 2012 to 2012 R2.
I have detailed the steps I took below, there may be some differences for your specific configuration but you will get a good idea.
Firstly, there is a list of SCDPM build numbers here;
http://social.technet.microsoft.com/wiki/contents/articles/4058.list-of-build-numbers-for-system-center-data-protection-manager-dpm.aspx
System Center 2012
I recently had an issue where System Center Data Protection Manager 2012 was constantly reporting Replica Inconsistent on my Exchange Server 2010 Protection Group for the relevant Storage Groups, upon investigation I was pointed towards Eseutil as being a possible cause.
Basically if there is a mismatch between the versions of Eseutil on the Exchange Server and on the DPM Server then the replicas will appear to be inconsistent.
This can occur if you install a Service Pack on Exchange.
So the solution is to copy the version of Eseutil.exe and ese.dll from your Exchange Server to your DPM Server;
<Exchange Install Path>\bin\eseutil.exe to <DPM Install Path>\bin\eseutil.exe
<Exchange Install Path>\bin\ese.dll to <DPM Install Path>\bin\ese.dll
This should then solve the Replica Inconsistent problem, after a Consistency Check.
Full details and further information can be found on the following
http://technet.microsoft.com/en-US/library/91198fbb-3016-4571-b83c-0ece920588ed#bkmk_EseutilEse
Following on from my previous blog post;
During the process of making all my replicas consistent something went wrong.
I don’t know as of yet what caused the issue but will investigate further later.
Basically the DPM Administrator Console suddenly shutdown and would not start back up, claiming the DPM Service was not running.
I checked my services and it was actually running however the DPM AccessManager service was stopped.
I checked the Windows System Logs in Event Viewer and found multiple instances of the following error;
Event ID: 7034
Description: The DPM AccessManager Service service terminated unexpectedly. It has done this 7 time(s).
I searched around but could find no-one with a similar problem or more importantly a solution, I did stumble across a post on the Microsoft Website;
http://technet.microsoft.com/en-us/library/bb808877.aspx
Which mentioned the DpmSync command;
“DpmSync is a command-line tool that enables you to synchronize the DPM database with the state of the disks in the storage pool and with the installed protection agents. The DpmSync tool restores the DPM database, synchronizes the DPM database with the replicas in the storage pool, restores the Report database, and reallocates missing replicas. “
Using the DPM Management Shell, I ran the command;
dpmsync -sync
dpmsync
I then re-tried the DPM Administrator Console and all was good in the world again.
As I said I do not know what cause this problem but this procedure repaired the problem and I have had no issues since.
Here are the steps I took in upgrading System Center DPM 2010 to System Center DPM 2012.
I have tried to keep it as simple as possible with nice pictures to make the process easy to follow.