How do I migrate Lotus Notes Resource Rooms?
Lotus Domino is unique in that it can store multiple Resource objects within a single database file, also referred to as a Notes Storage Facility (NSF) file. The MigrationWiz Lotus Extractor software cannot directly access the Resource NSF. To facilitate this, a fake person document is created and linked to a copy of the Resource NSF. The Extractor software will access this fake person document, which is tied to the Resource NSF, to pull the data. Within MigrationWiz, a filter is specified for each Resource migration thread so that the proper information is filtered from the NSF and migrated to the Destination.
Migration of Lotus Domino Resource objects requires the following to be taken into consideration:
- We always recommend migrating Lotus Domino Resource objects at the end of a migration project plan. For instance, once the MX and mail flow cutover is completed and all users are utilizing the new mail system, we recommend then migrating the Resource object data. This will ensure that the latest Resource data is migrated.
- Make a new migration project for all the Resource objects you plan to migrate. Within the Advanced Options of this project, set the concurrent migration value to 3 or lower. This setting will ensure that the NSF file is not overloaded on the Domino Source.
- Be aware that certain steps in this process MAY require a reboot of the Domino environment.
Create the Resource person document.
MigrationWiz must have a person document to use as a migration endpoint on the Lotus Domino Source for the Resource objects. In this step, a fake person document will be created which will be used for all Resource user migrations.
1. Open Lotus Domino Admin and navigate to People & Groups > domain’s Directory > People. Right-click on People and then click on Register Person.
2. Under the Basics tab, give the fake person a Firstname, Lastname, and a password. Checkmark the Advanced box, and then click on Address. Assign a unique internet address to the fake person, such as firstname.lastname@example.org. This value will be used in the Source email field within MigrationWiz. Click on Register All.
Make a copy of your current Resource NSF.
- Note: This step needs to be completed at the end of the migration to ensure that you capture and migrate the latest version of your Resource data.
Resource data is predominately calendar-based items. As with all migration guidance, we recommend that the migration of calendar data is always done during the Full Migration pass at the end of your migration plan. Calendar data changes frequently, and if that data is migrated prematurely, you may not migrate crucial changes to these items.
1. Locate the current Resource NSF file. Typically this file is located in C:\Program Files (x86)\IBM\Lotus\Domino\data and will be called resource.nsf. Your file and location may vary; to verify the Resource NSF location, open up one of the Resource document files in People & Groups > domain’s Directory > Mail-In Databases and Resources > Rooms. Within the Resource document, you should see a File name attribute.
2. Make a copy of the Resource NSF file found in the previous step, and place it into the C:\Program Files (x86)\IBM\Lotus\Domino\data\mail directory. This new file can be renamed if you choose. If the file is renamed, make note of the new name.
Link fake person document to Resource NSF copy.
MigrationWiz will be using the fake person document as a migration endpoint for migration of the Resource objects. To make this work, the newly created person document must be linked to the Resource NSF file that was copied to the C:\Program Files (x86)\IBM\Lotus\Domino\data\mail directory.
1. Open up Lotus Domino Admin and navigate to People & Groups > domain’s Directory > People. Find the fake person document that you created, and double-click on the user.
2. Once the person document is open, click on Edit Person, and navigate to the Mail File attribute. Replace the current mail file entry with the location and name of the copied Resource NSF file. The attribute syntax should be mail\yourfilename.nsf since the Resource NSF file was copied to the C:\Program Files (x86)\IBM\Lotus\Domino\data\mail directory in Step 2 above. Click on Save & Close.
Set up ACL entry on Resource NSF copy.
The administrator account used to connect the MigrationWiz Lotus Extractor to the Domino server must be given manager rights to the Resource NSF copy to allow the Extractor to pull data from the file. This is typically the account that is used to log into the Domino Admin application.
1. Open up Lotus Domino Admin and navigate to Files > mail directory folder. Find the Resource NSF file that was created/copied. Right-click on the NSF file and navigate to Access Control > Manage.
2. Under the Basic tab, ensure that the People, Servers, Groups selection is set to Show All. Within this list, find the user that is being used for the Lotus Extractor local server administrator. Click on this user and set the permissions to Manager and also checkmark the box for Delete Documents. Click on OK to set the permissions.
- Note: At this point, a reboot MAY be required of your Domino environment. Attempt to open up the newly linked Resource NSF by going to People & Groups > domain’s Directory > People. Find the fake person document that was created and had the Resource NSF copy linked to it. Click on the person document and then click on Open Mail File. If the mail file opens up correctly, proceed to the next step. If the NSF does not open, reboot the Domino server.
Set up Resource Migration project.
A separate migration project for Resource objects should be set up to allow customization to the project that is geared toward Resource migration utilizing the MigrationWiz Lotus Extractor.
1. Log in to the MigrationWiz portal, and start a new mailbox migration project. Fill out the required fields as requested by the tool. Click on Additional Options at the bottom left of the project creation screen.
2. Within the Additional Options page, find the Maximum Concurrent Migrations setting and set this to a maximum of 3. Any higher than 3, and there is a risk of potential corruption of data due to overloading of the Source NSF file. Once all settings and credentials have been entered, Save the project.
3. Create a Resource object migration entry for each Resource within the NSF.
- Resource object migration entries within the project will always use the address created from Step 2 of the "Create Resource person document" section above for the Source email field.
- The Destination email field will be the Destination Resource email address where the objects will be migrated to.
4. Each Resource migration entry must have a support option customization to filter out the appropriate objects for that specific migration entry. Select one of the Resource migration entries and then click on the Edit icon.
5. Within each Resource migration entry, a filter must be put in place that will filter objects based on the Resource Name attribute for the Resource. For example, if the Resource Name attribute of a Resource object is "BitTitan Resource/BitTitan Site Profile", the following will be entered in the support options field. Remember the Resource name consists of both the Resource name value and the site profile name it is associated with.
- LotusNotesRoomResourceFilter=BitTitan Resource/BitTitan Site Profile
The logic above would migrate any data found within the Resource NSF copy file that has a Resource name of "BitTitan Resource/BitTitan Site Profile".
- Note: A filter is required for every resource migration. Be sure that each resource migration has a filter in place before attempting a migration pass.
6. Repeat this procedure for every migration entry in the project, and ensure that the filter put in place is correct for the Destination mailbox you are migrating data into.
Start the Extractor and run a Full Migration.
- Note: The Lotus Extractor requires that you have the .NET Framework version 4.6.1 or later installed on the computer on which you install and run the extractor. To determine the .NET Framework version currently installed, follow instructions provided by Microsoft: How to: Determine Which .NET Framework Versions Are Installed.
- Note: If you have already run the MigrationWiz Lotus Extractor before this step, it will be necessary to delete the lotusextractor.csv file, which is located in the root directory where the Lotus Extractor was unzipped. Make sure that no migrations are currently processing, and delete the lotusextractor.csv file. Once the CSV file is deleted, restart the Extractor and let it regenerate the CSV file.
The MigrationWiz Lotus Extractor will generate a CSV the very first time it is started for user mapping. The CSV is generated by an exploration of the Domino directory. Once the CSV is generated, it will not be modified or regenerated without first deleting it.
1. Open LotusExtractor.exe and log in with the administrator credentials from the Domino server and the MigrationWiz credentials where the project created in Step 5 was made.
2. Once the Lotus Extractor is ready for processing, select the migration entries in the project and select Start > Full Migration.