Dell PowerVault 770N, Руководство по развертыванию

Страница: 40 / 73

Moving Exchange Files to a NAS System
Feature Pack Deployment Guide 40
Mapping Exchange Shares to a Local Drive
During a full move or a configuration update, a DFS link is created for each database (.edb) file and
streaming database (.stm) file that is moved. If transaction logs are moved, a single DFS link is
created for the log file path.
The link names have the format {
servername
.
n
}, where
servername
is the name of the Windows
Storage Server computer that hosts the files and
n
is a sequentially assigned number that uniquely
identifies the link on the host computer. The curly brackets ( { } ) are included in the name. The link
target is the UNC address.
The address that is stored in Active Directory is the address that is mapped to the local drive letter
being used for Exchange shares.
For more information about how the DFS links are created and mapped for use by Exchange Server
2003, see Chapter 2, “Installing the Feature Pack.” For a full discussion of how link names and link
targets relate to the current location and Active Directory location of remotely stored Exchange
database files and transaction logs, see Appendix A, “Interpreting the Detailed Report Log File.”
Processing a Configuration Update
During a configuration update, the remote storage tool performs the following steps:
1.
Dismounts any mounted stores that will be moved. If the transaction logs for the storage
group are being moved, the remote storage tool dismounts all stores of the storage group.
2.
Updates Active Directory with the specified destination locations.
3.
On the local Exchange server, creates a DFS link for each database (.edb) file and each
streaming database (.stm) file that was moved, and a link for the transaction logs if they
were moved. The tool then updates the registry with the DFS links and link targets.
Because the tool does not check for the existence of the source files or the state of the database
during a configuration update, the configuration update can complete successfully, even if the
files no longer exist or are no longer accessible.
As in the full move, the remote storage tool dismounts any mounted stores involved in the move.
However, the tool does not physically move the files; nor does it attempt to remount any stores
that were dismounted after updating the configuration. To restore access from the Exchange
database, the Exchange administrator must physically move the files to the destination locations
that were configured and then remount any stores that were dismounted.
Notice
After you perform a configuration update, it is important to finish physically copying the files to their
destination locations before attempting to mount the Exchange stores. Mounting the Exchange stores
before all of the existing transaction logs have been moved will invalidate previous backups. It is
recommended that you perform a full backup of Exchange immediately after successfully mounting
the storage groups.
A configuration update can succeed even if the databases that are involved have not been shut down
correctly. Moving databases that have not been shut down correctly will prevent the automated
recovery of those databases by the Microsoft Exchange Information Store service.
Processing a Move for an Exchange Cluster
If the Windows Storage Server computer stores databases and transaction logs for an Exchange
server cluster, each move is performed on the virtual server that owns the Exchange server that
currently owns the Exchange storage group. When you move a storage group for an Exchange
cluster, all nodes in the cluster must be online; otherwise, the move will not begin.
Each node in the cluster has its own stand-alone DFS root, which is used for Exchange files that
are hosted on Windows Storage Server computers. However, the DFS root is mapped to the
same drive letter on all of the servers so that the DFS links for Exchange storage groups on all of
the servers have the same local drive mapping.