How to use import and export in stsadm to migrate sub-websites in Moss?

We recommend that you use the stsadm command line export and import in moss to migrate sub-websites, because during actual development, a module may be closely related to a sub-website, I am not used to placing the main functions under the root website of the website set, because the root website may only serve as a navigation or information display function.

Many people fail to use the migration tool. I have summarized the following points:

1. The domain name and host name are different. It is best to have the same domain environment and host name when migrating the website. If they are different, you can change them to the same in your testing environment and set alternative access mapping.

During the migration, user permissions will also be imported to the production machine. If these users do not have the production environment, an error will occur.

2. If the SPD workflow is used, it is troublesome to use the SPD workflow. We recommend that you do not use it too complicated. If it is possible to use vs to develop workflow templates.

3. Use evnet handler to update other lists in evnet handler. This is the most troublesome because, when you use the stsadm-O import command, the import operation itself imports a list item with a fixed handler, the import operation will also trigger an event (My God, I don't know what Uncle Microsoft thinks, it will trigger the event during the import, I don't know if it is a bug ), in this way, an error is triggered when you import a list. Therefore, please uninstall all dangerous handler in the original website, export it, and then import it.

Finally, how to use the command line to export a sub-Website:

Stsadm-O export-URL http: // servername/sitename-filename D: \ exportfilename

Stsadm-O import-URL http: // destinatename/sitename-filename D: \ exportfilename

You can use stsadm-help export/import to query related parameters.