Once the iSCSI SAN volumes are ready for use on the Exchange Server, it is time to move data over to the volumes. This is a pretty straightforward task that most Exchange administrators will already be familiar with. The tasks and interface are slightly different for Exchange 2003 than for Exchange 2007, so I'll talk about them each briefly.
NOTE: Databases and transaction logs should be moved during periods of low usage and immediately after a backup so that you do not disrupt the users. Moving transaction logs immediately after a full or incremental backup ensures that there are not many transaction logs that must be moved.
Moving Exchange 2003 Data
Exchange 2003 databases and transaction logs are moved using the Exchange System Manager console program. It really does not matter the order in which you move the files. Each storage group's transaction log files are moved by displaying the properties of the storage group (see Figure 3.21). Use the Browse buttons to change the location of both the system path and transaction log locations.
Figure 3.21 Moving a storage group's transaction log files.
When you change the location of the transaction logs or the system path, you will be warned that if you continue, all databases in this particular storage group will be dismounted. Any users using these databases will be disconnected. Depending on the number of logs to move, this may take a considerable amount of time.
Exchange 2003 stores are moved using the properties of the mailbox store. Figure 3.22 shows the Database property page of a mailbox store properties. From this screen, the administrator browses the available disks and specifies new locations for the native content database (EDB file) and the streaming database (STM file).
Figure 3.22 Moving the STM and EDB files.
Just like moving the transaction log files, when the administrator specifies the new location for the EDB and STM files and clicks Apply or OK, the store is dismounted, users are disconnected, and the files are moved. For larger database files, this task can take a considerable amount of time. Exchange databases should not be moved when doing so could interfere with user operations. If you work in a 24 × 7 shop, consider creating new mailbox stores on the new volumes and move the mailboxes over a few at a time.
NOTE: One interesting tip I have learned is that you can also rename the EDB and STM files when you move them. Doing so can be useful if you are trying to standardize your database file names or if you are not happy with how you originally named them.
Moving Exchange 2007 Data
The concepts behind moving Exchange 2007 databases and transaction logs are exactly the same as for Exchange 2003, but there are a few small differences. First is that the transaction logs in Exchange 2003 are 5MB in size while the transaction log files in Exchange 2007 are 1MB; the size was lowered to better accommodate the Exchange 2007 replication technologies such as local continuous replication (LCR), cluster continuous replication (CCR), and standby continuous replication (SCR). The smaller transaction logs do not change the actual volume of transaction logs, this just means there are more of them.
Another difference is that Exchange 2007 does not have the streaming database file, just a native content file (EDB file). The databases are just referred to now as 'databases' rather than stores.
Finally, we have an additional option for moving database files and transaction logs. We can either use the GUI or the command-line interface. Let's look at both methods for moving the files. First is the Exchange Management Console (EMC); this is the GUI for Exchange 2007.
NOTE: Prior to moving Exchange 2007 databases or transaction logs, suspend local continuous replication if you have implemented it.
the system files path. When you are ready, click Move.
Once the wizard has completed, you will notice that the Completion screen includes the Exchange Management Shell (EMS) command that was used to move the log files and system files. The following is the command used to move the Toasters storage group files to the G:SG01-Logs folder:
Move-StorageGroupPath -Identity 'SFOEX01Toasters' -LogFolderPath 'G:SG01-Logs' -SystemFolderPath 'G:SG01-Logs'
Next, we want to concern ourselves with moving the database file. Highlight the database in the EMC, and select Move Database Path task from the Action pane or from the context menu. This will display the Move Database Path wizard (see Figure 3.24). Select the new location for the database file, then click Move. The move process will kick off any users that are connected to this database; the move could take a considerable amount of time if the database file is large.
When the move is completed, the Completion page includes the EMS command that was used to move the database. In this case, to move the Toasters DB to the F:SG01-DBs folder, the following command was used:
Move-DatabasePath -Identity 'SFOEX01ToastersToasters DB' -EdbFilePath 'F:SG01-DBsToasters DB.edb' -CopyEdbFilePath 'C:Program FilesMicrosoftExchange ServerMailboxLocalCopiesToastersToasters DB.edb'
ISCSI SAN STORAGE FOR MICROSOFT EXCHANGE
Tip 1: A basic primer on iSCSI storage architecture
Tip 2: iSCSI SAN storage design options for Microsoft Exchange Server
Tip 3: Setting up Windows iSCSI initiator support for a Microsoft Exchange SAN
Tip 4: Connecting Windows Server and Microsoft Exchange to iSCSI SAN LUNs
Tip 5: Moving Exchange Server databases and logs to iSCSI SAN LUNs
|This chapter excerpt from The Shortcut Guide to Exchange Server 2007 Storage Systems , by Jim McBee, is printed with permission from Realtimepublishers, Copyright 2007.|
This was first published in December 2007