DPM 2012 SP1 Installation with local SQL 2012 DB.
Active Directory Setup:
- Create 2 groups, one for your DPM admins and one for SQL.
- Add the user account that is going to administer DPM and SQL to the groups you created above.
Prerequisites List (DPM Server):
- Install Server 2012 OS
- Join server to the domain
- Install all windows updates so the server is fully patched.
- Add the DPM Admin group that you created above to the Local Administrators Group on the DPM server.
Windows Features Requirement:
- You need to install .NET 3.5, you can do so by selecting using the GUI of Server Manager or running it from powershell, remember you need to select a source. Replace D:\ with your drive letter.
Add-WindowsFeature NET-Framework-Core –source D:\sources\sxs
Install SQL Server
- Install the features as selected above, optionally you can install the Management tools.
- Select a Named Instance, I choose to give it a name that is easily identified, for example HODPM (I removed the name from the screenshot)
- Here you need to specify a domain account to use, if this is sandbox installation then a local account is fine. E.G. for the Account name: Domain\username
- Select your Authentication method, if you want to use Mixed Mode then to provide a password for the SA account (from experience if this server is hosted on the internet, rather create another account and set a strong password as SA accounts on the Internet are vulnerable)
- Add in your account or the account that will administrator SQL (as created in Step 1 when the AD accounts and groups were setup)
Install DPM 2012 SP1
- Mount the DPM media.
- I normally right click the install and select “Run As Administrator”
- Select “Use an existing instance of SQL Server” and then type in the name of your SQL Instance: YourDPMServerName\YourSQLInstance, click on Check Again.
- If the connection was successful the “Next” button is not greyed out anymore as shown below.
- If there are any warnings it will show in the details section. You might get warnings for memory or firewall etc.
- On the installation Settings screen you can modify where DPM will be installed or accept the defaults and then click the Next button.
- Review the Summary and then click Install.
- Once the installation completes it will show as above.
**Bug with the install ?**
- If you get the above error just re-launch the setup and it will be fine.
Hope it helps.
Microsoft released RU3 for DPM 2012 SP1. Finally I was able to upgrade the DPM Agent on SharePoint 2013 as I kept getting an error when trying to Protect SQL.
The updated agent installed fine, first initial sync when perfect until it finished with the above error.
Here are the steps I did to fix it:
- Reran ConfigureSharePoint.exe -EnableSharePointProtection and entered the same account as the Farm account in SharePoint.
- “c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN\stsadm” -o registerwsswriter (run this from an elevated prompt)
hope it helps
Today I upgraded one of my branches DPM 2012 evaluation to SP1. After upgrading all agents I ran consistency checks and all passed except one, Exchange. The server gave the following error:
“Cannot create a recovery point because of a transient problem. (ID 215 Details: VssError: The shadow copy provider had an error. Check the System and Application event logs for more information. (0x80042306))
So the first thing I did was check the writers from a command prompt on the problem server, all good. I then ran Windows Update and RU2 for DPM was available. I installed this rollup, rebooted the server and then upgraded all the Agents again.
After this I ran a consistency check and it returned with an OK status now.
Hope it helps
Today I installed a new DPM 2012 server. The installation went through fine and all backups were running well until the upgrade to SP1. Seems like a small bug as all my replica’s were inconsistent after applying the upgrade.
I uninstalled the DPM Agent, rebooted the DPM server plus the server where the Agent was installed and nothing.
Digging a bit deeper I came across this error: ID 53 – The service did not respond to the start or control request in a timely fashion (0x800t041D). I also checked the event log and no VSS writer information was being logged, DPM was saying it was running but nothing was actually happening.
Copied VssRequestor.dll from any of the servers that had the Agent installed to the DPM server (“C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\VssRequestor.dll”)
I then ran a consistency check and voila backups were back in progress.
Hope it helps.
If you want to protect a Server running Windows 2003 SP2 or SBS you need to ensure that the correct KB is applied as you will get the following error when trying to select a source.
One or more prerequisites for protecting this data source is missing.
Ensure that the following prerequisite software is installed on server and/or all nodes in the cluster:
Windows Server 2003 SP1 with Knowledge Base article 940349 (http://go.microsoft.com/fwlink/?LinkId=99034)
– OR –
Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=128812)
To fix this you need to download and install the KB940349. Once you apply this KB to your Windows 2003 Server and have rebooted, DPM will then allow you to select a source.
Hope it helps.
Today I moved my DC System State backups to DPM 2012. After running the first initial sync the status goes to a green OK and then immediately to a red “replica is inconsistent”. Made sure that space was not an issue as this can cause problems but the servers had ample space.
So like Windows Server 2008 R2 I i installed the following feature: Windows Server Backup.
After a reboot I ran a consistency check and all the DC’s were showing OK now.
Hope it helps.
Having multiple sites I look after and having Exchange 2010 running in each site the last thing you want to do is backup a corrupted Exchange 2010 Database. The nice thing with DPM is that you can run ESEUTIL and this ensures that everything on the Database is in a good state.
If you don’t want to run ESEUTIL, you will need a disaster recovery plan in place which is like restoring the database from time to time and see if you can mount it
I noticed that 2 of the sites did not have the option selected on the Exchange Protection Groups. If the files are not in the DPM/bin directory you will get the following error:
It is very easy to fix this error, you first need to copy ESE.dll and ESEUTIL.exe to the DPM\bin directory (quick shortcut to the folder is to right click the icon on the desktop for DPM and click on “open file location”) from your Exchange server (Program Files\Microsoft\Exchange Server\V14\Bin).
Once the files are copied you can modify the protection group and select the option for running ESEUTIL and follow all the prompts to update the group.
Hope it helps.
Today I downloaded DPM 2012 SP1. I ran the installation only to find out that DPM 2012 installed was the BETA version, you can check the version number here:
There is no direct upgrade path from BETA to RTM unless you install RC first and this is normally only available for MS Tap Customers.
I went to the Control Panel -> Programs and Features and I uninstalled DPM 2012 Beta. I left my data in place as I was now going to install DPM 2012 RTM. The uninstall went very smoothly. After the download of DPM 2012 RTM of about 2.8 GB, I extracted the files and started the install.
Installation went quickly with no errors at all. I then wanted to install DPM 2012 SP1 but before you can do that you need to install the following update or else the DPM installation will abort and give you an error that you need to install KB2706783.
Finally all updates are installed and it is time to install DPM 2012 SP1. The same splash screen appears as with the normal installation, once you get to the prerequisites SQL prompts you to make a backup before upgrading. The next few steps are simply about viewing the info and clicking next. Once you get to the install screen SQL 2008 is already marked as a success and DPM itself starts updating.
The installation takes about 20-25 min, well this is on my server. Afterwards I updated the Agents on my Exchange Server but on my SharePoint server it kept failing with error code: 1603. Normally this means that the Windows Installer Service is disabled, we it was set to Manual and was started so that fix was ruled out.
I uninstalled the AV, Agent and rebooted the server, I tried to push the Agent to SharePoint and it kept failing, I then manually mapped a drive to the DPM server and ran the installer DPMAgentInstaller_64.exe DPM Server Name. This also failed with error code: 0x80070514. I found that the server had a pending reboot, I rebooted the server and after that I was able to deploy the DPM Agent from the DPM Console.