I have a new install of DPM 2012 R2 with RU5. It protects one server with about 40 SQL Server databases.

I have created a single protection group for all databases and scheduled a recovery point (Express Full) at 22:00 for each day of the week. Retention range is 30 days.

Synchronisation frequency is set to "just before recovery point"

The PG also includes a few files, which are set to run at 21:00

I am only backing up to disk.

Some of the databases are quite large: 1-2 TB, but they change very little, so I think that we can manage 30 concurrent recovery points.

It took about two days to create the initial replicas and during that time I gues DPM would have wanted to run some recovery points, which probably faled.

Since DPM finished the initial replicas, it has gotten through two rounds of recovery point.

The strange part is that not only does DPM create new recovery points at 22:00. It ALSO does so at 21:04. And I have no clue why. And 21:04 is sufficiently close to 22:00 so that typically they run into each other and creates problems.

Any thoughts?

I am still hoping to get som help here. I have some extra info:

The issue still exists: DPM schedules two Express Full Backups per day for each database rather than just the one, which I want.

But I have determined that the "extra" EFBs are related to the File Recovery Point in the same PG. Originally the "extra" EFBs were scheduled at 21:04, but when we moved the File Recovery Point from 21:00 til 20:00 the extra EFB jobs also moved - from 21:04 to 20:04. I still have no clue where the four minute "delay" comes from.

Any suggestions?

I am thinking of pulling the files out of this protection group into their own PG. Just to see if that would resolve the problem. But I seem to recall that there was some reason why I did not do that originally. I cannot recall the details, though, so I might just try it.

• Edited by ThomasIsr 18 hours 12 minutes ago

I am still hoping to get som help here. I have some extra info:

The issue still exists: DPM schedules two Express Full Backups per day for each database rather than just the one, which I want.

But I have determined that the "extra" EFBs are related to the File Recovery Point in the same PG. Originally the "extra" EFBs were scheduled at 21:04, but when we moved the File Recovery Point from 21:00 til 20:00 the extra EFB jobs also moved - from 21:04 to 20:04. I still have no clue where the four minute "delay" comes from.

Any suggestions?

I am thinking of pulling the files out of this protection group into their own PG. Just to see if that would resolve the problem. But I seem to recall that there was some reason why I did not do that originally. I cannot recall the details, though, so I might just try it.

• Edited by ThomasIsr Sunday, April 05, 2015 1:25 PM

I am still hoping to get som help here. I have some extra info:

The issue still exists: DPM schedules two Express Full Backups per day for each database rather than just the one, which I want.

But I have determined that the "extra" EFBs are related to the File Recovery Point in the same PG. Originally the "extra" EFBs were scheduled at 21:04, but when we moved the File Recovery Point from 21:00 til 20:00 the extra EFB jobs also moved - from 21:04 to 20:04. I still have no clue where the four minute "delay" comes from.

Any suggestions?

I am thinking of pulling the files out of this protection group into their own PG. Just to see if that would resolve the problem. But I seem to recall that there was some reason why I did not do that originally. I cannot recall the details, though, so I might just try it.

• Edited by ThomasIsr Sunday, April 05, 2015 1:25 PM