Membership Directory Migration Scenarios

April 1999

Microsoft Corporation

Membership Directory Migration Scenarios

This paper is designed to help Microsoft® Site Server customers manage migration of the Microsoft® Site Server Membership Directory by presenting common migration scenarios, then matching those scenarios with workable migration solutions. The scenarios also describe the migration of partitions associated with a Membership Directory.

• Scenario 1: You want to set up a process that will back up your production Membership Directory to a warm-backup site for failsafe operations.

  Solution: Migration 1

• Scenario 2: You are having problems with your production Membership Directory and want to move it to a test site for analysis.

  Solution: Migration 1

• Scenario 3: You want to use your production Membership Directory as the starting point for expanding your data center, and need to move the production Membership Directory to one or more new, parallel computers.

  Solution: Migration 1

• Scenario 4: You have a large data center where the production Membership Directory is deployed. You also want a copy of the production Membership Directory in your offices where you do your development work. You want to be able to make changes to the schema of the development Membership Directory as new sites come online. As the new sites go live (to production), the schema on the production Membership Directory needs to be updated to reflect the development copy.

  Solution: Migration 2

• Scenario 5: Your site is growing rapidly and, for scalability reasons, you need to move one or more partitions off of your primary computer running Microsoft® SQL Server™ to another.

  Solution: Migration 3

Migration 1:  Migrating from Production to Backup or Test Computers

Requirements

• The process needs to support single and multiple partitions.
  
  
• The Membership Directory must remain up during the migration process.

How to do it

• Create the new Membership Directory on the test server that points to the production Membership Directory:
  • Open Microsoft® Management Console (MMC). On your test computer that is running the LDAP Service, go to Start\Programs\Microsoft Site Server\Administration\Site Server Service Admin (MMC). Expand Personalization and Membership, right-click the name of the computer running the LDAP Service and then select New. Click Membership Server Instance.

Follow the Wizard

1. Click Next.
   
   
2. Select Complete Configuration and click Next.
   
   
3. Select Connect to an Existing Membership Directory and click Next.
   
   
4. Select Microsoft SQL Server Database and enter the relevant information for your original database on the production computer. Click Next.
   
   
5. Select an appropriate IP Address and port number and click Next.
   
   
6. Enter a username and password for an Administrative account in the Membership Directory, and then click Next.
   
   
7. Select an SMTP server name and click Next.
   
   
8. Click Finish to create your new Membership Directory.
   
   
9. Create new databases on the test server and transfer the production Membership Directory to them:
   • Create a New Database Device. On your test computer, open SQL Server and create a new database device named TestMemDirTransfer that is the same size or larger than the Membership Directory database that you want to transfer.
     
     
   • Create a New Log Database Device. Create a new database device named TestMemDirTransferLog that is at least 15 percent of the size of the TestMemDirTransfer database created using the directions in the previous paragraph.
     
     
   • Create a New Database. Create a new database named TestMemDirTransferDB. For the data device, select TestMemDirTransfer and the default value for its size should automatically appear. For the log device, select TestMemDirTransferLog and select the default value for its size. Click Create Now to create your new database.
     
     
   • Truncate Log on Checkpoint. Right-click your new TestMemDirTransferDB database and select Edit. Click the Options tab, and select the Truncate Log on Checkpoint check box. Click OK to close the database and save your change.
     
     
   • Create Database Devices and Databases for Partitions. Repeat the preceding four steps for any partitions you want to migrate, substituting the appropriate database devices and database name.
     
     
   • Connect to the Production Computer. In SQL Server Enterprise Manager, register the production computer.
     
     
   • Transfer the Data from your Existing Production Membership Directory Database. Expand the production computer, expand Databases, right-click your existing Membership Directory database name, and then select Transfer. Select the production computer as your source server, and your existing Membership Directory database name as your source database. Select the test computer as your destination server, and TestMemDirTransferDB as your destination database. Ensure that all transfer options and advanced options are checked, then click Start Transfer.
     
     
   • Transfer the Data for Partitions. Repeat the step above for any partitions you want to migrate, substituting appropriate source and destination database names.
10. Change the new Test Membership Directory to point to the test server databases:
    • Open the Former LDAP Server: On your LDAP Service test computer, go to Start\ Programs\Microsoft Site Server\Administration\Site Server Service Admin (MMC). Expand Personalization and Membership, expand the new LDAP Service computer name, expand the Membership Directory name for the Membership Directory you created in step 1, right-click LDAP, and then select Properties.
      
      
    • Change your Root Database Information. Click the Root Database tab and change the computer name, database name, user name and password to match the test computer settings on your SQL Server computer.
      
      
    • Change your Membership Directory Properties Information. Click the Directory Properties tab. For each container partition (including the main partition) and/or each value partition that was moved, select that partition, and then click the Edit button and change the settings to point to the appropriate new Membership Directory database on the test computer. Click OK to change your settings, then click OK again to close your LDAP Service computer.

Migration 2:  Migrating from a Non-production Site to a Production Site

Requirements

• The process needs to support single and multiple partitions.
  
  
• You must move the Membership Directory structure while leaving existing members intact during migration.

Potential problems

You will need to schedule down time from the time the databases are transferred until the new Membership Directory is created.

How to do it

• In this case, the best course is to make manual schema changes to your production Membership Directory to reflect the structure of your test Membership Directory. Microsoft does not support migration of only the schema at the present time.

Migration 3:  Moving a Partition onto a Different SQL Server Computer

Requirements

• You must move partitions only.
  
  
• Your Membership Directory must remain up during the migration process.

Potential problems

You will need to schedule down time from the time the databases are transferred until the new Membership Directory is created.

How to do it

1. Create the new database on the new SQL Server computer and transfer the partition database to it. Perform the following steps once for each partition you want to move:
   • Create a New Database Device. On the new computer, open SQL Server and create a new database device named PartitionTransfer that is the same size or larger than the partition database that you want to transfer.
     
     
   • Create a New Log Database Device. Create a new database device named PartitionTransferLog that is at least 15 percent of the size of the database device you created in the step above.
     
     
   • Create a New Database. Create a new database named PartitionTransferDB. For the data device, select PartitionTransfer and select the default value for its size. For the log device, select PartitionTransferLog and select the default value for its size. Click Create Now to create your new database.
     
     
   • Truncate Log on Checkpoint. Right-click your new PartitionTransferDB database and select Edit. Click the Options tab, and select the Truncate Log on Checkpoint box. Click OK to close the database and save your change.
     
     
   • Connect to NewMachine. In SQL Server Enterprise Manager, register the new computer.
     
     
   • Transfer the Data from your Existing Partition Database. Expand ProductionMachine, expand Databases, right-click your existing partition database name and select Transfer. Select ProductionMachine as your source server, and your existing partition database name as your source database. Select the new computer as your destination server, and PartitionTransferDB as your destination database. Ensure that all transfer options and advanced options are checked, then click Start Transfer.
2. Change the production Membership Directory partition to point to the new SQL Server database:
   • Open the Production LDAP server. On the production computer, go to Start\ Programs\Microsoft Site Server\Administration\Site Server Service Admin (MMC). Expand Personalization and Membership, expand the name of the computer running the LDAP Service, expand the Membership Directory name for the partition database you just transferred, then right-click LDAP and select Properties.
     
     
   • Change your Directory Properties information. Click the Directory Properties tab. For each Container Partition (for example, ou=members) and/or each value partition that was moved, select that partition, then click the Edit button and change the settings to point to the appropriate new partition database on the new computer. Click OK to change your settings, then click OK again to close the computer running the LDAP Service.

Information in this document, including URL and other Internet web site references, is subject to change without notice.  The entire risk of the use or the results of the use of this resource kit remains with the user.  This resource kit is not supported and is provided as is without warranty of any kind, either express or implied.  The example companies, organizations, products, people and events depicted herein are fictitious.  No association with any real company, organization, product, person or event is intended or should be inferred.  Complying with all applicable copyright laws is the responsibility of the user.  Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.  Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 1999-2000 Microsoft Corporation.  All rights reserved.

Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation in the U.S.A. and/or other countries/regions.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.