This is really confusing to me.
I set up a Windows server 2008 r2 single server SP 2010 farm with SP2 on it. The DBAs copied the backup files from our MOSS 2007 SP3 farm over to the new SP 2010 instance. I ran test-spcontentdatabase and it worked like a champ.
Now, have created a new farm. One difference is that this is windows server 2012. We downloaded the microsoft sp 2010 with sp2 already applied and installed it.
The dbas once again copy over the backup files to the instance. This time, they rename the content databases a bit so that instead of calling them DB_1 ... they are DB_Planning, etc. These are the same content databases, from the same MOSS 2007 SP3 farm.
I run test-spcontentdatabase. 13 of the 14 databases fail with the error:
Category : DatabaseValidation
Error : True
UpgradeBlocking : False
Message : This database [ContentDB_Planning] is too old and cannot be upgraded.
Remedy : Upgrade this database to Windows SharePoint Services Version 3, SP2 or later.
One of the 14 databases was seen as upgradable and we got the list of warnings and errors expected.
As I said, these databases worked when taken to the original SP 2010 farm. They fail from this new one.
I know all about needing the SP 2007 to be a recent version - as I said, it is SP 3 and perhaps even a CU after that.
Since I know that 2007 is relatively current - what ELSE can cause this type of issue?
Could Windows Server 2012 cause it? Could renaming the content databases cause it?
I really am desperate to move forward here.