Before you migrate your Exchange database and transaction logs to LUNs during configuration, ensure that you do not manually store any files or directories on the LUNs that contain databases, SnapInfo directories, or host a mountpoint.
Note: After adding or moving Exchange Server storage groups and databases, always run the Configuration wizard. If you add more databases or move databases to different LUNs without using the Configuration wizard, you create an invalid configuration that causes backup or restore operations to fail.
Before you migrate your database and transaction logs to LUNs, ensure that you follow these points:
- Do not manually store any directories or files (including system paging files) on the LUNs that are used by databases and transaction logs.
- Do not manually store any directories or files on the LUNs that are used by the SnapInfo directory.
- Do not manually store databases on a LUN that hosts NTFS volume mountpoints.
- Do not place LUNs containing data from different Exchange servers in the same volume, for the following reasons:
- If you create backups for a different server on a volume that contains data from your current server, SnapManager uses all the Snapshot copies for the restore operation, but you can restore only the backups of the other server and not the backups of your current server.
- Conflicting backup schedules between two Exchange servers can lead to busy Snapshot copies.
- Do not place LUNs in the storage system’s root volume, which is reserved for use by Data ONTAP.
