I am currently in the process of migrating our backups to DPM 2012. I set up a protection group and moved 6 servers onto it the first night and all the jobs ran successfully. The second day I modified the protection group and added a further 20 servers to it. The backup jobs added are mostly just disk volumes and system state protection. Just after midnight, a lot of the jobs failed with this error:

Type:    Tape backup
Status:    Failed
Description:    The job was cancelled because the user modified the associated protection group. (ID 33342)
    More information
End time:    25/07/2012 12:05:01 a.m.
Start time:    25/07/2012 12:04:57 a.m.
Time elapsed:    00:00:03
Data transferred:    0 MB
Cluster node    -
Source details:    xxxxxxx\xxxx
Protection group:    xxxxxxxx
Library:    IBM TotalStorage 3573 Tape Library
Tape Label (Barcode):    -

I certainly wasn't modifying the protection group at the time. The modification was done early in the afternoon and the protection group was scheduled to start backup at 11:00pm. Has anyone else seen this error before?

Hi,

DPM maintenance jobs run at midnight, and one of those jobs is SQL Server / Sharepoint DB Autoprotect. This job looks for new DB's to automatically add to the protection group, which under the covers is a modify PG which cancels jobs.  Move SQL and sharepoint in a seperate PG and schedule to start the backup after midnight.

Thanks Mike, that's helpful.

What would be more helpful would be the ability to schedule that maintenance at a time that fits in with what we need to do in our backup schedule. Midnight seems to be a strange time to pick for that, as a lot of people would have jobs running at that time. Just something to feed back to the DPM developer team.

Thanks,
Graeme

I see the is an old thread however we are getting these same alerts in DPM2012R2. You can change the maintenance time w/Powershell.

https://technet.microsoft.com/en-us/library/hh881727(v=sc.20).aspx

https://technet.microsoft.com/en-us/library/jj627968.aspx

Hi,

Please find possible solutions here.