Fix for DPM Tape Backup Jobs Aren't Scheduled for One or More Servers in a Protection Group

"If you're performing Disk to Tape (D-T) backups using System Center Data Protection Manager 2007 or 2010 (DPM), after adding data sources (DS) to a protection group (PG) for two or more protected servers, the backup jobs mayn't be scheduled for any of the data sources for one or more members of the PG. If […]

"If you're performing Disk to Tape (D-T) backups using System Center Data Protection Manager 2007 or 2010 (DPM), after adding data sources (DS) to a protection group (PG) for two or more protected servers, the backup jobs mayn't be scheduled for any of the data sources for one or more members of the PG. If you look at the scheduled jobs for the next 7 days, there'll be no jobs scheduled for the effected protected server(s). Consequently, backups aren't performed for any servers whose data sources are missing from the scheduled jobs. If you remove the data sources from protection for the effected server(s) and place them in their own protection group, then the backup jobs are scheduled and run as expected," informed Microsoft.

Cause: Intent Manager schedules backup jobs based on the time zone for a D-T PG. Sorting is done based on TIME_ZONE_INFORMATION.Equals() API but the job definitions are created using TIME_ZONE_INFORMATION.StandardName. If two servers have same time zone but differ in Daylight settings, Sorting will treat them as two different time zones, but StandardName will be the same. As a result one will override the other's job definition so the final XML in the tbl_JM_JobDefinition table willn't be complete.

To view all the servers names and time settings, run following SQL Query to see if that is the problem. Look for servers in the same PG with the same time zone, but different daylightname and daylightBias settings.

Select svr.ServerName, svr.serverid, tz.Description, tz.DaylightName, tz.DaylightBias from tbl_AM_ServerTimeZone tz join dbo.tbl_AM_Server svr on tz.ServerId = svr.ServerId

To fix the problem, check the protected servers time zone and daylight savings settings and make sure they match. Then for the problematic server, remove the data sources from protection, remove the agent from the DPM console and re-install the agent. DPM should pick up the new time zone and daylight savings settings and then the problem should go away.

As an alternative, you can protect the offending server in a separate protection group, enable tape co-location and set both PG up to have the exact same recovery goals and retention ranges. DPM will write both PG's to the same tape as originally intended.