サポートと今すぐチャット
サポートとのチャット

Binary Tree Migrator for Notes 20.11 - User Guide

Section 1. Introduction Section 2. Pre-migration Activities Section 3. User Provisioning Section 4. Email Repliability Section 5. Migrating Mail Files Section 6. Rooms and Resources Database Migration Section 7. Mail-in Database Migration Section 8. Setting Migration Status Section 9. Access and Delegation Migration Section 10. All Accounts Section 12. Logs Appendix A: Staging Replicas Appendix B: Pre-Migration Troubleshooting Appendix C: Work with Files (Import/Export) Appendix D: Item Processing Results Appendix E: Migration Result Statuses Appendix F: Recovery Process Appendix G: Automatic Migration Restart Appendix H: Folder Processing Order Third Party Components

Creating Replica Stubs on Staging Server(s)

You may choose to migrate from Domino staging servers, instead of production mail servers for reasons such as connectivity constraints between Domino and Exchange or to use Domino replication to limit the data migrated. The following steps outline a process for doing so. This section assumes that a Domino System Administrator, with the appropriate knowledge and access will perform these tasks.

Creating Connection Documents

This process outlines how to set up and configure Domino Connection documents for the purpose of replicating data from the production Domino environment to Domino staging server(s).

At least one connection document with replication enabled is required for each server pushing data to the staging server for the source mail files. Another connection document is required to push the Migrator for Notes database (also known as the EMM Customer Module) to the staging server. Additional connection documents are required if Rooms and Resources are being migrated in the project. The following sections outline how to set up each of these connection document types for the purposes previously outlined.

Data Intended for Migration

Create a new connection document from each Domino server hosting databases intended for migration to the Domino Staging server(s).

  1. On the Replication/Routing tab, complete the fields with the following entries:

  • Replication task: Enabled

  • Replicate databases of: Low & Medium & High priority

  • Replication Type: Push Only

  • Files/Directories Paths to Replicate: <mail directories>

  • Routing task: -None-

  1. On the Schedule tab, it recommended to use every 60 minutes, but you should use an interval that best suits your environment

  2. Create additional connection documents for each Domino server hosting databases intended for migration

Enterprise Migration Manager (EMM) Database

Create another connection document from the Domino server hosting the Migrator for Notes database to the Domino Staging server.

Rooms & Resources

If rooms and resource reservations are to be migrated, create another connection document from the Domino server hosting the Resource Reservations database(s) to the Domino Staging Domino server(s). Repeat for each Resource Reservation database being migrated.

Creating Replica Stubs for Users

This process outlines how to configure Migrator for Notes for creating database replica stubs on the selected Domino staging server. Ensure that the Domino Staging servers have a minimum of Reader access to all databases that are to be replicated.

Configuring EMM Customer Module Database

The first step in the process is to configure Migrator for Notes with the proper replication formula for your requirements.

Common practice is to replicate 90 days, 1 year of calendar + all future Calendar documents, Contacts and To Do’s (shown below). Adjust the replication formula as needed.

The standard replication formula is as follows:

SELECT

((@LowerCase(Form)="appointment":"contact":"deliveryreport":"group":"memo":"nondeliveryreport":"notice":"person":"phone message":"reply":"reply with history":"return receipt":"returnnonreceipt":"task":"tasknotice":"trackingresponse") & @Modified > @Adjust(@Date([20.08.2010]);0;0;-100;0;0;0)) |

((@LowerCase(Form) = "appointment" & Repeats="1")  |  (@contains(@LowerCase(Form);"appointment":"notice") & @Date(StartDateTime) > @Adjust(@Date([20.08.2010]);0;0;-375;0;0;0))) | (@LowerCase(Form) = "person") | (@LowerCase(Form) = "contact") | (@LowerCase(Form) = "group")

The first portion of the formula selects the various message forms by the date highlighted in this example and selects back 100 days from the date set.

The second portion of the formula selects the various calendar forms by the date highlighted in this example and selects back 375 days from the date set.

Ten additional days are added to the formulas by default to catch any content that could be missed by replication.

The following information will assist in the configuration of the Migrator for Notes with regards to replication formulas and settings. This configuration is completed in Settings > Replica Settings.

  1. Enter the Staging Server name in the field provided

  2. Enter the Staging File Folder name in the field provided

  3. Select how to build the replication formula in the Replication Formula Options; select either, Specify My Own Formula or Build Formula Via Selections

  4. If you are specifying your own formula, enter the Replication Formula in the field provided; this is only required if selecting the option to, Specify My Own Formula

  5. Enter the Number of Calendar Days that should be replicated in the field provided

  6. Enter the Number of Email Days that should be replicated in the field provided

  7. Click the arrow to select the Forms to Include in Replica from the selection window

  8. Select which option to use for the Replicate Each Replica at Creation option:

The next step in the process is to create the database replica stub on the selected staging server in the Domino environment. 

  1. Expand the Create replicas view. Select Users and click Create Replicas:

  2. Select Migration Date and click OK:

  3. Select the staging server, then select the Override the replication formula checkbox if necessary and click OK:

  4. Select the Replica Settings tab:

  1. Yes to proceed with the replica creation or No to exit:

  2. The Results window displays:

  3. Click OK:

  4. The Replica Information section displays:

     

Appendix B: Pre-Migration Troubleshooting

Migrator for Notes requires access to source Domino applications (email .nsf and resources .nsf files) through the Notes client on the Migration Controller Server and any Migration Workers. Access to Exchange mail enabled AD objects is also required to provision these to have mailboxes for migration.

Notes Security Validation:

Check the Notes ID that is currently logged in for access to the Migrator for Notes application. This can be accessed through the Notes client using File | Security | User Security:

This will show the current Notes ID User name:

 

The current Notes ID user name must be present on the mail file Access Control List (ACL), as a Person entry or as part of a Domino Group, for all accounts to be migrated.

To check a mail file ACL for an account in Migrator for Notes, the current Notes Server and Mail File .nsf path can be checked on the imported account document by opening it in Migrator for Notes. The Notes Information tab will have the Notes Mail Server and Notes Mail File Name listed.

The Notes ACL can be accessed by opening the mail file through the Open link. This can be checked in the Notes Administration client by opening the Notes Mail server and locating the mail file in the Files tab.

To check the mail file ACL, in the Notes client, with the mail file open, navigation to File | Application | Access Control. The currently logged in Notes ID should be listed as a Manager on the mail file:

If you receive an error when opening the mail file or if your Notes ID is not listed as a Manager, you will need to switch Notes ID to a different account that has Administration access to the Notes system. This can be done in the Notes client using File | Security | Switch ID. You will be asked to select the file name of the Administration Notes ID and then required to enter the password for that Notes ID.

Once the Notes ID switch is completed you can open the mail file and access the Notes ACL for the mail file. Click on the Add button to apply your Migrator for Notes Notes ID to the ACL or a Group from the Domino Directory that has your Notes ID listed as a member. Be sure that this is set as a Manager for the Access type.

Notes Server Access Validation:

The Notes client being used to manage the Migrator for Notes application will require access to the Notes Servers on which the mail files and resource application are located.

To verify the Notes client connectivity to the Notes Mail Server that is specified in an account document, in Migrator for Notes you can check the network connectivity in the Notes client. To do this use File | Preferences | Notes Ports to perform a trace to the Notes Mail Server. If there are any connection errors reported then the network connectivity should be reviewed for the Windows Operating System on which the Notes client is installed.

 

Notes Template Validation:

To perform a migration of Notes mail file and resource data, the source Notes mail files must have a valid Notes email template applied. This must be a standard Notes email template (.ntf) and meet the required version from the Migrator for Notes Requirements Guide.

To verify the mail file template, check the account document in Migrator for Notes after the mail file is audited:

The template can also be checked directly on the mail file properties by opening the mail file and using File | |Application | Properties.

The Notes template on a mail file can be changed by opening the mail file and using File | Application | Replace Design. This will open a dialog box to select the template server (can be the same as the Notes Mail Server) and then the template to apply. This template should be a standard mail template such as Mail (85) or Mail (9):

This can also be completed through a console command on the Notes Mail Server using the Notes Mail File Name from the Migrator for Notes account document. Additional details on running Notes server console commands can be in the Notes Administration client help topics.

For example, on the Notes Mail Server console run: Load compact –u mail2\f1contacts.nsf * mail9.ntf

 


It is recommended to verify a backup of any mail files that require a template design replacement prior to making any updates.

Active Directory Account Validation:

Migrator for Notes allows for a pre-migration validation process of accounts to be migrated. This will check the target migration system for mail enabled user accounts that do not have mailboxes associated with them in Exchange.

This validation will use the matching field value for the Notes accounts and check this against Active Directory using the Match AD Account To configuration found in Settings | User Provisioning.

 


Migrator for Notes assumes that accounts will have mailboxes provisioned during the migration process workflow, but it is possible to migrate into accounts that already have a mailbox that was enabled outside of the Migrator for Notes processing. If accounts already have a mailbox, the Migrator for Notes validation will report this but the account can still be migrated.

Accounts that do report an error during validation should be checked in Active Directory to ensure that the corresponding account entry does exist, has the correct match value data and that the account matching is unique.

The matching value data can be checked in Migrator for Notes by opening the account document and checking the field data value. This field value can then be verified in Active Directory using the Action | Find option and entering the Notes matching field data value.

The account can then be checked for the Active Directory matching Attribute value.

If there are multiple accounts returned in Active Directory for the Notes matching field data then the Active Directory accounts should be verified to determine which account is correct for the Notes account to be migrated to. Then, any additional accounts returned should be checked, and the matching value data, in the Active Directory Attribute, should be removed or corrected for other Notes accounts.

If there are no accounts returned, then Active Directory should be checked for the correct account and the matching value data added to the Active Directory Attribute specified for the matching.

 


The Migrator for Notes Settings are configured for a Custom Match using the Other Domino Field Name “InternetAddress” and Other AD Property Name “mail”. The Person account to be migrated has Internet Address set to “Fix1.Contacts@corp5.cmtsandbox.com”. Also, in Active Directory, the “mail” Attribute should have a value of “Fix1.Contacts@corp5.cmtsandbox.com” for a correct validation match.

 

 

Notes Security Validation:

Migrator for Notes requires access to source Domino applications (email .nsf and resources .nsf files) through the Notes client on the Migration Controller Server and any Migration Workers. Access to Exchange mail enabled AD objects is also required to provision these to have mailboxes for migration.

Check the Notes ID that is currently logged in for access to the Migrator for Notes application. This can be accessed through the Notes client using File | Security | User Security:

This will show the current Notes ID User name:

 

The current Notes ID user name must be present on the mail file Access Control List (ACL), as a Person entry or as part of a Domino Group, for all accounts to be migrated.

To check a mail file ACL for an account in Migrator for Notes, the current Notes Server and Mail File .nsf path can be checked on the imported account document by opening it in Migrator for Notes. The Notes Information tab will have the Notes Mail Server and Notes Mail File Name listed.

The Notes ACL can be accessed by opening the mail file through the Open link. This can be checked in the Notes Administration client by opening the Notes Mail server and locating the mail file in the Files tab.

To check the mail file ACL, in the Notes client, with the mail file open, navigation to File | Application | Access Control. The currently logged in Notes ID should be listed as a Manager on the mail file:

If you receive an error when opening the mail file or if your Notes ID is not listed as a Manager, you will need to switch Notes ID to a different account that has Administration access to the Notes system. This can be done in the Notes client using File | Security | Switch ID. You will be asked to select the file name of the Administration Notes ID and then required to enter the password for that Notes ID.

Once the Notes ID switch is completed you can open the mail file and access the Notes ACL for the mail file. Click on the Add button to apply your Migrator for Notes Notes ID to the ACL or a Group from the Domino Directory that has your Notes ID listed as a member. Be sure that this is set as a Manager for the Access type.

Notes Server Access Validation:

The Notes client being used to manage the Migrator for Notes application will require access to the Notes Servers on which the mail files and resource application are located.

To verify the Notes client connectivity to the Notes Mail Server that is specified in an account document, in Migrator for Notes you can check the network connectivity in the Notes client. To do this use File | Preferences | Notes Ports to perform a trace to the Notes Mail Server. If there are any connection errors reported then the network connectivity should be reviewed for the Windows Operating System on which the Notes client is installed.

 

Notes Template Validation:

To perform a migration of Notes mail file and resource data, the source Notes mail files must have a valid Notes email template applied. This must be a standard Notes email template (.ntf) and meet the required version from the Migrator for Notes Requirements Guide.

To verify the mail file template, check the account document in Migrator for Notes after the mail file is audited:

The template can also be checked directly on the mail file properties by opening the mail file and using File | |Application | Properties.

The Notes template on a mail file can be changed by opening the mail file and using File | Application | Replace Design. This will open a dialog box to select the template server (can be the same as the Notes Mail Server) and then the template to apply. This template should be a standard mail template such as Mail (85) or Mail (9):

This can also be completed through a console command on the Notes Mail Server using the Notes Mail File Name from the Migrator for Notes account document. Additional details on running Notes server console commands can be in the Notes Administration client help topics.

For example, on the Notes Mail Server console run: Load compact –u mail2\f1contacts.nsf * mail9.ntf

 


It is recommended to verify a backup of any mail files that require a template design replacement prior to making any updates.

Active Directory Account Validation:

Migrator for Notes allows for a pre-migration validation process of accounts to be migrated. This will check the target migration system for mail enabled user accounts that do not have mailboxes associated with them in Exchange.

This validation will use the matching field value for the Notes accounts and check this against Active Directory using the Match AD Account To configuration found in Settings | User Provisioning.

 


Migrator for Notes assumes that accounts will have mailboxes provisioned during the migration process workflow, but it is possible to migrate into accounts that already have a mailbox that was enabled outside of the Migrator for Notes processing. If accounts already have a mailbox, the Migrator for Notes validation will report this but the account can still be migrated.

Accounts that do report an error during validation should be checked in Active Directory to ensure that the corresponding account entry does exist, has the correct match value data and that the account matching is unique.

The matching value data can be checked in Migrator for Notes by opening the account document and checking the field data value. This field value can then be verified in Active Directory using the Action | Find option and entering the Notes matching field data value.

The account can then be checked for the Active Directory matching Attribute value.

If there are multiple accounts returned in Active Directory for the Notes matching field data then the Active Directory accounts should be verified to determine which account is correct for the Notes account to be migrated to. Then, any additional accounts returned should be checked, and the matching value data, in the Active Directory Attribute, should be removed or corrected for other Notes accounts.

If there are no accounts returned, then Active Directory should be checked for the correct account and the matching value data added to the Active Directory Attribute specified for the matching.

 


The Migrator for Notes Settings are configured for a Custom Match using the Other Domino Field Name “InternetAddress” and Other AD Property Name “mail”. The Person account to be migrated has Internet Address set to “Fix1.Contacts@corp5.cmtsandbox.com”. Also, in Active Directory, the “mail” Attribute should have a value of “Fix1.Contacts@corp5.cmtsandbox.com” for a correct validation match.

 

 

Notes Server Access Validation:

Migrator for Notes requires access to source Domino applications (email .nsf and resources .nsf files) through the Notes client on the Migration Controller Server and any Migration Workers. Access to Exchange mail enabled AD objects is also required to provision these to have mailboxes for migration.

Notes Security Validation:

Check the Notes ID that is currently logged in for access to the Migrator for Notes application. This can be accessed through the Notes client using File | Security | User Security:

This will show the current Notes ID User name:

 

The current Notes ID user name must be present on the mail file Access Control List (ACL), as a Person entry or as part of a Domino Group, for all accounts to be migrated.

To check a mail file ACL for an account in Migrator for Notes, the current Notes Server and Mail File .nsf path can be checked on the imported account document by opening it in Migrator for Notes. The Notes Information tab will have the Notes Mail Server and Notes Mail File Name listed.

The Notes ACL can be accessed by opening the mail file through the Open link. This can be checked in the Notes Administration client by opening the Notes Mail server and locating the mail file in the Files tab.

To check the mail file ACL, in the Notes client, with the mail file open, navigation to File | Application | Access Control. The currently logged in Notes ID should be listed as a Manager on the mail file:

If you receive an error when opening the mail file or if your Notes ID is not listed as a Manager, you will need to switch Notes ID to a different account that has Administration access to the Notes system. This can be done in the Notes client using File | Security | Switch ID. You will be asked to select the file name of the Administration Notes ID and then required to enter the password for that Notes ID.

Once the Notes ID switch is completed you can open the mail file and access the Notes ACL for the mail file. Click on the Add button to apply your Migrator for Notes Notes ID to the ACL or a Group from the Domino Directory that has your Notes ID listed as a member. Be sure that this is set as a Manager for the Access type.

The Notes client being used to manage the Migrator for Notes application will require access to the Notes Servers on which the mail files and resource application are located.

To verify the Notes client connectivity to the Notes Mail Server that is specified in an account document, in Migrator for Notes you can check the network connectivity in the Notes client. To do this use File | Preferences | Notes Ports to perform a trace to the Notes Mail Server. If there are any connection errors reported then the network connectivity should be reviewed for the Windows Operating System on which the Notes client is installed.

 

Notes Template Validation:

To perform a migration of Notes mail file and resource data, the source Notes mail files must have a valid Notes email template applied. This must be a standard Notes email template (.ntf) and meet the required version from the Migrator for Notes Requirements Guide.

To verify the mail file template, check the account document in Migrator for Notes after the mail file is audited:

The template can also be checked directly on the mail file properties by opening the mail file and using File | |Application | Properties.

The Notes template on a mail file can be changed by opening the mail file and using File | Application | Replace Design. This will open a dialog box to select the template server (can be the same as the Notes Mail Server) and then the template to apply. This template should be a standard mail template such as Mail (85) or Mail (9):

This can also be completed through a console command on the Notes Mail Server using the Notes Mail File Name from the Migrator for Notes account document. Additional details on running Notes server console commands can be in the Notes Administration client help topics.

For example, on the Notes Mail Server console run: Load compact –u mail2\f1contacts.nsf * mail9.ntf

 


It is recommended to verify a backup of any mail files that require a template design replacement prior to making any updates.

Active Directory Account Validation:

Migrator for Notes allows for a pre-migration validation process of accounts to be migrated. This will check the target migration system for mail enabled user accounts that do not have mailboxes associated with them in Exchange.

This validation will use the matching field value for the Notes accounts and check this against Active Directory using the Match AD Account To configuration found in Settings | User Provisioning.

 


Migrator for Notes assumes that accounts will have mailboxes provisioned during the migration process workflow, but it is possible to migrate into accounts that already have a mailbox that was enabled outside of the Migrator for Notes processing. If accounts already have a mailbox, the Migrator for Notes validation will report this but the account can still be migrated.

Accounts that do report an error during validation should be checked in Active Directory to ensure that the corresponding account entry does exist, has the correct match value data and that the account matching is unique.

The matching value data can be checked in Migrator for Notes by opening the account document and checking the field data value. This field value can then be verified in Active Directory using the Action | Find option and entering the Notes matching field data value.

The account can then be checked for the Active Directory matching Attribute value.

If there are multiple accounts returned in Active Directory for the Notes matching field data then the Active Directory accounts should be verified to determine which account is correct for the Notes account to be migrated to. Then, any additional accounts returned should be checked, and the matching value data, in the Active Directory Attribute, should be removed or corrected for other Notes accounts.

If there are no accounts returned, then Active Directory should be checked for the correct account and the matching value data added to the Active Directory Attribute specified for the matching.

 


The Migrator for Notes Settings are configured for a Custom Match using the Other Domino Field Name “InternetAddress” and Other AD Property Name “mail”. The Person account to be migrated has Internet Address set to “Fix1.Contacts@corp5.cmtsandbox.com”. Also, in Active Directory, the “mail” Attribute should have a value of “Fix1.Contacts@corp5.cmtsandbox.com” for a correct validation match.

 

 

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択