I have just transitioned my SQL backups from a server running SCDPM 2012 SP1 to a different server running 2012 R2.  All backups are working as expected except for one.  The database in question is supposed to be backuped up iwht a daily express full and hourly incremental schedule.  Although the database is set to full recovery model, the new DPM server says that recovery points will be created for that database based on the express full backup schedule.  I checked the logs on the old DPM server and the transaction log backups were working just fine up until I stopped protection the data source.  The SQL server is 2008 R2 SP2.  Other databases on the same server that are set to full recovery model are working just fine.  If we switch the recovery model of a database that isn't protected by DPM and then start the wizard to add it to the protection group it properly sees the difference when we flip the recovery model back and forth.  We also tried switching the recovery model on the failing database from full to simple and then back again, but to no avail.  Both the SQL server and the DPM server have been rebooted.  We have successfully set up transaction log backups in a SQL maintenance plan as a test, so we know the database is really using the full recovery model.

Is there anything that someone knows about that can trigger a false positive for recovery model to backup type mismatches?

Hi,

did you also tried to remove the Database from Protectiongroup.

Open Protectiongroup Wizard, Clear the Cache

re add the Database to Protectiongroup

Yes, we have tried clearing the cache.  My only remaining solution is to create a copy of the database, but I was hoping to find a better solution.

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey 14 hours 33 minutes ago

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey 16 hours 35 minutes ago

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 10 hours 20 minutes ago

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 Monday, April 13, 2015 9:19 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 Monday, April 13, 2015 9:19 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 Monday, April 13, 2015 9:19 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 Monday, April 13, 2015 9:19 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 Monday, April 13, 2015 9:19 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 Monday, April 13, 2015 9:19 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 Monday, April 13, 2015 9:19 PM

I was having this same problem and appear to have found a solution.  I wanted hourly recovery points for all my SQL databases.  I was getting hourly for some but not for others.  The others were only getting a recovery point for the Full Express backup.  I noted that some of the databases were in simple recovery mode so I changed them to full recovery mode but that did not solve my problem.  I was still not getting the hourly recovery points.

I found an article that seemed to indicate that SCDPM did not recognize any change in the recovery model once protection had started.  My database was in simple recovery mode when I added it (auto) to protection so even though I changed it to full recovery mode SCDPM continued to treat it as simple. 

I tested this by 1) verify my db is set to full recovery, 2) back it up and restore it with a new name, 3) allow SCDPM to automatically add it to protection over night, 4) verify the next day I am getting hourly recovery points on the copy of the db. 

It worked.  The original db was still only getting express full recovery points and the copy was getting hourly.  I suppose that if I don't want to restore a production db with an alternate name I will have to remove the db from protection, verify that it is set to full, and then add it back to protection.   I have not tested this yet.

This is the article I read:  Article I read

• Edited by kevin.m.massey Thursday, April 09, 2015 5:06 PM
• Proposed as answer by kevin.m.massey Saturday, April 11, 2015 3:02 PM
• Unproposed as answer by gregg79 Monday, April 13, 2015 9:19 PM

Kevin, technically in your test you changed too many things.  A more definitive test would be to stop protection (but retain backed up data) of your database that was set to simple when it was added and now is set to full and then re-add it to the protection group.  In my experience this should fix it without requiring you to destroy your existing backups if the problem only has to do with the recovery model.

The reason I say you are changing too many things it that we just did some more testing on this issue and I have some additional info which relates to you changing the database name.  The problem is definitely not related to recovery model.  It actually appears to be related to the name of the database on that particular SQL server.  If we do nothing other than change the name of the database, incremental backups will work.  If we change the name of a different database that is working with incremental backups to match the name of the one that isn't, it now won't be backed up incrementally.  This caused me to suspect a problem with the DPM agent on that server, so I uninstalled and re-installed it, but the behavior persisted.  Doing some searching right now armed with this new info.

In my original post I was not clear about my test.  I did not destroy the original database.  I simply restored it with a new name resulting in two copies.  DB_original and DB_copy.  Technically the only difference between the two is the name.  

Your testing with the name changes supports my theory.  This is a quote from the TechNet article:  "When the recovery model of a protected database is changed from simple to full or bulk-logged, DPM Protection continues as configured." 

Link

It seems to me that DPM is doing exactly what this Microsoft article states it is designed to do.  Best of luck.

It seems to me that DPM is doing exactly what this Microsoft article states it is designed to do.  Best of luck.

Not sure how that is possible.  I am not currently protecting this database via SCDPM at all becuase I can't do incremental backups.  When I go to add it to a protection group (new or pre-existing), it tells me that it won't do incrmental backups for this database or any other database with the same name on the same protected server.  There is no change in recovery model as it has been set to full for years (except for us switching it back and forth as we have been troubleshooting this problem).

Was the database in question ever protected by SCDPM?  If so, was the recovery model set to full at the time the db was added to the protection group?

It was previously protected by another server running 2012 SP1 without issue.  I removed the protection and then the agent.  Then I pushed the 2012 R2 agent from this new server and immediately was unable to do incremental backups.

So what happened here? I am having the same problem.