"Stsadm" command for moss backup and Restoration

Recently I want to migrate Moss data. I tried the backup/restoration provided by moss. After the restoration, it seems that the website set cannot be restored. Sometimes the restoration will fail,

Therefore, I found a better backup/restoration mode for stsadm on Google. The specific summary is as follows:

The stsadm.exe command is in the directory % systemdriver % \ Program Files \ common files \ microsoft shared \ Web Server Extensions \ 12 \ bin>.

 

The specific operation commands are as follows:

1. Back up a site (only one site can be backed up at a time based on the URL, that is, one site set)

Stsadm-O backup-URL http: // localhost: 200-filename E: \ databak \ default200.bak (the backup file name can be customized)

Press enter. If the message "Operation completed successfully" is displayed,

 

If there are multiple website sets under this website, the URL address is changed to back up. For example, if there is an http: // localhost: 200/test website set, then:

Stsadm-O backup-URL http: // localhost: 200/test-filename E: \ databak \ default200test. Bak

 

2. Restore A site (one site is restored at a time based on the backup file)

Stsadm-O restore-URL http: // lmjob: 777-filename E: \ databak \ default200.bak

Restore one site. If you want to restore another site (default200test. Bak) in different directories ):

Stsadm-O restore-URL http: // lmjob: 777/test-filename E: \ databak \ default200test. Bak

 

If a site set already exists in the target location during restoration, you must delete it first, or add the parameter-overwrite and the site set is disabled. Otherwise, the following message is displayed: "/" has another website. Select a new URL or specify the-overwrite flag to overwrite the existing website.

 

This operation stores the whole site set data to the backupname. Bak file, which includes all site content, such as website, website content, document library, list and user, page, style, image, etc.

 

However, you cannot back up and restore all websites under a web application at a time.

 

 

The following is a backup and restoration method taken from others. You can use it for reference:

From: http://blog.csdn.net/bisheng_hu/archive/2009/02/12/4684976.aspx

 
Problems:
Since the system has been deployed and formed before and is applied in practical use, but the personnel who have deployed and maintained the system have left the system, and the relevant documents are not complete. Therefore, we performed a series of checks on the entire system before starting, and found that there was a major problem in the system. The communication between the moss server farm and the backend SQL Server is normal, but a problem occurs during the backup. The specific result is that all data to the content database fails to be backed up. Therefore, data is backed up on the moss management interface and cannot be directly imported to the new server through restoration.
In addition, because it was previously in the frontend and backend mode, I guess even if data can be restored through the moss management interface, it is also possible to direct the server farm configuration database and web application to the content database to the original background SQL Server. Of course, this idea cannot be confirmed because of the failure of the method mentioned above.
 
Solution:
Considering that all data from the MOSS system is stored in SQL data, I decided to use the method of backing up SQL database files to import the data to the new server through restoration, to migrate data.
 
The procedure is as follows:
1. Back up databases starting with wss_content (I have three corresponding applications), back up SSP database sharedservices1 _ dB, and back up SSP search database sharedservices1_search_db. Note: Do not back up the sharepoint_config and sharepoint_admincontent databases in the server farm.
2. Copy the backup files of these databases to the target server.
3. install sql2005 and moss2007 on the target machine, create a new server farm (my custom port is 8000), and start three services: office Sharepoint Server search, Windows SharePoint services help search, Excel calculation services; Note: Do not create SSP and applications at this time.
4. On the SQL console, restore the previously backed up moss-related databases.
5. Create a new Web Application: On the moss Application Management page, create a new Web application and configure its default content database to go offline. (I have three web applications before, so I have created three)
6. Restore the web application content database: In the content database created for the web application, select add content database. The database added here is the database we restored to SQL. (I have restored 3 here)
7. Restore SSP: In SSP configuration, select "Restore SSP", "SSP Database", and "SSP search database", and select "Restore to database in SQL.
8. Subsequent work: set this SSP as the default SSP and enable the SSP crawling Function
9. Check the website set in each web application, modify the pointing path of some website links, and notify the user to access the new server address.
10. The entire migration process is complete.
 
As shown in the preceding figure, all operations except the backup database operation must be performed on the original SQL Server, which can be performed on the target server without any configuration changes to the original two servers. This not only enables data migration on the server, but also ensures that the entire system will not be down due to some misoperation during the migration process. Of course, the process is relatively complicated.
 
Key Technical difficulties:
The entire migration process was not smooth sailing. It was a key technical issue. Since there were basically no similar cases on the internet, and I had no idea about Moss before, so it took me about two weeks. So I will share it with you here.
The specific problem is that in step 6 above, an error occurs after the database is recovered, for example:

I have posted a post asking this question before, but there is no effective solution. Reference :.
Http://bbs.winos.cn/thread-54153-1-1.html
Final Solution:
Since it is clearly stated that the version needs to be updated, I have been trying to update all aspects. Upgrades include OS updates, various SP and security updates of office2007, various SP and security updates of sql2005, and the latest SP and security updates of WSS; the latest SP and Security Update of MOSS; the infrastructure update of moss. None of this works.
Finally, at the time of renewal, we thought that there may also be an infrastructure update for WSS, because the infrastructure update of Moss had to work hard to know that there was such a thing. Find the WSS infrastructure update and try to add the content database again after installation. Depend on... ...
 
If you have experience, the whole process should be within one day. But the problem ended up being stuck for two weeks and asked gtsc people in the Microsoft community. At that time, it was really another day, so I planned to start the case. Well...
We hope this experience will help you.