Friday, March 19, 2010

DPM 2007 Limitation

Recently we have re-organized the content database for our MOSS 2007. We ended up with 196 content databases after the re-organized. Soon I start to see DPM failing to create recovery point for the MOSS farm. It threw out the following error.

DPM failed to start tracking changes for on because of insufficient memory resources (30130).

The recommended action is to "Verify that you do not have more than 100 protectable data sources on a single volume. If this is the case, check to see if you can split your data source across more volumes.".

Doesn't make any sense to me at all. Well after trying for a few days, I finally give up and log a call with Microsoft PSS.

The support engineer remote in and check on our DPM server as well as SQL server. He didn't take too long to figure out that it is a limitation of DPM 2007. Basically DPM 2007 will fail if there are more than 128 content databases on a single volumn on the SQL server. To workaround this problem, he hack the registry which allows DPM 2007 to bypass this limit. However, the consistency check took about 9 hours to complete and the recovery point creation took another 7 hours. Well according to him, DPM 2010 has addressed this issue.

No comments: