On this page, the wizard prompts you to select a method for registering new storages.
Table 94: User interface elements
| Access online Exchange |
Allows you to register source and/or target storages based on specific online Exchange Server mailboxes or public folder hierarchy. |
| Access Personal Folders (.pst) files |
Allows you to register Personal Folders (.pst) files from multiple folders. |
| Access Archive Manager instance |
Allows you to specify and register an Archive Manager instance. |
Use this page to enter the full path to the properties database (.edb) file that belongs to the offline Exchange Server database you want to register as a storage.
On this page, you can also specify the following:
- Streaming database (.stm) file that belongs to the specified Exchange Server database. You can only specify an .stm file for pre-Exchange Server 2007 databases, as databases originating from Exchange Server 2007 and later do not have .stm file.
Properties database (.edb) and streaming database (.stm) files are final repositories for all Exchange Server database information. An .stm file is an Internet content store that contains transmitted messages with their native Internet content.
By default, the .edb and .stm files of an Exchange Server database are located in the same folder. If the Exchange Server database you register is configured so that its .stm file is located in a different folder, you can specify that folder.
- Transaction log files that belong to the specified Exchange Server database. Transaction log files are used to store changes that are made to the database in memory, thus providing a way to restore transactions that were committed but not written to the database files.
By default, log files are located in the same folder as the .edb file. If the Exchange Server database you register is configured so that its log files are located in a different folder, you can specify that folder.
Table 95: User interface elements
| Path to .edb file |
Enter the full path to the .edb file that belongs to the offline Exchange Server database you want to register as a storage. |
| Path to .stm file |
Enter the full path to the .edb file that corresponds to the specified .edb file.
You can only specify an .stm file for pre-Exchange Server 2007 databases, as databases originating from Exchange Server 2007 and later do not have an .stm file. |
| Path to log files |
Enter the transaction log files that correspond to the specified .edb file. The wizard looks for the log files in the folder you specify and its subfolders. |
| Perform a hard repair on the database |
Performs a hard repair operation on the database. You can select this check box if the .stm file and/or transaction log files are inaccessible, missing, or corrupted. |
| Defragment the database to reduce its size on disk |
Allows you to reduce the size of the specified offline Exchange Server database by defragmenting it. |
Use this page to enter parameters to defragment the offline Exchange Server database being registered and save it to the files you want. Defragmenting an Exchange Server database allows you to reduce the database size on disk.
Table 96: User interface elements
| Path to defragmented .edb file |
Enter the full path at which you want to save the defragmented .edb file of the Exchange Server database. |
| Path to defragmented .stm file |
Enter the full path at which you want to save the defragmented .stm file of the Exchange Server database. |
| Delete the source fragmented database |
When this check box is selected, the wizard deletes the source fragmented Exchange Server database after the defragmentation operation completes and the defragmented database is saved to the specified target files.
When this check box is cleared, the wizard leaves the source fragmented Exchange Server database intact. |
Use this page to defragment Exchange Server databases extracted from backup by using integration with thirdparty backup software. The wizard creates a defragmented copy for each fragmented source Exchange Server database extracted from backup. Optionally, you can delete the source fragmented databases to save disk space.
Database defragmentation is required because the computer from which the Exchange Server databases originate and the Recovery Manager for Exchange computer have different language and locale settings. Defragmentation makes the Exchange Server databases compatible with the language and locale settings on the Recovery Manager for Exchange computer.
Table 97: User interface elements
| Databases to defragment |
Lists the Exchange Server databases that require defragmentation. |
| Delete source databases after successful defragmentation |
Delete the source fragmented Exchange Server database extracted from backup for which a defragmented copy was successfully created. |
