HP DL160 HP ProLiant Storage Server release notes (5697-7750, November 2008) - Page 7

All-in-One Storage Manager When SQL Server or Exchange databases that are part of user-defined storage Workaround areas are promoted to SQL or Exchange storage areas in ASM, disable and delete all data protection settings for those areas (replication, snapshots, and backup) and reset them using ASM. Issue: Replicating a storage component whose application data exists in a single iSCSI LUN results in extra space utilization on the replication target Description When a single iSCSI LUN is presented to a SQL or Exchange server, the database file and database transaction log file are both created on the volume contained in the iSCSI LUN. If the iSCSI LUN was created on the storage server as a user-defined application, ASM will discover that the database files are now in the volume and it will promote the user-defined application to a SQL Server or Exchange application instance. If the SQL Server or Exchange application instance is replicated to another system, the iSCSI LUN is replicated to the target system twice: once for the database file and again for the log file. In general, the amount of space used on the replication target is equal to the size of each iSCSI LUN that contains multiple components multiplied by the number of components in that iSCSI LUN. If multiple components exist in multiple iSCSCI LUNs, the sum of the product of the sizes is the total consumed space. Snapshot space usage is similar. For example, a single iSCSI LUN of 200MB that contains a volume that has both the database file and the log file would consume 400 MB of space on the replication target (200MB x 2 = 400MB). Likewise, an Exchange server with one storage group of three mail stores on one iSCSI LUN of 500MB and the log and public store on a separate iSCSI LUN of 250 MB would consume 2000MB of space on the replication target (500MB x 3 + 250MB x 2). As a best practice, when configuring storage for SQL Server and Exchange databases, create the database files on one iSCSI LUN and create the associated Workaround log and system files on a separate iSCSI LUN. This way, when storage areas are replicated, there will be one component per iSCSI LUN and space will be utilized on the replication target more efficiently. Issue: Application credential error appears while running the Host a SQL Server Database Wizard Description When attempting to host a SQL Server 2008 database using the Host a SQL Server Database Wizard, an application credential error message may appear. This error might appear because SQL Distributed Management Objects (SQL-DMO) is not installed with SQL Server 2008 by default. Before attempting the following workaround, check to make sure that you have properly entered your SQL Server 2008 credentials. If your credentials are correct and the error message still appears, install SQL-DMO. To install SQL-DMO, run the SQL Server 2005 Backwards Compatibility installer: 1. On the SQL Server 2008 Installation Media, navigate to the \x64\Setup\x64\ Workaround folder on 64-bit application servers and \x86\Setup\x86\ on 32-bit application servers. 2. Double-click SQLServer2005_BC.msi. 3. Follow the on-screen instructions. After installing SQL-DMO, run the Host a SQL Server Database Wizard again. The wizard will complete without error. Issue: ASM attempts to create non-existent storage during discovery 8