Select the appropriate option to tell the wizard how it should look for users' archives:
• |
Scan for replicas on the server: Looks for users' archives in replicas that have been uploaded to a particular location on a server. For this option the administrator account specified in the Specify Notes Login Information screen (or in the Notes Server Configuration screen in Notes Migration Manager) must be listed as a manager for all NSF files to be migrated. |
• |
Scan file system directories that I specify: Looks for users' archives via the file system, in a subtree to be specified later in this Wizard. |
A third option is shown only if at least one user has an entry for ArchivePaths or SharedArchiveDirs in the SQL database:
• |
Use ArchivePaths and/or SharedArchiveDirs from database (m of n populated): Looks for users' archives in the locations specified per-user in the ArchivePaths or SharedArchiveDirs column of the SQL database. The “m of n populated” reports the number of users who have an ArchivePaths or SharedArchiveDirs value (m) out of the total number of users in the collection (n). |
Click Next.
This screen appears selected (in the preceding screen) Scan for replicas on the server. The screen asks you to specify the location of the archive replicas by Server and Directory:
• |
Server: The name of the server to which users' archive replicas will be uploaded. The Server specified here must be accessible by the Notes Login User ID file and Password specified in the Specify Notes Login Information screen, or specified in the Default Settings of Notes Migration Manager (see Edit Default Settings: Notes Server Configuration in chapter 1). |
• |
Directory: The directory on the specified Server to which users' archive replicas will be uploaded. |
Click Next.
This screen appears only if you told the wizard (in the Specify How to Find Notes Archives screen) to Scan file system directories to look for users' archives.
Directories must be specified here as UNC paths.
Specify the directory subtree(s) where the wizard should look for users' archives, and click Next.
When the Root directories list contains all the subtrees you want, click Next.
This screen indicates whether file ownership should be determined by checking the Manager entries in a file’s Access Control List (ACL) if ownership cannot be determined using the file profile.
Examine ACLs to determine owner: Select the check box to enable this feature or clear it to disable the feature.
If you enable this feature, you can also specify a list of administrative users to be ignored when the wizard consults the ACLs. Many organizations routinely list one or more administrators as co-Managers of all (or most) files, but you can tell the program to ignore any such administrator/managers that appear in the file ACLs, but who are not the owners of the files. To add one or more new names to the “ignore” list, click Add to display a selection dialog box: Select Administrative Users to Ignore (described in next topic). That dialog box lets you prepare a list of administrator names to add to the “ignore” list, and displays this screen when you click OK.
You can also select one or more names in the “ignore” list and click Remove Selected to remove them from the list of administrator users to ignore.
When the entries correctly specify how file ownership should be determined, click Next to display the Generating Task screen.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center