Guidelines for using Internet Information Server with HP StorageWorks Storage Mirroring (T2558-96338, June 2009)

Using the Microsoft IIS migration tools
This Microsoft IIS 6.0 Migration Tool automates several of the steps needed to move a Web site or
application from IIS 6.0 to a clean installation of IIS 6.0 running on Windows Server 2003. The tool
transfers configuration data, Web site content, and application settings to a new IIS 6.0 server.
The Microsoft Web Deployment Tool (MS Deploy) automates several of the steps needed to migrate
your Web server or Web site from an IIS 7.0 Web server to a clean installation of IIS 7.0 running
on Windows Server 2008. The tool transfers all IIS configuration, .NET configuration, Web content,
and associated NTFS ACLs and certificates to a new IIS 7.0 server.
Both of these utilities and detailed instructions about how to use them are available for download
from the Microsoft website.
Enabling compression
By enabling compression, you can reduce the amount of bandwidth needed to transmit Storage
Mirroring data. When compression is enabled, the data is compressed before it is transmitted from
the source. When the target receives the compressed data, it uncompresses it and then writes it to
disk. On a default Storage Mirroring connection, compression is disabled.
Because the files that should be included in a replication set may generate a significant amount of
data, you should enable compression for the connection. For more information about enabling
compression, see the HP StorageWorks Storage Mirroring User’s Guide. However, keep in mind that
the process of compressing data impacts processor usage. If you notice an impact on performance
while compression is enabled in your environment, either adjust to a lower level of compression, or
leave compression disabled.
Configuring memory usage
Storage Mirroring uses memory to queue operations and data on both the source and target. Since
the source server is typically running a production application, it is important that the amount of
memory Storage Mirroring and the other applications use does not exceed the amount of RAM in the
system. If the applications require more memory than there is RAM, the system will begin to swap
pages of memory to disk and the system performance will degrade.
As an example, SQL Server will use all of the available system memory when needed by default, and
it may use almost all of the system memory during high-load operations. These high-load operations
are precisely what cause Storage Mirroring to need memory to queue the data being changed by
SQL Server. On a server with 1 GB of RAM running SQL Server and Storage Mirroring, you might
configure SQL Server to use only 512 MB and Storage Mirroring to use 256 MB, leaving 256 MB
for the operating system and other applications on the system. Many other server applications will
use almost all system memory by default, so it is important to check and configure applications
appropriately, particularly on high-capacity servers.
Solution Overview10