Application Manager user’s guide Part number: T2558-96322 Ninth edition: March 2009
© Copyright 2009 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Table of Contents Chapter 1 Introduction ..........................................................1-1 About the Storage Mirroring Application Manager ............................. 1-1 Supported configurations .................................................................. 1-1 Exchange ............................................................................................................. 1-1 SQL ........................................................................................................
Connection settings ......................................................................... 3-13 Route................................................................................................................. Protected Storage Groups ..................................................................................... Mirror type ......................................................................................................... Enable compression ..............................................
Advanced settings ........................................................................... 5-19 Replication set rules ............................................................................................. Failover/failback scripts ........................................................................................ Items to failover .................................................................................................. Advanced settings................................................
Connection settings ......................................................................... 7-13 Route................................................................................................................. Protected Databases ............................................................................................ Mirror type ......................................................................................................... Enable compression ............................................
Verify target data viability ............................................................... 10-5 Relocating the MTA and SMTP pickup path and queues.............................................. 10-7 Managing snapshots ........................................................................ 10-8 Chapter 11 Failover, Failback, and Restoration....................11-1 DNS failover, failback, and restoration ............................................ 11-1 Initiating automatic failover ......................
Introduction This document describes how to use the Storage Mirroring Application Manager to create and validate your application configuration. The Application Manager lets you quickly configure protection for an application without requiring you to haveadvanced knowledge of either Storage Mirroring or your application. The Application Manager works by gathering information about your source andtarget environments, then configuring Storage Mirroring to protect the source.
Exchange 2003 Exchange 2007 Parent/child Yes Yes Child/child Yes Yes NOTE: For Exchange 2007, in a consolidated role environment only the mailbox role is protected. The Hub Transport and Client Access roles are not protected or failed over because they are already installed on the target.
SQL Server 2000 SQL Server 2005 SQL Server 2008 SQL Express Cluster to standalone No No No No Standalone to cluster No No No No Application configurations Named instance Yes Yes Yes Yes Database only Yes Yes (standalone only) Yes (standalone only) Yes Single forest Yes Yes Yes Yes Multiple forest No No No No Parent/child Yes Yes Yes Yes Child/child Yes Yes Yes Yes Domain topology Using the Application Manager with SQL in clustered environments The Application Man
SQL 2000 SQL 2005 SQL 2008 Single forest Yes Yes Yes Multiple forest No No No Parent/child Yes Yes Yes Child/child Yes Yes Yes Application Manager for SharePoint supports only SQL instance mode protection. Database-only protection mode is not available. By default, Application Manager for SharePoint displays the Advanced options and automatically selects to failover Server Name and Hostname (SPNs). These two options are required to make SharePoint failover work correctly.
BlackBerry The Application Manager can be used to configure Storage Mirroring to provide high availability for BlackBerry Enterprise Server using a Microsoft SQL Server database back end. This allows a secondary server to assume the identity and role of a failed server while maintaining the availability of BlackBerry Enterprise Server and/or SQL Server services with minimal disruption or data loss.
A copy of the most recent version of the Storage Mirroring Application Manager NOTE: The version of Storage Mirroring and Storage Mirroring Application Manager must be the same. See the Hewlett-Packard support website to obtain the most recent version of the Application Manager. .NET Framework version 3.5 with service pack 1 or later. If you do not have .NET Framework version 3.5 SP 1 installed, Application Manager will prompt you to install it Microsoft Installer version 3.
Exchange 2007 NOTE: Hewlett-Packard recommends that the Exchange version be the same as the operating system version (for example, Windows Server 2003 running Exchange 2003). Only Exchange 2007 is supported with Windows Server 2008. The source and target servers must both be running a Microsoft-supported operating system/Exchange combination. Both source and target Exchange versions must be identical.
SQL Server 2005 SQL Server 2008 SQL Sever Express NOTE: You should use the same version and service pack of SQL Server on both the source and target servers.
SQL Server 2000, SQL Server 2005, or SQL Server 2008 back-end NOTE: SharePoint protection is currently only supported in a flat domain. Windows Firewall—You will need to open port 6350 for Sharepoint communication. BlackBerry requirements If you are using the Application Manager for BlackBerry, your system must meet the following requirements.
Application notes While the Application Manager greatly simplifies the process of configuring your application for use with Storage Mirroring, Hewlett-Packard recognizes that in some environments a manual process for application configuration is more desirable. However, the manual process is much more time consuming and labor intensive. Hewlett-Packard has application notes which provide guidelines on using manual processes to configure your application with Storage Mirroring.
Navigating the user interface The Application Manager interface is designed to guide you through the process of configuring protection for your servers. The default configuration parameters have been selected to be appropriate for most configurations; however, you may need to modify them for your specific environment. Any changes you make to non-machine specific configuration settings (such as Missed Packets) will become the default the next time you run the Application Manager.
The Application Manager installation uses an active internet connection to download the Microsoft Admin Pack and SQL server backward compatibility (SQLDMO) files. In addition, if you do not have .NET Framework version 3.5 SP1 installed, you will be prompted to install it. Microsoft Installer version 3.0 or later is required to install the .NET Framework.
Menu options Based on the current protection status and/or failover state, the Protection, Monitoring, and Failover/Failback menu options will be updated to display the available commands. If the Application Manager is not in a state that will allow any of these options to be executed, the corresponding menu option(s) will be grayed out (disabled).
Change Application Manager preferences To change display preferences for the Application Manager, select Tools, Options. The Options dialog box will appear. 1. In the Service Listen Port field, enter the value for the Storage Mirroring port to be used for Application Manager communication. The default port is 6320. NOTE: The Storage Mirroring Application Manager Service Listen Port must be the same as the Storage Mirroring Service Listen Port on both the source and target servers.
9. Select the Enable Alternative DNS checkbox to launch Application Manager in \Altdns mode the next time it is opened. For more information, see Using a non-Microsoft DNS Server on page D-1. 10. Select the Display Advanced Options checkbox to launch Application Manager in \Advanced mode the next time it is opened. 11. Click the Clear Cached Credentials button to clear the cached user name and password. 12.
Protecting an Exchange Server To configure protection for your Exchange servers, you will complete the following steps: 1. Install Exchange on the source server and apply any Exchange service packs or patches. Use the default installation options for Exchange. 2. Install Exchange on the target, placing it in the same Exchange organization as the source and verifying that the installation location for the target is the same as the source. Apply any Exchange service packs or patches.
Select a task To protect an Exchange server, open the Application Manager (Start, Programs, Storage Mirroring, Application Manager), then on the Tasks area on the left pane, select Protect Exchange Server. The Manage Exchange page will appear in the right pane. Make sure that the Setup tab is in view. NOTE: You can also launch Application Manager for Exchange by using the command line /exchange option (dtam /exchange).
You may enter a user name for a different domain by entering a fully-qualified user name. The fully-qualified user name must be in the formatNetBIOS domain name\username or username. If you enter a non-qualified name, the default domain will be used. NOTE: When the Application Manager launches, it selects the forest root automatically.
Notice that after the source and target servers are selected, the Protection Status on the Monitor tab changes to Unprotected. NOTE: If you select a target that ismonitoring a connection that has met a failover condition and requires manual intervention, a prompt will appear asking if you want to initiate failover. Enter server login information After you select a server for the first time, you will be prompted to enter a user name and password to use for logging in to the selected server.
Failover settings The Failover tab includes options that will be applied during Exchange failover. Failover type Failover Type indicates what name resolution method will be used to redirect users to the target Exchange server in the event of a source failure. By default, DNS Failover is selected. NOTE: For clustered environments, only DNS failover is supported. DNS failover DNS Failover is the recommended method for failover.
After you select the DNS Failover option, click Configure. The Configure DNS Failover window will appear. Configure the following information for DNS failover: 1. To add additional DNS server IP addresses, type the IP address into the DNS Server field, then click Add. 2. The list box under the DNS Server field contains all DNS IP addresses for the source and target servers. The label after the DNS IP address indicates whether the DNS IP address belongs to the source, target, or both.
7. In the Password field, enter the password that will be used to access/modify DNS records. 8. Click the Test button to validate that DNS failover is configured correctly for the selected DNS server(s) and that the specified credentials are sufficient to update DNS. 9. When the DNS configuration is complete, click OK to save your entries and return to the Configure Protection window.
After you select the Identity Failover option, click Configure. The Configure Identity Failover window will appear. Enter the following information for Identity failover: 1. In the Source IP column, select the source IP address(es) to be monitored for failover. 2. In the Target NIC column, select the target NIC to be used when failover occurs. 3. The Target IP Addresses area displays the IP address(es) of the selected target NIC. 4.
Modifying the default configuration for services may affect whether data can be successfully replicated. Do not modify the services to start/stop unless you are very familiar with Storage Mirroring and Exchange. 1. To add a service, click Add. The Add Service window will appear. 2. Select the Service name from the drop-down box, then click Add; or, type the name of a service, then press Enter. 3. If available, select the Service must be stopped on target checkbox.
Monitor settings The Monitoring tab includes options for configuring how you want to monitor the source server for failure. Configure how you want to monitor the source server for failure. 1. Select the Active Monitoring Enabled option to enable or disable failover for the selected source/target pair. 2. By default, Manual Intervention Required is selected. Manual intervention allows you to control when failover occurs.
Application Monitoring (BETA) By default, application monitor settings are not available in this release of the Storage Mirroring Application Manager. Application monitoring is only available when you launch Application Manager using the command line /exchange /advanced option (dtam /exchange /advanced) WARNING: This feature is currently BETA and should not be used in production environments. 1.
8. (Optional) Click the Clear Cached Credentials button to clear the cached user name and password. Snapshot settings The following allow you to set up snapshots of your target data that can be used when failing over. By default, snapshots are not enabled in the Application Manager. 1. To enable snapshots, select the Enable periodic snapshots checkbox. This will enable the remaining controls. 2. In the Snapshot interval field, select the interval at which you want to perform snapshots (in minutes).
Connection settings The Connection tab includes options that will be applied to the specified source/target connection. Route This setting identifies the Target IP Address that the Storage Mirroring data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring activity.
To refresh the tree view to show new source directories or files that may have been added or removed, select the logical node, then click the Refresh button. If a node in the volumes branch is selected, then the items under that node will be refreshed. Mirror type The following options specify what files you want sent from the source to the target during a mirror. Full—Copies all of the directories and files in the replication set to the target machine.
Replication set rules A replication set defines what directories/files are to be protected by Storage Mirroring. By default, Application Manager selects all of the necessary directories/files to protect Exchange based on your source server configuration. These include all storage groups (system and log files), each database store (mailbox and public folder system and log files), Message Transfer Agent (MTA) files, and SMTP queues (pickup path and queuepath).
Failover/failback scripts Scripts are executed at different points during the failover/failback process to perform the actions necessary to make Exchange available on the appropriate server. Scripts perform steps such as starting/stopping services, modifying mailbox values in Active Directory to point users to the appropriate server, and modifying DNS entries on the DNS server to point users to the appropriate server. Editing scripts is an advanced feature.
Before running Application Manager multiple times (for example, when re-enabling protection after a failover/failback), save a copy of your post-restore and pre-failback batch files. After Application Manager executes, replace the default script file(s) with the customized file(s) that you saved. Force AD replication (Default = selected) When selected, replication is initiated from the domain controller with which the source or target server communicates.
Advanced settings The following options allow you to control what functions Application Manager will perform during configuration. By default, Application Manager performs all of these functions. Individual functions should only be disabled for testing or debugging purposes. NOTE: These options are only available when you launch Application Manager using the command line /exchange /advanced option (dtam /exchange /advanced). 1.
7. Select the Create Failover Monitor checkbox to create a failover monitor on the target to monitor the source for failure. This monitor will use the failover parameters specified during configuration as well as the script files that have been created (Default = selected). 8. When you are finished, click OK. 9. If you want to add the target back to the PF list to which the source belongs, you will need to enable the Restore PF Tree option. a. Select Tools, Actions. b. Choose Display Advanced Options.
Protecting an Exchange Cluster with a Like-Named Cluster This section describes the process used to configure protection for an Exchange cluster with a like-named (also known as a standby) cluster. When you protect a cluster with a like-named cluster, the Application Manager moves the EVS (Exchange virtual server) location from the source cluster to the target cluster.
Failover multiple EVS servers to pre-existing EVS servers on the target. If you choose this option, instead of selecting the like-named equivalent, you will select the target EVS with which to setup protection. The Like-named cluster setup window will not appear since you are not using a like-named target. NOTE: If you are running Exchange 2003 in mixed mode, the first installed EVS contains the MTA (Message Transfer Agent) resource that is needed to communicate with versions prior to Exchange 2003.
3. After you select a like-named cluster for the target, you will need to configure the like-named cluster. After you select the target server, the Like-named cluster setup dialog box will appear. 4. Enter the following information: Target Cluster—Enter the name of one of the target nodes, then click Connect. Network—Select the NIC to which you will assign the IP address. IP Address (to create)—Enter a new IP address for the target to use when it stands in for the source.
6. On the Manage Exchange window, click Configure to open the Configure Protection window, then select the Failover tab. 7. DNS Failover is the only option available for configuring protection with like-named clusters. For more information about DNS failover, see DNS failover on page 3-5. 8. If you want to modify DNS configuration options, click Configure. The Configure DNS Failover window will appear.
9. On the Configure DNS window, you can modify the TTL value for the DNS record. You can also specify the user credentials needed to modify DNS. When you are finished, you can click Test to test the DNS configuration for the selected DNS server(s), or click OK to return to the Configure Protection window. NOTE: Decreasing the TTL value will increase the speed at which clients get the updated information. 10.
Dealing with a failure Graceful failover At the user's discretion, the Application Manager can perform a graceful, or “soft”, failover. A soft failover means the source cluster remains up and running while the EVS is transferred to the target cluster. This can be accomplished by using the failover button in Application Manager.
Protecting a SQL Server To configure protection for your SQL servers using Application Manager, you will complete the following steps: 1. Install SQL on the source server and apply any SQL service packs or patches. Use the default installation options for SQL. 2. Install SQL on the target, verifying that the installation location for the target is the same as the source. Apply the same SQL service packs or patches that were installed on the source.
Select a domain The Domain Name on the main window will be populated automatically with the domain where the Application Manager client resides. If you want to change the domain, type in a domain name for a trusted domain that the Application Manager client can connect to, then press Tab or click on another field. If the domain you entered doesn’t exist or you do not have the credentials to modify Active Directory for the new domain, the Domain Login window will appear.
Select source and target servers If this is your first time to select a SQL server to protect, you may need to click the Advanced Find button to add servers to the Source Server and Target Server fields. For more information, see Add or manage servers on page 5-4.
Add or manage servers If the servers you need do not appear, click the Advanced Find button, or select Actions, Manage SQL Servers. The Manage SQL Servers window will appear. To discover all servers in the domain: 1. Click the Search button. The Discovered Servers list will be populated with all servers that the Application Manager can discover that reside in the domain. 2.
Enter server login information After you select a server for the first time, you will be prompted to enter a user name and password to use for logging in to the selected server. The login account MUST be a member of the Storage Mirroring Admin local security group for the selected server. For more information about permissions, see Recommended Credentials on page A-1. You may enter a user name for a different domain by entering a fully-qualified user name.
Select SQL instances If you launch the Application Manager using the /sql /advanced switch (dtam /sql /advanced), you can select which instances to protect, for example, when an instance is offline or does not exist on the target. This window will appear only when Application Manager is launched in advanced mode and when there are two or more SQL instances (default plus one or more named instance, or two or more named instances and no default instance).
Failover type Failover Type indicates what name resolution method will be used to redirect users to the target SQL server in the event of a source failure. By default, DNS Failover is selected. NOTE: For clustered environments, only DNS failover is supported. DNS failover DNS Failover is the recommended method for failover. Use this option if you want to failover by updating the DNS records associated with the source.
5. To specify the value the Application Manager will establish for Time to Live (TTL) on the source’s affected DNS records, select the Update TTL checkbox, then enter the desired update interval (in seconds). The default is the current maximum TTL of all the source’s A records. The recommended value is 300 seconds (5 minutes). 6. In the Username field, enter the user name that will be used to access/modify DNS records.
If you have client applications that are configured to connect to an IP address ratherthan a server name. After you select the Identity Failover option, click Configure. The Configure Identity Failover window will appear. Enter the following information for Identity failover: 1. In the Source IP column, select the source IP address(es) to be monitored for failover. 2. In the Target NIC column, select the target NIC to be used when failover occurs. 3.
Modifying the default configuration for services may affect whether data can be successfully replicated. Do not modify the services to start/stop unless you are very familiar with Storage Mirroring and SQL. 1. To add a service, click Add. The Add Service window will appear. 2. Select the Service name from the drop-down box, then click Add; or, type the name of a service, then press Enter. 3. If available, select the Service must be stopped on target checkbox.
Monitor settings The Monitoring tab includes options for configuring how you want to monitor the source server for failure. Configure how you want to monitor the source server for failure. 1. Select the Active Monitoring Enabled option to enable or disable failover for the selected source/target pair. 2. By default, Manual Intervention Required is selected. Manual intervention allows you to control when failover occurs.
Application Monitoring (BETA) By default, application monitor settings are not available in this release of the Storage Mirroring Application Manager. Application monitoring is only available when you launch Application Manager using the command line /sql /advanced option (dtam /sql /advanced) WARNING: This feature is currently BETA and should not be used in production environments. 1.
8. (Optional) Click the Clear Cached Credentials button to clear the cached user name and password. Snapshot settings The following allow you to set up snapshots of your target data that can be used when failing over. By default, snapshots are not enabled in the Application Manager. 1. To enable snapshots, select the Enable periodic snapshots checkbox. This will enable the remaining controls. 2. In the Snapshot interval field, select the interval at which you want to perform snapshots (in minutes).
Connection settings The Connection tab includes options that will be applied to the specified source/target connection. Route This setting identifies the Target IP Address that the Storage Mirroring data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring activity.
SQL Instance protection mode requires that the source and target servers both have the exact same version of SQL (major and minor versions) as well as similar logical drive structures (the target must have at least the same logical drives as the source where SQL program and data files are stored). Certain user databases can be de-selected, but the System databases (except for tempdb) are required.
If you select Database Only protection mode, you can select a non-system database and map it to a unique path on the target. NOTE: You must first select the database in order for the Target Path commands to be visible. 1. Select the database you want to re-map, then click the ellipse button. The Choose a Target Folder window will appear. 2. Enter the desired path in the Target Path field, then click OK.
3. To confirm the new path, click Apply. NOTE: If Database-Only protection mode is used to protect SQL Server, attempting to attach a replicated SQL database on the target server after failover can fail when done outside of the Application Manager. The Storage Mirroring service account (typically the target's LocalSystem account) is the account used to attach/detach databases on failover/failback.
Case: Both source SQL servers have a database named “Accounting” (Source3\instance1|Accounting and Source4\instance2|Accounting). You can protect and failover each SQL server’s copy of the database without any issue. NOTE: All the database filenames (*.mdf, *.ldf, and *.ndf ) must either be: Uniquely named (for example, accounting1.mdf and accounting2.mdf), or Uniquely located on the target (for example, c:\Source3\accounting1\accounting1.mdf and c:\Source4\accounting2\accounting2.
Advanced settings The Advanced tab includes advanced configuration options. Replication set rules A replication set defines what directories/files are to be protected by Storage Mirroring. By default, Application Manager selects all of the necessary directories/files to protect SQL based on your source server configuration. These include the SQL application data and transaction logs, tempdb files, and SQL error logs.
5. In the Recursive area, select whether the directory should be recursive (protecting all sub-folders under the directory) or non-recursive (protecting only the files in the directory). 6. Click Add. 7. When you have entered all of your replication set rules, click Close to return to the Advanced configuration tab. NOTE: You will need to manually verify that the rule path is correct since the Application Manager does not validate rule paths. 8.
Any change you make to the script in the editor will be copied to the appropriate server when configuration changes are accepted, thus overwriting any changes that have been made outside the Application Manager. The scripts can be overwritten by certain operations during setup. For example, any changes to configuration options done in the Application Manager will overwrite previous script changes. If you want to make permanent changes to a script, you must modify the appropriate .
Advanced settings The following options allow you to control what functions Application Manager will perform during configuration. By default, Application Manager performs all of these functions. Individual functions should only be disabled for testing or debugging purposes. NOTE: These options are only available when you launch Application Manager using the command line /sql /advanced option (dtam /sql /advanced). 1.
When you have finished configuring the optional protection options, continue with Validate the Configuration on page 9-1. NOTE: If you close the Application Manager prior to enabling protection, your changes will not be saved. You must enable protection in order to save your configuration settings for a source/target pair.
Protecting a File Server To configure protection for your file servers using Application Manager, you will complete the following steps: 1. Install Storage Mirroring on the source and target file servers. See the Storage Mirroring Getting Started guide for more information. 2. Install the Application Manager on page 2-1 3. Select a task on page 6-1 4. Select a domain on page 6-2 5. Select source and target servers on page 6-3 6. (Optional) Configure protection settings on page 6-5 7.
Select a domain The Domain Name on the main window will be populated automatically with the domain where the Application Manager client resides. If you want to change the domain, type in a domain name for a trusted domain that the Application Manager client can connect to, then press Tab or click on another field. If the domain you entered doesn’t exist or you do not have the credentials to modify Active Directory for the new domain, the Domain Login window will appear.
Select source and target servers Click the Advanced Find button to add servers to the Source Server and Target Server fields. For more information, see Add or manage servers on page 6-4. If you select a source/target pair for which you have previously enabled and disabled protection, you may use the existing configuration settings (provided that the source/target connection is not currently active, in which case the existing settings will always be used).
Add or manage servers If the servers you need do not appear, click the Advanced Find button. The Manage Servers window will appear. To discover all servers in the domain: 1. Click the Search button. The Discovered Servers list will be populated with all servers that the Application Manager can discover that reside in the domain. 2.
Configure protection settings If you do not need to change the configuration settings, continue with Validate the Configuration on page 9-1. If you have already enabled protection for a connection and need to change the configuration parameters, you will first need to disable protection as described in Disable protection on page 10-2. To change the default configuration parameters, click Configure from the main Application Manager window, or select Actions, Configure Protection from the menu.
After you select the DNS Failover option, click Configure. The Configure DNS Failover window will appear. Configure the following information for DNS failover: 1. To add additional DNS server IP addresses, type the IP address into the DNS Server field, then click Add. 2. The list box under the DNS Server field contains all DNS IP addresses for the source and target servers. The label after the DNS IP address indicates whether the DNS IP address belongs to the source, target, or both.
8. Click the Test button to validate that DNS failover is configured correctly for the selected DNS server(s) and that the specified credentials are sufficient to update DNS. 9. When the DNS configuration is complete, click OK to save your entries and return to the Configure Protection window.
After you select the Identity Failover option, click Configure. The Configure Identity Failover window will appear. Enter the following information for Identity failover: 1. In the Source IP column, select the source IP address(es) to be monitored for failover. 2. In the Target NIC column, select the target NIC to be used when failover occurs. 3. The Target IP Addresses area displays the IP address(es) of the selected target NIC. 4.
Modifying the default configuration for services may affect whether data can be successfully replicated. Do not modify the services to start/stop unless you are very familiar with Storage Mirroring and the applications running on your server. 1. To add a service, click Add. The Add Service window will appear. 2. Select the Service name from the drop-down box, then click Add; or, type the name of a service, then press Enter. 3. If available, select the Service must be stopped on target checkbox.
Network Access (ICMP)—Storage Mirroring failover uses ICMP pings to determine if the source server is online. If a network device, such as a firewall or router, between the source and target is blocking ICMP traffic, failover monitors cannot be created or used. Replication Service (UDP)—The Storage Mirroring service on the target server sends a ping-like UDP request to the source Storage Mirroring service, which replies immediately to confirm it is running.
Connection settings The Connection tab includes options that will be applied to the specified source/target connection. Route This setting identifies the Target IP Address that the Storage Mirroring data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring activity.
Checksum—(Default) This option performs a checksum comparison calculation. A checksum calculation is a formula applied to blocks of data to determine if the binary make-up of the block is identical. If the checksums on the source and target machine are the same, the block is skipped. If the checksums on the source and target machine are not the same, the block on the source is sent to the target.
To change the replication set rules: 1. Select the Override Generated Rules checkbox. NOTE: When this box is selected, the File Shares control on the Connection tab will be disabled. For more information, see File Shares on page 6-11. 2. To add a replication set rule, click Add. The Add Repset Rule dialog box will appear. 3. In the Rule Path field, type the directory that you want to protect or exclude. 4.
Scripts are automatically generated by Application Manager during configuration. The scripts are copied to the Storage Mirroring installation directory on the specified server using the administrative share for that server’s drive. Script File name Description Failover post_failover_FilePrint.txt A post-failover script is executed after the core failover processes have completed on the target server.
3. Select the Active Directory Hostname (SPNs) checkbox if you want to remove the host SPN (Service Principle Name) automatically from Active Directory for the source and add it to Active Directory for the target during failover (Default = selected). NOTE: If you are using Active Directory, you should enable this option. Otherwise, you may experience problems with failover. Advanced settings The following options allow you to control what functions Application Manager will perform during configuration.
When you have finished configuring the optional protection options, continue with Validate the Configuration on page 9-1. NOTE: If you close the Application Manager prior to enabling protection, your changes will not be saved. You must enable protection in order to save your configuration settings for a source/target pair.
Protecting a SharePoint Server The SharePoint databases will be protected by default and the Application Manager can be used to extend the target web front-end into the source SharePoint configuration. Target database server and front-end web server Source front-end web server Internet Information Services WSS 3.0 or MOSS 2007 Internet Information Services Microsoft SQL Server (default or named instance) WSS 3.
7. Install Storage Mirroring the source and target SQL servers using the installation defaults. See the Storage Mirroring Getting Started guide for details. 8. Install the Application Manager on page 2-1 9. Select a task on page 7-2 10. Select a domain on page 7-2 11. Select SharePoint front end on page 7-3 12. Select source and target servers on page 7-3 13. (Optional) Configure protection settings on page 7-5 14.
If you want to change the domain, type in a domain name for a trusted domain that the Application Manager client can connect to, then press Tab or click on another field. If the domain you entered doesn’t exist or you do not have the credentials to modify Active Directory for the new domain, the Domain Login window will appear. You will be prompted to enter the domain name, user name, and password to use for logging in to the domain. NOTE: Domain names must include a suffix, such as .com, .corp, or .net.
or Validate, a prompt will appear asking if you want to re-use the previous configuration information. Click Yes to re-use the previous information, or click No to revert to the Application Manager default settings. NOTE: If the IP address(es) for the source or target server have changed since you originally configured protection (for example, ifyou configure the source or target in a staging area and then send it to a production location), you must re-configure the protection settings.
3. To add a non-discovered server to the Current Servers list, enter the server name in the field next to the Add button, then click Add. NOTE: In environments with a very large number of servers in Active Directory, you may experience significant delays while the Application Manager searches for SQL servers. To override the automatic scan for SQL servers, you can launch Application Manager through the command line using the /nosqlsearch option (dtam /sharepoint /nosqlsearch).
Failover settings The Failover tab includes options that will be applied during SharePoint failover. Failover type Failover Type indicates what name resolution method will be used to redirect users to the target SharePoint server in the event of a source failure. By default, DNS Failover is selected. DNS failover DNS Failover is the recommended method for failover. Use this option if you want to failover by updating the DNS records associated with the source.
After you select the DNS Failover option, click Configure. The Configure DNS Failover window will appear. Configure the following information for DNS failover: 1. To add additional DNS server IP addresses, type the IP address into the DNS Server field, then click Add. 2. The list box under the DNS Server field contains all DNS IP addresses for the source and target servers. The label after the DNS IP address indicates whether the DNS IP address belongs to the source, target, or both.
8. Click the Test button to validate that DNS failover is configured correctly for the selected DNS server(s) and that the specified credentials are sufficient to update DNS. 9. When the DNS configuration is complete, click OK to save your entries and return to the Configure Protection window.
After you select the Identity Failover option, click Configure. The Configure Identity Failover window will appear. Enter the following information for Identity failover: 1. In the Source IP column, select the source IP address(es) to be monitored for failover. 2. In the Target NIC column, select the target NIC to be used when failover occurs. 3. The Target IP Addresses area displays the IP address(es) of the selected target NIC. 4.
Modifying the default configuration for services may affect whether data can be successfully replicated. Do not modify the services to start/stop unless you are very familiar with Storage Mirroring and SharePoint. 1. To add a service, click Add. The Add Service window will appear. 2. Select the Service name from the drop-down box, then click Add; or, type the name of a service, then press Enter. 3. If available, select the Service must be stopped on target checkbox.
Configure how you want to monitor the source server for failure. 1. Select the Active Monitoring Enabled option to enable or disable failover for the selected source/target pair. 2. By default, Manual Intervention Required is selected. Manual intervention allows you to control when failover occurs. When a failure occurs, a prompt appears and waits for you to initiate the failover process manually.
2. In the Monitor Interval field, enter the interval (in seconds) at which you want to check application health. 3. In the Error Threshold field, enter the number of consecutive errors that can be received before an error alert appears. 4. In the Type of Monitoring area, select one of the following options. Built-in Monitoring Points—Use the default monitoring options. Custom Script—Launch a batch file to check application health.
Snapshot settings The following allow you to set up snapshots of your target data that can be used when failing over. By default, snapshots are not enabled in the Application Manager. 1. To enable snapshots, select the Enable periodic snapshots checkbox. This will enable the remaining controls. 2. In the Snapshot interval field, select the interval at which you want to perform snapshots (in minutes). The minimum interval is 15 minutes. 3.
Route This setting identifies the Target IP Address that the Storage Mirroring data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring activity. For example, you can separate regular network traffic and Storage Mirroring traffic on a machine. The default ports will be used.
You can specify compression for different source/target connections, but all connections to the same target will have the same compression settings. By default, compression is disabled. To enable it, select Enable Compression, then set the level from minimum to maximum compression. Advanced settings The Advanced tab includes advanced configuration options. Replication set rules A replication set defines what directories/files are to be protected by Storage Mirroring.
3. In the Rule Path field, type the directory that you want to protect or exclude. 4. In the Include/Exclude area, select whether to include or exclude the path from the replication set. 5. In the Recursive area, select whether the directory should be recursive (protecting all sub-folders under the directory) or non-recursive (protecting only the files in the directory). 6. Click Add. 7. When you have entered all of your replication set rules, click Close to return to the Advanced configuration tab.
By default, Application Manager generates all the required scripts for you automatically based on your system configuration. You can also edit the scripts to add, modify, or delete specific commands. To edit a script: 1. Click on the button for the script you want to update. The script file will be displayed using your machine’s default editor. 2. Enter your changes. 3. Save the script file.
Advanced settings The following options allow you to control what functions Application Manager will perform during configuration. By default, Application Manager performs all of these functions. Individual functions should only be disabled for testing or debugging purposes. NOTE: These options are only available when you launch Application Manager using the command line /sharepoint /advanced option (dtam /sharepoint /advanced). 1.
SharePoint settings The SharePoint tab includes options you can use to join or extend the target front-end web server to the production SharePoint configuration or web farm. The Application Manager determines the Microsoft SQL server and configuration database used by the source SharePoint web front-end server, then uses that information to connect the specified target web server to the same SharePoint configuration. The target web server specified can be local or remote.
When you select this button, the SharePoint front-end web server specified in the Server Name field will be extended into the source SharePoint configuration. NOTE: After you click Connect Server, it is recommended that you connect to both the source and target front-end web servers using a browser. The process of connecting a front-end web server to an existing SharePoint configuration can take several minutes to complete.
Protecting a BlackBerry Server To configure protection for a consolidated one-to-one configuration of your BlackBerry servers using the Application Manager, you will complete the following steps: 1. Install Microsoft SQL Server on the source, if it is not already installed. NOTE: Microsoft recommends that all service packs be installed independently for each source and target instance. This ensures that operating system files and registry entries are applied appropriately. 2.
Select a task To protect a BlackBerry server, open the Application Manager (Start, Programs, Storage Mirroring, Application Manager), then on the Tasks area on the left pane, select Protect BlackBerry Server. The Manage BlackBerry page will appear in the right pane. Make sure that the Setup tab is in view. NOTE: You can also launch Application Manager for BlackBerry by using the command line /blackberry option (dtam /blackberry).
You may enter a user name for a different domain by entering a fully-qualified user name. The fully-qualified user name must be in the formatNetBIOS domain name\username or username. If you enter a non-qualified name, the default domain will be used. Select source and target servers If this is your first time to select a BlackBerry server to protect, you may need to click the Advanced Find button to add servers to the Source Server and Target Server fields.
Add or manage servers If the servers you need do not appear, click the Advanced Find button. The Manage BlackBerry Servers window will appear. To discover all servers in the domain: 1. Click the Search button. The Discovered Servers list will be populated with all servers that the Application Manager can discover that reside in the domain. 2.
Configure protection settings If you do not need to change the configuration settings, continue with Validate the Configuration on page 9-1. If you have already enabled protection for a connection and need to change the configuration parameters, you will first need to disable protection as described in Disable protection on page 10-2. To change the default configuration parameters, click Configure from the main Application Manager window, or select Actions, Configure Protection from the menu.
After you select the DNS Failover option, click Configure. The Configure DNS Failover window will appear. Configure the following information for DNS failover: 1. To add additional DNS server IP addresses, type the IP address into the DNS Server field, then click Add. 2. The list box under the DNS Server field contains all DNS IP addresses for the source and target servers. The label after the DNS IP address indicates whether the DNS IP address belongs to the source, target, or both.
8. Click the Test button to validate that DNS failover is configured correctly for the selected DNS server(s) and that the specified credentials are sufficient to update DNS. 9. When the DNS configuration is complete, click OK to save your entries and return to the Configure Protection window.
After you select the Identity Failover option, click Configure. The Configure Identity Failover window will appear. Enter the following information for Identity failover: 1. In the Source IP column, select the source IP address(es) to be monitored for failover. 2. In the Target NIC column, select the target NIC to be used when failover occurs. 3. The Target IP Addresses area displays the IP address(es) of the selected target NIC. 4.
Modifying the default configuration for services may affect whether data can be successfully replicated. Do not modify the services to start/stop unless you are very familiar with Storage Mirroring and BlackBerry. 1. To add a service, click Add. The Add Service window will appear. 2. Select the Service name from the drop-down box, then click Add; or, type the name of a service, then press Enter. 3. If available, select the Service must be stopped on target checkbox.
3. In the Method to monitor for Failover field, select the ping method to use when monitoring source IP addresses. Network Access (ICMP)—Storage Mirroring failover uses ICMP pings to determine if the source server is online. If a network device, such as a firewall or router, between the source and target is blocking ICMP traffic, failover monitors cannot be created or used.
Connection settings The Connection tab includes options that will be applied to the specified source/target connection. Route This setting identifies the Target IP Address that the Storage Mirroring data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring activity.
Checksum—(Default) This option performs a checksum comparison calculation. A checksum calculation is a formula applied to blocks of data to determine if the binary make-up of the block is identical. If the checksums on the source and target machine are the same, the block is skipped. If the checksums on the source and target machine are not the same, the block on the source is sent to the target.
3. To add a service, click Add. The Add Service window will appear. 4. Select the Service name from the drop-down box, then click Add; or, type the name of a service, then press Enter. 5. If available, select the Service must be stopped on target checkbox. Most services must be stopped on the target for replication to occur properly. 6. When you are finished entering services, click Close to return to the BlackBerry configuration window. 7.
Replication set rules A replication set defines what directories/files are to be protected by Storage Mirroring. By default, Application Manager selects all of the necessary directories/files to protect BlackBerry based on your source server configuration. These include the BlackBerry application data and transaction logs, tempdb files, and BlackBerry error logs. By default, the Application Manager-generated replication set will be named BB__.
Scripts are automatically generated by Application Manager during configuration. The scripts are copied to the Storage Mirroring installation directory on the specified server using the administrative share for that server’s drive. Script File name Description Failover post_failover__ _bb.bat for distributed environments, or post_failover__ _sql_bb.
Advanced settings The following options allow you to control what functions Application Manager will perform during configuration. By default, Application Manager performs all of these functions. Individual functions should only be disabled for testing or debugging purposes. NOTE: These options are only available when you launch Application Manager using the command line /blackberry /advanced option (dtam /blackberry /advanced). 1.
Saving configuration changes After you have changed the configuration parameters, click OK to apply the settings. If you click Cancel, any changes you have made will be discarded and the previous configuration parameters will be used. When you have finished configuring the optional protection options, continue with Validate the Configuration on page 9-1. NOTE: If you close the Application Manager prior to enabling protection, your changes will not be saved.
Validate the Configuration Click Validate, or select Actions, Validate, to ensure that the source and target servers are configured correctly for failover. A description of the validation activity being performed is displayed in the status bar at the bottom of the Application Manager window, along with status progress indicator. When validation completes, the status progress indicator is removed.
Enabling Protection for a Server Based on the current protection status, the Enable/Disable Protection button (on both the Setup and Monitor tabs) and menu options will be updated to display the available actions. If the Application Manager is not in a state that will allow protection to be enabled, the Enable/Disable Protection button and menu option will be grayed out (disabled).
Application Replication set name SharePoint BB__ BlackBerry SharePointdag01__ While there may be other Storage Mirroring connections between the selected source and target, Application Manager only recognizes connections that it has created. Any connection that has been built by Application Manager will be recognized as a valid connection, regardless of the connection state.
Protection Status Description Failing over Failover from the source to the target is in progress Failed over Target has assumed source role Failing back Failback from the target to the original source is in progress Restoring (% complete) Mirroring (target to source) is in progress The following table describes the possible monitoring status states.
Replication Status Description Mirroring If the file size of the replication set has not been calculated and the data is being mirrored to the target machine, the Replication Status will indicate Mirroring Paused Mirroring has been paused Removing orphans Storage Mirroring is checking for orphan files within the target path location (files that exist on the target but not on the source).
Target Status Description Target path blocked Target pat h blocking is enabled for the connection (Unknown) Target status could not be determined Verify target data viability NOTE: Target data verification can only be used with Exchange and SQL. After you have configured your servers, you can use the Application Manager to run a test that verifies that the database on the target is viable for failover.
You can verify the target stores at any time following the successful completion of a mirror. When you select Actions, Verify Target Data, the Database Verification window will appear. 1. The Status area displays the overall status of the database verification. Click on the status description for more information. 2. Click the Options button to change the services and scripts that are used during the target data verification. The Options dialog box will appear. a.
3. The Results area displays the status of the target Exchange Stores and Storage Groups or SQL databases and instances. Initially, the state of the Stores and Storage Groups is unknown (indicated by a question mark icon); it will change to green when the stores or databases have successfully mounted. 4. The History area displays a log showing the sequence of verification events. 5. The status messages at the bottom of the screen describe the progress of the validation test and protection restoration.
Managing snapshots If snapshots were enabled when you configured protection, you can open the Snapshot Manager to take and delete snapshots. To launch the snapshot manager, select Tools, Manage Snapshots. 1. To take an on-the-fly snapshot, click Take Snapshot. A snapshot will begin immediately. 2. To remove a snapshot, select the snapshot in the list, then click Delete Snapshot. NOTE: In order to fully delete a snapshot, you will need to use the VSAdmin tool.
Failover, Failback, and Restoration If you selected DNS failover, you can use the Application Manager to automate failover, failback, and restoration. If you selected Identity failover, you will need to use the manual processes described in Identity failover, failback, and restoration on page 11-4. If an error occurs during failover or failback, a message box will appear. You can use the Actions menu to launch the failover and failback log files.
Initiating manual failover To initiate a manual failover, select Actions, Failover, or click the Failover button on the Monitoring tab. The Initiate Failover box will appear. 1. Select either Immediate Failover (to begin failover immediately and not wait for the queues to empty), or Graceful failover (to wait for the target queue to empty before failing over). 2. The queues could contain any messages or data recently sent to the target from the source.
4. If you want to use the data from a snapshot, select Revert to specified snapshot, then select the snapshot in the list. Click Initiate Failover to begin failover process. After you select Initiate Failover, the failover process will begin and the Protection Status and Failover/Monitoring Status indicators on the Monitor tab will display Failing Over. NOTE: You cannot cancel or interrupt the failover process.
5. Depending on how long the server has been failed over or the amount of data changed, it may be more efficient to perform a full mirror upon restore. Specify what files you want sent from the target to the source during a mirror. Full—Copies all of the directories and files in the replication set to the target machine. If a mirror has already been completed, another full mirror will overwrite the data on the target. Checksum—(Default) This option performs a checksum comparison calculation.
Before you begin to restore to the original source, resolve the issue(s) that caused the failure. If the source server has to be rebuilt, follow the instructions in Rebuilding the Source on page B-1. Recovering to the original source 1. After repairing/rebuilding the source server offline, bring the server up but leave the network connection disabled by unplugging the cable or disabling the network interface adapter. 2.
File Server Computer Browser SharePoint IISADMIN HTTPFilter SMTPSVC W3SVC SPAdmin SPSearch SPTimerV3 SPTrace SPWriter NOTE: If the source is purely a SQL server (that is, the back-end for a SharePoint configuration), you will not need these services. If the source is a combined SharePoint front-end and SQL back-end, you will need to add these services.
Application Connection name SharePoint BB__ BlackBerry SharePointdag01__ 11. Select Tools, Restoration Manager. 12. Complete the appropriate fields on the Restoration Manager. Original Source—The source where the data originally resided. Restore From—The target that contains the replicated data that users have been updating. Replication Set—The name of the replication set.
Appendix A: Recommended Credentials Application Manager credentials Proper rights must be assigned to the account that is entered when the Application Manager prompts for credentials. If these credentials are not properly assigned, you will be prompted to enter alternate credentials before protection can be enabled. 1. The user must be a member of the Power Users group on the client machine. 2. In order to update DNS, the user account must be part of the Domain Admins group. 3.
6. Select the user to be included in the Storage Mirroring Admin group. 7. Click OK to return to the Local Group Properties dialog box. 8. Click OK to return to the User Manager. 9. Exit the User Manager. Assigning the user to the local servers’ Administrators group The user running the Application Manager must have access to both the servers' administrative shares and have rights to modify the SPN permissions.
Assigning the user to the DnsAdmins group Follow these steps to add a user to the domain DnsAdmins group. 1. Select Start, Programs, Administrative Tools (Common), Active Directory Users and Computers. 2. Right-click the DnsAdmins group and select Properties. 3. Select the Members tab. 4. To add a user to the group, click Add. 5. In Location, click the domain containing the users you want to add, then click OK. 6. In Name, type the name of the user you want to add to the group.
DNS permissions for Windows 2003 SP2 or later Verify that the user has permissions to update DNS. The user must be: The user must be a member of the DnsAdmins domain local group. For details, see Assigning the user to the DnsAdmins group on page A-3. A member of the Server Operator, at the very least, to Deny the source access to the records. The resource record security can be set through the record properties within the DNSMgmt console.
15. Click Add. Type the user or group name you want to use in the Enter the object names to select box, click Check Names to verify your entry or entries, then click OK. 16. In the Permissions for User list, select the Allow checkbox next to the following permissions: Local Access Remote Access 17. Click OK. 18. In the Launch and Activation Permissions section, click Edit Limits. 19. Click Add.
Assigning the user to the local Administrators group Follow these steps to add a user to the local Administrators group. 1. Select Start, Programs, Administrative Tools (Common), Active Directory Users and Computers. 2. Click on Builtin. 3. Right-click the Administrators group and select Properties. 4. Select the Members tab. 5. To add a user to the group, click Add. 6. In Location, click the domain containing the users you want to add, then click OK. 7.
The user running the Application Manager must be an Exchange full administrator at the organizational level, as delegated via the Exchange System Manager at the user level or have delegated rights via the Application Manager Delegate Rights control, described in Delegating Exchange administrative rights on page A-8. The Application Manager will first attempt to impersonate the current logged-on user before prompting for different credentials.
Delegating Exchange administrative rights To assign Exchange administrative rights to a user through the Application Manager, select Tools, Delegate Rights. The Delegate Rights dialog box will appear. 1. The Domain will be populated automatically with the domain where the Application Manager client resides. 2. In the Username field, enter the user name for the account that needs to be assigned Exchange administrative rights. 3.
If the SQL Server service is not using the same domain user account on the source and target servers, the SQL Service Principal Names (SPNs) of the source and target servers must be modified. NOTE: The Application Manager will fix this during validation, granting permission to the local system account on the target. For more information, see Manually set SPN update permissions on page A-6.
Appendix B: Rebuilding the Source The following sections guide you through rebuilding a source server following a failure. Rebuilding the original Exchange source The following steps guide you through rebuilding a source with the same name and IP address as the original source. 1. Install Windows on the source, if necessary, configuring it as a Windows 200x member server with the same name and IP address as the original source.
9. If you accepted the default installation on the original source (before it failed), set Microsoft Exchange Messaging and Collaboration Services and Microsoft Exchange System Management Tools to Disaster Recovery.
Rebuilding the original SQL source 1. Verify that your source machine is not connected to the network. If it is, disconnect it. 2. Resolve the source machine problem that caused the failure. 3. If you must rebuild your hard drive, complete the following. a. Install Windows. Since your source machine is not connected to the network, go ahead and use the source’s original name and IP address. b. Install Storage Mirroring using the installation defaults. c.
Appendix C: Exchange and SQL Failover with BlackBerry If you are using a standalone BlackBerry server with Exchange or SQL, complete the following steps so that the BlackBerry server will recognize when the server that has the BESAdmin account has been failed over. 1. Prior to failing over, shut down the BlackBerry server. 2. After failover, bring the BlackBerry server back up. 3. For BlackBerry Enterprise Server 3.0: a. Open a command prompt on the BlackBerry server and cd to b. c.
Appendix D: Using a non-Microsoft DNS Server In order to update Windows-based Active Directory-Integrated DNS records, the account specified must be a domain user account with appropriate permissions. If you are not using Windows-based DNS (that is, if you are using the /altdns switch), a domain user account is not required. The following steps provide one example of how you can use a BIND DNS client for DNS failover/failback scripting. 1. Go to www.isc.org and download the appropriate BIND DNS client. 2.
Appendix E: Using the Target Data Verification (TDV) Utility There are several options available in the Target Data Verification utility for performing a verification of the target data. The functions in this utility allow you to use a command line interface to perform the same target data verification tests that you can using the Application Manager interface. These options and the full command syntax are described in the following tables.
Options /apptype SQL|EXCH —Select whether to verify SQL or Exchange data on ht e target server /dnsdomain domainname—The fully-qualified name of the domain /srcname source—The source Exchange server name /tarname target—The target Exchange server name /username username (optional)—The user name associated with the domain account that is a member of the Administrators and Storage Mirroring Admin local groups on the source and target servers.
Examples TDV.EXE /help Display TDV usage syntax help for Exchange and SQL. TDV.EXE /apptype EXCH /setpassword mydomain.com\admin mypassword Stores encrypted user ID and password for Exchange. TDV.exe /apptype EXCH /dnsdomain MYDOMAIN.dc /srcname SRCEXCH /tarname TGTEXCH /svc APP /srcexchver 2003 /tarexchver 2003 TDV.exe /apptype EXCH /dnsdomain MYDOMAIN.dc /srcname SRCEXCH /tarname TGTEXCH /svc APP /srcexchver 2007 /tarexchver 2007 /interactive TDV.
Options /apptype SQL|EXCH—Select whether to verify SQL or Exchange data on the target server /srcname source—The source SQL server name /tarname target—The target SQL server name /mode INSTANCE|DATABASE—(required)—Select whether to use SQL instance protection mode or SQL database-only protection mode. /port port (optional)—Define the port used to communicate with the Storage Mirroring service.
Examples TDV.EXE /apptype SQL /help Displays usage for SQL. TDV.EXE /setpassword mydomain.com\admin mypassword Stores encrypted user ID and password for Exchange. > [/port ] TDV.EXE /apptype SQL /srcname mysource /tarname mytarget /mode INSTANCE /svc APP /srcver 2005 /tarver 2005 TDV.EXE /apptype SQL /srcname mysource /tarname mytarget /mode INSTANCE /svc APP /srcver 2000 /tarver 2000 TDV.EXE /apptype SQL /setpassword mydomain.
Appendix F: Using the DNS Failover (DFO) Utility The DNS Failover utility (dfo.exe) can be used in the failover and failback scripts to delete and add host and reverse lookup entries so that the source host name will resolve to the target IP address. For example, the following command could be executed from a command line or included in a batch file: “:Program Files\StorageWorks\Storage Mirroring\dfo.
Options dnsservername—The name of the source domain/zone's primary DNS server sourceFQDN—The source machine's Fully Qualified Domain Name (required (optional; local machine name will be used if missing) for modify) sourceip—The source machine's IP address (required for modify) targetip—The target machine's IP address (required for modify) targetFQDN—The target machine's Fully Qualified Domain Name (required for modify on failback) recordtype—The type of DNS resource recor
Password Encryption /setpassword—Allows the user to store a username/password pairing in an encrypted file for later use. (Optional, but required if /getpassword will be used) NOTE: This function must be run separate from a modify or list activity. /getpassword—Once a username/password pair has been encrypted and stored using /setpassword, this command can be used at the command line to retrieve the password associated with a specific username.
Appendix G: Using the Exchange Failover (EFO) Utility There are several options available in the Exchange Failover utility for configuring Exchange for failover and failback. These options and the full command syntax are described in the following table.
Options (continued) Examples Notes r—(Optional) By itself, this option creates a one-to-one mapping of the groups and mail stores from the source to the target r source_group:target_group—(Optional) The r option with the group names will direct the source group name specified to the target group name specified r source_group, source_mail_store:target_group, source_mail_store—(Optional) The r option with all of the r options will direct the source group
