gtrapp
asked on
SharePoint backup files incompatible with SharePoint
I have made BAKs files with SQL Server of my SharePoint 3.0 content databases. When I take my backups that were created 3 weeks ago, and try to restore to a sub-site on the same SharePoint server, I see this error:
Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version '1162887508.196608.1769486 0.0' or later.
In the past week, MS Security patches have been applied to the server, so I my BAK file is now from an older site.
I have restored the database using MS SQL Server Management Studio to the SharePoint instance, as described in this article:
http://portalsolutions.net/Blog/Lists/Posts/Post.aspx?List=1fef67f0%2D70ca%2D4263%2Db683%2Df10c1958687a&ID=45&Web=2a4e9897%2D6530%2D44a1%2D80b5%2D4fac295c2c26
But site does not come up. I have HTTP 400 Bad Request on the site and the Site Collection List information in for the subsite has blank information. Title, URL, database name, email address and other info is blank.
Is there a way to make a backup of a SharePoint content database compatible with a newer SharePoint server/site?
Thanks
Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version '1162887508.196608.1769486
In the past week, MS Security patches have been applied to the server, so I my BAK file is now from an older site.
I have restored the database using MS SQL Server Management Studio to the SharePoint instance, as described in this article:
http://portalsolutions.net/Blog/Lists/Posts/Post.aspx?List=1fef67f0%2D70ca%2D4263%2Db683%2Df10c1958687a&ID=45&Web=2a4e9897%2D6530%2D44a1%2D80b5%2D4fac295c2c26
But site does not come up. I have HTTP 400 Bad Request on the site and the Site Collection List information in for the subsite has blank information. Title, URL, database name, email address and other info is blank.
Is there a way to make a backup of a SharePoint content database compatible with a newer SharePoint server/site?
Thanks
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I ran this command, stsadm –o restore. I was following this aticle:
http://portalsolutions.net/Blog/Lists/Posts/Post.aspx?List=1fef67f0%2D70ca%2D4263%2Db683%2Df10c1958687a&ID=45&Web=2a4e9897%2D6530%2D44a1%2D80b5%2D4fac295c2c26
http://portalsolutions.net/Blog/Lists/Posts/Post.aspx?List=1fef67f0%2D70ca%2D4263%2Db683%2Df10c1958687a&ID=45&Web=2a4e9897%2D6530%2D44a1%2D80b5%2D4fac295c2c26
as part of your stsadm -o restore, were you pointing to the .bak file you created through sql? because this isn't going to work. you can't create a backup file in sql and restore it through stsadm.
if you are restoring a sql database, over an existing sql database with the same name, you don't have to run anything in sharepoint. SharePoint will just pick the restored database up since it's the same name.
if you are restoring a sql database, over an existing sql database with the same name, you don't have to run anything in sharepoint. SharePoint will just pick the restored database up since it's the same name.
also, what was the database name that you restored? are you positive it was the content db for your web app and not the config db?
ASKER
It was the content database for sure.
I was restoring a content database to a subsite, on the same SharePoint server. However, as you noted, I was attempting to restore it to a different database name, since the backup of the database came from the live database on the site, which I can't write over.
So its like this:
Production Site A --> Database A
Restored Site of the Production Site A --> Database B (really a backup of database A, but renamed)
Make sense? I was following these steps: http://technet.microsoft.com/en-us/library/cc747463(WS.10).aspx
Problem is that I need a development SP site, so I can stop and restart services as needed. I can't do this to on a server with a production site.
.
I was restoring a content database to a subsite, on the same SharePoint server. However, as you noted, I was attempting to restore it to a different database name, since the backup of the database came from the live database on the site, which I can't write over.
So its like this:
Production Site A --> Database A
Restored Site of the Production Site A --> Database B (really a backup of database A, but renamed)
Make sense? I was following these steps: http://technet.microsoft.com/en-us/library/cc747463(WS.10).aspx
Problem is that I need a development SP site, so I can stop and restart services as needed. I can't do this to on a server with a production site.
.
You can't restore a content db to a subsite.
You can't restore a content database to the same farm without overwriting the original, then try to attach it to a web app. It just won't work.
You can't restore a content database to the same farm without overwriting the original, then try to attach it to a web app. It just won't work.
ASKER
Oh, so what can I do?
either restore over, or stand up a temporary farm, restore to that.
ASKER
One last question - So with the problems I have been having are not related to security patches applied to the server after a backup has been made, but the design of restoring a SharePoint content database just won't allow it?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version '1162887508.196608.1769486
You said you resored the DB through SQL manager, but what did you do in SharePoint?