Video - How Do I Specify Per-User Locations for Notes Source Data? (4321760)

How Do I Specify Per-User Locations for Notes Source Data?

Per-user locations for users' source data are (if necessary) specified in the SQL Server database. To edit the contents of that database, you must export the data to a .tsv (tab-separated-values format) file, then edit the contents of the table, and then import the edited .tsv file back into the SQL Server database. If you are unfamiliar with this export-edit-import process, see the topic How Do I Edit Exported Directory and Collections Data Tables? found in the Migrator for Notes to Exchange (MNE) User Guide.

Note: After importing values into any of the listed columns, you must run the Notes Data Locator Wizard so the data stores that are specified by the values you provide are located and the user's datastore information is updated. To run the Notes Data Locator Wizard, select the Locate Notes Data Stores page in MNE Migration Manager.

For Personal Address Books (PABs): To designate the locations of user PABs, enter the appropriate per-user values into one of these columns (not both):

PABPaths column: The specific UNC path and filename for a user's Notes address book(s). Multiple address books can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file name are given, and file ownership is not checked. If a directory (only) is specified, all PABs found in the directory are assumed to be owned by the user. The server!! is the path to the Domino data directory and the dirname\filename.nsf is relative to the Domino data directory. Examples:

server!!user\address_book.nsf
\\server\data\addr1.nsf | \\server\data\addr2.nsf
\\server\data\user\address_book.nsf
server!!user\
\\server\data\

SharedPabDirs column: A file system directory or Notes server directory that contains NSF files for multiple users. This column can be used to specify a more specific set of directories to scan for a user's data, so the application can scan a subset of a larger shared directory structure and determine the owner based on profile documents and/or ACLs. This is useful if a group of users to be migrated shares a directory structure and you can't be certain that all address books belong to just one user. If a file system path is specified here, ownership is checked based on the profile documents and/or ACLs. If a Domino server directory path is used, the admin account used must be listed as a manager in the ACLs. Examples:

\\server\data\groupdir
server!!groupdir
server!!groupdir\address_book.nsf
\\server\data\groupdir\address_book.nsf

Actions to Migrate PAB files with Migrator for Notes to Exchange (MNE) :

1. Find the users Names.NSF and copy them to a central location
2. Export the desired user collection from MNE to TSV (Tab Separated Value)
3. Modify the PABPaths/SharedPabDirs column as described above (full path or UNC path to NSF file)
4. Once complete, import the TSV file back into MNE.
5. Run the Quest Notes Migrator for Exchange 'Locate Notes Data Store' wizard and choose the new "Use PABPaths and/or SharedPABDirs from database" radio button (Note: If this does not appear, then the TSV import did not work)
6. Once complete, use the MNE 'Migrator User Data' wizard to move the Personal Address Book(s).

=> For Archives: To designate the locations of user archives, enter the appropriate per-user values into one of these columns (not both):

ArchivePaths column: The specific UNC path and filename for a user's Notes archive file(s). Multiple archives can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file name are given, and file ownership is not checked. If a directory (only) is specified, all archives found in the directory are assumed to be owned by the user. The server!! is the path to the Domino data directory and the dirname\filename.nsf is relative to the Domino data directory. Examples:

\\server\data\arch1.nsf | \\server\data\arch2.nsf
server!!user\archive_jdoe.nsf
\\server\data\user\archive_jdoe.nsf
server!!user\jdoe_archives\
\\server\data\

SharedArchiveDirs column: A file system directory or Notes server directory that contains NSF files for multiple users. This column can be used to specify a more specific set of directories to scan for a user's data, so the application can scan a subset of a larger shared directory structure and determine the owner based on profile documents and/or ACLs. This is useful if a group of users to be migrated shares a directory structure and you can't be certain that all address books belong to just one user. If a file system path is specified here, ownership is checked based on the profile documents and/or ACLs. If a Domino server directory path is used, the admin account used must be listed as a manager in the ACLs. Examples:

\\server\data\archives
server!!archives
server!!archives\archive_jdoe.nsf
\\server\data\archives\archive_jdoe.nsf

*Please Note that MNE treats Journal Files as Archives. Please use the following actions to move either Archive or Journal Files:

Actions to Migrate Archive/Journal files with MNE:

1. Find the users Archive file(s) and copy them to a central location
2. Export the desired user collection from MNE to TSV (Tab Separated Value)
3. Modify the ArchivePaths/SharedArchiveDirs column as described above (full path or UNC path to NSF file)
4. Once complete, import the TSV file back into MNE.
5. Run the Quest Notes Migrator for Exchange 'Locate Notes Data Store' wizard and choose the new "Use ArchivePaths and/or SharedArchiveDir from database" radio button (Note: If this does not appear, then the TSV import did not work)
6. Once complete, use the MNE 'Migrator User Data' wizard to move the Archive(s).

For Mail Files: To specify per-user locations and filenames for users' source mail files in the SQL Server database rather than from entries in the Data Migration Wizard, enter the appropriate per-user values into this column.

MailFilePath column: The specific path and NSF filename to a user's mail file, used when an administrator knows the specific path and NSF file name for each user. Example:

\\server\home\user\jdoe.nsf

If the MailFilePath column does not exist or is left empty, the program will look for the user's mail file in the path entered in the Notes Data Locator Wizard (on the Specify Notes Mail File Directories screen).

Actions to migrate Mail files with Migrator for Notes to Exchange:

1. Find the Mail file and copy them to a central location
2. Export the desired user collection from MNE to TSV (Tab Separated Value)
3. Modify the MailFilePath column as described above (full path or UNC path to NSF file)
4. Once complete, import the TSV file back into MNE.
5. Run the MNE 'Locate Notes Data Store' wizard and choose the new "Use MailFilePath from database" radio button
   • Note: If this does not appear, then the TSV import did not work
6. Once complete, use the MNE 'Migrator User Data' wizard to move the Mail File.

Note: If migrating a Notes database local to the MNE server, have the MailFilePath specified to the folder containing the mailbox.  Select "Through the file system" to ensure it does not reach out to the mail server copy of the mailbox.