HP StorageWorks X5000 Release Note page 15

Issue:
No mail operations available during database file movement
Description
After the Exchange database files are moved from local storage to the storage
server, any mail client accessing the Exchange server must be restarted to resume
mail operations.
Workaround Refer to Guidelines for Moving Files in the HP Storage Server Service
Release Feature Pack Deployment Guide, located at
information_storage/software/nsas/nas/366581-004.pdf.
Issue:
Database fails to remount after Exchange database movement
Description
On Exchange cluster nodes, Feature Pack CLUI commands may fail to remount the
database after the Exchange database is moved.
Workaround When an Exchange share is created for a clustered Exchange server, all the
member nodes of the cluster should be added to the list of servers that can access
the Exchange share.
Issue:
Error when creating a mailstore
Description
When you try to create a new Microsoft Exchange mailbox store or a new
Exchange public folder store, you receive an error message stating the specified
location is not a fixed drive.
Workaround This issue and the associated workaround are discussed in the Microsoft KB article
839211 at http://support.microsoft.com/?id=839211.
Issue:
Microsoft Exchange Information Store has to be restarted after doing a configuration update
using the Feature Pack
Description
After doing a configuration update using the Microsoft Windows Storage Server
2003 Feature Pack, the Microsoft Exchange Information Store service has to be
restarted before the mail client can access the storage group.
Workaround Refer to Guidelines for Moving Files in the HP Storage Server Service
Release Feature Pack Deployment Guide, located at
information_storage/software/nsas/nas/366581-004.pdf.
Issue:
Unexpected reporting of moved mailstores during configuration change
Description
While using the Remote Storage Wizard from the Exchange System Manager and
performing a configuration change, a report stating that the wizard is moving
all files may be shown.
Workaround The report generated is erroneous. During configuration changes, no data files
are moved.
Issue:
Copy fails when moving multiple mailstores
Description
When moving multiple mailstores in the same storage group to the same Exchange
path, the copy fails if both mailstore databases have the same filename (but
different original paths). For example, you are unable to copy mailstore1
(c:\one\priv1.edb) and mailstore2 (c:\two\priv1.edb) to the same
Exchange share.
Workaround Make sure that you use different filenames for the mailstores.
Exchange databases
Storage Server with Windows Storage Server 2003 R2 release notes
ftp://ftp.hp.com/pub/
ftp://ftp.hp.com/pub/
15