Showing posts with label DPM 2007. Show all posts
Showing posts with label DPM 2007. Show all posts

Saturday, 5 December 2009

Latest hotfix for DPM 2007

I think I explained earlier that my DPM 2007 product does not get updated by Microsoft update.

I tried reseting Windows Update components, but that didn't help:
http://support.microsoft.com/kb/971058
I've discovered I'm a little bit behind on hot fixes, and that Microsoft have released KB976542 on October 23rd 2009.

This seems to include all the hotfixes posted since DPM 2007 SP1:
Still, looks like DPM 2010 will soon be here.

Saturday, 28 February 2009

Feb 2009 Hotfix Package for DPM 2007 (KB963102)

For some reason, my DPM server doesn't seem to pick up on updates from Microsoft, so I occasionally scan download.microsoft.com for any updates.

Today, I found a new hotfix download for DPM 2007:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8a551a13-270e-46c0-91ee-4a6d3d8bf034

It patches some issues detailed here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;963102

Can anyone tell me how to make DPM 2007 register with Windows update on this server?

Saturday, 29 November 2008

DPM 2007 SP1 Real Soon

Launched at the start of December 2008 apparently.
I'm not clear as to how the Hyper-V protection will work though - Will we have to pause Hyper-V guests or not during protection?

More details here:
http://blogs.technet.com/jbuff/archive/2008/11/24/what-is-new-for-protecting-sharepoint-with-dpm-2007-sp1-technet-edge-video.aspx

Saturday, 12 July 2008

Microsoft DPM 2007 - Enable colocation of data on tape

If you have multiple storage groups with the same data retention policies, you can now colocate the data on the same tapes as long as you have installed theDPM 2007 feature pack. Most useful if you have a single drive rather than a library.

It's not settable in the GUI, but the following Powershell command turns it on:
Set-DPMGlobalProperty -DpmServer -OptimizeTapeUsage $true

More details here

Thursday, 10 July 2008

DPM 2007 Feature Pack - Out!

The feature pack that is supposed to fix quite a few issues was released on the 1st July. I seemed to have missed it even though my DPM server is subscribed to Windows Update.

Found out about it here:
http://blogs.technet.com/dpm/archive/2008/07/01/dpm-2007-rollup-update-now-available.aspx

Details from Microsoft here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=e9e1fe35-b175-40a8-8378-2f306ccc9e28&DisplayLang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=ad5cd1a2-9b87-4a2c-90a2-9dbaf1024310&DisplayLang=en

Sunday, 15 June 2008

DPM 2007 Agent failing to protect Windows Vista SP1

I recently modifed my DPM 2007 installation to backup my local users folder on Windows Vista Ultimate x64. This would not work and kept producing the following event logs when I attemted to manually sync the share:
Log Name:      Application
Source:        Application Error
Date:          15/06/2008 08:50:37
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Cartman2.thefoleyhouse.co.uk
Description:
Faulting application DPMRA.exe, version 2.0.5820.0, time stamp 0x46f990f7, faulting module kernel32.dll, version 6.0.6001.18000, time stamp 0x4791ada5, exception code 0x80070002, fault offset 0x000000000002649d, process id 0x1ff8, application start time 0x01c8cebaac1ac7c8.
After some research I found the following fix:
http://www.eggheadcafe.com/software/aspnet/31450629/cant-create-recovery-poi.aspx

You have to create the following DWORD registry key with a value of 1:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitive

Sunday, 25 May 2008

DPM 2007 DPMRA Error 10048 (0x2740)

After rebooting my Exchange server because of DNS issue, the DPM protection stopped. Further investigation found this in the event log:
The DPMRA service terminated with service-specific error 10048 (0x2740).

Google found this:
http://support.microsoft.com/kb/947682

Essentialy you use 'netstat -oan' to find the PID of the process using port 5718 or 5719, which are both required by DPMRA.
Then use 'tasklist' and 'tasklist /svc' to discover which process it is. In my case, it was the MS Exchange Information Store.

I fixed it by stopping all Exchange services, starting DPMRA and then restarting Exchange.

It's kind of weird that MS Exchange can use the DPMRA ports when DPM is speciffically for protecting Exchange (amongst other things).

Thursday, 22 May 2008

DPM 2007 Internal error code: 0x80990A93

When changing the PG (Protection Group) that my server belongs to, I normally get this error message:
DPM cannot protect \\CHEF2.thefoleyhouse.co.uk\Optical Drive\. The recycle bin, the System Volume Information folder, non-NTFS volumes, DFS links, CDs, Quorum Disk (for cluster) and other removable media cannot be protected. (ID: 38)

Today, it suddenly changed to:
DPM cannot access the path \\CHEF2.thefoleyhouse.co.uk\Optical Drive\ because part of the path has been deleted or renamed.
Check the path and enter it again.
ID: 36
Details: Internal error code: 0x80990A93

It took me a little while to realise that this was because I had removed the DVD from the drive! I thought I'd broken something by reinstalling the DPM client!

Tuesday, 20 May 2008

SQL Database missing from DPM 2007

Having fixed my SQL 2005 issues with DPM 2007, I found my main production SQL database was missing from the list of resources available to be protected. When attempting a normal SQL backup, I got an error message telling me that the Full Text Index was missing.

I recreated the Full Text Index, (got lost when changing SQL versions - No backup, that's what DPM was supposed to do!), and everything worked great.

The thing I learned here was, if DPM is having problems protecting a resource, try another backup type for more information on the error!

DPM SQL Issues

I had the following scenario:
  • DPM 2007 Running on Windows Server 2003 R2 SP2 (x86)
  • SQL 2005 Standard (x86) running on Windows Server 2008 (x64)
DPM would not protect the SQL databases, and kept giving errors that the protection was "inconsistant". There were lots of SQLVDI errors in event viewer, including a BADMEM error.
To cut a long story short, I found the fix was to replace the x86 version of SQL 2005 with an x64 version.