I have just made a brand new Exchange 2007 SP1 CCR cluster on a Windows 2008 platform for one of my customers, and that kind of environment needs to be backed up from time to time.
And since HP Data Protector 6 doesn’t support Windows 2008 before version 6.1 which is scheduled to be released in September, I decided to test Microsoft Data Protection Manager 2007 which has support for both Exchange 2007 SP1 CCR clusters and Windows 2008.
From other bloggers and forums on the internet I have found that I’m not the only one which has got at lot of “fun” with DPM 2007 in that kind of environment.
So I will like to share some of the experience I have got with the product so fare and hopefully help others.
Problem 1: Installing the agent on Windows 2008
I had/have like many others problems with remote installing the agent to Windows 2008 servers. But the last installation I made I have disabled the Windows firewall before I pushed the agent to the servers. And that worked the first time with no problems.
Also remember to install the feature pack 1:
With Feature Pack 1 you get System State Support for Windows 2008, SQL 2008 Support and better tape support.
I haven’t found the golden way to remote install the agent when Windows firewall is enabled (yet), But I have seen in other blogs that File and Print Service and WMI MUST be enabled in the firewall on the server that you try to push the agent to.
Problem 2: How-to Protect Exchange 2007
I did like many others – installed the DPM and when I couldn’t get it to work I read the manual.
My first problem was that I couldn’t see or select my Exchange stores in the Protection Group wizard.
Solution: Install EMC on the DPM server (with the same patch level), and on the same drive as the DPM.
Copy ese.dll and eseutil.exe to the DPMBIN folderAnd run this command on the DPM server:
Fsutil hardlink create “C:Program FilesMicrosoftDPMbineseutil.exe” “C:Program FilesMicrosoftExchange Serverbineseutil.exe”
The fsutil requires that DPM and EMC is installed on the same drive, otherwise the command will fail.
Link to the agent Prerequisites in the manual: http://technet.microsoft.com/da-dk/library/bb808827(en-us).aspx#ExchangeServerDatabaseUtilities
Problem 3: Protecting Windows 2003 Server
Before you deploy the DPM agent to Windows 2003 servers remember to install the VSS patch.http://support.microsoft.com/kb/940349/
I didn’t install the patch on my first 2003 server, and it took 30 min for the server boot – not cool for a production server.
Problem 4: Couldn’t see the virtual cluster node
As I wrote in the beginning, one of my installations was to protect a Windows 2007 CCR SP1 cluster installed on two Windows 2008 servers.
I manage to install the agent on both nodes in the cluster with no problems. Afterwards I could also see the virtual cluster name, but I couldn’t see or select my virtual exchange server.
After some time I found the problem – a failure in my CCR cluster.
I had at some point after I have installed the cluster created a new storage group and mailbox store which I then later on deleted from the EMC. No problem with that – but it seems like that there might be a bug somewhere (either in Exchange or in Windows 2008), because the deleted mailbox store was still a resource in my Failover cluster management tool.
After I deleted the failed resource in FCM then I could see my virtual exchange server name in the “Protection Group wizard” – and then backup works.
Problem 5: Can’t select System State on Windows 2008 Server
When I’m selecting my Windows 2008 servers I can only see “All Shares” and “All Volumes” but not my System State.
Solution: Install Feature Pack 1 and you will get Windows 2008 System State Support.