HP StorageWorks Storage Mirroring Application Manager for Windows release notes Part number: T2558-96088 First edition: February, 2008
Legal and notice information © Copyright 2005, 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Version: 5.0 Description This version of the Storage Mirroring Application Manager (SMAM) is an updated release that supersedes all previous releases, including previous releases of the Exchange Failover utility, Exchange Failover Toolkit, and eXchange Protection Wizard.
DTAM /EXCHANGE Launches the Application Manager in the Exchange context DTAM /SQL Launches the Application Manager in the SQL context DTAM /SharePoint Launches the Application Manager in the SharePoint context DTAM /FilePrint Launches the Application Manager in the File server context DTAM /Advanced Launches the Application Manager with Advanced options available.
11. The Dynamic updates setting for the DNS zone should be set to Secure only. Otherwise, you must disable dynamic registration on the source server in order to prevent the source from reclaiming its DNS record. Exchange 1. 2. 3. 4. 5. 6. 7. 8. 9. When NAT or certain VPNs exist between the Application Manager and either the source or target, the Application Manager will be unable to configure protection due to limitations of WMI.
4. When setting up SQL servers in a workgroup, make sure the source server’s NIC does not register the IP addresses with DNS. 5. When using a domain service account for SQL server 2005 that is not in the domain admins or local admins group, the replicated databases will not mount on the target. This is due to security restrictions at the file system level. The workaround is to place the SQL 2005 service account in the local admins group of the target. 6.
