Chat now with support
Chat with Support

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

Section 12. Logs

Logs are available from the Navigation Pane. The log record in the Data Pane below shows information about the last time the Custom Status Report agent was run.

  1. Click Logs in the Navigation Pane

  2. If prompted, select a server to search and click OK:

 

 

Appendix A: Staging Replicas

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:

Creating Replica Stubs on Staging Server(s)

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:

     

Creating Connection Documents

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.

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:

Creating Replica Stubs on Staging Server(s)

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:

     

Creating Replica Stubs for Users

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.

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:

Creating Replica Stubs on Staging Server(s)

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:

     

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating