Enterprise Vault™ NSF Migration
- Introduction to Enterprise Vault NSF migration
- NSF migration: scripted
- NSF migration: wizard assisted
- About NSF migrator
- Outline of the NSF migration process
- About planning for NSF migration
- How to edit the welcome messages for NSF migration
- NSF file locations for NSF migration
- How to match NSF files to archives for NSF migration
- Standard mail templates for NSF migration
- NSF migration failed and ineligible items
- Item age limit for NSF migration
- Mail file limits and NSF file access control
- Users' execution control lists for NSF migration
- Multiple instances of NSF migrator
- How NSF migration affects users
- Running NSF migrator
- NSF migration audits
Item age limit for NSF migration
By default, NSF migrator processes all items in NSF files irrespective of their age. This applies both to items converted to shortcuts, and to other items that are moved to mail files, such as items that are not eligible for migration.
You can control this behavior by specifying an age threshold, as a number of days, in two registry DWORD values, ShortcutMoveRestrictDays and NotesMoveRestrictDays. Both values are under this key:
HKEY_LOCAL_MACHINE
\Software
\Wow6432Node
\KVS
\Enterprise Vault
\AgentsBoth values are set to 0 by default, which means no threshold is set. To set thresholds, change the DWORD values to a number of days.
When ShortcutMoveRestrictDays is set to a non-zero value, NSF migrator migrates all eligible items and creates shortcuts. Initially, all the shortcuts are in the NSF file. NSF migrator does not move the shortcuts to items older than the specified number of days, from the NSF file to the mail file.
When NotesMoveRestrictDays is set to a non-zero value, other items, such as those ineligible for migration, are moved to mail files only if they are within the number of days specified. Otherwise, they remain in the NSF files.