HP ProLiant Storage Server Release Notes (January 2006)

Storage Server release notes 29
Issue: Unable to move an Exchange database using Remote Storage Wizard
Description On an Exchange cluster node, it may not be possible to move an Exchange
database using the Remote Storage Wizard from the Exchange System Manager.
No available target exchange shares are listed.
Workaround Whenever an Exchange share is created for a clustered Exchange server using
the WebUI, 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 work around 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 in the DOC folder on the NAS Service
Release DVD.
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.
Issue: Incorrect configuration summary report seen when moving individual mailstores
Description When using the Microsoft wizard provided in the Feature Pack to move a single
mailstore to a Windows Storage Server 2003 storage server device from an
Exchange server hosting several different mailstores, the wizard may report that
all files will be moved.
Workaround This is erroneous. Only the files selected for relocation are moved.