Description of Issue
From time to time, it may be desired to create a new WSP Web site by "cloning" an existing site. This can be easily done, however, to do so, you must follow the procedure provided in this article.

Cloning a WSP site is fairly straight-forward, and involves creating a copy of the existing site's file system structure as well as database.

Throughout this article, we will refer to the existing site as "Site A" and the new site (or copy) as "Site B."

Preparation for Cloning Operation
Prior to starting this process, you must make sure the following are accomplished:

1. Ensure that ALL objects on Site A have been checked in. This includes file system object, components, page layouts, stylesheets and articles.

2. Using WSP System Administration, create "Site B" using the "Site Manager" option. Make note of the physical file path for the new site, the database information and the database user. You will "clone" Site A into this site in the next step.

Cloning the Site
Having completed the above steps, you are now ready to create the copy. You will need to perform the following steps to complete this process, and may need the assistance of your database administrator (DBA) for some of the operations.

1. Backup the database for Site A: This can be performed using the "dump database" directive in SQL server. Assuming the database for Site A is named "wspSiteA" and that you have a physical directory on the SQL Server of "D:\sqlTemp", the command would be as follows:

dump database wspSiteA
to disk='d:\sqlTemp\wspSiteA_db.bak'
with init,retaindays=0

2. Copy the files for Site A to Site B: You will copy ALL the files and folders (except for WSPTemp and WSPWork) from the Web root directory for Site A into the Web root directory for Site B.

3. Restore Site A database into the Site B database: You may need your DBA's assistance in order to accomplish this operation. When performing this restore, you will need to change the path and names associated with the data and log files. Your DBA should know how to do this. They/you may need to "kill" any processes attached to this database, prior to performing the restore. You will also need to check the option to force the restore on the existing database.

4. Update SQL Account Associations: After the restore completes, you will need to add appropriate user authorities, within SQL Server Enterprise Manager to this database. The appropriate authorities are as follows:

• Account associated with this instance (as showing in WSP Site Manager): dbOwner
• WSPConfig Account: dbOwner

Additionally, the instance account should have read/write access to the WSPConfig database in order to operate properly.

5. Update any CMS properties, etc., in the WSP Administrator: If you are using CMS registries in the new site, you will need to update these, as appropriate, for your environment.

6. Set User Authorities: You will need to configure groups and user authorities for this new site (Site B) as they will not properly migrate.