Recover User’s Guide First Edition (November 2009) Part Number: T5437-96008
© 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 particul ar 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 Table of Contents 1 Storage Mirroring Recover overview 14 Core operations 15 Storage Mirroring Recover workloads 19 Full-server workload protection 19 Application workload protection 20 Virtual workload protection 21 Cluster workload protection 24 Supported configurations 27 Supported application configurations 31 Using the Application Manager with Exchange in clustered environments 33 Using the Application Manager with SQL in clustered environments 34 Supported Hyp
Data protection 78 Establishing a connection using the automated Connection Wizard 78 Creating a replication set 80 Establishing a connection manually using the Connection Manager 82 Establishing a connection across a NAT or firewall 87 Simulating a connection 88 Data workload failover 91 Configuring failover monitoring 91 Updating shares on the target 98 Editing failover monitoring configuration 98 Removing failover monitoring configuration 98 Server settings 98 Identifying a server
Taking snapshots of the target 127 Configuring failover monitoring and processing 128 Mapping network configuration on the target for post-failover 129 Routing data transmissions 130 Mirroring data 130 Compressing data 131 Using firewalls with full-server workloads 131 Full-server ports 131 Microsoft Windows ports 132 Hardware ports 132 Application protection 133 Protecting an Exchange server 133 Verify the Exchange environment (recommended) 134 Launching the Exchange protection wo
Configuring a like-named cluster 161 Enabling protection for like-named Exchange clusters 165 Protecting a SQL server 166 Launch the SQL protection workflow 166 Selecting a domain 167 Selecting source and target servers 168 Configuring SQL protection settings 171 Selecting SQL instances 172 Configuring failover settings 172 DNS failover 173 Identity failover 176 Configuring monitor settings 179 Configuring snapshot settings 182 Configuring connection settings 182 SQL instance (de
Configuring connection settings 210 Configuring advanced settings 212 Saving configuration changes 216 Protecting a SharePoint server 217 Launch the SharePoint protection workflow 219 Selecting a domain 219 Selecting servers 220 Configuring protection settings 223 Configuring failover settings 224 DNS failover 224 Identity failover 227 Configuring monitor settings 230 Configuring snapshot settings 232 Configuring connection settings 233 Configuring advanced settings 236 Configu
Configuring advanced settings 262 Saving configuration changes 267 Completing BlackBerry protection 267 Validate the configuration 268 Enable protection for an application server 269 Enable protection 270 Disable protection 271 Virtual machine protection 273 Protect a virtual machine on an ESX server 273 Port configuration 273 Configuring VMware ESX server login 274 Connecting to the Storage Mirroring Recover for Virtual Infrastructure server 276 Protecting a virtual machine 279 Pre-
Selecting volumes to protect 320 Selecting a target server 322 Selecting the target volume 324 Configuring the replica virtual machine 325 Setting protection options 326 Reusing virtual hard disks 329 Protect virtual machines running on the Microsoft Hyper-V platform 330 Firewall configuration 330 Starting the Hyper-V protection workflow 331 Selecting the Hyper-V source machine 333 Selecting a virtual machine on the Hyper-V server 334 Selecting a target server 335 Selecting the targe
Workload monitoring 383 Data workloads 384 Monitoring a data workload 384 Monitoring failover monitoring 392 Monitoring a full-server workload 395 Monitoring an application workload 397 Virtual workloads 402 Monitoring protected virtual machines 402 Monitoring protection jobs 405 Monitoring Hyper-V protection jobs 406 Monitoring connections 406 Viewing connection summary information 407 Managing a connection 410 Viewing connection details 415 Monitoring a cluster workload 420 M
Monitoring Performance Monitor statistics 494 Performance Monitor statistics 494 SNMP 499 Configuring SNMP on your server 499 SNMP traps 500 SNMP statistics 502 Error codes 506 Failover 513 Failing over data and cluster workloads 514 Full-server workload failover 516 Failing over using the Full-Server Failover Manager 516 Failing over from the command line 518 Application failover 520 Failing over using DNS 522 Failing over using identity 525 Initiating a failover 525 Failing
Rebuilding an Exchange or SQL source 548 Failing back using DNS 551 Failback and restoration 551 Failing back using identity 553 Re-enabling protection 558 Connections 559 Data queues 560 Queuing data 561 Auto-disconnect and auto-reconnect Reconnecting automatically 565 566 Pausing and resuming target processing 568 Blocking writing to the target paths 569 Disconnecting a connection 570 Mirroring 571 Stopping, starting, pausing, or resuming mirroring 572 Mirroring automatically
Verification 600 Verifying manually 601 Verifying on a schedule 603 Configuring the verification log 605 Verify target data viability 610 Data transmission 614 Stopping, starting, pausing, and resuming transmission 615 Scheduling data transmission 616 Limiting transmission bandwidth 622 Compressing data for transmission 626 Snapshots 628 Snapshots for data workloads 630 Snapshot states 630 Automatic snapshots 634 Scheduling snapshots 634 Taking snapshots manually 635 Managing
Setting SPN update permissions 649 Exchange credentials 650 SQL credentials 652 SharePoint credentials 654 BlackBerry credentials 654 Changing the account used to run the Storage Mirroring service 655 Configuring the Storage Mirroring service for Active Directory 657 Utilities 659 DNS failover (DFO) utility 660 Using a non-Microsoft DNS server 664 Using the Target Data Verification (TDV) utility 666 Using the Exchange Failover (EFO) utility 674 Consoles 678 Data workload consoles
Clearing maintained security credentials 692 Saving and reusing configuration options 692 Storage Mirroring Recover Application ManagerConsole 693 Changing Application Manager preferences 694 Application Manager menu commands 696 Virtual workload consoles 698 Storage Mirroring Recover for Virtual Infrastructure console Server management in Storage Mirroring Recover for Virtual Infrastructure 698 699 Managing VirtualCenter servers 699 Managing ESX servers 702 Managing the e-mail server 705
Storage Mirroring Recover overview Storage Mirroring Recover ensures the availability of critical workloads. Using real-time replication and failover, you can protect data, individual applications, entire servers, or virtual machines. Identify your critical workload on your production server, known as the source, and replicate the workload to a backup server, known as the target. The target server, on a local network or at a remote site, stores the copy of the workload from the source.
Core operations Storage Mirroring Recover performs four basic types of operations.
Replication Replication is the real-time transmission of file changes. Unlike other related technologies, which are based on a disk driver or a specific application, the Storage Mirroring Recover replication process operates at the file system level and is able to track file changes independently from the file’s related application. In terms of network resources and time, replicating changes is a more efficient method of maintaining a realtime copy of data than copying an entire file that has changed.
The failover target assumes the network identity of the failed source. When the target assumes the identity of the source, user and application requests destined for the source server or its IP address(es) are routed to the target. When partnered with the Storage Mirroring Recover data replication capabilities, failover routes user and application requests with minimal disruption and little or no data loss.
Restoration Restoration provides an easy method for copying replicated data from the target back to its original location on the source. The process only requires you to select the source, target, and the appropriate replication set. There is no need to select files or to remember where the data came from on the source since that information is maintained by Storage Mirroring Recover.
Storage Mirroring Recover workloads Building on Storage Mirroring Recover core operations, you can protect specific workloads to meet your protection goals. ● ● ● Full-server workload protection—You can protect an entire server, including the data and system state, which is the server's configured operating system and applications. In the event of a failure, the target becomes the source.
Application workload protection The Application Manager lets you quickly configure protection for an application without requiring you to have advanced knowledge of either Storage Mirroring Recover or your application. The Application Manager discovers all servers running a designated application in your environment so that you can determine which servers are not protected.
which provide guidelines on using manual processes to configure your application with Storge Mirroring. Virtual workload protection Protect an ESX virtual machine using host-level protection Storage Mirroring Recover for Virtual Infrastructure uses host-level protection to protect entire virtual machines on the VMware ESX Server platform by actively replicating virtual machine files between datastores.
Storage Mirroring Recover for Virtual Infrastructure cannot be used to protect a Storage Mirroring Recover Virtual Recovery Assistant for ESX recovery Note: appliance. Storage Mirroring Recover for Virtual Infrastructure includes support for VMware Distributed Resource Scheduler (DRS).
Storage Mirroring Recover Virtual Recovery Assistant uses Storge Mirroring to configure the replication set and monitor failover conditions. Protect an entire physical or virtual machine using a Microsoft Hyper-V virtual machine Storage Mirroring Recover can be used to protect entire physical or virtual machines with Microsoft Hyper-V virtual machines.
Protect a Hyper-V virtual machine using host-level protection You can use the Storage Mirroring Console to protect virtual machines running on the Microsoft Hyper-V platform. Storage Mirroring Recover replicates all of the files associated with the virtual machine for one Microsoft Hyper-V host to another. You can: ● ● ● ● Automate the discovery and protection of virtual machines. Map the source virtual switches for a virtual machine to the available virtual switches on the target Hyper-V host.
In a GeoCluster configuration, data is stored on volumes local to each node and replicated to each node in the cluster using Storage Mirroring Recover. Resources and groups are handled in the same manner as a standard cluster. Instead of assigning one group by SCSI drive, you assign one group per logical volume. If a server, disk, group, or network interface should fail, MSCS relocates the failed group to another node, which contains the replicated copy of the data, thus maintaining availability.
26 of 739
Supported configurations Storage Mirroring Recover is an exceptionally flexible product that can be used in a wide variety of network configurations. To implement Storage Mirroring Recover effectively, it is important to understand the possible configuration options and their relative benefits. Storage Mirroring Recover configuration options can be used independently or in varying combinations.
One-to-one, active/active Description Each server acts as both a source and target actively replicating data to each other Applications This configuration is appropriate for failover and critical data backup. This configuration is more cost-effective than the Active/Standby configuration because there is no need to buy a dedicated target server for each source. In this case, both servers can do full-time production work.
Many-to-one Description Many source servers are protected by one target server. Applications This configuration is appropriate for offsite disaster recovery. This is also an excellent choice for providing centralized tape backup because it spreads the cost of one target server among many source servers. ● Considerations ● ● The target server must be carefully managed. It must have enough disk space and RAM to support replication from all of the source systems.
One-to-many Description One source server sends data to multiple target servers. The target servers may or may not be accessible by one another. Applications This configuration provides offsite disaster recovery, redundant backups, and data distribution. For example, this configuration can replicate all data to a local target server and separately replicate a subset of the mission-critical data to an offsite disaster recovery server.
Chained Description The source servers sends replicated data to a target server, which acts as a source server and sends data to a final target server, which is often offsite. Applications This is a convenient approach for integrating local high availability with offsite disaster recovery. This configuration moves the processing burden of WAN communications from the source server to the target/source server.
Exchange 2003 Exchange 2007 One to one Yes Yes Many to one No No One to many No No Cascaded (chained) No No Cluster to cluster Yes Mailbox role only Cluster to standalone Yes Mailbox role only Standalone to cluster No No Cluster support Application configurations 2000/2003 front-end server No N/A 2000/2003 back-end server Yes N/A 2007 consolidated roles N/A Mailbox role only 2007 distributed roles N/A Mailbox role only Single forest Yes Yes Multiple forest No No Paren
Transport, and Client Access roles installed. In these configurations, Storge Mirroring will not replicate any data associated with the Hub Transport/Client Access data; however, the target Hub Transport/Client Access roles function properly when failing over the source Mailbox role, allowing necessary operations to resume.
SQL Server 2000 SQL Server 2005 SQL Server 2008 SQL Express Cluster support Cluster to cluster No Yes Yes No Cluster to standalone No Yes Yes No Standalone to cluster No No No No Yes Yes Yes Yes Yes Yes (standalone only) Yes (standalone only) Yes Application configurations Named instance Database only Domain topology Single forest Yes Yes Yes Yes Multiple forest No No No No Parent/child Yes Yes Yes Yes Child/child Yes Yes Yes Yes Using the Application Manager
SQL 2000 SQL 2005 SQL 2008 Source to target topology One to one Yes Yes Yes Many to one No No No One to many No No No Cascaded (chained) No No No No No No Cluster to standalone No No No Standalone to cluster No No No Cluster support Cluster to cluster Application configurations WSS Yes Yes Yes MOSS 2007 Yes Yes Yes Single forest Yes Yes Yes Multiple forest No No No Parent/child Yes Yes Yes Child/child Yes Yes Yes Domain topology ● ● ● ● Application Manag
● The SharePoint Admin account used to install WSS 3 or MOSS 2007 on the source web front-end is required to extend a target web server into the SharePoint configuration.
The Application Manager can be used to configure Storage Mirroring Recover 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.
● ● ● Many to One—Virtual machines from multiple Hyper-V hosts can be protected on a single Hyper-V target host. One to One—Virtual machines from a single Hyper-V host can be protected on a single Hyper-V target host. Many to Many—The Storage Mirroring Console can manage multiple Hyper-V source and target hosts, allowing you to protect virtual machines from multiple Hyper-V hosts on multiple Hyper-V targets.
Storage Mirroring Recover requirements Each Storage Mirroring Recover server must meet minimum requirements, although if you are protecting certain workloads, your servers may need to meet additional requirements. Verify that each server meets the requirements for the function of that machine. Additionally, the machine where you will be running the console must also meet some basic requirements.
Source and target server requirements ● Operating system—There are different licenses depending on the operating system you are using. Be sure you have the correct license for your operating system. Each of the Windows 2003 operating systems listed require Service Pack 1 or later. (In-Guest protection means Storage Mirroring Recover runs inside the virtual server to provide workload protection for data and/or applications running on the guest operating system.
● ● ● ● ● Windows 2008 Storage Server Edition i386 and x64, Small Business Server Standard and Premium x64, Foundation Server, Essential Business Server x64, Web Server i386 and x64, Standard Edition i386 and x64, Enterprise Edition i386 and x64, Itanium Edition , Datacenter Edition i386 and x64 In-Guest Protection—Unlimited Virtual Host Standard Edition ● Windows 2008 Standard ● Guest Protection—5 ESX hosts and unlimited Hyper-V hosts Virtual Host Advanced Edition ● Windows 2008 Standard and Ente
Operating System Any Windows i386 operating system Minimum System Memory 128 MB Any Windows x64 operating 512 MB system ● Recommended System Memory At least 512 MB At least 1024 MB Disk Usage—The amount of disk space required for the Storage Mirroring Recover program files is approximately 70 MB. You will need to verify that you have additional disk space for Storage Mirroring Recover queuing, logging, and so on.
● ● ● Windows Management Instrumentation (WMI)—Storage Mirroring Recover is dependent on the WMI service. If you do not use this service in your environment, contact technical support. Windows Firewall—The installation program will automatically attempt to configure port 6320 for Storage Mirroring Recover. If you cancel this step, you will have to configure that port manually. Snapshots—Storage Mirroring Recover uses the Microsoft Volume Shadow Copy service for snapshot capabilities.
Full server workload requirements If you will be protecting your entire server, there are no separate source or target server requirements. However, the general source and target requirements are high-level requirements that each server must meet for the full-server functionality. A target server may meet these requirements but may not be suitable to stand-in for a source in the event of a source failure.
Application workload protection requirements Application Manager requirements The Application Manager will run from any client (or server) on any Microsoft Windows operating system that has access to the domain in which the servers are located. Storage Mirroring Recover Application Manager should be run on a machine that is not a domain controller.
installed, an error message will appear that states "An error has occurred while verifying access credentials for server . Please enter valid credentials for a user that is in the Double-Take Admin group on the server ." You will not actually need to enter credentials; however, you will need to install the admin pack for your version of Windows. ● ● ● ● If you are using the Target Data Verification feature, you will need to install the Volume Shadow Copy Service SDK (Vshadow.
● ● ● Note: ● ● ● ● ● ● ● ● ● ● HP 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 Application Manager does not check the edition of Exchange 2007 (Enterprise or Standard); however, it is able to differentiate between service pack levels.
● ● ● In a parent\child domain, at least one domain controller in the child domain must designated as a global catalog server. The Application Manager does not support configurations where Exchange and the domain controller are on the same node of a cluster. While installing Exchange Server 2003 on a domain controller is a supported operation, it is not generally recommended. HP also does not recommend this configuration.
● ● Note: ● ● ● ● ● ● You should use the same version and service pack of SQL Server on both the source and target servers.
● Before enabling protection on a SQL Cluster, it is strongly recommended that you configure your cluster so that there is only one instance of SQL Server per owning node on your source and target cluster. For example, SQL instance 1 could be on node 1 and SQL instance 2 could be on node 2, but instances 1 and 2 should NOT reside on the same owning node.
Note: ● ● ● Windows SharePoint Services (WSS) version 3 ● Microsoft Office SharePoint Server (MOSS) 2007 WSS 3.0 service pack 1 is required for Windows 2008. MOSS 2007 service pack 1 is required for Windows 2008. Each source back-end server and target server must be running a licensed copy of SQL Server 2000, SQL Server 2005, or SQL Server 2008. Windows Firewall—You will need to open port 6350 for SharePoint communication. Note: SharePoint protection is currently only supported in a flat domain.
● Note: ● ● ● HP recommends that the Exchange version be the same as the operating system version (for example, Windows Server 2003 running Exchange 2003). 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. To perform target data verification, you must be using Exchange 2003 with service pack 1 or later.
Virtual server workload requirements Protecting an ESX virtual machine using host-level protection ● ● Client and service—The Storage Mirroring Recover for Virtual Infrastructure client and service can be installed on servers running one of the following operating systems: ● Microsoft Windows XP (32-bit) ● Microsoft Windows 2003 (32-bit) ● Microsoft Windows 2008 (32- or 64-bit) ● Microsoft Windows Vista (32-bit) VirtualCenter server—VMware VirtualCenter 2.
virtual NICs to a target ESX 3.0.x server which only supports 4 virtual NICs. ● Windows Firewall—Ports 6331, 443, and 22 must be opened on the source and target ESX hosts. For more information, see Configuring ports. In order to use automatic e-mail notification, you must add VI_Service.exe to the exception list of most anti-virus and spam filters. In addition, you may need to Note: open port 25 in your antitrust software to allow SMTP e-mail. For more information, see Setting e-mail notification options.
● ● VirtualCenter server—VMware VirtualCenter 2.0.1 or later is required. Target ESX host server—The target VMware ESX host server is a physical machine running VMware ESX Server 3.0.x, ESX 3.5 classic, or ESX 4.0 classic, Enterprise edition or higher. ESXi versions 3 and 4 are also supported as long as ESXi is managed by VCenter or VSphere. Note: ESX Server 3.01 or later with HotRemove patch #6921838 is required.
● Windows Firewall—You will need to verify that port 6330 is open for Storage Mirroring Recover Virtual Recovery Assistant communications. For more information, see Configuring firewalls with ESX. The following table identifies supported source server/virtual recovery appliance configurations.
Windows 2003, 32-bit source Windows 2008, 64-bit target Hyper-V host ● yes Windows 2003, 64-bit source yes Windows 2008, 32-bit source yes Windows 2008, 64-bit source yes Ports—Ports 6320, 6330, and 135 must be opened on the source and target Hyper-V hosts. For more information, see Configuring firewalls.
Cluster workload protection requirements ● Standard cluster—If you will be protecting a standard cluster configuration, with a shared SCSI disk, there are two additional requirements. ● ● ● Network—The cluster's private network should be a unique subnet so that Storage Mirroring Recover will not attempt to use an unreachable private network. Volumes—The source and target should have identical drive mappings.
Storge Mirroring Console requirements There are various Storage Mirroring Recover consoles, many of which are being phased out over time. To help consolidate the consoles and help you locate the necessary workflows to complete your work, use the console called Storge Mirroring Console. You must meet the following requirements for the Storge Mirroring Console. ● ● Operating system—The Storge Mirroring Console can be run from a source or target.
Installation Review Storage Mirroring Recover requirements and Installation and upgrade notes then use the installation instructions appropriate for the type of workload you are protecting. ● ● ● ● ● Specific data—If you are protecting data only, you can install using the standard installation program or use the command-line automatic installation process.
Installation and upgrade notes Review the following installation and upgrade notes before beginning your installation or upgrade. ● ● ● ● ● Since Storage Mirroring Recover installs device drivers, it is recommended that you update your Windows Recovery Disk, before installing or making changes to your servers. For detailed instructions on creating a recovery disk, see your Windows reference manuals. Make sure that you select the option to backup the registry when building the repair disks.
● ● ● ● Client Source Target Supported 5.2 5.1 5.0 No 5.2 5.1 5.1 or 5.2 Yes 5.2 5.2 5.0 or 5.1 No 5.2 5.2 5.2 Yes When performing a rolling upgrade, update the target servers first. After the upgrade is complete, the sources will automatically reconnect to the targets. Upgrade the sources when convenient. If you are using a chained configuration, update the last target first, then update the middle server acting as both a source and target, and update the production source last.
Installing or upgrading Storage Mirroring Recover Use these instructions to install Storage Mirroring Recover or upgrade an existing Storage Mirroring Recover installation. 1. Close any open applications. 2. Start the installation program using the appropriate instructions, depending on your media source. ● ● CD—Load the Storage Mirroring Recover CD into the local CD-ROM drive. If auto-run is enabled, the installation program will start automatically.
8. If desired, specify where the Storage Mirroring Recover files will be installed. 9. Click Next to continue. 10. You will be prompted to enter your activation code information. Your Activation Code is a 24-character, alpha-numeric activation code which applies the appropriate license to your installation. You must have a valid activation code to use Storage Mirroring Recover. Enter your code and click Add. 11. Click Next to continue. 12. The next screen will depend on the activation code you entered.
15. During the installation, you may be prompted to add an exception to the Windows Firewall for Storage Mirroring Recover. Click OK to add the port exception. If you Cancel the port modification, you will have to manually modify your firewall settings for Storage Mirroring Recover processing. 16. After the files have completed copying, click Finish to exit the installation program.
Installing or upgrading Storage Mirroring Recover for Virtual Infrastructure If you are upgrading from Storage Mirroring Recover for Virtual Infrastructure version 1.0 or 2.0: Before you begin the upgrade, first put all Note: active protection jobs into Stop mode (in order to avoid re-synchronization after upgrade). Next, upgrade the Storage Mirroring Recover for Virtual Infrastructure service. Finally, upgrade the clients. Storage Mirroring Recover for Virtual Infrastructure is a client/server application.
3. When the installation program begins, the HP Setup Launcher appears allowing you to install software and view documentation for various applications from HP. The listed applications will depend on which products are included on the CD or in the web download. To install Storage Mirroring Recover for Virtual Infrastructure, select Storage Mirroring Recover from the list of products and then select Install Storage Mirroring Recover for Virtual Infrastructure . 4.
appropriate license to your installation. You must have a valid activation code to use Storage Mirroring Recover for Virtual Infrastructure. Click Next to continue. 11. If you are satisfied with the selections you have made and are ready to begin copying the Storage Mirroring Recover files, click Install. 12. After the files have completed copying, click Finish to exit the installation program. Following an uninstall, the product leaves the log files on the system.
Installing Storage Mirroring Recover automatically The Storage Mirroring Recover installation program can accept command-line parameters which allow you to automate the installation or upgrade process by running an unattended, or silent, installation. The automatic process allows you to pass parameters through to the installation program instead of entering information manually during the installation or upgrade.
DOUBLETAKEFOLDER="C:\Program Files\HP\Storage Mirroring" QMEMORYBUFFERMAX=128 DISKQUEUEFOLDER="C:\Program Files\HP\Storage Mirroring" DISKQUEUEMAXSIZE=UNLIMITED DISKFREESPACEMIN=50 DTSERVICESTARTUP=1 PORT=6320 SET_FWPORT=Y In the sample DTSetup file, the server Alpha would use the parameters defined under the [Alpha] heading. The server Beta would use the parameters defined under the [Beta] heading. All other servers would use the configuration under the [Config] section.
Parameter Valid Values available disk space expands DiskFreeSpaceMin Any integer representing the amount of disk space, in MB, that must remain free at all times ● DTServiceStartup ● Y or 1—Start the Storage Mirroring service automatically N or 0—Do not start the Storage Mirroring service automatically This parameter is not applied if your DTSetupType is DTCO. Any integer between 1024 and 65535 that identifies the Windows Firewall port used for Storage Mirroring Recover.
xxxx.exe where xxxx is four numbers that specify the build number. For example, your setup file might be called setup.exe or setup_1352.exe. 7. Run one of the following case-sensitive commands from the temporary directory, depending on if you have setup.exe or setup_xxxx.exe where xxxx is a four digit build number. setup /s /v"DTSETUPINI=\"c:\dtinstall\DTSetup.ini\" /qn" setup_xxxx /s /v"DTSETUPINI=\"c:\dtinstall\DTSetup.
The command must be run from the shared folder as well as specifying that directory for the .ini file. Note: Substitute your mapped drive for m:\. Spacing is critical with this command. A space should precede /s, /v, and /qn but should not appear anywhere else for the command to work correctly. C:\>net use m: \\server_name\share The command completed successfully C:\>M: M:\>setup_1352 /s /v"DTSETUPINI=\"m:\DTSetup.
Configuring your cluster for GeoCluster installation If you want to use a GeoCluster configuration, where data is stored on volumes local to each node and replicated to each node in the cluster, complete the cluster configuration appropriate for the operating system you are using. Configuring your Windows 2003 cluster In a typical Windows 2003 MSCS shared disk cluster configuration, the quorum resource, by default, is the Local Quorum and is located on the first shared disk in the cluster.
3. Add your additional nodes to the cluster. See your Windows documentation for instructions on how to add nodes to the cluster. 4. Install GeoCluster on each node of the cluster. 5. Configure your quorum. See your Windows documentation for instructions on configuring the quorum appropriate for your environment. 6. If desired, you can install GeoCluster on non-clustered client machines if you want to use Cluster Administrator to control the GeoCluster resources.
Use the following instructions as a guideline for configuring your Windows 2008 cluster. See your Windows cluster documentation as a complete reference. 1. Login with an account that has administrative rights on the domain and the local machine. 2. Create the cluster, if it is not already created. See your Windows documentation for instructions on how to create a cluster. 3. Configure a Node and File Share Majority quorum. See your Windows documentation for instructions on how to configure the quorum. 4.
Workload protection Storage Mirroring Recover flexible configurations allow you to protect different workloads depending on the needs of your organization. ● ● ● ● ● Specific data—You can protect specific data (volumes, directories, files, and/or wildcards). In the event of a failure, the data you protected is available on the target. Entire server—You can protect an entire server, including the data and system state, which is the server's configured operating system and applications.
Data protection Protecting specific data consists of two main tasks - creating a replication set (to identify the data to protect) and connecting that replication set to a target. You have the following data protection options. ● ● ● ● Automated process—If you would like to use an automated process that walks you through both the replication and connection tasks, you only need to complete the steps Establishing a connection using the automated Connection Wizard.
2. The Connection Wizard opens to the Welcome screen. Review this screen and click Next to continue. Note: At any time while using the Connection Wizard, click Back to return to previous screens and review your selections. 3. If you highlighted a source in the Replication Console, the source will already be selected. If it is not, select the Storage Mirroring Recover source. This is the server where the files reside that you want to protect.
● ● ● Send all data to a single path on the target—This option sends all selected volumes and directories to the same location on the target. The default location is \source_name\replication_set_name\volume_letter. Send all data to the same path on the target—This option sends all selected volumes and directories to the same directories on the target. For example, c:\data and d:\files on the source will go to c:\data and d:\files on the target.
click on the source name and select New, Replication Set. 2. A replication set icon appears in the left pane under the source. By default, it is named New Replication Set. Rename the newly inserted replication set with a unique name by typing over the default name and pressing Enter. This process is similar to naming a new folder in Windows Explorer. 3. Expand the tree under the replication set name to view the volume and directory tree for the source.
5. After selecting the data for this replication set, right-click the new replication set icon and select Save. A saved replication set icon will change from red to black. Establishing a connection manually using the Connection Manager After you have created a replication set, you can establish a connection through the Connection Manager by connecting the replication set to a target. 1. From the Replication Console, open the Connection Manager to establish the connection.
● ● ● ● ● Source Server—Specify the source server that contains the replication set that is going to be transmitted to the Storage Mirroring Recover target. Replication Set—At least one replication set must exist on the source before establishing a connection. Specify the replication set that will be connected to the target. Target Server—Specify which Storage Mirroring Recover target will maintain the copy of the source’s replication set data.
available must be equal to or greater than the on-disc size of the sparse file. If you are mirroring and replicating multiple mount points, your directory mapping must not create a cycle or loop. For example, if you have the c: volume mounted at d:\c and the d: volume mounted at c:\d, this is a circular configuration. If you create and connect a replication set for either c:\d or d:\c, there will be a circular configuration and mirroring will never complete.
● ● Full Mirror—All files in the replication set will be sent from the source to the target. File Differences—Only those files that are different based on date, time, and/or size will be sent from the source to the target. ● Send data only if Source is newer than Target—Only those files that are newer on the source are sent to the target. If you are using a database application, do not use the newer option unless you know for certain you need it.
work with the global checksum setting on the Source tab of the Server Properties. ● Remirror on Auto-Reconnect—In certain circumstances, for example if the disk-based queues on the source are exhausted, Storage Mirroring Recover will automatically disconnect connections (called auto-disconnect) and then automatically reconnect them (called auto-reconnect).
4. Click Connect to establish the connection. The settings on the other tabs of the Connection Manager are advanced settings. You can modify any of them before or after establishing your connection. Note: If you decide to enable orphan file processing while you are establishing your connection, orphan files will not be immediately processed when you create the connection. This setting is for processes that are run after a connection is already established (remirror, auto-remirror, verification, and so on).
Storage Mirroring service for the new port setting to take effect. 2. You need to configure your hardware so that Storage Mirroring Recover traffic is permitted access through the router and directed appropriately. Configure your router identifying each Storage Mirroring Recover server, its IP address, and the Storage Mirroring Recover and router ports. Also, note the following caveats.
Storage Mirroring Recover performance. The DTInfo utility can be found on the product CD or in the Storage Mirroring Recover installation directory. 1. From the source where you will be running the TDU, run DTInfo.exe. It may take several minutes for DTInfo to finish processing. After DTInfo processing is complete, a \support subdirectory will automatically be created in the Storage Mirroring Recover installation directory. A .zip file will contain the information gathered.
● ● ● ● ● ● ● ● Source Server—Specify the source server that contains the replication set that is going to be simulated to the TDU. Replication Set—At least one replication set must exist on the source before establishing a connection. Specify the replication set that will be connected to the TDU. Target Server—Select the Diagnostics target. Route—After selecting the Diagnostics target, the Route will automatically be populated with Throughput Diagnostics Utility (TDU).
Data workload failover When you established your data workload protection, you only protected the data. You still need to establish failover monitoring, so that the target can stand in for the source in the event of a source failure, and your end users can access the data from the target. ● Configuring failover monitoring ● Updating shares on the target ● Editing failover monitoring configuration ● Removing failover monitoring configuration Configuring failover monitoring 1.
● ● Click Browse to search for a machine. Select a domain from the list box at the top of the Select Machine dialog box to list the available machines for that domain. Highlight a source to be monitored and click OK. Click Custom. Enter the name of the server and click Add. Specify the IP address and subnet mask of the specified server and click OK. Click OK again. The Insert Source Machine dialog closes and the Monitor Settings dialog remains open with your source listed in the Names to Monitor tree. 6.
To achieve shorter delays before failover, use lower Monitor Interval and Missed Packets values. This may be necessary for IP addresses on machines, such as a web server or order processing database, which must remain available and responsive at all times. Lower values should be used where redundant interfaces and high-speed, reliable network Note: links are available to prevent the false detection of failure.
addresses to fail. ● One Monitored IP Address Fails—Failover begins when any one of the monitored IP addresses fails. If each IP address is on a different subnet, you may want to trigger failover after one fails. 13. If Manual Intervention is enabled, Target Data State at Failover will be disabled because the same options will be presented to you at failover time. If Manual Intervention is disabled, the options will be enabled so that an option can be selected to occur automatically when failover occurs.
Note: ● ● If you are monitoring multiple IP addresses, IP address conflicts may occur during failover when the number of IP addresses that trigger failover is less than the number of IP addresses that are assumed by the target during failover. For example, if a source has four IP addresses (three public and one private), and two of the three public addresses are monitored, but all three public addresses are configured to failover, a conflict could occur.
Automatic share failover only occurs for standard Windows file system shares. Other shares must be configured for failover through the failover scripts or created manually on the target. See Macintosh shares or NFS Shares for more information. If you are failing over Windows shares but your source and target do not have the same drive letters, you must use the All to One selection when establishing your Storage Mirroring Recover connection.
19. If you are failing over or failing back hostnames, you need to specify an Active Directory user that has update privileges within Active Directory. Click Credentials and identify a user and the associated password that has privileges to create and delete SPNs. The username must be in the format fully_qualified_domain\user. Click OK to return to the Monitor Settings dialog box. Note: The Active Directory account password cannot be blank. 20.
21. Click OK to return to the Monitor Settings dialog box. Failover scripts will run but will not be displayed on the screen if the Storage Mirroring service is not set to interact with the desktop. Enable this option through the Services applet. With these flexible scripting features, application failover using Storage Note: Mirroring Recover can be seamless to the end user. HP tests many of the popular applications on the market today.
Scripting Guide. This section contains the following topics, each corresponding to a tab in the Server Properties dialog box.
4. Specify the server identity information. Some of the fields are informational only. ● Nickname—A nickname is saved in the Replication Console workspace, therefore, it only appears in the Replication Console on this server. It is not communicated across the network. If you export a workspace and use it on another Storage Mirroring Recover server, the server nickname will appear there also. ● Machine—This is the actual server name. This field is not modifiable.
server was manually inserted into the Replication Console server tree. Active Directory indicates a server is registered with Windows Active Directory. ● ● Operating System—The server’s operating system version is displayed. Product Information—The Storage Mirroring service name and the build number are displayed. 5. Click OK to save the settings. Licensing a server From the Replication Console, you can manage your server activation codes.
4. Enter an activation code and click Add. Repeat for each activation code. 5. If you need to remove a code from the server, highlight it in the list and click Remove. 6. Click OK to save the settings. Configuring server startup options From the Replication Console, you can configure server startup options for each Storage Mirroring Recover server. 1. Open the Replication Console and right-click the server on the left pane of the Replication Console. 2. Select Properties 3. Select the Setup tab.
4. Specify the server setup and source startup options. ● ● Log Statistics Automatically—If enabled, Storage Mirroring Recover statistics logging will start automatically when Storage Mirroring Recover is started. Enable Task Command Processing—Task command processing is a Storage Mirroring Recover feature that allows you to insert and run tasks at various points during the replication of data. Because the tasks are userdefined, you can achieve a wide variety of goals with this feature.
If you disable this option on a source server, you can still submit tasks to be processed on a target, although task command processing must be enabled on the target. ● ● ● ● Advertise service with Active Directory—If enabled, the Storage Mirroring service registers with Windows Active Directory when the service is started. Automatically Reconnect During Source Initialization—If enabled, Storage Mirroring Recover will automatically reconnect any connections that it automatically disconnected.
Configuring network communication properties for a server 1. Open the Replication Console and right-click the server on the left pane of the Replication Console. 2. Select Properties 3. Select the Network tab. 4. Specify the network communication properties. ● ● Default Address—On a machine with multiple NICs, you can specify which address Storage Mirroring Recover traffic will use. It can also be used on machines with multiple IP addresses on a single NIC.
Queuing data You should configure queuing on both the source and target. 1. Open the Replication Console and right-click the server on the left pane of the Replication Console. 2. Select Properties. 3. Select the Queue tab. 4. Specify the queue settings for the server. ● Folder—This is the location where the disk queue will be stored. Storage Mirroring Recover displays the amount of free space on the volume selected.
reliability, this should be a dedicated, non-boot volume. The disk queue should not be on the same physical or logical volume as the data being replicated. Also, for best results, select a location that is on a different volume as the location of the Windows pagefile.
applications use does not exceed the amount of RAM in the system. If the applications are configured to use more memory than there is RAM, the system will begin to swap pages of memory to disk and the system performance will degrade. For example, by default an application may be configured to use all of the available system memory when needed, and this may happen during high-load operations.
in the Linux system log. By default, the alert will be generated when the queue reaches 50%. 5. Click OK to save the settings. Configuring source data processing options 1. Open the Replication Console and right-click the server on the left pane of the Replication Console. 2. Select Properties 3. Select the Source tab. 4. Specify how the source will process data.
● Replicate NT Security by Name—Storage Mirroring Recover allows you to replicate Windows permission attributes by local name as well as security ID (SID). By replicating Windows security by name, you can transmit the owner name with the file. If that user exists on the target, then the SID associated with the user will be applied to the target file ownership. If that user does not exist on the target, then the ownership will be unknown. By default, this option is disabled.
information associated with any files in your replication set can be transmitted to the target. ● ● ● Maximum Pending Mirror Operations—This option is the maximum number of mirror operations that are queued on the source. The default setting is 1000. If, during mirroring, the mirror queued statistic regularly shows low numbers, for example, less than 50, this value can be increased to allow Storage Mirroring Recover to queue more data for transfer.
4. Specify how the target will process data. ● ● ● ● Target Mirror Capacity High Percentage—You can specify the maximum percentage of Windows system memory that can contain mirror data before the target signals the source to pause the sending of mirror operations. The default setting is 20. Target Mirror Capacity Low Percentage—You can specify the minimum percentage of Windows system memory that can contain mirror data before the target signals the source to resume the sending of mirror operations.
If you are going to use failover, any target paths that are blocked will automatically be unblocked during the failover process so that users can modify data on the target after failover. During a restoration, the paths are automatically blocked again. If you failover and failback without Note: performing a restoration, the target paths will remain unblocked. You can manually block or unblock the target paths by right-clicking on a connection.
Encrypted files that are deleted on the source will only be moved on the target if the move location is on the same volume as the replication set target path. Compressed and sparse files that are deleted on the source will be moved on the target, although the compression and sparse flags will only be retained on the target if the move location is on the same volume as the replication set target path. 5. Click OK to save the settings. Specifying the Storage Mirroring Recover database storage files 1.
4. Specify the database files that store the Storage Mirroring Recover replication set, connection, and scheduling information. ● ● ● ● Folder—Specify the directory where each of the database files on this tab are stored. The default location is the directory where the Storage Mirroring Recover program files are installed. Replication Set—This database file maintains which replication sets have been created on the server along with their names, rules, and so on. The default file name is DblTake.db.
4. Specify the location and file names for the log and statistics files. ● ● Folder—Specify the directory where each of the log files on this tab are stored. The default location is the directory where the Storage Mirroring Recover program files are installed. Messages & Alerts ● ● ● Maximum Length—Specify the maximum length of the client and service log files. The default size is 1048576 bytes and is limited by the available hard drive space.
verification process. The replication set name will be prefixed to the base log file name. For example, since the default is DTVerify.log, the verification log for the replication set called UserData would be UserData DTVerify.log. ● ● ● ● Append—Mark the Append check box if you want to append each verification process to the same log file. If this check box is not marked, each verification process that is logged will overwrite the previous log file. By default, this check box is selected.
4. If you will be using any customized scripts (mirroring, failover, task command processing, and so on) specify a Username, Password, and Domain to use when running the scripts. If you do not specify any security credentials, the account running the Storage Mirroring service will be used. 5. Click OK to save the settings. E-mailing event messages You can e-mail Storage Mirroring Recover event messages to specific addresses.
4. Select Enable notification. Note: Any specified notification settings are retained when Enable notification is disabled. 5. Specify your e-mail settings. ● ● Mail Server (SMTP)—Specify the name of your SMTP mail server. Log on to SMTP Server—If your SMTP server requires authentication, enable Log on to SMTP Server and specify the Username and Password to be used for authentication. Your SMTP server must support the LOGIN authentication method to use this feature.
● ● ● From Address—Specify the e-mail address that you want to appear in the From field of each Storage Mirroring Recover e-mail message. The address is limited to 256 characters. Send To—Specify the e-mail address that each Storage Mirroring Recover e-mail message should be sent to and click Add. The e-mail address will be inserted into the list of addresses. Each address is limited to 256 characters. You can add up to 256 e-mail addresses.
again be generated. This is a cyclical process where one message will be generated for each group of failed e-mail messages, one for each group of successful e-mail messages, one for the next group of failed messages, and so on. If you start and then immediately stop the Storage Mirroring service, you may not get e-mail notifications for the log entries that occur during startup. By default, most virus scan software blocks unknown processes from sending traffic on port 25.
Full-server protection Before you can protect your entire source, you need to select a target that is suitable to become the source, in the event of a source failure. Storage Mirroring Recover will validate the target you select and identify any incompatibilities. Errors will disqualify the target as a suitable server. First you will need to find a compatible target, then you can establish full-server protection.
Requirement Configuration performance impacts for the users after failover. Network adapters You must map at least one NIC from the source to one NIC on the target. If the source has more NICs than the target, some of the source NICs will not be mapped to the target. Therefore, the IP addresses associated with those NICs will not be available after failover, unless you configure the advanced options.
Requirement Configuration System path The source and the target must have the same system path. The system path includes the location of the Windows files, Program Files, and Documents and Settings. Storage Mirroring Recover path Storage Mirroring Recover must be installed on the system path on the source and the target. Storage Mirroring Recover data state The source should be from a time when the Storage Mirroring Recover data state is good.
1. Login as a user that is a member of both the Double-Take Admin and local Administrators security groups. 2. Open the Full-Server Failover Manager. 3. Enter your source and target servers. You can click Browse when selecting either server to locate it by drilling down through your network. After you have specified a server name, enter login credentials when prompted.
to click Fix or Fix All and let Storage Mirroring Recover correct the problem for you. For those errors that Storage Mirroring Recover cannot correct automatically, you will need to modify the target to correct the error, or you can select a different target. You must revalidate the selected servers until the validation check passes without errors. 7. Once the validation check passes without errors, click Enable Protection to begin monitoring.
● ● Volumes to include—Select the volumes that you want to protect. You must have the same volumes on the source and target. You cannot deselect the boot volume. If you deselect other volumes, you will not be protecting the entire source server. Directories to exclude—Select the directories that you want to exclude. If you exclude any directories, you will not be protecting the entire source server. ● ● ● Add—Click Add to specify a directory to exclude.
example, recover from cases where corrupted source data was replicated to the target. By default, Storage Mirroring Recover takes periodic snapshots of the data on the target. When failover is triggered, you can use the target data at the time of failover or you can revert to a snapshot of the target data. Specify how you want to handle snapshots. ● ● ● ● Enable periodic snapshots—By default, periodic snapshots are enabled.
● Pre-Failover Script and Post-Failover Script—If you want to execute a script on the target before failover (pre-failover) begins or after failover has occurred (post-failover), specify the path to the script on the target. You can also search for the script by clicking Browse. The script will be processed using the same user account that is configured to run the Storage Mirroring service. Scripts may contain any valid Windows command, executable, batch, or script file.
username@domain. If you enter a non-qualified name, the DNS domain will be used by default. The domain name is obtained from the DNS server name, provided that reverse lookup in DNS is enabled. ● Password—Enter the password that is associated with the specified user name. 3. After you have entered the DNS information, click Test to validate that DNS is configured correctly and that the specified credentials are sufficient to update DNS.
selected data, which can be a slower calculation. The mirror will remain in an initializing state until the calculation is complete. 3. Click OK to save the settings. Compressing data 1. Make sure you have a valid source and target specified, click Configure protection from the main Full-Server Failover Manager page, and then select the Advanced tab. 2. Compression allows you to reduce the amount of bandwidth needed to transmit data from the source to the target.
Storage Mirroring Recover uses ICMP pings to monitor the source for failover. A failover monitor will not be created if ICMP is blocked (although the data and system state will still be protected). You should configure your hardware to allow ICMP pings between the source and target. If you cannot, you will have to monitor for a failure manually and create a dummy monitor at failover time that can be manually failed over. Contact technical support for assistance with this manual process.
Application protection Launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. The Application Manager will open. You can protect servers for a different application by selecting one of the following options in the Tasks area on the left pane: ● ● ● ● ● Protect Exchange Server—To protect an Exchange server, click this option.
● Logical drive mapping must be the same on the source and target, and must be assigned prior to running the Application Manager. 3. Install Storage Mirroring Recover on the source and target Exchange servers. 4. Verify the Exchange environment (recommended) 5. Launch the Exchange Server protection workflow. 6. Select a domain 7. Select source and target servers 8. (Optional) Configure protection settings 9.
3. To verify connectivity, create an Outlook profile for the new user on a client machine and connect to the target. If /domainprep has not been run in an Exchange 2007 environment, users will not be failed over and SPNs will not be updated during failover due to access Note: denied errors. To fix this issue, run setup with the /domainprep parameter in the environment. Next step: Launch the Exchange protection workflow Launching the Exchange protection workflow 1.
Selecting a domain If you have not done so already, launch the Protecting an Exchange Server workflow. The Domain Name on the main window will be populated automatically with the root domain where the Application Manager client resides. This is necessary for Application Manager to gather Exchange information from the Configuration container.
Selecting Exchange source and target servers If you have not done so already, launch the Protecting an Exchange Server workflow. The Application Manager will automatically attempt to populate the Source Server and Target Server lists with any servers in the specified domain that are running Exchange.
If you select a target that is monitoring a connection that has met a failover Note: condition and requires manual intervention, a prompt will appear asking if you want to initiate failover. Logging in to servers 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 Double-Take Admin local security group for the selected server.
To change the default Exchange configuration parameters, make sure you have selected a valid source and target, then click Configure from the Manage Exchange page. The Configure Protection window will appear.
The following topics explain how to configure the options on the Failover tab: Failover type DNS failover Identity failover 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.
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. Note: To remove an IP address from the DNS server list, select the IP address, then click the Delete button. 3.
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 TTL of the source’s A records. The recommended value is 300 seconds (5 minutes) or less. If the server that the Application Manager is running on has a problem connecting to the DNS server through WMI, the TTL record will not be Note: updated.
● ● ● ● ● Note: ● ● ● ● If you are running Windows Server 2000 on the primary DNS server hosting zones or domains that contain source and/or target resource records, you must have the DNS WMI Provider installed on that DNS server. 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.
conflict can occur either during failover or when the original source server comes back online. To avoid this conflict, use DNS Failover. Identity failover is not supported in clustered environments. Application Manager cannot be used for failover or failback when the Identity Note: failover method is selected. However, the Failover Control Center can still be used to initiate failover. DNS failover reduces downtime and provides other benefits. It is recommended for most environments.
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. Select the IP Address checkbox if you want the specified source IP address to be monitored (Default = selected). If your source and target servers are on different subnets, you should NOT failover the IP address.
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. Most services must be stopped on the target for replication to occur properly. 4. When you are finished entering services, click Close to return to the Failover configuration window. 5. To remove a service, select one or more services, then click Remove.
Configure how you want to monitor the source server for failure. 1. By default, Active Monitoring Enabled is selected. Active Monitoring allows you 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.
service, which replies immediately to confirm it is running. This method is useful when ICMP is blocked on routers between the source and target. ● Application Monitoring—If you select the Application Monitoring option, the fields in Application Monitoring Settings area will be enabled. In order to use Application Monitoring, the monitored servers must be running Note: Storage Mirroring Recover version 5.2 or later. Application monitoring is not available when dealing with a cluster. 4.
Note: The required credentials for running WMI scripts is full WMI access to the CIMV2 namespace. Under Windows 2008, the supplied credentials must also be allowed through DCOM and User Access Control. It is recommended that a group be created for running scripts, and that the required permissions be given to the group. By default, the administrative group of a Windows 2008 machine has full WMI access. However, DCOM and User Access Control settings may need to be adjusted.
Mirroring Recover version 5.2 or later. If the target server is on a cluster, the Snapshot feature is not available. 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.
The following topics explain how to configure the options on the Connection tab: Route This setting identifies the Target IP Address that the Storage Mirroring Recover data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring Recover traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring Recover activity.
The replication set that the Application Manager generates will include the directories and files needed to protect the selected storage groups. It is recommended that you protect all storage groups. ● ● Note: ● If you do not select all storage groups, you should make sure that other backups are available from which to recover the storage groups that are not failed over.
Significant improvements in bandwidth utilization have been seen in Wide Area Network (WAN) configurations or in any case where network bandwidth is a constraint. Compression may be used in Local Area Network (LAN) configurations, though it may not provide any significant network improvements. 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.
You should only modify the replication set rules if there are additional directories/files specific to your configuration that must also be protected with Exchange. Modifying the default configuration for replication set rules may affect whether data can be successfully replicated. Do not modify the replication set unless you are very familiar with Storage Mirroring Recover and Exchange.
Removing rules that were automatically added by Application Manager could Note: impact the success of failover. Any changes to rules should be thoroughly tested. 9. To reset the rules to the auto-generated rules and to re-enable the Protected Storage Groups control, remove the selection from the Override Generated Rules checkbox.
Script File name Description _ restart services on the source server and rehome the public .txt folders hosted on the source server. Note: The post-restore script must be run from the source server. 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.
In the Max wait time for AD replication field, enter the maximum time you want to wait for Active Directory replication to complete before continuing on with the failover/back process. The default is 30 minutes. The wait time is a factor determining when failover is complete. Note: If replication exceeds the amount of time specified, a log entry is created and replication continues. If it is exceeded, failover is not reported as incomplete or failed.
1. Select the Server Name checkbox if you want the source name to be added to the target when failover occurs (Default = NOT selected). 2. Select the Shares checkbox if you want the source file shares to be added to the target when failover occurs (Default = NOT selected). 3.
6. Select the Create Connection checkbox to create the connection between the source and target using the automatically-generated replication set. This should only be disabled if you would like to verify the replication set that is created by Application Manager prior to connection (Default = selected). 7. Select the Create Failover Monitor checkbox to create a failover monitor on the target to monitor the source for failure.
Next step: Validate the configuration Protect an Exchange cluster with a like-named (standby) cluster You can use the Application Manager to configure protection for an Exchange cluster with a like-named (also known as a standby) cluster. These instructions also apply to setting up multiple EVS (Exchange virtual server). When you protect a cluster with a like-named cluster, the Application Manager moves the EVS location from the source cluster to the target cluster.
Like-named cluster permissions When protecting a cluster with a like-named cluster, you can perform the setup, failover, and failback with the following permissions: ● The user must be a member of the local Double-Take Admin group. ● The user must be a member of the local Administrators group on all cluster nodes. ● ● The user must be delegated Full Exchange Administrator access through Exchange System Manager.
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. Subnet Mask—Enter the subnet mask to use for the new IP address. Storage Resources—The Application Manager will automatically select the required storage resources on the target, provided that they exist (for example, if the source and target both have E:\ and S:\). Verify that the drive letters where Exchange data is located are selected.
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.
Enabling protection for like-named Exchange clusters If you have not done so already, launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. After protection is enabled, the Application Manager creates four resources on the target cluster: two generic script resources, an IP address resource, and a temporary name resource.
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.
Manager. To protect a SQL server, on the Tasks area on the left pane, select Protect SQL Server. The Manage SQL page will appear in the right pane. Make sure that the Setup tab is in view. Note: You can also launch Application Manager for SQL by using the command line /sql option (dtam /sql). Next step: Select the domain Selecting a domain If you have not done so already, launch the Protecting a SQL Server workflow.
Note: Domain names must include a suffix, such as .com, .corp, or .net. The user account should have administrator permissions. For more information about configuring permissions, see Credentials. 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 format NetBIOS domain name\username or username. If you enter a non-qualified name, the default domain will be used.
1. In the Source Server field, select the SQL server that you want to protect. If this is your first time to log in to the selected server, you will be prompted to enter server login information. For more information about logging in to servers, see Entering server login information. You cannot protect a server if it is already functioning as a target server.
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. To directly add a server to the drop-down list on the Manage SQL main page, select the server in the Discovered Servers list, then use the >> button to move it into the Current Servers list. 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.
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 format domain\username or username@domain. If you enter a non-qualified name, the DNS domain will be used. Entering the credentials for the logged-on user may be valid. The Application Manager will attempt to use the same user name and password the next time you select a server.
Selecting SQL instances If you have not done so already, launch the Protecting a SQL Server workflow. 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.
The following topics explain how to configure the options on the Failover tab: Failover type DNS failover Identity failover 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.
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. Note: To remove an IP address from the DNS server list, select the IP address, then click the Delete button. 3.
If the server that the Application Manager is running on has a problem connecting to the DNS server through WMI, the TTL record will not be Note: updated. This will cause the Application Manager to return an error that the RPC server is unavailable. 6. In the Username field, enter the user name that will be used to access/modify DNS records. The login account MUST be a member of the DNSAdmins group for the domain in which the DNS server resides.
binding order on all the source and target servers/nodes involved so that the domain IP address should be at the top of the order. Then, reboot the servers involved. ● For more information about using the DNS Failover utility, access the dfo.exe help by typing dfo.exe /? from a command prompt. Identity failover Select this option if you want to failover by transferring the source IP address and name to the target.
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. Select the IP Address checkbox if you want the specified source IP address to be monitored (Default = selected).
your operating system/SQL configuration. You should only modify this selection if there are additional services that need to be started along with SQL during the failover/failback process. 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 Recover and SQL. 1. To add a service, click Add. The Add Service window will appear. 2.
Next step: Configure monitor settings Configuring monitor settings If you have not done so already, launch the Protecting a SQL Server workflow. 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. By default, Active Monitoring Enabled is selected. Active Monitoring allows you 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. Disable Manual Intervention Required only if you want failover to occur immediately when a failure condition is met. 3.
5. If you are monitoring multiple IP addresses, select one of the Failover Trigger options. ● ● All Monitored IP Addresses Fail—Failover begins when all monitored IP addresses fail. One Monitored IP Address Fails—Failover begins when any of the monitored IP addresses fail. 6. If you selected Application Monitoring as the Method to Monitor for Failover, enter information in the Application Monitoring Settings area. a.
Next step: Configure snapshot settings Configuring snapshot settings If you have not done so already, launch the Protecting a SQL Server workflow. 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. In order to use snapshots, the monitored servers must be running Storage Note: Mirroring Recover version 5.2 or later. If the target server is on a cluster, the Snapshot feature is not available. 1.
The following topics explain how to configure the options on the Connection tab: Route This setting identifies the Target IP Address that the Storage Mirroring Recover data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring Recover traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring Recover activity.
SQL instance (default) Select SQL Instance protection mode to replicate all of the SQL program and data files (except the \binn directory) to the target SQL server. This will allow the clients to access your production SQL Server data and functionality on the target in the event of a failure.
Note: If Override Generated Rules is selected on the Advanced tab, this control will be disabled. 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.
You must first select the database in order for the Target Path commands to be visible. In Database Only mode, if there are multiple databases being protected and the target paths for these databases are changed, it will cause problems mirroring other databases that are at the same or lower in the directory structure. For example, if your databases are located in the following paths: F:\Data\database1.mdf F:\Data\database1.ldf F:\Data\Level1\database2.mdf Note: F:\Data\Level1\database2.
detect if the target database is still online. Clicking Fix will detach that database on the target. 3. To confirm the new path, click Apply. 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.
(because SQL on the target will not allow you to attach more than one copy of the same-named database). If you select and setup both servers’ default instances for protection and both source servers fail, the “Accounting” database on the first source server to be Note: failed over will be attached. The second server to failover will not be able to attach its “Accounting” database.
● 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.
The following topics explain how to configure the options on the Advanced tab: Replication set rules A replication set defines what directories/files are to be protected by Storage Mirroring Recover. 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.
replicated. Do not modify the replication set unless you are very familiar with Storage Mirroring Recover and SQL. To change the replication set rules: 1. Select the Override Generated Rules checkbox. When this box is selected, the Protected Databases control on the Note: Connection tab will be disabled. For more information, see Protected databases. 2. To add a replication set rule, click Add. The Add Repset Rule dialog box will appear. 3.
Scripts are executed at different points during the failover/failback process to perform the actions necessary to make SQL available on the appropriate server. Scripts perform steps such as starting/stopping services, attaching/detaching databases in databaseonly protection mode, and modifying DNS entries on the DNS server to point users to the appropriate server. Editing scripts is an advanced feature. Do not edit scripts unless you fully understand what each command is doing.
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 .txt file within the Application Manager installation directory. If there is more than one client machine that will be configuring failover, the change must be made to all the appropriate .txt files.
1. Select the Create Replication Set checkbox to automatically create a replication set that includes all of the necessary directories/files that must be protected for your specific configuration. This should only be disabled if you have customized your replication set and do not want to overwrite it (Default = selected). 2. Select the Create Failover Scripts checkbox to automatically generate the failover/failback scripts and copy them to the appropriate server.
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. 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.
To protect a File server, on the Tasks area on the left pane, select Protect File Server. The Manage File Server page will appear in the right pane. Make sure that the Setup tab is in view. Note: You can also launch Application Manager for File Servers by using the command line /fileprint option (dtam /fileprint). Next step: Select domain Selecting a domain If you have not done so already, launch the Protecting a File Server workflow.
The user account should have administrator permissions. For more information about configuring permissions, see Credentials. 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 format NetBIOS domain name\username or username. If you enter a non-qualified name, the default domain will be used.
● You cannot protect a server if it is already functioning as a target server. If you attempt to select a source that is currently unavailable, a prompt will appear stating that the source is not available and that if the source is failed over, you should first select the target. If you select the target, then select the source (as recommended in the prompt), the same prompt appears (though you would expect to get a prompt to failover).
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. To directly add a server to the drop-down list on the Manage File Server main page, select the server in the Discovered Servers list, then use the >> button to move it into the Current Servers list. 3.
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 format domain\username or username@domain. If you enter a non-qualified name, the DNS domain will be used by default. Entering the credentials for the logged-on user may be valid. The Application Manager will attempt to use the same user name and password the next time you select a server.
The following topics explain how to configure the options on the Failover tab: Failover type Failover Type indicates what name resolution method will be used to redirect users to the target File server in the event of a source failure. By default, DNS Failover is selected. DNS failover Identity failover 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.
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. Note: To remove an IP address from the DNS server list, select the IP address, then click the Delete button. 3.
If the server that the Application Manager is running on has a problem connecting to the DNS server through WMI, the TTL record will not be Note: updated. This will cause the Application Manager to return an error that the RPC server is unavailable. 6. In the Username field, enter the user name that will be used to access/modify DNS records. The login account MUST be a member of the DNSAdmins group for the domain in which the DNS server resides.
Identity failover Select this option if you want to failover by transferring the source IP address and name to the target. When using identity failover, it is possible that a name and/or IP address conflict can occur either during failover or when the original source server comes back online. To avoid this conflict, use DNS Failover. Application Manager cannot be used for failover or failback when the Identity failover method is selected.
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. Select the IP Address checkbox if you want the specified source IP address to be monitored (Default = selected).
3. If available, select the Service must be stopped on target checkbox. Most services must be stopped on the target for replication to occur properly. 4. When you are finished entering services, click Close to return to the Failover configuration window. 5. To remove a service, select one or more services, then click Remove. You can only remove services that you added manually using the Application Manager. 6.
Configure how you want to monitor the source server for failure. 1. By default, Active Monitoring Enabled is selected. Active Monitoring allows you 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.
service, which replies immediately to confirm it is running. This method is useful when ICMP is blocked on routers between the source and target. ● Note: Application Monitoring—If you select the Application Monitoring option, the fields in Application Monitoring Settings area will be enabled. In order to use Application Monitoring, the monitored servers must be running Storage Mirroring Recover version 5.2 or later. 4. Configure how long to wait after a source failure to initiate failover.
b. In the Password field, enter the password for the specified user account. c. Click the Test Credentials button to validate that the specified credentials are sufficient to run WMI scripts. d. In the Monitoring Option area, select one of the following options. ● Built-in Monitoring—Use the default application monitoring options. If desired, you can select the Attempt to restart services checkbox to automatically attempt to restart the monitored application services.
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. Select one of the following options for when to begin collecting snapshots: ● ● Start now—Select this option to take the first snapshot as soon as protection is enabled. Start at—Select this option to start taking snapshots at a future time.
NIC, this increases the flexibility of configuring Storage Mirroring Recover activity. For example, you can separate regular network traffic and Storage Mirroring Recover traffic on a machine. The default ports will be used. File Shares By default, all non-administrative file shares are selected. You can add other data that you want to protect by selecting the checkbox next to it in the tree view.
Compression may be used in Local Area Network (LAN) configurations, though it may not provide any significant network improvements. 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.
replicated. Do not modify the replication set unless you are very familiar with Storage Mirroring Recover. 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. 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.
actions necessary to make the file shares available on the appropriate server. Editing scripts is an advanced feature. Do not edit scripts unless you fully understand what each command is doing. Scripts are automatically generated by Application Manager during configuration. The scripts are copied to the Storage Mirroring Recover installation directory on the specified server using the administrative share for that server’s drive.
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 .txt file within the Storage Mirroring Recover installation directory. If there is more than one client machine that will be configuring failover, the change must be made to all the appropriate .txt files.
1. Select the Create Replication Set checkbox to automatically create a replication set that includes all of the necessary directories/files that must be protected for your specific configuration. This should only be disabled if you have customized your replication set and do not want to overwrite it (Default = selected). 2. Select the Create Failover Scripts checkbox to automatically generate the failover/failback scripts and copy them to the appropriate server.
When you have finished configuring the optional protection options, continue with Validate the configuration. 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.
3. Install and configure Windows SharePoint Services (WSS 3.0) or Microsoft Office SharePoint Server (MOSS 2007) on each source that will be used as a front-end server, according to Microsoft guidelines. 4. Configure each Windows 2003 target as a member server in the same Active Directory domain or trusted domain environment as the source. 5. Install SQL on the target, verifying that the locations for the SQL installation and the location of the data and log files for the target are the same as the source.
Launch the SharePoint protection workflow Launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. To protect a SharePoint server, on the Tasks area on the left pane, select Protect SharePoint Server. The Manage SharePoint page will appear in the right pane. Make sure that the Setup tab is in view.
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.
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). When you select Configure or Validate, a prompt will appear asking if you want to re-use the previous configuration information.
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. To directly add a server to the drop-down list on the Manage SharePoint main page, select the server in the Discovered Servers list, then use the >> button to move it into the Current Servers list. 3.
password to use for logging in to the selected server. The login account MUST be a member of the Double-Take Admin local security group for the selected server. For more information about permissions, see Credentials. 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 format domain\username or username@domain. If you enter a non-qualified name, the DNS domain will be used.
If you do not need to change the configuration settings, Validate the configuration, then enable protection. If you have already enabled protection for a connection and need to change the configuration parameters, you will first need to disable protection. Next step: Configure failover settings Configuring failover settings If you have not done so already, launch the Protecting a SharePoint Server workflow. The Failover tab includes options that will be applied during SharePoint failover.
In DNS Failover, the DNS records for the source server are modified to point to the target server’s IP address. This allows clients to resolve the source SharePoint server name to the target server’s network name and IP address at failover time. DNS Failover eliminates duplicate server name and IP addresses on your network. After you select the DNS Failover option, click Configure. The Configure DNS Failover window will appear. Configure the following information for DNS failover: 1.
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). If the server that the Application Manager is running on has a problem connecting to the DNS server through WMI, the TTL record will not be Note: updated.
● ● If dynamic updates are enabled on a standard primary zone, the source server will be able to update its DNS records after failover. To prevent this, configure DNS to use an Active Directory-integrated zone. For more information about using the DNS Failover utility, access the dfo.exe help by typing dfo.exe /? from a command prompt. Identity failover Select this option if you want to failover by transferring the source IP address and name to the target.
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. Select the IP Address checkbox if you want the specified source IP address to be monitored (Default = selected).
based on your operating system/SharePoint configuration. You should only modify this selection if there are additional services that need to be started along with SharePoint during the failover/failback process. 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 Recover and SharePoint. 1. To add a service, click Add. The Add Service window will appear. 2.
Configuring monitor settings If you have not done so already, launch the Protecting a SharePoint Server workflow. 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. By default, Active Monitoring Enabled is selected. Active Monitoring allows you to enable or disable failover for the selected source/target pair. 2. By default, Manual Intervention Required is selected.
● ● ● Network Access (ICMP)—Storage Mirroring Recover 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.
Note: The required credentials for running WMI scripts is full WMI access to the CIMV2 namespace. Under Windows 2008, the supplied credentials must also be allowed through DCOM and User Access Control. It is recommended that a group be created for running scripts, and that the required permissions be given to the group. By default, the administrative group of a Windows 2008 machine has full WMI access. However, DCOM and User Access Control settings may need to be adjusted.
Note: In order to use snapshots, the monitored servers must be running Storage Mirroring Recover version 5.2 or later. 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.
The following topics explain how to configure the options on the Connection tab: Route This setting identifies the Target IP Address that the Storage Mirroring Recover data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring Recover traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring Recover activity.
● ● Note: ● If you are using a SQL server named instance for a back-end database server in your SharePoint setup, both the source and target SQL servers must have named instances with the exact same name and logical drive structure as the source SQL server installed prior to configuring protection. To enable the ability to add or remove SharePoint instances, you can launch Application Manager through the command line using the /sharepoint /advanced option (dtam /sharepoint /advanced).
Significant improvements in bandwidth utilization have been seen in Wide Area Network (WAN) configurations or in any case where network bandwidth is a constraint. Compression may be used in Local Area Network (LAN) configurations, though it may not provide any significant network improvements. 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.
You should only modify the replication set rules if there are additional directories/files specific to your configuration that must also be protected with SharePoint. Modifying the default configuration for replication set rules may affect whether data can be successfully replicated. Do not modify the replication set unless you are very familiar with Storage Mirroring Recover and SharePoint. To change the replication set rules: 1. Select the Override Generated Rules checkbox.
9. To reset the rules to the auto-generated rules and to re-enable the Protected Databases control, remove the selection from the Override Generated Rules checkbox. Failover/failback scripts Scripts are executed at different points during the failover/failback process to perform the actions necessary to make SharePoint available on the appropriate server.
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 .
1. Select the Create Replication Set checkbox to automatically create a replication set that includes all of the necessary directories/files that must be protected for your specific configuration. This should only be disabled if you have customized your replication set and do not want to overwrite it (Default = selected). 2. Select the Create Failover Scripts checkbox to automatically generate the failover/failback scripts and copy them to the appropriate server.
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.
4. In the Config Database Server field, enter the name of the Microsoft SQL Server that hosts the configuration database. 5. In the Config Database Name field, enter the name of the configuration database for the production SharePoint web front-end server. 6. In the SharePoint Admin Name field, enter the account used to install and configure SharePoint on the production SharePoint web front-end server. This should be entered as a fully-qualified domain name (domain\username). 7.
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.
● BlackBerry Controller ● BlackBerry Dispatcher ● BlackBerry MDS Connection Service (if installed) ● BlackBerry MDS Services - Apache Tomcat Service (if installed) ● BlackBerry Policy Service ● BlackBerry Router ● BlackBerry Synchronization Service 7. Install Storage Mirroring Recover on the source and target servers using the installation defaults. 8. Launch the BlackBerry Server protection workflow. 9. Select a domain. 10. Select source and target servers. 11.
Next step: Select the domain Selecting a domain If you have not done so already, launch the Protecting a BlackBerry Server workflow. 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.
name\username or username. If you enter a non-qualified name, the default domain will be used. Next step: Select source and target servers Selecting source and target servers If you have not done so already, launch the Protecting a BlackBerry Server workflow. 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. For more information, see Adding or managing servers.
You cannot protect a server if it is already functioning as a target server. If you attempt to select a source that is currently unavailable, a prompt will appear stating that the source is not available and that if the source is failed over, you should first select the target. Note: If you select the target, then select the source (as recommended in the prompt), the same prompt appears (though you would expect to get a prompt to failover).
2. To directly add a server to the drop-down list on the Manage BlackBerry main page, select the server in the Discovered Servers list, then use the >> button to move it into the Current Servers list. 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. 4.
● Failover settings ● Monitor settings ● Snapshot settings ● Connection settings ● BlackBerry settings ● Advanced settings If any important aspect of your configuration changes (for example, service account name change, server IP address change, server logical drive Note: configuration change, recently added server hardware), you should reconfigure protection and, if possible, not re-use the existing configuration in order to capture the new configuration.
The following topics explain how to configure the options on the Failover tab: Failover type Failover Type indicates what name resolution method will be used to redirect users to the target BlackBerry server in the event of a source failure. By default, DNS Failover is selected. DNS failover Identity failover 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.
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. Note: To remove an IP address from the DNS server list, select the IP address, then click the Delete button. 3.
9. When the DNS configuration is complete, click OK to save your entries and return to the Configure Protection window. ● ● ● Note: ● ● ● ● If you are running Windows Server 2000 on the primary DNS server hosting zones or domains that contain source and/or target resource records, you must have the DNS WMI Provider installed on that DNS server. The Dynamic updates setting for the DNS zone should be set to Secure only.
and drive shares during a failover. Identity failover may be required in the following situations: ● ● ● Access to the domain controller or DNS server is not available (for example, due to permissions) from the account that Storage Mirroring Recover runs under on the source/target servers. If you determine that the time it takes to propagate the necessary DNS or Active Directory changes to the rest of your environment is not acceptable.
choose DNS failover with the Advanced switch and select the Server Name. For more information, see Advanced settings. 5. Select the Server Name checkbox if you want the source name to be added to the target when failover occurs (Default = NOT selected). 6. Select the Shares checkbox if you want the source file shares to be added to the target when failover occurs (Default = NOT selected). 7.
column). To re-arrange the order in which services are started/stopped: a. Add any additional services. b. Select a service in the list, then use the up and down arrow buttons to move the service to the appropriate position in startup/shutdown order. Next step: Configure monitor settings Configuring monitor settings If you have not done so already, launch the Protecting a BlackBerry Server workflow. The Monitoring tab includes options for configuring how you want to monitor the source server for failure.
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. Disable Manual Intervention Required only if you want failover to occur immediately when a failure condition is met. 3. In the Method to monitor for Failover field, select the ping method to use when monitoring source IP addresses.
a. In the Username field, enter the fully-qualified user name that will be used to run WMI scripts. The fully-qualified user name must be in the format domain\username or username@domain. Note: The required credentials for running WMI scripts is full WMI access to the CIMV2 namespace. Under Windows 2008, the supplied credentials must also be allowed through DCOM and User Access Control. It is recommended that a group be created for running scripts, and that the required permissions be given to the group.
Note: In order to use snapshots, the monitored servers must be running Storage Mirroring Recover version 5.2 or later. 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.
The following topics explain how to configure the options on the Connection tab: Route This setting identifies the Target IP Address that the Storage Mirroring Recover data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring Recover traffic. On a machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring Recover activity.
may choose to deselect the tempdb database if it is not necessary. 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. 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.
1. Select Protect MDS services if you want to protect the MDS services. 2. In the BlackBerry Services area, Application Manager will determine the appropriate BlackBerry services to start/stop based on your operating system/BlackBerry configuration. You should only modify this selection if there are additional services that need to be started along with BlackBerry during the failover/failback process. Modifying the default configuration for services may affect whether data can be successfully replicated.
You can only remove services that you added manually using the Application Manager. 8. Services will be started in the displayed order (top-to-bottom starting with the left column) and shutdown in reverse order (bottom-to-top starting with the right column). To re-arrange the order in which services are started/stopped: a. Add any additional services. b. Select a service in the list, and use the up and down arrow buttons to move the service to the appropriate position in startup/shutdown order.
_. You should only modify the replication set rules if there are additional directories/files specific to your configuration that must also be protected with BlackBerry. Modifying the default configuration for replication set rules may affect whether data can be successfully replicated. Do not modify the replication set unless you are very familiar with Storage Mirroring Recover and BlackBerry. To change the replication set rules: 1.
9. To reset the rules to the auto-generated rules and to re-enable the Protected Databases control, remove the selection from the Override Generated Rules checkbox. Failover/failback scripts Scripts are executed at different points during the failover/failback process to perform the actions necessary to make BlackBerry available on the appropriate server. Editing scripts is an advanced feature. Do not edit scripts unless you fully understand what each command is doing.
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. 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.
1. Select the Server Name checkbox if you want the source name to be added to the target when failover occurs (Default = selected). 2. Select the Shares checkbox if you want the source file shares to be added to the target when failover occurs (Default = NOT selected). 3.
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). Next step: Save configuration settings Saving configuration changes If you have not done so already, launch the Protecting a BlackBerry Server workflow.
To protect the Exchange servers, click on the name of the Exchange server under step 2. The Protect Exchange servers window will appear. For more information about protecting Exchange servers, see Protecting an Exchange server. Next step: Protect Exchange server Validate the configuration If you have not done so already, launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager.
Icon Validation Status addressed prior to failover. Can be fixed by Application Manager. Warning, Not Fixable—The Application Manager detected an issue that should be addressed prior to failover. Must be fixed manually. ● ● Note: ● ● If you run a validation against a source/target pair that is in a Protected state and the validation detects issues with the target (such as the target is missing or contains incorrect data), the Fix or Fix All button will be disabled.
You can click the Show/Hide button to display or hide details about the protected pair. For details about changing the units used to display bytes remaining in the mirror and queues, see Changing Application Manager preferences. Next step: Enable protection Enable protection If you have not done so already, launch the Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. Click Enable Protection.
was created before any of the routable IP resources, the Application Manager will fail to enable protection. To enable protection, you will need to delete the non-routable IP resource(s), re-create them, and then re-add them as dependencies on the network name resource for the virtual server A source server can have a Protected status only if the source is currently connected to a target and an Application Manager-generated replication set exists.
You must disable protection before you can change any of the Application Manager configuration parameters. 1. If you select a source that is already protected in the Source Server field, the target server will be filled in automatically and the Protection Status should indicated Protected. 2. Click Disable Protection at the bottom of the window, or select Actions, Disable Protection, to disable protection.
Virtual machine protection Select one of the following virtual machine protection scenarios: ● ● ● ● Protect an ESX virtual machine using Storage Mirroring Recover for Virtual Infrastructure Protect a server to a virtual target machine on VMware ESX using Storage Mirroring Recover Virtual Recovery Assistant for ESX Protect a physical or virtual machine with Hyper-V using Storage Mirroring Recover Virtual Recovery Assistant for Hyper-V Protect a Hyper-V virtual machine using Storage Mirroring Recover for
● Port 22—Used by Storage Mirroring Recover for Virtual Infrastructure to communicate with the VMware ESX Host(s) via SSH. Also used by each ESX host to connect to each other. This port cannot be changed. If any of the ports in your environment differ from those listed here, you will have to provide the correct port number when setting up connections to the various servers.
1. Log on to the ESX server through the console, using root credentials. 2. Use a text editor to open the SSH system configuration file /etc/ssh/sshd_config. 3. Change the line “PermitRootLogin no” to “PermitRootLogin yes”. 4. Save the configuration file. 5. From the command line, enter the following line to restart the SSH service. service sshd restart Login using a non-root account Storage Mirroring Recover for Virtual Infrastructure can use non-root accounts to set up and configure protection jobs.
home folder), then sudo is configured correctly. If it fails with a “permission denied” error or prompts for a password, then sudo is misconfigured. sudo ls ~root Next step: Connect to the SMRVI server Connecting to the Storage Mirroring Recover for Virtual Infrastructure server You will need to enter valid credentials for the SMRVI server. The SMRVI server is where replication and licensing management takes place. The account you specify must have permission to read and write files to that server.
If you have changed the default port (6331) used by the SMRVI server, specify the port as well. Enter the IP address and port in the Server field, using one of the following formats: Note: IPv4Address:Port [IPv6Address]:Port hostname:Port 2. In the User name field, enter the user name for the account that will access the SMRVI server. 3. In the Password field, enter the password that is associated with the user name. 4.
Each valid activation code corresponds to a number of slots, where each slot represents the capacity to protect a single virtual machine. The slots are not bound to a specific socket or piece of hardware. Instead, a slot can be used to protect a virtual machine on any server in your VI enterprise. Each time a protection is created using the wizard, the application will automatically update the number of slots available for subsequent protections.
Protecting a virtual machine If you have not done so already, launch the Storage Mirroring Recover for Virtual Infrastructure console. To set up protection for a virtual machine, click the Protect a virtual machine button to launch the protection workflow. Expand the following sections for more information about each page in the Protect a virtual machine workflow. Selecting the source virtual machine When you select Protect a virtual machine, the Select virtual machine page will appear.
While generic SCSI device mappings in virtual machines are supported by Storage Mirroring Recover for Virtual Infrastructure, the generic SCSI device will not be created on the target virtual machine. This is necessary because the target virtual machine will fail to start if the SCSI device hardware does not exist Note: on the target ESX host. Upon failback, the generic SCSI device will be mapped back to the original source.
● Storage Mirroring Recover for Virtual Infrastructure does not support virtual machines using raw or independent disks on ESX. 3. To browse virtual machines, either select a VirtualCenter server or enter the ESX host information, then click the Browse button to locate a virtual machine. The Select virtual machine window will appear. a. In the Select virtual machine window, browse through the file tree on the left side to select a source virtual machine.
4. The Source ESX server IP address or DNS name field displays the IP address or DNS name of the selected VMware ESX server. 5. In the User name field, enter the user name for the account you will be using to log on to the source VMWare ESX server. 6. In the Password field, enter the password that is associated with the user account. 7. After all fields have been completed, click Next.
2. If you want to create a connection directly from one ESX server to another without using VirtualCenter, select (None) (for instance, if the target is not administered by a VirtualCenter server). 3. In the Target ESX server IP address or DNS Name field, enter the IP address or DNS name of the VMware server that will provide a backup for your source virtual machine. Or, click the Browse button to browse VirtualCenter to locate a server. The Select ESX server window will appear. a.
c. After you have found the target server in the left pane, select it then click Choose. 4. In the User name field, enter the user name for the account you will be using to log on to the target server. 5. In the Password field, enter the password that is associated with the user account.
1. In the Choose target datastore area, select the datastore where the source virtual machine data will be replicated. 2. By default, the path for the replica virtual machine will be filled in with the source virtual machine name. If you want to change the replica virtual machine path, enter it in the field. Do not use any special or unique characters in the replica virtual machine Note: path, including the following: #\:*?'"<>| 3. When you are finished, click Next.
Do not use any special characters in the replica virtual machine name, Note: including the following: #/\:*?'"<>| 2. In the Map replica virtual network adapters to target VSwitches area, if there are multiple target networks, you can select the network on the target to use. 3. In the Number of processors field, select the number of processors for the replica virtual machine. Note: The Processors on the source server field displays the number of processors on the original source virtual machine. 4.
287 of 739
You can change protection settings for this job by clicking on the Change buttons. Scheduling protection start time By default, Storage Mirroring Recover for Virtual Infrastructure starts the initial synchronization of a protection immediately after the protection is created. If you want to specify a date and time in the future at which the initial synchronization will be started, click the Schedule button at the top of the window. The Configure protection start time window will appear.
Enter a name for the protection job. You might want to name it something like “source vm name to target”. When you are finished, click Save. Setting data transmission options You can modify the data transmission options in order to make them more suitable for your environment. Click the Change button in the Data Transmission area. The Set data transmission options window will appear.
1. You can change the snapshot data compression settings in the Compression area. The following options are available: ● ● ● Note: Never—(Default) No compression will be applied to the data. Always—All transmissions associated with the protection set will be compressed. Only during the initial synchronization—Data will be compressed only during the initial transmission of the flat virtual disk files. Enabling compression requires that additional CPU cycles be used on both the source and target servers.
a. Transmit when the snapshot data reaches this size (MB)—(Default = 32 MB x the number of snapshot-capable virtual disks) Enter the size of snapshot file (in MB) that will trigger a transmission from the source to the target. When multiple virtual disks are used, any combination of writes across all virtual disks that accumulate to this size will trigger replication. The minimum size allowed is 32 MB. b.
If you have not yet configured an e-mail server, a message will appear at the top of the window prompting you to set up the e-mail server. Click Configure to launch the Set up e-mail server window. For more information, see Managing the e-mail server. Note: The e-mail server configuration will apply to all protection jobs. 1. In the Recipients area, enter the e-mail address(es) to which you want to send the automatic e-mail notifications.
3. To verify that your settings are valid, click the Test E-mail Settings button. Storage Mirroring Recover for Virtual Infrastructure will verify that e-mail notifications can be sent to the recipients you entered using the configured e-mail server. If you receive the following error message after testing the e-mail notification, the anti-virus software on your SMRVI server may be blocking the outbound e-mails. “Failure sending mail. Unable to connect to the remote server.
Changes you make here will only apply to the current protection job. Click the Change button in the VirtualCenter credentials area. The Set VirtualCenter server credentials window will appear. Enter the following information in the appropriate fields: 1. Source VirtualCenter credentials a. Server—The Server field is automatically filled in with the IP address of the server you selected. b. User name—Enter the user name for the account that will access the VirtualCenter server. c.
b. User name—Enter the user name for the account that will access the VirtualCenter server. c. Password—Enter the password that is associated with the user name. 3. When you are finished, click Save. Changing restart and threshold options Click the Change button in the Restart and Thresholds area. The Configure restart and thresholds window will appear. 1. If you want to disable auto-restart, un-select the Restart this protection automatically if the connection fails checkbox.
b. MB—Enter the number of megabytes remaining that should trigger the protection to stop. 3. When you are finished, click Save. Saving protection settings Review the protection settings on the Protection summary page. If the settings are acceptable, click Finish to save your protection settings. After your protection has been configured, you will be able to monitor the protection status of your virtual machine(s). See Monitoring protected virtual machines.
5. Using an external tool, copy each source .vmdk file to its corresponding target location shown in the replica virtual machine disk mapping file. Be sure to copy the files to the exact locations shown; otherwise, Storage Mirroring Recover for Virtual Infrastructure will not be able to find them. Also, note that in the mapping, the .vmdk filenames may be different on the target than the source. If this is the case, you must use the target .
internal IP address can be mapped to any one of a group of external IP addresses managed by the router. Virtual Recovery Assistant ports By default, Storage Mirroring Recover uses port 6320 for all communications. You will also need to verify that port 6330 is open for Storage Mirroring Recover Virtual Recovery Assistant communications. Virtual Recovery Assistant uses ICMP pings to monitor the source for failover.
Virtual Recovery Assistant can use VMware VirtualCenter to manage the VMware ESX host server. To use VirtualCenter, you must enter credentials for logging in to the VMware VirtualCenter server. The first time you log in, the Connect to VirtualCenter Server dialog box will appear: The VirtualCenter server is where the VMware VirtualCenter service is running. The VMware VirtualCenter service manages all the VMware ESX servers in the environment.
1. Server—Enter the IP address or fully-qualified domain name of the VirtualCenter server. 2. User name—Enter the user name for the account that will access the VirtualCenter server. 3. Password—Enter the password that is associated with the user name. 4. If you want Virtual Recovery Assistant to remember the login information, select the Save VirtualCenter connection informationcheckbox.
Selecting the source machine If you have not done so already, launch the Storage Mirroring Recover Virtual Recovery Assistant console. When you click Protect a server, the Select source server window will appear. Enter the following information for the source server: 1. Server—Enter the IP address or DNS name of the source server you want to protect. Or, click the Browsebutton to browse to locate a server. a. In the Browse for server window, browse through the server tree to select a source server.
b. After you have found the source server, select it, then click Choose. ● Note: ● In order to protect a source, the source must have no more than four NICs enabled. Thin-provisioned virtual disks on VMware ESX are not supported because they cannot be shared by two virtual machines simultaneously. 2. User name—Enter the user name for the account that will access the source server. Note: The user account specified must have Double-Take Admin privileges on the source server. 3.
Selecting volumes to protect If you have not done so already, launch the Storage Mirroring Recover Virtual Recovery Assistant console. Select the volumes you want to protect to the target virtual machine. By default, the system volume will be selected. ● Note:N ● Virtual Recovery Assistant can protect a maximum of 14 source volumes per SCSI controller installed on the Virtual Recovery Appliance virtual machine.
1. Select the name of the volume in the Volume table. 2. Enter a value in the Size of the selected volume on the replica virtual machine field. If the size of the virtual disk on the replica is identical to the size of the disk on the source and the source has less than 20 MB of disk space remaining, you may run out of disk space on the replica due to differences Note: in how the virtual disk's block size is formatted.
Enter the following information for the target server: 1. IP address or DNS name—Enter the IP address or DNS name of the target server which will host your virtual recovery appliance and replica virtual machines. Or, click the Browse button to browse to locate a server. If you did not specify a VirtualCenter server, the Browse button will not be Note: available. You will be prompted to add a username and password for the target server. a.
Selecting the target datastore If you have not done so already, launch the Storage Mirroring Recover Virtual Recovery Assistant console. Select the datastore where the protected data will be stored, then click Next. The target datastore must have enough free space to store the source data. Next step: Select the virtual recovery appliance Selecting the virtual recovery appliance If you have not done so already, launch the Storage Mirroring Recover Virtual Recovery Assistant console.
Enter the following information for the virtual recovery appliance: 1. Choose an existing virtual machine—Select the virtual machine you would like to use as the virtual recovery appliance. Note: This field will only display virtual recovery appliances that are powered on and that are running Windows 2003, Standard or Enterprise edition. 2. User name—Enter the user name for the account that will access the virtual recovery appliance.
Defining the replica virtual machine If you have not done so already, launch the Storage Mirroring Recover Virtual Recovery Assistant console. Select the options that will configure the virtual machine that will stand in for the source server after failover. 1. Replica virtual machine name—Use the default replica virtual machine name, or enter a new name. 2. Map replica virtual network IP to target networks—If there are multiple target networks, you can select the network on the target to use. 3.
5. When you are finished configuring the replica virtual machine, click Next. Next step: Set protection options Setting protection options If you have not done so already, launch the Storage Mirroring Recover Virtual Recovery Assistant console. Select the options you want to use during protection. 1. Compression—Select the compression level (None, Low, Medium, or High) to use when sending data from the source to target server. 2.
with those networks, you can choose to use an IP address other than the one you entered for the target in Select a target server. 3. Enable automatic failover—If you want the replica virtual machine to stand in for the source server when the source is inaccessible, select this checkbox. If automatic failover is enabled and a failover condition is met before the initial mirror has completed, Virtual Recovery Assistant will attempt to failover Note: to the target virtual machine.
8. Review the protection options, then click Finish to initiate the protection process. When you click Finish, a message box will appear identifying the status of the protection check.
Managing virtual recovery appliances If you have not done so already, launch the Storage Mirroring Recover Virtual Recovery Assistant console. Select Manage virtual recovery appliances in the left pane to view the Manage virtual recovery appliances pane. From this pane, you can select a virtual machine, then choose one of the following actions: Toolbar button Function Add virtual recovery appliance—Click this button to add a new virtual recovery appliance.
Enter the following information for the target server: 1. IP address or DNS name—Enter the IP address or DNS name of the server which will host your virtual recovery appliance. Or, click the Browse button to browse to locate a server. If you did not specify a VirtualCenter server, the Browse button will not be Note: available. You will be prompted to add a username and password for the target server. a. In the Browse for server window, browse through the file tree to select a target server.
b. After you have found the target server, select it, then click Choose. 2. When you are finished, click Next. The Add virtual recovery appliance window will appear.
3. Choose an existing virtual machine—Select the virtual machine you would like to use as the virtual recovery appliance. Note: This field will only display virtual recovery appliances that are powered on and that are running a supported operating system. 4. User name—Enter the user name for the account that will access the virtual recovery appliance.
Firewall configuration If you have not done so already, launch the Storage Mirroring Console. If your source and target are on opposite sides of a NAT or firewall, you will need to configure your hardware to accommodate Storage Mirroring Recover communications. You must have the hardware already in place and know how to configure the hardware ports. If you do not, see the reference manual for your hardware.
● Microsoft Directory uses port 445 for TCP and UDP communications. These ports must be open on your firewall. Check your Microsoft documentation if you need to modify these ports. Hardware ports You need to configure your hardware so that the Storage Mirroring Recover and Microsoft Windows ports are open. Since communication occurs bidirectionally, make sure you configure both incoming and outgoing traffic. There are many types of hardware on the market, and each can be configured differently.
Note: Depending on which Storge Mirroring components you have installed, you may see additional tasks on this screen. 3. To begin setting up protection for a server with a Hyper-V virtual machine, select Protect an entire server using a Hyper-V virtual machine, then click Next. The workflow will guide you through the steps to configure protection for a physical source server whose data and system state you will be protecting with a virtual target server.
Enter the following information for the source server: 1. Server—Enter or select the DNS name or IP address of the physical or virtual source server that you want to protect. Or, click the Browse button to locate a server. a. In the Browse for Server window, browse through the server tree to locate a source server. b. After you have found the source server, select it, then click OK.
In order to protect a source, the source must have no more than four NICs enabled. If you enter the fully-qualified domain name for the server, the Storage Note: Mirroring Console will resolve the entry to the server short name. This could result in name resolution issues for servers with the same short name that reside in two different domains. To avoid this, enter the IP address of the server. 2. User name—Enter the user name for the account that will access the source server.
You can specify the size of the selected volume on the replica virtual machine. 1. Select the checkbox next to the volume(s) to protect in the Volume table. 2. In the Storage Controller column, select the type of storage controller for the volume (IDE or SCSI). Note: A maximum of three volumes can be attached to an IDE controller. If you are protecting more than three volumes on the source, you will need to install the Hyper-V integration components to acquire a SCSI device.
● ● Note: The value entered must be equal to or greater than the Used Space on the source volume. If the size of the virtual disk on the replica is identical to the size of the disk on the source and the source has less than 20 MB of disk space remaining, you may run out of disk space on the replica due to differences in how the virtual disk's block size is formatted. To avoid this issue, create a virtual disk with at least 20 MB more disk space than the amount of data that will be mirrored to it. c.
Enter the following information for the target server: 1. Server—Enter or select the IP address or DNS name of the target server that will host the virtual replica machines. Or, click the Browsebutton to locate a server. a. In the Browse for server window, browse through the file tree to locate a target server. b. After you have found the target server, select it, then click OK.
Selecting the target volume If you have not done so already, launch the Protect an entire server using a Hyper-V virtual machine workflow. 1. Select the volume where you would like the replica virtual machine to be stored. The target volume must have enough free space to store the source data. 2. By default, the replica virtual machine will be created in the HVRA_ Replicas\ folder. If you want to change the replica virtual machine path, enter it in the field.
Configuring the replica virtual machine If you have not done so already, launch the Protect an entire server using a Hyper-V virtual machine workflow. Select the options that will configure the virtual machine that will stand in for the source server after failover. 1. Replica virtual machine display name—Use the default replica virtual machine name, or enter a new name. 2. Number of processors—Select the number of processors for the replica virtual machine.
Note: The Memory on the source server field displays the amount of memory (in MB) on the original source server. 4. Map source IP addresses to target virtual switches—If there are multiple target networks, you can select the network on the target to use. 5. When you are finished configuring the replica virtual machine, click Next.
1. Compression—Select the compression level (None, Low, Medium, or High) to use when sending data from the source to target server. 2. Send data to this target route—Select the IP v4 or IP v6 address on the target server to which you want to send data from the source. 3. Limit Bandwidth—You can specify a limit for the bandwidth to be used by sourceto-target communications for this protection job. Select the Limit Bandwidth checkbox, then enter a value (in kilobits per second) that bandwidth cannot exceed.
Note:Automatic failover will not occur until after the initial mirror has completed. 5. Monitor these addresses on the source server—Select the IP address(es) to monitor for automatic failover. 6. Monitoring interval (seconds)—(Default = 5) Select how often the monitor will check the source machine availability. 7. Number of missed intervals that trigger failover—(Default = 5) Select how many monitor replies can be missed before assuming the source machine has failed. 8.
10. Review the protection options, then click Finish to initiate the protection process. After you click Finish, Storage Mirroring Console creates the job. The Monitor Connections page will appear. Next step: Monitor your protection job Reusing virtual hard disks Virtual hard disks (VHDs) created by a virtual recovery protection job can be re-used.
7. During job creation, when you select the replica path, if a VHD file with the same name exists, Storage Mirroring Console will display a prompt asking if you would like to re-use the existing VHD. Select Yes. 8. Storage Mirroring Console will re-use the existing VHD files and perform a file difference mirror over the LAN. Protect virtual machines running on the Microsoft Hyper-V platform You can use the Storage Mirroring Console to protect virtual machines running on the Microsoft Hyper-V platform.
Storage Mirroring Recover uses ICMP pings to monitor the source for failover. A failover monitor will not be created if ICMP is blocked (although the data and system state will still be protected). You should configure your hardware to allow ICMP pings between the source and target. If you cannot, you will have to monitor for a failure manually and create a dummy monitor at failover time that can be manually failed over. Contact technical support for assistance with this manual process.
2. Select the option Storage Mirroring Recover, then click Next.
Note: Depending on which Storge Mirroring components you have installed, you may see additional tasks on this screen. 3. To begin setting up protection for a Hyper-V virtual machine, select Protect a Hyper-V virtual machine using host-level protection, then click Next. The workflow will guide you through the steps to configure protection for a Hyper-V virtual machine.
b. After you have found the source server, select it, then click OK. If you enter the fully-qualified domain name for the server, the Storage Mirroring Console will resolve the entry to the server short name. This could result in Note: name resolution issues for servers with the same short name that reside in two different domains. To avoid this, enter the IP address of the server. 2. User name—Enter the user name for the account that will access the source server.
The virtual machines that are found on the source server will be added to the list on the Choose Virtual Machine window. Select a virtual machine to protect from the list, then click Next. Guest operating system information for the virtual machine will only be shown if Note: Microsoft Integration Services is installed on the virtual machine and the machine is powered on.
Enter the following information for the target server: 1. Server—Enter the IP address or DNS name of the Hyper-V server that will be the target host. Or, click the Browse button to browse to locate a server. a. In the Browse for server window, browse through the file tree to select a target server. a. After you have found the target server, select it, then click OK. 2. User name—Enter the user name for the account that will access the target host.
The user account entered here must have administrative rights for Microsoft Note: Hyper-V on that server, and be a member of the Double-Take Administrators group. 3. Password—Enter the password that is associated with the user account. 4. After all fields have been completed, click Next. A window will display the progress. Next step: Select target volume Selecting the target volume If you have not done so already, launch the Protect a Hyper-V virtual machine using host-level protection workflow. 1.
directory will be created on the root level of the selected volume. 3. When you are finished, click Next. Next step: Configure the replica virtual machine Configuring the replica virtual machine If you have not done so already, launch the Protect a Hyper-V virtual machine using host-level protection workflow. Configure the virtual switches for the replica virtual machine. 1. Replica virtual machine display name—Use the default replica virtual machine name, or enter a new name. 2.
Setting protection options If you have not done so already, launch the Protect a Hyper-V virtual machine using host-level protection workflow. Configure the parameters for the protection job. Note: Compression and bandwidth limit settings will apply to all protections that use the same source-to-target route. 1. Send data to this target route—Select the IP address on the target server to which you want to send data from the source.
If your host is on multiple networks and has multiple addresses associated with Note: those networks, you can choose to use an IP address other than the one you entered for the target in Selecting a target server. 2. Compression—Select the compression level (None, Low, Medium, or High) to use when sending data from the source to target server. 3. Limit Bandwidth—You can specify a limit for the bandwidth to be used by sourceto-target communications for this protection job.
8. (Optional) If you want to change the name of the protection, click the Change button. The Change Name window will appear. Enter a new name for the protection, then click Save.
9. Review the protection options, then click Finish to initiate the protection process. When you click Finish, a message box will appear identifying the status of the protection check. Next step: Monitor your protection job Virtual hard disks Storage Mirroring Recover for Hyper-V monitors the virtual disks of a protected virtual machine for changes to the disk layout.
Cluster protection Your cluster protection will depend on the type of cluster configuration you are using. ● ● Standard cluster configuration—If you are using a standard cluster, where a single copy of data resides on a SCSI disk that is shared between cluster nodes, you will be using the Double-Take Source Connection cluster resource to protect your cluster.
2. If your target is a cluster, create a virtual server (including resources for an IP address, network name, and physical disk) on the target cluster. With this configuration, if there is a source failure, the data will be available for the users from the target cluster, regardless of which node is currently in control. MSCS will handle failover between the nodes of the target cluster. Storage Mirroring Recover will handle failover between the source (cluster or standalone) and the target cluster.
The default number of files that are listed in the right pane of the Replication Console is 2500, but this is user configurable. A larger number of file listings allows you to see more files in the Replication Console, but results in a slower display rate. A smaller number of file listings displays faster, but may not show all files contained in the Note: directory. To change the number of files displayed, select File, Options and adjust the File Listings slider bar to the desired number.
As an alternative to the following manual steps, you can stop the Storage Mirroring service on the other nodes of the source cluster, copy the file Note: DblTake.db from the first node to the other nodes, and then restart the Storage Mirroring service. a. Right-click the replication set created on the owning node and select Properties. b. Record the exact drive and directories of each path displayed, including where the rule is included or excluded and if recursion is applied. c.
Note: Each replication set rule on the non-owning nodes must be identical to the replication set rule on the owning node. h. After entering all of the replication set rules, save the replication set. The replication set rules will be saved even though the non-owning nodes do not have access to the locations right now. The rules will function properly when the node becomes an owner. 5.
d. Click OK to save the changes. e. Repeat these steps on each node of the cluster(s). 6. If your source is a standalone server, establish your connection through the Connection Manager, selecting the virtual server network name for the Target Server and the virtual server IP address for the Route. 7. If your source is a cluster, establish your connection by creating and bringing online a Double-Take Source Connection resource. These instructions will vary depending on your operating system.
● ● ● ● Replication Set—Select the Storage Mirroring Recover replication set that you want to use. If the replication set you want to use is not listed, click Update List to refresh the list of replication sets from the source. Double-Take Target—Specify the name or IP address of the target. If your target is a cluster, this is the virtual name or virtual IP address of the virtual server you created on the target cluster.
● ● No Bandwidth Limit—Data will be transmitted using all available bandwidth. Fixed Bandwidth Limit—Data will be transmitted according to the user-specified bandwidth configuration. By default, the Unlimited checkbox is enabled. This configuration is identical to selecting No Bandwidth Limit. If you want to limit your bandwidth usage, clear this checkbox. To limit the bandwidth usage, enter the maximum amount of data you want to transfer per second.
● ● ● Full Mirror—All files in the replication set will be sent from the source to the target. File differences—Only those files that are different based size or date and time will be sent from the source to the target. Send data only if Source is newer than Target—Only those files that are newer on the source are sent to the target. If you are using a database application, do not use the newer option unless you know for certain you need it.
virtual server you are protecting and select Add a resource, More resources, Add Double-Take Source Connection. b. Right-click on the new resource and select Properties. c. On the General tab, specify a Resource Name that indicates this is the Storage Mirroring Recover virtual server connection. d. Select the Dependencies tab. This resource is dependent on the physical disk and network name resources. Insert these two resources so that the Double-Take Source Connection resource is dependent on both of them.
● ● ● Double-Take Target—Specify the name or IP address of the target. If your target is a cluster, this is the virtual name or virtual IP address of the virtual server you created on the target cluster. If your target is a standalone server, this is the name or IP address of the standalone target server. Target Credentials—To specify the account to use when logging on to the target, click Set and enter the user name, password and domain.
● ● No Bandwidth Limit—Data will be transmitted using all available bandwidth. Fixed Bandwidth Limit—Data will be transmitted according to the user-specified bandwidth configuration. By default, the Unlimited checkbox is enabled. This configuration is identical to selecting No Bandwidth Limit. If you want to limit your bandwidth usage, clear this checkbox. To limit the bandwidth usage, enter the maximum amount of data you want to transfer per second.
i. Select the Compression tab and specify your Storage Mirroring Recover compression parameters. By default, compression is disabled. To enable it, select Enable Compression. Depending on the compression algorithms available for your operating system, you may see a slider bar indicating different compression levels. Set the level from minimum to maximum compression to suit your needs. j. Select the Mirror Properties tab and specify how you want to mirror the data.
● ● ● Full Mirror—All files in the replication set will be sent from the source to the target. File differences—Only those files that are different based size or date and time will be sent from the source to the target. Send data only if Source is newer than Target—Only those files that are newer on the source are sent to the target. If you are using a database application, do not use the newer option unless you know for certain you need it.
● Calculate Replication Set size prior to mirror—Determines the size of the replication set prior to starting the mirror. The mirroring status will update the percentage complete if the replication set size is calculated. f. Click OK to complete the creation of the Double-Take Source Connection resource. 8. Bring the Double-Take Source Connection resource and the virtual server resources online.
● ● ● ● ● ● Volumes which are not already being replicated by another GeoCluster Replicated Disk resource Volumes that are not physical disk resources Volumes that do not contain system files (The volume that you booted Windows from will not be displayed.) Volumes that exist on all nodes of the cluster Network—Select the network that you want to use for Storage Mirroring Recover mirroring and replication traffic.
critical that all files, not just some of them that might be newer, get mirrored. ● ● Use block checksum—For those files flagged as different, the mirror performs a checksum comparison and only sends those blocks that are different. Calculate Replication Set size prior to mirror—Determines the size of the replication set prior to starting the mirror. The mirroring status will update the percentage complete if the replication set size is calculated. 8.
network. For example, if you have two network routes, separate Storage Mirroring Recover and your public traffic. If you have three routes, separate the public traffic and then separate Storage Mirroring Recover from the cluster heartbeat. ● ● ● Interval to check unresponsive nodes—Specify how much time, in seconds, between checks of nodes to see if a Storage Mirroring Recover connection can be made.
To control the resource, you can bring it online and take it offline. Neither of these actions trigger failover. They just control the activity of the resource. Bringing the resource online The GeoCluster Replicated Disk resource will appear offline after it is created. When you bring it online, the following actions occur. 1. A Storage Mirroring Recover replication set is created with the same name that was assigned to the resource. 2.
GeoCluster resource properties Resource properties are displayed differently in Windows 2003 and Windows 2008. For example, the possible owners of a resource is listed on the General tab of the resource properties in Windows 2003, while in Windows 2008 they are listed on the Advanced Policies tab. For both operating systems, right-click the resource and select Properties, when you want to view or modify the resource properties.
● ● ● ● The Threshold and Period values determine the number of times cluster service will attempt to restart the failed resource within a specified period of time before moving the group to another node. "Looks Alive" poll interval—This setting specifies how often the resource is polled to determine whether it is still running on the active node. You can choose a value from the resource type, or you can specify your own value.
connection, the chance of a conflict occurring because application resources are attempting to open files exclusively while GeoCluster is mirroring those files is removed. ● Orphan files—An orphan is a file that exists in the target location but is not in the source location. You can enable the resource to remove or delete orphans during a mirror. If you choose to move orphan files, specify the location where you want to move them.
message. 2. Dependencies—By default, the GeoCluster Replicated Disk resource is not dependent on any other resources. 3. Policies—This tab controls how and when MSCS handles a failure of the resource. ● ● ● ● ● If resource fails, do no restart—Select this option if you do not want cluster service to restart the resource if it fails. If resource fails, attempt restart on current node—Select this option if you want cluster service to restart the resource if it fails.
polled to determine whether the specified disk on each node can be written to and read from. You can choose the standard time period of 1 minute, or you can specify your own value. ● Run this resource in a separate Resource Monitor—You should enable this option so that each GeoCluster Replicated Disk resource runs in its own monitor. For more information on Advanced Policies options, see your Windows documentation. 5.
volume for the orphan files because it could impact the stability of the cluster service. 6. Compression—If you want to configure Storage Mirroring Recover compression, verify that Enable Compression is selected. Depending on the compression algorithms available for your operating system, you may see a slider bar indicating different compression levels. Set the level from minimum to maximum compression to suit your needs. 7.
● You must use a pre-failback and post-failover script. The pre-failback script must contain the following case-sensitive command, substituting the name of the IP address resource assigned to the target virtual server. Cluster resource “IP_Address_Resource_Name” /OFFLINE The post-failback script must contain the following case-sensitive command, substituting the name of the group on the target virtual server.
Special configurations Storage Mirroring Recover can be implemented with very little configuration necessary in small or simple networks, but additional configuration may be required in large or complex environments. Because an infinite number of network configurations and environments exist, it is difficult to identify all of the possible configurations. Select a link to review configuration information for particular network environments.
Failover across a firewall can be performed. By default, a destination host unreachable message will trigger failover. If you do not desire this functionality, it can be disabled using the FailoverOnRouteFailure server setting. See the Scripting Guide for more information on this option.
Variable Description wins_ server_ IP_ address The IP address of the WINS server source_ server_ name The name of the source server IP_ address The IP address of the target that has taken over for the failed source (for the failover script) or the IP address of the source that is reassuming its original identity (for the failback script) For example, suppose you had the following environment. ● Source name—Alpha ● Source IP address—192.168.1.108 ● Target name—Beta ● Target IP address—116.123.
WINS replication can be added to your failover and failback scripts by using the Windows NETSH command with the WINS set replicate context. Add the following command to your failover and failback scripts. netsh wins server target’s_primary_wins_server_IP_address set replicateflag 1 Variable Description target's_primary_wins_server_IP_ address The IP address of the target's primary WINS server For example, suppose you had the following environment. ● Source name—Alpha ● Source IP address—192.168.1.
scripting the DNS updates in the failover and failback scripts. You have two options for scripting the DNS updates. ● ● Windows DNSCMD command—The Windows Support Tools contain a DNS Server Troubleshooting Tool utility. This utility includes the DNSCMD command which can be scripted to delete and add host and reverse lookup entries in DNS. Storage Mirroring Recover DFO command—Storage Mirroring Recover also has a utility, called the DFO (DNS Failover).
Variable Description www.xxx The first two octets of the source’s IP address. For example, if the source’s IP address is 192.168.1.108, this variable would be 192.168. zzz.yyy The last two octets, in reverse order, of the source’s IP address. For example, if the source’s IP address is 192.168.1.108, this variable would be 108.1. source_ server’s_ FQDN The fully qualified domain name of the source server target_ server_IP_ address The IP address on the source aaa.
You would add the following to your failback script to delete the host and reverse lookup entries and add new entries associating the source with its original identity. dnscmd DNSServer.domain.com dnscmd DNSServer.domain.com alpha.domain.com /f dnscmd DNSServer.domain.com dnscmd DNSServer.domain.com alpha.domain.com /RecordDelete domain.com alpha A 116.123.2.47 /f /RecordDelete 116.123.in-addr.arpa 47.2 PTR /RecordAdd domain.com alpha A 192.168.1.108 /RecordAdd 192.168.in-addr.arpa 108.
4. Add the same user account that has full control on the WMI DNS namespace to the domain’s DnsAdmins group where the source's primary DNS server is located. a. Select Start, Programs, Administrative Tools (Common), and Active Directory Users and Computers. b. Right-click the DnsAdmins group and select Properties. c. Select the Members tab, click Add, and identify the user account that you granted full control on the WMI DNS namespace. d.
● ● dnsservername—The name of the source domain/zone's primary DNS server (optional; local machine name will be used if missing) sourceFQDN—The source machine's Fully Qualified Domain Name (required for modify) ● sourceip—The source machine's IP address (required for modify) ● targetip—The target machine's IP address (required for modify) ● ● ● ● ● ● Options ● ● ● ● ● ● targetFQDN—The target machine's Fully Qualified Domain Name (required for modify on failback) recordtype—The type of DNS r
● ● ● ● ● ● sourceDN—The distinguished name of the source machine's computer account (CN=,DC=domain,DC=local). DFO will add a deny "Read All Properties" permission to the computer account on failover and remove the permission on failback for the trustees specified with the /trustee parameter. This prevents a source virtual server from being brought online in Windows 2008 prior to failback.
● 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.
dfo /setpassword mydomain.com\admin mypassword Stores the username (mydomain.com\admin) and password (mypassword) in the default credentials file (dfo_credentials.dat) Password Encryption Examples dfo /dnssrvname mydnsserver.mydomain.com /srcname mysource.mydomain.com /srcip 206.31.4.10 /tarip 210.11.12.13 /username mydomain.
web site to the directory where Storage Mirroring Recover is installed. 4. Add the following to your failover script. rem Commands for Macintosh-accessible volume failover rem The chngname utility (chngname.exe) must be located in the same rem directory where Storage Mirroring Recover is installed. rem The following command temporarily changes the name of the server.
rem Commands for NFS share failover rem The chngname utility (chngname.exe) must be located in the same rem directory where Storage Mirroring Recover is installed. rem The following command temporarily changes the name of the server. You rem will need to replace :\\ with the location of rem your Storage Mirroring Recover chngname utility and replace rem source_name with the name of the source machine.
Workload monitoring Once a workload protection is established you will want to monitor the protection. You can monitor the workload protection using the same Storage Mirroring Recover client that you used to establish the workload protection, or you can use several general monitoring tools that are available for all workload types.
Data workloads When you are working with data workloads, you can monitor the connection and you can monitor the status of failover monitoring. ● Monitoring a data workload ● Monitoring failover monitoring Monitoring a data workload When a source is highlighted in the left pane of the Replication Console, the connections and their statistics are displayed in the right pane.
Statistic Description Connection ID The connection ID is the incremental counter used to number each connection established. This number is reset to one each time the Storage Mirroring service is restarted. Target Name The name of the target as it appears in the server tree in the left pane of the Replication Console. If the server’s name is not in the server tree, the IP address will be displayed.
Statistic Description The commit mode status indicates the connection status. Commit Mode * ● ● ● ● Transmit Mode ● Real-time—Data is being transmitted to the target machine in realtime. Scheduled—Data is waiting to be transmitted to the target machine until one or more transmit options have been met. Started—Data is being transferred to the target machine. Paused—If the transmission is real-time and the transmission has been paused, the Transmit Mode indicates Paused.
Statistic Description ● Replicating—Data is being replicated to the target machine. ● Ready—There is no data to replicate to the target machine. ● Stopped—Replication has stopped. ● Replication Status ● ● Pending—If auto-remirror is enabled and you have experienced a source or target failure and recovery, the status will change to pending while the connections are reestablished and will update when the remirror begins.
Statistic Description Sent Compressed Replication (Bytes) * The sent compressed replication (bytes) statistic is the total number of compressed replication bytes that have been transmitted to the target. If compression is disabled, this statistic will be the same as sent replication (bytes). Queued Mirror (Ops) * The queue mirror (ops) statistic is the total number of mirror operations in the queue.
Statistic Bandwidth Limit (Kbps) Description If bandwidth limiting has been set, this statistic identifies the limit. The keyword Unlimited means there is no bandwidth limit set for the connection. Connection and sever display You can configure when the icons and colors change to accommodate your network environment. For example, a slow or busy network may need longer delays before updating the icons or colors. 1. Select File, Options.
Location Icon or Color Description Icons and colors displayed in the right pane when a server is highlighted in the left pane A green checkmark on a connection indicates the connection is working properly. Icons and colors displayed in the right pane when a server is highlighted in the left pane A red X on a connection indicates a connection error. For example, an error may be caused by broken transmission or pending replication.
Location Icon or Color Description Icons displayed in the right pane when a group is highlighted in the left pane An icon with two servers on the right pane indicates this server has active connections that are working properly. Icons displayed in the right pane when a group is highlighted in the left pane A yellow server icon with a red X on the right pane indicates a connection error. For example, an error may be caused by broken transmission or pending replication.
Location Icon or Color Description background is gray, it is a communication issue. If the connection also has a red X, it is a connection issue. Left pane icon Two red vertical lines on a server icon indicates the target is paused. Left pane icon A red tree view (folder structure) on a server icon indicates a restore is required because of a failover. Left pane icon A black X on a server icon indicates the server is not running Storage Mirroring Recover.
You can minimize the Failover Control Center and, although it will not appear in your Windows taskbar, it will still be active and the failover icon Note: will still appear in the desktop icon tray. The Failover Control Center does not have to be running for failover to occur. The following table identifies how the visual indicators change as the status of failover changes.
Time to Fail Countdown Status Bar Colored Bullets Desktop Icon Tray The bullets are green. The Time to Fail counter is counting down and resetting Source is each time a Online response is received from the source machine. The status bar indicates that the target machine is monitoring the source machine. Source Fails and Failover is Initiated The Time to Fail countdown value is 0. The status bar displays the source machine and IP The bullets are red. address currently being assumed by the target.
Monitoring a full-server workload After you have enabled full-server protection, you can monitor the protection from the Full-Server Failover Manager, and you can review the log file generated by Full-Server Failover Manager. The Protection Status is displayed in the right center of the Full-Server Failover Manager. You can tell the status of your protection from this field. ● ● ● ● ● ● ● ● ● ● Disabled—Protection for the source has not been started.
determine the status of the source. If the source is still up and users are accessing it, you need to resolve the communications errors between the source and target. Once the communication issue is resolved, the status will update to the appropriate state. If the source is indeed down and users are unable to access it, start failover. ● ● Failing over (% complete)—The target is in the process of failing over for the source. The percentage indicates how much of the failover has been completed.
Monitoring an application workload If you have not done so already, launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. After the initial mirror, your source server is protected. To change whether failover monitoring is enabled, click the Enable/Disable Monitoring button at the bottom of the window, or select either Enable Monitoring or Disable Monitoring from the Actions menu.
Protection Status Protected Description Storge Mirroring connection exists and is active Synchronizing Mirroring is in progress (% complete) Unknown Source server is not selected 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
Mirror Status Description Idle Data is not being mirrored to the target machine Mirroring If the file size of the replication set has not been calculated and the data is being mirrored to the target machine, the Mirror Status will indicate Mirroring Paused Mirroring has been paused Removing orphans Storge Mirroring is checking for orphan files within the target path location (files that exist on the target but not on the source).
Replication Status Restoring Description Data is being restored from the target to the source Transmitting Data is being sent to the target machine (Unknown) Replication status could not be determined The following table identifies the possible transmit modes.
Target Status Description Replicating Data is being replicated to the target machine Snapshot reverted The data on the source and target do not match because a snapshot has been applied on the target. Restore the data from the target back to the source. If you want to discard the changes on the target, you can remirror to resynchronize the source and target.
Virtual workloads When you are working with virtual workloads, you can monitor the connection and you can monitor the status of failover monitoring.
On this page, you can monitor and manage your protection jobs. To manage a protection, select a protection in the area at the top of the window, then use the buttons at the top of the page to perform the following tasks: ● ● Configure protection—Select a protection, then click the Configure Protection button to open the protection summary for the selected protection. Click the Change button next to setting you want to modify.
When you select this option, the target will be preserved and registered (provided that it has been fully synchronized), and the target virtual machine will appear in VirtualCenter with the name _Replica. If the target is not fully synchronized, related files will be kept on the target ESX server but will not be registered. ● Start protection—Select a protection, then click the Start button to enable protection for the protection.
● View protection details—Click this button to show or hide the bottom pane, which shows protection information for the selected protection job. Monitoring protection jobs If you have not done so already, launch the Storage Mirroring Recover Virtual Recovery Assistant console. After you have finished setting up the protection, the Monitor Protection pane will appear. From this window, you can view the status of machine protection jobs.
Toolbar button Function Undo failover—Select a protection that has already failed over, then click the Undo Failover button to undo the failover of the selected protection. Undoing failover will lose any changes to data on the replica virtual machine.For more information, see Undo failover. Next step: Failover Monitoring Hyper-V protection jobs If you have not done so already, launch the Storage Mirroring Console. In order to monitor a connection, you will first need to set up the protection job.
On this page, you can monitor and manage your protection jobs. The top part of the screen displays summary information about all connections that have been created in Storage Mirroring Console. The bottom part of the screen will display additional information and management controls specific to the type of protection job selected in the upper half of the screen. For instance, the controls will be different for a Hyper-V virtual machine protection connection or for a server being protected with Hyper-V.
Connection Information Connection Detail Description The connection is in a healthy state. State The connection is in a warning state. The connection is in an error state. The connection is in an unknown state. Connection The name of the connection. Source Server The name of the source. Target Server The name of the target. Replication Set The name of the replication set. ● ● ● Activity ● ● ● ● Connection pending—A connection has been configured but has not yet been established.
Connection Detail Description ● ● Mirror Status Idle—Data is not being mirrored. ● Paused—Mirroring has been paused. ● Stopped—Mirroring has been stopped. Removing Orphans—Orphan files on the target are being removed or deleted depending on the configuration. ● Verifying—Data is being verified between the source and target. ● Restoring—Data is being restored from the target to the source. ● Unknown—Cannot determine the mirroring status.
Toolbar Buttons Description Filter—Select an option from the drop-down list to filter the connections shown in the Monitor Connections page. ● ● ● ● All Connections—Displays all connections for all of the servers you have added to Storage Mirroring Console. Healthy connections—Displays only those connections in a healthy state. Connections with warnings—Displays only those connections in a warning state. Connections with errors—Displays only those connections in an error state.
Toolbar Button Description Configure—Select a protection, then click the Configure button to open the protection summary for the selected protection. Click the Change button next to setting you want to modify. For more information about changing protection settings, see Setting protection options. Delete—Select a protection, then click the Delete button to remove configuration information for the selected protection.
Toolbar Button Description Stop protection—Select a protection, then click the Stop button to disable protection for the job. After the initial synchronization has completed, you can use the Stop button to stop protection for a job. This allows the end user to perform a manual failover. Failover—Select a protection, then click the Failover button to shut down the source virtual machine and start the replica virtual machine. For more information, see Failing over to the replica virtual machine.
Toolbar Button Description Delete—Select a protection, then click the Delete button to remove configuration information for the selected protection. When you click the Delete button, you will be prompted to either keep or delete the associated replica virtual machine. If you no longer want to protect the source and are no longer interested in the target replica, then select the Delete the replica virtual machine files on the target server option.
Toolbar Button Description Pause protection—Select a protection, then click the Pause button to pause the protection job. Note—All protections that use the same source-to-target route will be paused. Stop protection—Select a protection, then click the Stop button to disable protection for the job. After the initial synchronization has completed, you can use the Stop button to stop protection for a job. This allows the end user to perform a manual failover.
Connection Details Summary Statistic Description Name Name of the server. Activity What Storage Mirroring Console is currently doing on the server. Source Server The name of the source. Target Server The name of the target. Bytes Sent The total number of mirror and replication bytes that have been transmitted from the source to the target. The total number of compressed mirror and replication bytes that have Bytes Sent been transmitted to the target.
1. Navigate to the Monitor Connections page by clicking the Monitor Connections button on the main toolbar. 2. Select a connection. 3. Click the View Connection Details button. The View Connection Details page will appear. Connection Properties Statistic Description Description A short description of the connection status. The connection is in a healthy state. Health The connection is in a warning state. The connection is in an error state. The connection is in an unknown state.
Statistic Connection ID Transmit Mode Description The incremental counter used to number each connection established. This number is reset to one (1) each time the Storage Mirroring service is restarted. ● Active—Data is being transmitted from the source to the target. ● Paused—Data transmission has been paused. ● Scheduled—Data transmission is waiting on schedule criteria. ● Error—There is a transmission error. ● Unknown—Cannot determine the transmission status.
Connection Statistics Statistic Description ● ● Mirror Status Calculating—The size of the data to be mirrored is being calculated. In Progress—Data is being mirrored from the source to the target. If the amount of data has been calculated, a percentage of the data that has been sent will be displayed. ● Idle—Data is not being mirrored. ● Paused—Mirroring has been paused. ● Stopped—Mirroring has been stopped. ● Removing Orphans—Orphan files on the target are being removed.
Statistic Description The total number of compressed mirror and replication bytes that have Bytes Sent been transmitted to the target. If compression is disabled, this statistic (Compressed) will be the same as Bytes Sent. Source Server and Target Server Statistic Description Name Name of the server. Activity What Storge Mirroring is currently doing on the server. State of the client communication to the server. Status may be: ● Status ● Online—Server is online. ● Offline—Server is offline.
Monitoring a cluster workload In a standard cluster configuration, where a single copy of data resides on a SCSI disk that is shared between cluster nodes, the Double-Take Source Connection resource keeps the data synchronized between your source and target. Use the standard Windows cluster tools to monitor the status of the resource.
Windows Windows 2003 2008 Discard target queue Force Resource Offline Verify Group Accept Data Reject Data Description Flush Target If you have data in the target queue, you can discard that data. If you discard the queued data, you will lose the changes associated with that data made on the previously owning node. A Storage Mirroring Recover connection will be established to replicate the node’s data (without the data that was in queue) to the other nodes.
is automatically created when the first GeoCluster Replicated Disk resource is created in a group. Once the status resource is created, it will exist as long as there is a GeoCluster Replicated Disk resource in the group. When the last GeoCluster Replicated Disk resource in a group is deleted, the status resource will be deleted. Only one status resource is created per group.
Monitoring Storge Mirroring servers If you have not done so already, launch the Storage Mirroring Console, then click the Monitor Connections button. After you specify servers in your environment, Storage Mirroring Console monitors the Storage Mirroring Console connections on those servers. Storage Mirroring Console provides easy, at-a-glance monitoring of the connections, including statistics and status information. The intent of the Storage Mirroring Console is to monitor Storge Mirroring source servers.
Log files Various Storage Mirroring Recover components (Storage Mirroring service, Replication Console, Failover Control Center, and the Command Line Client) generate a log file to gather alerts, which are notification, warning, and error messages. The log files are written to disk. Each log file consists of a base name, a series number, and an extension. ● Base Name—The base name is determined by the application or process that is running.
Viewing the log file You can view the Storage Mirroring Recover log file through the Replication Console or through any text editor. You can view any of the other component log files through any text editor. Viewing the log file through the Replication Console 1. Open a new message window by using any of the following methods: ● ● ● Note: Right-click on the server that you want to monitor in the left pane and select New, Message Window. Select the Message Window icon from the toolbar.
2. Repeat step 1 to open multiple message windows. 3. To control the window after it is created, use either of the following methods to access the control methods listed in the following table. ● Right-click on the message window and select the appropriate control. ● Select the appropriate toolbar control. ● Select Monitor, the name of the message window, and the appropriate control.
5. To move the message window to other locations on your desktop, click and drag it to another area or double-click it to automatically undock it from the Replication Console. Viewing the log file through a text editor The log files can be viewed, from the location where Storage Mirroring Recover is installed, with a standard text editor. The following table describes the information found in each column of the log file.
ip://206.31.4.305 01/15/2009 14:25:22.5030 134 131 11 2 0 Transmission Create to ip://206.31.4.305. 01/15/2009 14:25:22.6060 135 133 12 2 500000 UserData is connected to ip://206.31.4.305 01/15/2009 14:25:23.5030 136 98 13 2 87 Start Replication on connection 1 Sample Replication Console log file 00/00/0000 00:00:00.0000 Application starting 09/11/2009 12:45:53.8980 704 1032 1 2 0 Could not find XML file: C:\Program Files\HP\Storage Mirroring\Administrator.xml, default groups will be added.
● ● ● ● ● Options Notes TYPE number—Allows you to filter the messages that are displayed. Specify 1 to display warning and error messages or specify 2 to display warnings, errors, and notifications INCLUDE—Only includes specified IDs. All other IDs will not be displayed in the output EXCLUDE—Excludes specified IDs. Ignore the specified IDs and display all others list—A comma-separated list of IDs or ID ranges that follows the INCLUDE and EXCLUDE switches.
4. Modify any of the options under Messages and Alerts, if necessary. ● ● Maximum Length—Specify the maximum length of the log file. The default size is 1048576 bytes and is limited by the available hard drive space. Maximum Files—Specify the maximum number of log files that are maintained. The default is 5 and the maximum is 999. Note: If you change the Maximum Length or Maximum Files, you must restart the Storage Mirroring service for the change to take effect. 5. Click OK to save the changes.
ID Message Description 70 Double-Take kernel stopped 71 Originator A source is requesting to connect a replication set to a attempting target machine. ip://xxx.xxx.xxx.xxx 72 Connection A target machine has received a source machine’s request from request to connect a replication set to the target. ip://xxx.xxx.xxx.xxx 73 Connected to A source machine has successfully connected a ip://xxx.xxx.xxx.xxx replication set to a target machine.
ID Message Description broken, and then manually reestablish the connection in the Replication Console. 79 Memory freed to bring Double-Take Data in the source queue has been sent to the target memory usage machine, bringing the pagefile below its limit. below the limit 80 Storage Mirroring Recover is attempting to automatically Trying to autoreconnect previously established source and target retransmit to connections after a server reboot or auto-disconnect. ip://xxx.xxx.xxx.
ID Message Description transmitting the data in queue when the target catches up. 92 Mirror resumed con_id The process of mirroring data from a source machine to a target machine has resumed. 93 Mirror ended con_ id The process of mirroring data from a source machine to a target machine has ended. 94 The verification process of confirming that the Storage Verification started Mirroring Recover data on the target is identical to the con_id data on the source has started.
ID Message Description 801 Auto-disconnect has occurred on IP address with Auto-disconnect has occurred for the specified connection con_id connection. This is due to the source queue filling up Disconnected because of a network or target failure or bottleneck. replication set name: repset_ name. 10001 Activation key is not valid. An invalid activation code was identified when the Storage Mirroring service was started. 10002 Evaluation period has expired. The evaluation license has expired.
ID Message ● 52000 ● The target has been paused due to manual intervention. The target has been resumed due to manual intervention Description The target has been paused or resumed through user intervention. This error message contains various Microsoft API codes. The text Code - Internal appears at the end of this message. The code value indicates why the operation failed, and the internal value indicates the type of operation that failed.
ID Message Description File was missing from target The verification process confirms that the files on the target are identical to the files on the source. This message would only appear if the verification process showed that a file on the source was missing from the target. 53003 Could not read filename Storage Mirroring Recover could not read a file on the source machine because the file may have been renamed or deleted.
ID Message ● 600002 ● Unified login provides ADMIN access ● 800000 ● ● ● User has level access (x) The source machine source_ 700000 machine is not responding to a ping. ● Description Active Directory GetHostSpns function call failed Active Directory RemoveSpns function call failed Active Directory AddSpns function call failed Using the current login grants ADMIN access. The listed user has listed access level and access level ID.
Monitoring event messages An event is a significant occurrence in the system or in an application that requires administrators to be notified. The operating system writes notifications for these events to a log that can be displayed using the Windows Event Viewer. Three different log files are generated: application, security, and system. 1. To access the Event Viewer, select Programs, Administrative Tools, Event Viewer. 2.
ID 1 2 3 4 5 1000 1001 Category Event Message Required Response This evaluation period has expired. Mirroring and replication have been stopped. To obtain a license, please contact your vendor. Contact your vendor to purchase either a single or site license. Info. The evaluation period expires in %1 day(s). Contact your vendor before the evaluation period expires to purchase either a single or site license. Info. The evaluation period has been activated and expires in %1 day(s).
ID Category Severity Event Message Required Response gather performance data. event occurs again. DTCounters Error The Double-Take counter DLL could not map shared memory file containing the performance data. Run the installation and select Repair. Contact technical support if this event occurs again. DTCounters Error The Double-Take counter DLL could not open the "Performance" key in the Double-Take section of the registry. Run the installation and select Repair.
ID Category Severity Event Message Required Response 4003 Service Info. Source service was successfully stopped. No action required. 4004 Service Info. Target service was successfully stopped. No action required. 4005 Service Info. Kernel was successfully stopped. No action required. Error Service has aborted due to Restart the Storage the following unrecoverable Mirroring service.
ID 4011 4012 Category Service Service Severity Error Warning Event Message Required Response Auto-reconnect has failed connecting Replication Set %1 to %2 (%3) Manually reestablish the replication set to target connection. %1 This is a placeholder message for many other messages. See the specific log message for additional details. This is a placeholder message for many other messages. See the specific log message for additional details. 4013 Service Info. %1 4014 Service Info.
ID 4021 4022 4023 Category Service Service Service Severity Event Message Required Response Info. Service has resumed a mirror to %1 (%2) for Replication Set %3, ID: %4 No action required. Info. Service has stopped a mirror to %1 for Replication Set %2, ID: %3, %4 No action required. Info. Service has completed a mirror to %1 %2 for No action required. Replication Set %3, ID: %4, %5 No action required. 4024 Service Info.
ID Category Severity Event Message Required Response update its entries. 4030 4031 4032 4033 4034 Service Service Service Service Service Error Reinstall the software, using the installation RSResource.dll has an Repair option, to install a unknown error. The product new copy of the functionality has been RSResource.dll. Contact disabled. technical support if this error persists. Error RSResource.dll could not be opened. The product functionality has been disabled.
ID 4035 4036 4037 4038 4039 Category Service Service Service Service Service Severity Error Error Error Error Error Event Message Required Response Error verifying the product name. The product functionality has been disabled. Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact technical support if this error persists. Error verifying the vendor name. The product functionality has been disabled.
ID 4040 4041 4042 4043 4044 Category Service Service Service Service Service Severity Event Message Required Response The product code is illegal for this computer hardware. The product functionality has been disabled. Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact technical support if this error persists. The product code is illegal for this operating system version. The product functionality has been disabled.
ID 4045 4046 4047 4048 4049 4050 Category Service Service Service Service Service Service Severity Event Message Required Response %1 value must be between 1025 and 65535. Using default of %2. Verify that the Storage Mirroring Recover port value you are trying to use is within the valid range. If it is not, it will automatically be reset to the default value. This service failed to start because of a possible port conflict.
ID 4051 4052 4053 4054 4055 Category Service Service Service Service Service Severity Event Message Required Response Info. Service has stopped a delete orphans task to %1 (%2) for Replication Set %3, ID: %4 No action required. Info. Service has completed a delete orphans task to %1 (%2) for Replication Set %3, ID: %4 No action required. Info. Service has started a restore task to %1 (%2) for Replication Set %3, ID: %4 No action required. Info.
ID Category Severity Event Message Required Response %4 4061 Service Info. Service has stopped a verification task to %1 (%2) for Replication Set %3, ID: %4 No action required. No action required. No action required. 4062 Service Info. Service has completed a verification task to %1 (%2) for Replication Set %3, ID: %4 4063 Service Info. Bandwidth limit to %1 (%2) has changed to %3. Info. Bandwidth limit to %1 (%2) is now in the "%3" period at No action required. %4.
ID 4068 4069 4096 4097 4097 4098 4098 Category Service Service System System System System System Severity Event Message Required Response Error Failed to write to a replicating volume. Reboot the source server. Contact technical support if this event occurs again. Warning The option MoveOrphansDir has been updated because it was missing or empty. No action required. Warning The registry parameter %2 is unknown. Delete the parameter and report this issue to technical support.
ID Category Severity Event Message Required Response this error occurs again. The last Word in the Data window is the NT status code. 4099 4099 4100 4100 System System Activation Key System Warning The driver detected a hard link for a file on drive %2. Hard links are not supported. Changes to this file will not be replicated. Error The driver failed to register with filter manager.
ID 4101 4110 4111 4112 Category Activation Key Service Service Service Severity Event Message Required Response reinstalled. The last three Words in the Data window are the NT status code and the driver version numbers. Contact technical support if this event occurs after reinstalling the software. Error This service will not run on this device. Contact your sales representative for upgrade procedures. The activation code does not match the type of server you are attempting to run on.
ID 4113 4120 4150 Category Service Service Service Severity Event Message Required Response Warning Target can not write %1 due to an unknown reason. Operation will be retried (%2 times or forever). Please check the log files for further information on the error. An unknown error is prohibiting Storage Mirroring Recover from writing on the target. The operation will be retried according to the TGExecutionRetryLimit setting. Info. Target write to %1 was completed successfully after %2 retries.
ID Category Severity Event Message Required Response A task may be discarded in the following scenarios: all connections to a target are manually disconnected, replication is stopped for all connections to a target, or an auto-disconnect occurs. If one of these scenarios did not cause the task to be discarded, contact technical support. 4201 Service Warning In band task %1 discarded (submitted from %2 by %3 at %4) 4202 Service Info.
ID 4207 4300 Category Service Service Severity Event Message Required Response Warning In band scripts disabled by server - no attempt will be made to run %1 Enable task command processing. Error A connection request was received on the target before the persistent target paths could be loaded. You may need to disconnect and reconnect your replication set. If you need to block your target paths, contact technical support.
ID 4400 4401 4402 Category Service Service Service Severity Error Error Error Event Message Required Response Failed to create snapshot set for source %1 (%2) Connection ID: %3. Error: %4 The snapshot could not be created. This may be due to a lack of disk space or memory or another reason. The error code is the Microsoft VSS error. Check your VSS documentation or contact technical support. Failed to delete automatic snapshot set for source %1 (%2) Connection ID: %3.
ID 4403 4404 Category Service Service Severity Event Message Required Response Error A scheduled snapshot could not be created for source %1 (%2) Connection ID: %3. because the target data was in a bad state. A snapshot will automatically be created when the target data reaches a good state. No action required. A snapshot will automatically be created when the target data reaches a good state. Info. Set snapshot schedule for source %1 (%2) connection No action required. %3 to every %4 minutes.
ID Category Severity Event Message Required Response 4411 Service Warning The Service has detected that port %1 is being %2 by the Windows Firewall. The firewall port needs to be unblocked or restrictions against Storage Mirroring Recover removed so that Storage Mirroring Recover data can be transmitted. 5000 Service Info. Server Monitor service was successfully started. No action required. 5001 Service Info. Server Monitor service was successfully stopped. No action required.
ID 5107 5108 Category Failover Failover Severity Error Error Event Message Required Response Error occurred in running %1 script. Verify that the script identified exists with the proper permissions. The source machine %1 is not responding to a ping. This occurs when all monitored IP addresses on the source machine stop responding to pings. Countdown to failover will begin at the first occurrence and will continue until the source machine responds or until failover occurs.
ID 5301 5302 5303 5304 5305 5306 Category Monitoring Monitoring Monitoring Monitoring Monitoring Monitoring Severity Event Message Required Response Info. The following IP address was removed from target's monitoring list: %1 No action required. Info. Drive share information for %1 has been updated on the target machine. No action required. Info. The application monitor script has started successfully. No action required.
ID 5500 5501 5502 Category Service Service Service Severity Event Message Required Response Warning Storage Mirroring Recover could not connect to your SMTP server or the username and/or password supplied is incorrect. Could not connect to e-mail Verify that SMTP server server. Check to make sure is available and that you the SMTP server %1 is have identified it available (error code: %2). correctly in your e-mail notification configuration.
ID 5503 5504 5505 5506 Category Service Service Service Service Severity Event Message Required Response Warning If you are using Storage Mirroring Recover 4.4.2.1 or earlier and Windows E-mail notification could not NT 4.0, e-mail be processed. Check to notification requires make sure the correct Windows Management version of SMTPMail.DLL Instrumentation (WMI) to is registered on the system be installed. Verify that (error code: %1).
ID 5507 5508 5600 7106 7107 Category Service Service Service RepDrv RepDrv Severity Event Message Required Response Warning If you are using Storage Mirroring Recover 4.4.2.1 or earlier and Windows E-mail notification could not NT 4.0, e-mail be initialized. Check to notification requires make sure WMI is installed Windows Management and available (error code: Instrumentation (WMI) to %1). be installed. Verify that you have it installed on the Storage Mirroring Recover server.
ID 8100 8192 8192 8193 Category RepDac Resources RepDrv System Severity Event Message Required Response Error The driver encountered an unrecoverable internal error. Contact technical support. The last Word in the Data window is the internal error code. Error Driver failed to allocate Kernel memory. Replication is stopped and Reboot the server and server must be rebooted for contact technical support replication to continue. The if this event occurs again.
ID Category Severity Event Message Required Response default registry path will be used. 8200 9000 9100 9101 Resources RepKap RepKap RepKap Warning The driver failed to allocate a buffer for a file name longer than 260 characters. Reboot the server and The file will be skipped. contact technical support The last Word in the Data if this event occurs again. window is the NT status code. Warning The driver has failed to process a rename operation. The driver will resend the rename operation.
ID Category Severity Event Message Required Response Word in the Data window is the exception code. 9102 9103 9104 9105 RepKap RepKap RepKap RepKap Error The driver encountered an error writing to the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Check for related service messages. Contact technical support if this event occurs again.
ID Category Severity Event Message Required Response technical support. The last Word in the Data window is the exception code. 9106 9107 9108 RepKap RepKap RepKap Error The driver encountered an error writing file security data to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Check for related service messages.
ID 9109 9110 9111 9112 Category RepKap RepKap RepKap RepKap Severity Event Message Required Response Error The driver encountered an error writing an allocated range to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Check for related service messages. Contact technical support if this event occurs again.
ID Category Severity Event Message Required Response Word in the Data window is the exception code. 9113 9114 9115 9116 RepKap RepKap RepKap RepKap Error The driver encountered an error querying a stream from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Check for related service messages. Contact technical support if this event occurs again.
ID Category Severity Event Message Required Response Word in the Data window is the NT status code. 9117 9118 9119 RepKap RepKap RepKap Error The driver encountered an error querying for extended attributes from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Check for related service messages. Contact technical support if this event occurs again.
ID 9120 9121 9122 9123 Category RepKap RepKap RepKap RepKap Severity Event Message Required Response Error The driver encountered an error querying for file information from the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Check for related service messages. Contact technical support if this event occurs again.
ID Category Severity Event Message Required Response Word in the Data window is the exception code. 9124 9125 RepKap RepKap 10000 RepHsm 10000 GeoCluster Error The driver encountered an error writing fsctl information to the service output buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Check for related service messages. Contact technical support if this event occurs again.
ID Category Severity Event Message Required Response node interval specified for the resource. 10001 GeoCluster 10002 GeoCluster 10003 GeoCluster 10004 GeoCluster 10005 GeoCluster Info. Reconnect succeeded to node %1 for resource %2. Will be added as a possible No action required. owner when mirror is complete. Ensure that GeoCluster is running on all possible owners and that it can communicate on the public network.
ID Category Severity Event Message Required Response Warning The cluster notification thread failed to start on node %1 for resource %2. The resource should be taken offline and brought back online. 10007 GeoCluster Warning The user %1 has reverted a No action required. The snapshot for the %2 snapshot you selected resource on node %3. will be reverted. 10008 GeoCluster Warning The user %1 has discarded No action required. The queued data for the %2 queue you selected will resource on node %3.
ID Category Severity Event Message Required Response and selecting the appropriate option. Error The driver could not recall a file because it did not have a token for Contact technical impersonation. The security support if this event provider service should set occurs again. this token. The last Word in the Data window is the exception code. Error The driver could not access the file in the archive bin, due to a failed Contact technical impersonation attempt.
ID Category 11004 Service 11005 Service 11006 Service 11007 Service 11008 Service 11009 Service 11010 Service 11011 Service 12000 DTRecall Severity Event Message Warning Service has failed connection to the RepHSM driver. %1 Reboot the server or manually restart the RepHSM.sys driver. Service has aborted the archive operation. Verify the activation code on the source and target is valid for archiving. Reboot an unlicensed server. Warning Service has aborted the archive recall operation.
ID Category Severity Event Message Required Response required. 12001 DTRecall 12002 DTRecall 12003 DTRecall 12004 DTRecall 12005 DTRecall 12006 DTRecall The service failed to start. Check the user name and password for the Storage Mirroring Recall service to ensure validity. Reinstall the software if this event occurs again. Info. The service has stopped. This message indicates a system shutdown or the user stopped the Storage Mirroring Recall service. No action is required.
ID Category 12007 DTRecall 12288 RepDrv 16384 RepDrv 16385 RepDrv 16393 RepDrv 16395 Resources Severity Event Message Required Response Warning Service failed a periodic security update. (Error %1) This message refers to the Storage Mirroring Recall service. The operation will be performed every five minutes. Reinstall the software if this event occurs after five minutes. Error The driver encountered an error accessing a buffer from the service. Contact Contact technical technical support.
ID Category 16396 Resources 16400 RepDrv Severity Event Message Required Response Error The driver failed to create work queues for normal operation. This may have been caused by low system Reboot the server and resources. Reboot the contact technical support server and contact if this event occurs again. technical support if this error occurs again. The last Word in the Data window is the NT status code. Info. RepDrv has encountered an unexpected condition, usually caused by low kernel memory.
4. Select Enable notification. Note: Any specified notification settings are retained when Enable notification is disabled. 5. Specify your e-mail settings. ● ● Mail Server (SMTP)—Specify the name of your SMTP mail server. Log on to SMTP Server—If your SMTP server requires authentication, enable Log on to SMTP Server and specify the Username and Password to be used for authentication. Your SMTP server must support the LOGIN authentication method to use this feature.
● ● ● From Address—Specify the e-mail address that you want to appear in the From field of each Storage Mirroring Recover e-mail message. The address is limited to 256 characters. Send To—Specify the e-mail address that each Storage Mirroring Recover e-mail message should be sent to and click Add. The e-mail address will be inserted into the list of addresses. Each address is limited to 256 characters. You can add up to 256 e-mail addresses.
again be generated. This is a cyclical process where one message will be generated for each group of failed e-mail messages, one for each group of successful e-mail messages, one for the next group of failed messages, and so on. If you start and then immediately stop the Storage Mirroring service, you may not get e-mail notifications for the log entries that occur during startup. By default, most virus scan software blocks unknown processes from sending traffic on port 25.
Statistics Statistics logging is the process of taking snapshots of Storage Mirroring Recover statistical data. The data can be written to a file for future use. Changes to the statistics file configuration are detected and applied immediately without restarting the Storage Mirroring service. The statistics log file created is a binary file. To view the log file, you must run the DTStat utility from the command prompt.
Configuring the properties of the statistics file 1. Right-click a machine in the left pane of the Replication Console and select Properties. 2. Select the Logging tab. 3. At the top of the tab, specify the Folder where the log files for messages, alerts, verification, and statistics will be saved. 4. Under Statistics, specify the following information: ● ● ● Filename—The name of the statistics log file. The default file name is statistic.sts.
5. Select the Setup tab. 6. Verify that Log Statistics Automatically is enabled. If disabled, statistics will not be logged. 7. Click OK to save the settings. Viewing the statistics file The statistics log file created is a binary file. To view the log file, you must run the DTStat utility from a command prompt. From the directory where Storage Mirroring Recover is installed, run the DTStat command.
specified date and time ● ● Examples -STOP mm/dd/yyyy hh:mm—Filters out any data after the specified date and time -SERVER ip_address port_number—Connects DTStat to the specified IP address using the specified port number instead of to the local machine ● DTStat -i 300 ● DTStat -p -i 300 -t AlphaStats.sts ● DTStat -f AlphaStats.sts -s AlphaStats.csv -start 02/02/2007 09:25 ● DTStat -server 206.31.4.51 1106 ● This command is not case-sensitive.
Category Statistic Description Date/Time Stamp The date and time that the snapshot was taken. This is the date and time that each statistic was logged. By default, these are generated once a second, as long as there are statistics being generated. If mirroring/replication is idle, then DTStat will be idle as well.
Category Statistic Description RepBytesGenerated The number of replication bytes generated by the file system driver. This is the number of bytes generated during replication. In other words, this is roughly the amount of traffic being sent across the network that is generated by replication. It does not take into account TCP/IP overhead (headers and such). MirOpsGenerated The number of mirror operations transmitted to the target.
Category Statistic Description Kernel TargetOpenHandles The number of handles currently open on the target Kernel DriverQueuePercent The amount of throttling calculated as a percentage of the stop replicating limit Target PeerAddress The IP address of the source machine Target LocalAddress The IP address of the target machine.
Category Statistic Description Target Bytes In Target Disk Queue The number of bytes currently in the disk queue on the target Target TasksSucceeded The number of task commands that have succeeded on the target Target TasksFailed The number of task commands that have failed on the target Target TasksIgnored The number of task commands that have been ignored on the target autoDisConnects The number of automatic disconnects since starting Storage Mirroring Recover.
Category Statistic Description The state of the active connection ● ● ● Connection conState ● ● 0—None. This indicates a connection has not been established. Statistics are still available for the source and target machines. 1—Active. This indicates that the connection is functioning normally and has no scheduling restrictions imposed on it at this time. (There may be restrictions, but it is currently in a state that allows it to transmit.) 2—Paused.
Category Statistic Description acknowledgement of receipt. Connection conOpsInRepQueue The number of replication operations currently waiting to be executed on the target Connection conOpsInMirQueue The number of mirror operations currently waiting to be executed on the target Connection conBytesInRepQueue The number of replication bytes remaining to be transmitted to the target Connection conOpsTx The number of operations transmitted to the target.
Category Statistic Description Connection conResentOpCount The number of operations resent because they were not acknowledged Connection conBytesInDiskQueue The number of bytes in the source disk queue Connection conBandwidthLimit The amount of bandwidth that may be used to transfer data Connection conBytesSkipped The number of bytes skipped during a difference mirror.
Performance Monitor Performance Monitor is the Windows graphical tool for measuring performance. It provides charting, alerting, and reporting capabilities that reflect both current activity and ongoing logging. Storage Mirroring Recoverstatistics are available through the Performance Monitor. ● Monitoring Performance Monitor statistics ● Performance Monitor statistics Monitoring Performance Monitor statistics 1.
Object Statistic Description queue queue Connection Bytes in replication queue The number of replication bytes in the source queue Connection Bytes in mirror queue The number of mirror bytes in the source queue Connection Bytes received The number of bytes received by the target since the last Performance Monitor refresh Connection Bytes transferred The number of bytes transmitted from the source Connection Compressed bytes transferred The number of compressed bytes transmitted from the sou
Object Connection Statistic Task commands submitted Description The number of task commands submitted on the source Connection Tasks failed The number of task commands that have failed to execute on the source Connection Tasks ignored The number of task commands that have been ignored on the source Connection Tasks succeeded The number of task commands that have succeeded on the source Kernel Activation code failures The number of activation code failures when loading the source or target, since
Object Statistic Description Replication operations generated The number of replication operations generated on the source by the file system driver Failed logins Number of failed login attempts since the last time the Storage Mirroring service was restarted Successful logins Number of successful login attempts since the last time the Storage Mirroring service was restarted Auto disconnects The number of automatic disconnects since the last time the Storage Mirroring service was restarted on the s
Object Statistic Description Orphan Files The number of orphan files removed from the target Target Retries The number of retries performed on the target since the last time the Storage Mirroringservice was restarted on the target Target Tasks failed The number of task commands that have failed on the target.
SNMP SNMP, Simple Network Management Protocol, is the Internet's standard for remote monitoring and management of hosts, routers and other nodes and devices on a network. Storage Mirroring Recover provides an SNMP sub-agent that can be managed from an SNMP Management Console. Storage Mirroring Recover installs two components to work with SNMP. ● ● The sub-agent is a program that installs and runs on the same machine as Storage Mirroring Recover and gathers statistics, data, and traps.
SNMP traps The following table lists the Storage Mirroring Recover SNMP traps.
Object Type Trap Description Connection dttrapConnectionFailed The source to target connection was not successful Connection dttrapConnectionLost The source to target connection has been disconnected Connection dttrapMemoryLimitReached The Storage Mirroring Recover memory pool limit has been reached Connection dttrapMemoryLimitRemedied The memory pool usage is below the maximum limit specified Connection dttrapAutoReconnect Auto-reconnect needs to make a new connection Connection dttrapSchedule
Object Type Trap Description Mirroring dttrapMirrorResume Mirroring has resumed Mirroring dttrapMirrorEnd Mirroring has ended Verification dttrapVerificationStart Verification has started Verification dttrapVerificationEnd Verification has ended Verification dttrapVerificationFailure Verification has failed Restoration dttrapRestoreStarted Restoration has started Restoration dttrapRestoreComplete Restoration is complete Replication dttrapRepSetModified Sets Replication has been modified
Object Type Statistic Description General dtRepOpsGenerated The number of operations (create, modify, or delete) that have been transmitted by the replication process General dtRepBytesGenerated The number of bytes that have been transmitted by the replication process General dtFailedMirrorCount The number of operations that failed to mirror because they could not be read on the source General dtFailedRepCount The number of operations that failed to be replicated because they could not be read
Object Type Statistic Description Connection dtConnectionCount The number of active connections between machines Connection dtconIpAddress The IP address of the connected machine. If at the source, then the IP address of the target. If at the target, then the IP address of the source. Connection dtconConnectTime The duration of time since the connection was first established The state of the active connection ● ● ● Connection dtconState ● ● 0—None.
Object Type Statistic Description Connection dtconOpsInCmdQueue The number of operations (create, modify, or delete) in the retransmit queue on the source Connection dtconOpsInAckQueue The number of operations (create, modify, or delete) waiting for verification acknowledgements from the target Connection dtconOpsInRepQueue The number of replication operations (create, modify, or delete) in the queue Connection dtconOpsInMirQueue The number of mirror operations (create, modify, or delete) in the q
Error codes The following table contains error codes that you may see in the various user interfaces or in log files.
Error Code Description -120 Connection already connected -121 Mirror is not running -122 Replication set exists -123 Replication set does not exist -124 No replication set has been selected -125 Connection is replicating -126 Connection is not replicating -127 Replication set is enabled -128 Schedule is not defined -129 Replication set is changed -130 Replication set is in use -131 No Storage Mirroring Recover target identified -132 Memory is low -133 Memory is sufficient -134
Error Code Description -144 Replication set not saved -145 Connection failed -146 Cleaner option is not enabled -147 Target mirror capacity high threshold is met -148 Target mirror capacity low threshold is met -149 New option applied -150 Target is restarted -151 Replication is out of memory -152 Write access is blocked on the volume -153 This error code could be one of two errors.
Error Code Description -167 Restore required state is unknown -168 Not a valid failover source -169 Failover login failed -170 Feature is not supported -171 Command is not supported -172 Target queue log file error -173 Target disk is full -174 Target disk has sufficient disk space -175 Error reading from or writing to the queue log file -176 Memory-based queue is in use -177 Disk-based queue is in use -178 Restore is required -179 ID the driver supplied to the service is invalid
Error Code Description -201 Monitor name exists -202 Monitor name does not exist -203 Monitor configuration exists -204 Monitor configuration does not exist -205 Monitor configuration is in use -206 Monitor configuration is not in use -207 Source is online -208 Source is offline -209 Server is not failed over -210 Server is failed over -211 Server is not being monitored -212 Failback is in progress -213 IP address placeholders on the target are unavailable -214 Target NIC was no
Error Code Description -225 Invalid path -226 Kernel module is not loaded -2201 Error communicating with e-mail server -2202 Error connecting to e-mail server -2203 E-mail notification is disabled -2204 E-mail notification is enabled -2205 E-mail notification requires Internet Explorer version 5.0 and WMI -2206 E-mail notification requires Internet Explorer version 5.
Error Code Description -2303 Bandwidth limit not found -2304 Bandwidth limit day is invalid -2305 Bandwidth limit label is invalid -2401 Snapshot module is not loaded -2402 Error reading the snapshot .
Failover Your failover process will depend on the type of workload you are protecting.
Failing over data and cluster workloads The failover process, including script processing, can be tested at any time. To force unavailability, disconnect the network cable from a monitored machine, wait for the Time to Fail counter to decrease to zero and failover begins. To avoid the countdown delay, highlight the monitored machine name in the Failover Control Center window and select Failover. If Manual Intervention is enabled, the Failover Control Center will prompt you when a failure occurs.
Target Data State at Failover Apply Data in Target Queues Then Failover Description All of the data in the target queue will be applied before failover begins. Discard Data in Target All of the data in the target queue will be Queues discarded and failover will begin immediately.
Full-server workload failover Full-server failover can be initiated through the Full-Server Failover Manager client or by using a command line interface. ● Failing over using the Full-Server Failover Manager ● Failing over from the command line Failing over using the Full-Server Failover Manager When a failover condition is met, you will want to start failover. Additionally, you can start it without a failover condition, as long as protection is enabled.
● ● ● Shutdown source server if running—If the source is still running, FullServer Failover Manager can stop it. Although, if Full-Server Failover Manager cannot communicate with the source, the shutdown command will fail. This option prevents network conflicts in those cases where the source and target are still both running and communicating, such as a forced failover. Use live data—Select this option to use the data on the target at the time of failover.
Failing over from the command line You can configure connections and initiate failover without using the Full-Server Failover Manager user interface. The same executable that launches the user interface can be used from a command prompt with options. The command line execution opens the user interface, passes through specified parameters, and initiates specified processes.
● ● ● Examples ● Notes 6—Informational, error, exception, debug, and internal coding messages are logged CONFIG filename—Name of the file that contains the failover options. If no file is specified, the FFMDefaults.xml file will be used.
Application failover If you have not done so already, launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. There are two options for how to perform failover: ● ● If you selected DNS failover, you can use the Application Manager to automate failover. If you selected Identity failover, you will need to use a manual process for failover.
the stores manually and run the Replace replicas PowerShell call from the failover script to update the PF replicas (if applicable). ● ● ● ● After failover, linked databases in the SQL instance will be unavailable until the service master key is updated. After failover, you will need to run the command “alter service master key force regenerate” against the SQL target server to reset the service master key, then remove and re-add the linked servers into the target SQL instance.
Failing over using DNS If you have not done so already, launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. Based on the current protection status and/or failover state, the Failover/Failback button on the Monitor tab and menu options will be updated to display the available command.
When the Manual Intervention Required option is selected on the Failover tab of the Configure Protection window, a prompt will occur when a failover condition is met. For more information about setting failover options, see the Failover settings section for your application.
a. If you want to use the most recently replicated data on the target, select Use live data. b. If you want to use the data from a snapshot, select Revert to specified snapshot, then select the snapshot in the list. To help you understand what snapshots are available, use the Type and Status columns. The Status indicates the state of the connection between the source and target at the time the snapshot was taken. The Type information is displayed in the following table.
You cannot cancel or interrupt the failover process. Note: The length of time needed for a failover depends on the number of users and how long it takes to start services on the target. For a large number of users, the failover process could take a while. Next step: Fail back using DNS Failing over using identity If you have not done so already, launch the Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager.
If DNS failover was selected, the clients will have to wait for the IP cache to expire, or type in ipconfig /flushdns in a command window. This time can be adjusted by lowering the TTL (Time to Live) setting within your DNS server’s configuration. For more information, refer to your DNS server documentation.
display a prompt asking if a failover is desired. The time it takes for the Application Manager to realize a complete source cluster failure varies greatly. At times, the prompt can be seconds after the failure, or it might take several minutes. If you want the prompt to appear more quickly and you know that the source cluster has failed, you can decrease the amount of wait time by closing the Application Manager, re-opening it, and selecting the protected pair (if it is not automatically selected).
Virtual workload failover Select one of the following virtual machine failover scenarios: ● Fail over an ESX virtual machine ● Fail over a server to a virtual target machine on VMware ESX ● Fail over a physical or virtual machine with Hyper-V ● Fail over a Hyper-V virtual machine Failing over an ESX virtual machine If you have not done so already, launch the Storage Mirroring Recover for Virtual Infrastructure console.
7. Click the Reverse protection button. When you are prompted to confirm, click Yes . At this point, the protection job will be back in its original configuration. Verifying the quality of the backup data without disrupting clients 1. Click the Failover button. 2. Choose the Test failover option. 3. Review the target virtual machine to verify that the data quality is acceptable. At this point, you can either: ● ● Undo the failover as described in step 4.
3. Complete the current replication cycle before failover—Select this option to let the current replication cycle complete before failing over. If the protection job is not in the “Stopped” state, the failover will begin after the ongoing synchronization or replication cycle is complete. Note: If the protection job is in “Stopped” or “Error” state, or if the source is down, this option is not available. Failover will begin immediately. 4.
2. The VMware virtual drivers for video, mouse, disk controllers, and network adapters are injected into the Windows registry on the target virtual disk. 3. The target virtual disk volumes are un-mounted and removed from the Virtual Recovery Appliance. 4. If you are performing manual failover, the source machine is shut down. 5. The target virtual disk volumes are connected to the replica virtual machine. 6. The replica virtual machine is powered on.
3. Delete the protection job from the Virtual Recovery Assistant client. If asked whether or not to delete the associated replica virtual machine, DO NOT delete the replica, then confirm the selection. Failing over a physical or virtual machine with Hyper-V to a replica virtual machine If you have not done so already, launch the Storage Mirroring Console, then click the Monitor Connections button to manage failover.
1. The replica virtual machine will be shut down. 2. The source virtual machine will be restarted (if it was shutdown with a live failover). 3. The protection will be restarted (a file difference mirror will be performed). Note: All changes made to the replica virtual machine while the job is in a failed over state will be lost when an Undo is performed.
● ● Live failover—Select this option to perform a live failover with network connectivity to the target replica virtual machine. Live failover will shut down the source virtual machine (if available), stop the protection job, and start the replica virtual machine with full network connectivity. Test failover—Select this option to perform a test failover without network connectivity to the target replica virtual machine.
Failback Your failover process will depend on the type of workload you are protecting. ● Failback for data workloads ● Failing back a full-server workload ● Failing back an application workload ● Failing back a virtual workload Note: Failback is not available for some types of virtual workloads.
Failback for data workloads Failover occurred because the target was monitoring the source for a failure, and when a failure occurred, the target stood in for the source. User and application requests that were directed to the failed source are routed to the target. While the users are accessing their data on the target, you can repair the issue(s) on the source. Before users can access the source again, you will need to restore the data from the target back to the source and perform failback.
5. Configure that IP address so that it does not automatically register with DNS. This option is on the Advanced TCP/IP Settings dialog box on the DNS tab. 6. Do not enable the modified NIC yet. If you do, you will receive a network name conflict, because the target has the source’s identity because of failover. There are many variations for dealing with a name conflict, here are a few examples. ● ● ● Enable the modified NIC, knowing you will get the name conflict error. Disregard the error.
b. Identify the Original Source machine. This is your source machine where the data originally resided. c. Select the Restore From machine. This is the target machine where the copy of the data is stored. If your target is a cluster, you can specify just one node in the cluster and restore only from that node.
f. The Restore To and Restore From paths will automatically be populated when the replication set is selected. The restore to path is the directory that is the common parent directory for all of the directories in the replication set. If the replication set crosses volumes, then there will be a separate path for each volume. The restore from path is the path on the target server where the replicated files are located.
k. If your original source was using Replicate NT Security by Name, you must enable that option on the target before you start the restoration. The option is available on the target’s Server Properties on the Source tab. l. Click Restore to begin the restoration. You can identify a restoration connection because it is enclosed in parenthesis ( ) and it has _Restore appended to the end of the replication set name. The initial restoration is complete when the Mirror Status is Idle.
created on the target during failover will need to be created manually on the source. 15. On the source, change the IP address that you modified earlier to the unique address back to its original address. You can also enable any other NICs on the source. 16. Also on the source, change the source name back to its original name and reboot, or restart the Workstation, Server, and any other services you were prompted to stop. 17. Once the source is back online, users can reconnect to the source. 18.
a. Open the Failover Control Center and select the target that is currently standing in for the failed source. b. Select the failed source and click Failback. The user downtime starts now. If you have a pre-failback script configured, it will be started. If the target is a cluster, you will need to determine the active node and Note: failback from that node. Then you will need to failback from each of the other nodes to synchronize all of the nodes of the cluster. c.
b. Identify the Original Source machine. This is your source machine where the data originally resided. c. Select the Restore From machine. This is the target machine where the copy of the data is stored. If your target is a cluster, you can specify just one node in the cluster and restore only from that node.
f. The Restore To and Restore From paths will automatically be populated when the replication set is selected. The restore to path is the directory that is the common parent directory for all of the directories in the replication set. If the replication set crosses volumes, then there will be a separate path for each volume. The restore from path is the path on the target server where the replicated files are located.
k. If your original source was using Replicate NT Security by Name, you must enable that option on the target before you start the restoration. The option is available on the target’s Server Properties on the Source tab. l. Click Restore to begin the restoration. You can identify a restoration connection because it is enclosed in parenthesis ( ) and it has _Restore appended to the end of the replication set name.
Failing back a full-server workload After your target has failed over and becomes your source, you can stay with that configuration long term. However, in some instances, it may be necessary or desired to go back to using the original hardware after you have failed over. Use the following process to failback to your original (or other) hardware. 1. Because your new source is on the network, you must make sure your original source is unique on the network to avoid name and IP address conflicts.
Application failback and restoration If you have not done so already, launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. 1. Before you failback, you may need to rebuild your source server. If necessary, refer to instructions on rebuilding an Exchange or SQL source server. 2.
failback the CCR, LCR, or SCC replication will need to be manually reseeded after verifying Exchange is functioning properly. For information about this process, see Microsoft TechNet Article How to Seed a Cluster Continuous Replication Copy. If an error occurs during failback, a message box will appear. You can use the Actions menu to launch the failback log file. Rebuilding an Exchange or SQL source The following sections guide you through rebuilding a source application server following a failure.
5. Using the Exchange CD, start the Exchange installation on the source using the following command :\setup\i386\setup.exe /DisasterRecovery. 6. At the Component Selection dialog box, set the Action column to Disaster Recovery for all of the components that were originally installed on the source (before it failed). 7. Verify that each of the components selected are installed in the same location on the source as they are on the target.
11. Install Storage Mirroring Recover, if necessary. 12. Copy the following files from the target to the Storage Mirroring Recover directory on the source: ● exchfailover.exe ● post_restore__.bat 13. Continue the failback and restoration process. 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.
Failing back using DNS If you have not done so already, launch the Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. Based on the current protection status and/or failover state, the Failover/Failback button on the Monitor tab and menu options will be updated to display the available command.
To initiate failback, click the Failback button, or select Actions, Failback. The Initiate Failback window will appear. On the Initiate Failback window, select the following failback options: 1. In the Source IP Address field, select the IP address the Storage Mirroring Recover data will be transmitted through. You should only change this setting if you want to select a different route for Storage Mirroring Recover traffic.
● 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.
2. Stop all of the services on the source so that you can overwrite the data with the newer data on the target. Because the source server cannot communicate with a domain controller because its network connection is still inactive, this will take longer than normal. The following lists the services that must be stopped, in the order in which they must be stopped. Stop the services appropriate to your application.
W3SVC SMTPSVC SQL MSSqlServer SQLServerAgent MSSearch (SQL 2000)/MSFteSQL (SQL 2005) MSSQLServerADHelper MSDTC MSSQLServerOLAPService MSDTSServer SQLWriter SQLBrowser (SQL 2005) File Server Computer Browser SharePoint IISADMIN HTTPFilter SMTPSVC W3SVC SPAdmin SPSearch SPTimerV3 SPTrace SPWriter If the source is purely a SQL server (that is, the back-end for a SharePoint Note: configuration), you will not need these services.
BlackBerry Server Alert BBAttachServer BlackBerry Controller BlackBerry Database Consistency Service BlackBerry Dispatcher BlackBerry Policy Service BlackBerry SyncServer BlackBerry MDS Connection Service MdsTomcat 3. On the target, open the Failover Control Center (Start, Programs, Storge Mirroring, Availability, Storage Mirroring RecoverFailover Control Center). 4. Double-click the target machine that is currently standing in for the failed source to login. 5.
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. ● Restore To—The source where the data will be restored to. 13. Disable Only if backup copy is more recent.
If DNS failover was selected, the clients will have to wait for the IP cache to expire, or type in “ipconfig /flushdns” in a command window. This time can be adjusted by lowering the TTL (Time to Live) setting within your DNS server’s configuration. For more information, refer to your DNS server documentation.
Connections A unique connection ID is associated with each Storage Mirroring Recover connection. The connection ID provides a reference point for each connection. The connection ID is determined by sequential numbers starting at one (1). Each time a connection is established, the ID counter is incremented. It is reset back to one each time the Storage Mirroring service is restarted.
Data queues During the Storage Mirroring Recover installation, you identified the amount of disk space that can be used for Storage Mirroring Recover queuing. Queuing to disk allows Storage Mirroring Recover to accommodate high volume processing that might otherwise fill up system memory. For example, on the source, this may occur if the data is changing faster than it can be transmitted to the target, or on the target, a locked file might cause processing to back up.
that next operation. Also, if one operation is larger than the defined size limit, the entire operation will be written to one transaction log. 3. When system memory is full, the most recent changed data is added to the disk queue, as described in step 2. This means that system memory contains the oldest data. Therefore, when data is transmitted to the target, Storage Mirroring Recover pulls the data from system memory and sends it.
● Folder—This is the location where the disk queue will be stored. Storage Mirroring Recover displays the amount of free space on the volume selected. Any changes made to the queue location will not take effect until the Storage Mirroring service has been restarted on the server. Select a location on a non-clustered volume that will have minimal impact on the operating system and applications being protected. For best results and reliability, this should be a dedicated, non-boot volume.
not perform as well as a mirrored or non-parity striped set because writing to a RAID 5 array incurs the overhead of generating and writing parity data. RAID 5 write performance can be up to 50% less than the write performance of a single disk, depending on the adapter and disk. Another option is to use a solid state disk, which are hard drives that use RAM instead of disk platters.
Mirroring Recover, you might configure the application to use 512 MB and Storage Mirroring Recover to use 256 MB, leaving 256 MB for the operating system and other applications on the system. Many server applications default to using all available system memory, so it is important to check and configure applications appropriately, particularly on high-capacity servers. Any changes to the memory usage will not take effect until the Storage Mirroring service has been restarted on the server.
Auto-disconnect and auto-reconnect While disk queues are user configurable and can be extensive, they are limited. If the amount of disk space specified for disk queuing is met, additional data could not be added to the queue and data would be lost. To avoid any data loss, the auto-disconnect and auto-reconnect processes occur. ● ● ● ● Exhausted queues on the source—If disk queuing is exhausted on the source, Storage Mirroring Recover will automatically start disconnecting connections.
● Target service shutdown—If the target service is stopped and restarted, there could have been data in the target queue when the service was stopped. To prevent any loss of data, the Storage Mirroring service will attempt to persist to disk important target connection information (such as the source and target IP addresses for the connection, various target queue information, the last acknowledged operation, data in memory moved to disk, and so on) before the service is stopped.
3. Verify that the check box Automatically Reconnect During Source Initialization is marked to enable the auto-reconnect feature. 4. Click OK to save the settings.
Pausing and resuming target processing You can break the source/target connection without disconnecting the connection, so that you can control the transmission of data across the network. You can do this by pausing the target. If the target is paused, data is queued on the source until you manually resume the target.
Blocking writing to the target paths You can block writing to the paths on the target that contain the copy of the replication set data. This keeps the data from being changed outside of Storage Mirroring Recover processing. To block the replication set data paths on the target, open the Replication Console, and right-click the connection on the right pane of the Replication Console. Select Block Target Path(s). To unblock the paths, right-click the connection and deselect Block Target Path(s).
Disconnecting a connection To disconnect a Storage Mirroring Recover connection, open the Replication Console, and right-click the connection on the right pane of the Replication Console. Select Disconnect. The source and target will be disconnected. If a connection is disconnected and the target is monitoring the source for failover, you will be prompted if you would like to continue monitoring for a failure.
Mirroring Mirroring is one of the key components of Storage Mirroring Recover. You can perform the following functions to manage mirroring.
Stopping, starting, pausing, or resuming mirroring After a connection is established, you need to be able to control the mirroring. You can start, stop, pause and resume mirroring. open the Replication Console, and right-click the connection on the right pane of the Replication Console. Select Mirroring and the appropriate mirror control.
Properties Source tab can be on or off. The use of this option does not change the action performed during the mirror. Server Properties Source Tab Checksum All (X) (X) Connection Manager Mirroring Tab or Start Mirror Dialog Only if File Source Differences is Newer Action Performed Checksum X Any file that is different on the source and target based on the date, time, and/or size is transmitted to the target. The mirror sends the entire file.
Server Properties Source Tab Checksum All Connection Manager Mirroring Tab or Start Mirror Dialog Only if File Source Differences is Newer Action Performed Checksum blocks that are different.
Mirroring automatically In certain circumstances, for example if the disk-based queues on the source are exhausted, Storage Mirroring Recover will automatically disconnect connections (called auto-disconnect) and then automatically reconnect them (called auto-reconnect). In order to ensure data integrity on the target, Storage Mirroring Recover will perform an automatic mirror (called an auto-remirror) after an auto-reconnect. Auto-remirror is a per source option.
3. Verify that Perform Remirror After Auto-Reconnect is selected to initiate an auto-remirror after an auto-reconnect. If auto-remirror is disabled and an auto-reconnect occurs, the transmission Note: state of the connection will remain pending after the reconnect until a mirror is started manually. 4. Verify that Mirror only Changed Files on Source Reboot is selected to use the Windows NTFS change journal to track file changes.
Running scripts during mirroring You can customize your mirroring process by running customized scripts on the target at predefined points in the mirroring process. Scripts may contain any valid Windows command, executable, batch, or script file. The scripts are processed using the same account running the Storage Mirroring service, unless you provide specific credentials on the Server Properties Script Credentials tab for the target server. There are three types of mirroring scripts.
4. For each of the three predefined points in the mirroring process, specify the following information. ● ● ● ● ● Script path—Specify the path and filename for each script. Arguments—If needed, specify any arguments that are required to execute your script. The arguments must be valid for your script. Allow interaction with the Desktop—Enable this option if you want the script processing to be displayed on the screen. Otherwise, the script will execute silently in the background.
5. Click OK to save the settings. Mirror scripts are dependent on the target and target path location of a connection. Therefore, if you establish mirror scripts for one connection and then establish additional connections to the same target using the Note: same target path location, the mirror scripts will automatically be applied to those subsequent connections. If you select a different target path location, the mirror scripts will have to be reconfigured for the new connection(s).
Removing orphan files An orphan file is a file that exists in the target’s copy of the replication set data, but it does not exist in the source replication set data. An orphan file can be created when you delete a file contained in the source replication set while there is no Storage Mirroring Recover connection. For example, if a connection was made and a mirror was completed and then the connection was stopped and a file was deleted on the source, an orphan file will exist on the target.
4. To configure orphan files for processing during a mirror, verify, or restore, use the following instructions. a. Right-click the connection on the right pane of the Replication Console and select Connection Manager. b. Select the Orphans tab. c. Specify if you want to log the name of the orphan files to the Storage Mirroring Recover log file on the target by marking Log Orphaned Files to Target Log. d. By default, the orphan files feature is disabled. To enable it, mark Move/Delete Orphan Files. e.
f. Specify if you want to Remove All Orphans or Remove Orphans not modified within the following time period. If you select the time-based option, only orphans older than the time you specify will be removed. g. Click OK to save the settings.
Replication Replication is one of the key components of Storage Mirroring Recover. This section contains the following replication topics. ● ● ● ● Replication capabilities—Review this list to learn what Storage Mirroring Recover supports for replication. Replication sets—This section contains instructions for creating and using Storage Mirroring Recover replication sets.
Replication capabilities Storage Mirroring Recover replicates file and directory data stored on any Windows file system (FAT, FAT32, NTFS4, and NTFS5). Replicated items also include Macintosh files, compressed files, NTFS attributes and ACLs (access control list), dynamic volumes, files with alternate data streams, sparse files, and encrypted files. Files can be replicated across mount points, even though mount points are not created on the target.
3. If you select a dynamic volume and you increase the size of the volume, the target must be able to compensate for an increase in the size of the dynamic volume. 4. If you select files with alternate data streams, keep in mind the following. a. Alternate data streams are not included in the replication set size calculation. Therefore, you may see the mirror process at 100% complete while mirroring continues. b. The number of files and directories reported to be mirrored will be incorrect.
where the encrypted file is located is out of space, when it actually may be the location where the temporary file is trying to be created that is out of disk space. 6. If you are using mount points, keep in mind the following. a. By default, the mount point data will be stored in a directory on the target. You can create a mount point on the target to store the data or maintain the replicated data in a directory.
restoration is complete and replication will continue from the target to the source. e. If you have restored your data before starting the failback process, make sure the restoration process does not have pending transactions and is complete before starting failback. If you are restoring your data after the failback the process has completed, users will not be accessing the data once failback occurs, so there are no opportunities for pending transactions. 8.
Replication sets A replication set defines the data on a source machine that Storage Mirroring Recover protects. Replication sets are defined by volumes, directories, files, or wild card combinations. Creating multiple replication sets allows you to customize sets of data that need to be protected. When working with data workloads, you need to define the replication set data yourself.
● Calculating replication set size ● Deleting a replication set Keep in mind the following notes when creating and working with replication sets and connections. ● Limitations ● ● ● ● Replication set rules are limited in length meaning that the entire volume\directory\filename including slashes, spaces, periods, extensions, cannot exceed 259 characters.
● ● ● If you rename the root folder of a connected replication set, Storage Mirroring Recover interprets this operation as a move from inside the replication set to outside the replication set. Therefore, since all of the files under that directory have been moved outside the replication set and are no longer a part of the replication set, those files will be deleted from the target copy of the replication set. This, in essence, will delete all of your replicated data from the target.
replication set to ensure the data is replicated to the correct location. (The second file can be a zero byte file if desired.) ● Backups ● ● Storage Mirroring Recover does not replicate the last access time if it is the only thing that has changed. Therefore, if you are performing incremental or differential backups on your target machine, you need to make sure that your backup software is using an appropriate flag to identify what files have been updated since the last backup.
To hide offline files, such as those generated by snapshot applications, select File, Options and disable Display Offline Files. Offline files and folders are denoted by the arrow over the lower left corner of the folder or file icon. 4. Identify the data on the source that you want to protect by selecting volumes, drives, directories, and/or specific files. Note: Be sure and verify what files can be included by reviewing Replication capabilities. 5.
1. Open the Replication Console. 2. If you do not have a replication set created, you need to create one. Highlight a source in the left pane of the Replication Console and select Insert, Replication Set from the menu bar. You can also right-click on the source name and select New, Replication Set. A replication set icon appears in the left pane under the source. By default, it is named New Replication Set.
4. From the Replication Set Properties dialog box, click Add. 5. Specify a path, wild card, or specific file name. Select the Include, Exclude, and/or Recurse sub-directories attributes to be applied to this rule and click OK. 6. Repeat steps 3 and 4 to add additional replication set rules. 7. If you need to edit an existing rule, highlight it and click Edit. 8. If you need to remove a rule, highlight it and click Remove. 9.
Renaming and copying a replication set To rename or copy a replication set, open the Replication Console. Click once on a highlighted replication set name to edit the field. Specify a unique name and press Enter . The process is similar to renaming a folder in Windows Explorer. If the original replication set has not been saved (red icon), the new name replaces the original name. If the original replication set is saved (black icon), the new name creates a copy of the original replication set.
4. If the replication set size has never been determined, click Calculate. If the replication set has previously been determined, the button will be labeled Recalculate. Depending on user activity, the size shown may not accurately reflect the current size of the replication set. If changes are occurring to files in the replication set while the calculation is being made, the actual size may differ slightly. The amount of data is determined at the exact time the calculation is made. 5.
Deleting a replication set You can only delete a replication set if it is not currently connected. If the replication set is connected, you must disconnect the connection and then delete the replication set. To delete a replication set, open the Replication Console. Right-click the replication set icon and select Delete. Additionally, you can highlight the replication set and press the Delete key on the keyboard.
Starting replication Starting replication when establishing a connection is the default and recommended configuration. If replication is not started, data is not added to the queue on the source, and source/target data integrity is not guaranteed. To start replication, open the Replication Console. Right-click the connection on the right pane of the Replication Console and select Replication, Start.
Inserting tasks during replication Task command processing is a Storage Mirroring Recover feature that allows you to insert and run tasks at various points during the replication of data. Because the tasks are user-defined, you can achieve a wide variety of goals with this feature. For example, you might insert a task to create a snapshot or run a backup on the target after a certain segment of data from the source has been applied on the target.
Verification Verification is the process of confirming that the data on the target is identical to the data on the source. Verification creates a log file detailing what was verified as well as which files are not synchronized. If the data is not the same, Storage Mirroring Recover can automatically initiate a remirror. The remirror ensures data integrity between the source and target.
Verifying manually A manual verification can be run anytime a mirror is not in progress. 1. Open the Replication Console. 2. Right-click the connection on the right pane of the Replication Console and select Verify. 3. Select the verification options that you would like to perform. ● ● ● Verify only—This option verifies the data and generates a verification log, but it does not remirror any files that are different on the source and target.
Database applications may update files without changing the date, time, or file size. Therefore, if you are using database applications, you should Note: use the block checksum comparison to ensure proper verification and remirroring. 4. Click OK to start the verification.
Verifying on a schedule Verification can be scheduled to occur automatically at periodic intervals. 1. Open the Replication Console. 2. Right-click the connection on the right pane of the Replication Console and select Connection Manager. 3. Select the Verify tab. 4. Specify when you want to start the initial verification. Select the immediate date and time by clicking Now, or enter a specific Date and Time. The down arrow next to Date displays a calendar allowing easy selection of any date.
7. If you are remirroring your files, you can specify Only if Source file is newer than Target copy so that only files that are newer on the source than on the target are remirrored. If you are using a database application, do not use the newer option unless you know for certain you need it. With database applications, it is Note: critical that all files, not just some of them that might be newer, get mirrored. 8.
Configuring the verification log A verification log is created on the source during the verification process. The log identifies what is verified as well as which files are not synchronized. 1. Open the Replication Console. 2. Right-click the source server on the left pane of the Replication Console and select Properties. 3. Select the Logging tab. 4. At the top of the window, Folder identifies the location where the log files identified on this tab are stored.
name. For example, since the default is DTVerify.log, the verification log for the replication set called UserData would be UserData DTVerify.log. 6. Specify the Maximum Length of the log file. The default is 1048576 bytes (1 MB). When the log file reaches this limit, no additional data will be logged. 7. By default, the log is appended to itself each time a verification process is completed. Clear the Append check box if you do not want to append to the previous log file.
Source Attributes: Timestamp = 1/12/2008 3:28:20 PM Size = 17 Mask = [0x20] Target Attributes: Timestamp = 1/20/2008 5:05:26 PM Size = 2 Mask = [0x20] 17 BYTES OUT OF SYNC Completion Time: 1/24/2008 12:37:44 PM for connection 2 (Sales data for alpha --> 206.31.65.40 : 1100) Elapsed Time (seconds): 1320.
in is 23. The hexadecimal number may be up to four digits. 2. Convert the hexadecimal number to its 16-digit binary equivalent. You can use the Windows calculator for this conversion. a. Select Start, Programs, Accessories, Calculator. b. Switch to scientific view, if it is not already in that view, by selecting View, Scientific. c. Select Hex. d. Enter the hexadecimal number, for example 23, as specified in your verification log. e.
Position (from right to left) Attribute Sample Hexadecimal Number 23 13 Offline 0 14 Not content indexed 0 15 None 0 16 None 0 4. Using the same chart above, identify those attributes that are enabled by those positions equal to one (1). The positions equal to zero (0) are disabled and that attribute does not apply. So hexadecimal number 23, which converted to 0000000000100011, indicates read only, hidden, and archive.
Verify target data viability If you have not done so already, launch the Application Manager. ● ● Note: ● ● Target data verification can only be used with Exchange and SQL. In order to use target data verification, the target server must be running Storage Mirroring Recover version 5.2 or later. If the target server is on a cluster, the Target Data Verification feature is not available. In a workgroup (with no DNS), Target Data Verification for SQL is not supported.
● ● Note: ● ● You can also verify target data viability from a command line interface. The TDV.exe utility is available from the Application Manager folder in the directory where you installed Storage Mirroring Recover. For more information about using the target data verification command line utility, see Using the Target Data Verification (TDV) utility.
a. In the Services area, select whether you want to start only the core application services, or all of the services you selected on the Failover tab when you configured protection. The Start Selected Services option would be used to include application add-ons such as BlackBerry or anti-virus when configured with failover. b.
7. You must click the Continue button to revert the target to the pre-test state and transition out of testing mode. 8. If an issue is encountered during the target data verification process, the Undo button will be enabled. Click Undo to revert the target to its pre-test state and remove the snapshots and any other items created for the verification test. Vshadow is used to delete snapshots created during target data verification.
Data transmission Storage Mirroring Recover data is continuously transmitted to the target machine. Although the data may be queued if the network or target machine is slow, the default transmission setting is to transmit the data as soon as possible. You can modify the transmission to suit your environment.
Stopping, starting, pausing, and resuming transmission To start, pause, or resume the transmission of data from the source to the target, open the Replication Console. Right-click an established connection, select Transmit and the appropriate transmission control.
Scheduling data transmission Using the Connection Manager Transmit tab, you can set start and stop criteria along with a schedule window. Storage Mirroring Recover checks the schedule once every second, and if a user-defined criteria is met, transmission will start or stop, depending on the Note: option specified. Any replication sets from a source connected to the same IP address on a target will share the same scheduled transmission configuration. 1. Open the Replication Console. 2.
● ● ● Transmission session start—This option establishes a date and time of the day to begin transmitting data. For example, you may want to specify a transmission time that corresponds to a low bandwidth usage time. Once started, Storage Mirroring Recover will continue to transmit data until the queue is empty or until another limitation stops the transmission. Specify a Date and Time to start transmitting data.
for loss of data. To avoid using the entire queue, you can configure Storage Mirroring Recover to begin transmitting data to the target when the queue reaches a certain point. This point can be defined as a percentage of the disk queue that must be in use or the number of bytes in the disk queue. For example, if you specify 40%, when 40% of the queue is in use, Storage Mirroring Recover initiates the transmission process and sends the data in the queue to the target machine.
● ● Time Limit—The time limit specifies the maximum length of time for each transmission period. Any data that is not sent during the specified time limit remains on the source queue. When used in conjunction with the session interval start option, you can explicitly define how often data is transmitted and how long each transmission lasts. Specify the maximum length of time that Storage Mirroring Recover can continue transmitting by indicating a length of time and choosing minutes, hours, or days.
transmitted and when the 10 MB Byte Limit is reached, the network connection closes. This is useful in configurations where metered charges are based on connection time. 6. Schedule a transmission window to establish a period of availability for all Storage Mirroring Recover transmissions. You can specify a begin and end time for all Storage Mirroring Recover transmissions. When a transmission window is in effect, all other start and stop criteria are bound by this window.
● ● ● Enable Transmission Window—This option specifies whether a transmission window is in use. Open window time—Specifies the time, formatted for AM or PM, when the transmission window will open, allowing transmission to begin. Close window time—Specifies the time, formatted for AM or PM, when the transmission window will close, stopping all transmission. 7. Click OK to save the settings.
Limiting transmission bandwidth Bandwidth limitations are available to restrict the amount of network bandwidth used for Storage Mirroring Recoverdata transmissions. The network administrator specifies a percentage of bandwidth that is available or an absolute bandwidth limit for Storage Mirroring Recover transmissions and Storage Mirroring Recover never exceeds that allotted amount. The bandwidth not in use by Storage Mirroring Recover is available for all other network traffic.
4. You have three bandwidth choices. ● ● ● No Bandwidth Limit—Data will be transmitted at all times using all available bandwidth. Fixed Bandwidth Limit—Data will be transmitted at all times according to the user-specified bandwidth configuration. Scheduled Bandwidth Limit—Data will be transmitted according to the user-specified schedule and the user-specified bandwidth configuration. 5. If you want to transmit data at all times using all of the available bandwidth, select No Bandwidth Limit. 6.
7. If you want to transmit data according to a schedule using limited bandwidth, select Scheduled Bandwidth Limit. a. Click New Event to create a bandwidth schedule event. 1. Specify a name for the bandwidth schedule event. 2. Select the day(s) of the week that you want this event to be initiated on. 3. Specify the time when you want this event to start. 4. Specify the bandwidth limitation. By default, the Unlimited checkbox is enabled.
8. Click OK to save the settings. You can establish a bandwidth schedule and then disable or override it by selecting No Bandwidth Limit or Fixed Bandwidth Limit. The schedule criteria will be saved and will not be reactivated until you reselect Scheduled Bandwidth Limit. Note: You can modify the bandwidth limits applied to a connection that is already established by right-clicking on the connection and selecting Set Bandwidth.
Compressing data for transmission To help reduce the amount of bandwidth needed to transmit Storage Mirroring Recover data, compression allows you to compress data prior to transmitting it across the network. In a WAN environment this provides optimal use of your network resources. If compression is enabled, the data is compressed before it is transmitted from the source. When the target receives the compressed data, it decompresses it and then writes it to disk.
3. By default, compression is disabled. To enable it, select Enable Compression. 4. Depending on the compression algorithms available for your operating system, you may see a slider bar indicating different compression levels. Set the level from minimum to maximum compression to suit your needs. 5. Click OK to save the settings.
Snapshots A snapshot is an image of data taken at a single point in time. Snapshots allow you to view files and folders as they existed at points of time in the past, so you can, for example, recover files that were accidentally deleted or overwritten. You could also compare a current revision of a file with an older revision. Storage Mirroring Recover utilizes snapshot functionality by allowing you to create snapshots of the replicated data stored on the Storage Mirroring Recover target.
to be aware of the impacts that functionality may have on Storage Mirroring Recover. For example, if you change the location where the shadow copies are stored and an error occurs, it may appear to be a Storage Mirroring Recover error when it is in fact a Volume Shadow Copy error. Be sure and review any events created by the VolSnap driver and check your Volume Shadow Copy documentation for details.
Snapshots for data workloads ● Snapshot states explains the various states of data workload snapshots. ● Automatic snapshots explains when automatic snapshots are taken. ● Scheduling snapshots contains instructions for scheduling periodic snapshots. ● Taking snapshots manually contains instructions for taking manual snapshots. Snapshot states A snapshot may not necessarily be useful if the data on the target is in a bad state. You only want snapshots of data that is in a good state.
Action State Automatic Action Taken for Scheduled and Automatic Snapshots Description User Interaction Required for Manual Snapshots Mirror Complete Because the mirror is complete, the data on the source and target Scheduled and is synchronized. Good automatic snapshots Storage Mirroring will occur normally. Recover will take a snapshot while the data is in a good state. Manual snapshots can be taken normally. Write Operation Retried An operation cannot be written to the hard drive on the target.
Action State Automatic Action Taken for Scheduled and Automatic Snapshots Description User Interaction Required for Manual Snapshots drive. Target The target service Restarted was able to Scheduled and with Good persist connection automatic snapshots Connection information prior will occur normally. Persistence to restarting.
Action State Description Automatic Action Taken for Scheduled and Automatic Snapshots User Interaction Required for Manual Snapshots Scheduled and automatic snapshots will be delayed until a restore is completed or the Snapshot Reverted state is overruled by a mirror. Once the restoration or mirror is complete, automatic and scheduled snapshots will occur normally. Restore the target data back to the source or overrule the Snapshot Reverted state by performing a mirror.
Because the driver for Volume Shadow Copy is started before the driver for Storage Mirroring Recover, if you revert any files on the source that are Note: contained in your replication set, Storage Mirroring Recover will not be aware of the revert and, therefore, the file change will not be replicated to the target. The file change will be mirrored to the target during the next mirroring process.
4. Select Enable Scheduled Snapshots. 5. Specify when snapshots should be taken, indicating minutes, hours, or days. The snapshots should be at least 15 minutes apart. By default, a snapshot is taken every hour. 6. Specify if you want the snapshots to start immediately. Otherwise, enter a date and time for when the snapshot schedule will begin. 7. Click OK to save the settings. Taking snapshots manually You can manually take a snapshot of the data on the target at any time.
Managing full-server snapshots By default, snapshots are enabled for full-server protection. Also by default, a snapshot is taken every 60 minutes. This may lead to numerous snapshots on the target that you may want to manage. You can do that from the Full-Server Failover Manger by selecting Actions, Snapshot Manager. (This option is only available when a source and target are selected and protection is enabled.) Use the following options to manage your full-server workload snapshots.
● ● ● ● ● Snapshot Interval—By default, a snapshot of the target data is taken every 60 minutes. If desired, increase or decrease the interval between snapshots. Start now—If you want to start taking snapshots immediately after the full-server protection is established, select Start now. Start at—If you want to start taking snapshots at a specific data and time, select Start at and specify the date and time parameters.
Managing snapshots If you have not done so already, launch the Application Manager. If snapshots were enabled when you configured protection, you can open the Snapshot Manager to take and delete snapshots. 1. To launch the Snapshot Manager, select Tools, Manage Snapshots. 2. To take an on-the-fly snapshot, click Take Snapshot. A snapshot will begin immediately. 3. To remove a snapshot, select the snapshot in the list, then click Delete Snapshot.
Security To ensure protection of your data, HP products offer multi-level security using native operating system security features. Privileges are granted through membership in user groups defined on each machine. To gain access to a source or target, the user must provide a valid operating system user name and password and the specified user name must be a member of one of the Storage Mirroring Recover security groups.
Security credentials When a client machine attempts to access a source or target machine running on Windows, it will attempt to automatically logon to the source or target using the three methods below. ● ● The security credentials of the user currently logged into the client machine are sent to the source or target machine. From the security credentials, the source or target machine determines if the user is a member of the security groups and if so, grants the appropriate level of access.
Adding users to the security groups The security groups are automatically created during the installation process. The groups are assigned specific case-sensitive names. ● Double-Take Admin ● Double-Take Monitors The local administrator and the domain administrator are automatically added to the Double-Take Admin group. If Storage Mirroring Recover is installed on a member servers, it will use the local groups.
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. See Assigning the user to the Power Users group. 2. In order to update DNS, the user account must be part of the Domain Admins group. 3.
5. Click Add. 6. In Location, click the domain containing the users and computers you want to add, then click OK. 7. In Name, type the name of the user you want to add to the group. 8. If you want to validate the user or group names that you are adding, click Check Names. 9. Click OK to close all open dialog boxes.
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. The target's machine account needs to be added to the source's Active Directory computer object for the purpose of updating the SPNs during failover and failback. The administrative shares are used to manage the configuration files and failover scripts on the source and target.
DNS permissions for Windows 2003 SP1 or earlier The following permissions are required to use the DNS Failover Utility to modify DNS records on Windows 2003 with service pack 1 or earlier: ● ● ● The user must be a member of the DnsAdmins domain local group. For details, see Assigning the user to the DnsAdmins group. The user must be a member of the Server Operator group, at the very least, to Deny the source access to the records.
7. Select the Security tab. 8. Double-click on Root to expand the tree. 9. Select MicrosoftDNS, then click the Security button. 10. Verify that the user is in the ACL list with the following permissions. If the permissions are not assigned, proceed to the next step. ● Execute Methods ● Full Write ● Partial Write ● Provider Write ● Enable Account ● Remote Enable ● Read Security 11. Click Add, then enter the login name for the user account that the DFO.exe command line will be using.
3. Right-click the Server Operators 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. In Name, type the name of the user you want to add to the group. If you want to validate the user or group names that you are adding, click Check Names. 8. Click OK to close all open dialog boxes.
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.
DNS permissions for non-Active Directory Windows 2003 SP2 or later The following permissions are required to use the DNS Failover Utility to modify DNS records on Windows 2003 with SP2 or later that is not co-hosted with the Active Directory domain controller: ● ● ● The user must be a member of the DnsAdmins domain local group. For details, see Assigning the user to the DnsAdmins group. The user must be a member of the local Administrator group.
● ● The target's Storage Mirroring service logon account. If the target's Storage Mirroring service is configured to log on as the System account, the target's Active Directory computer account should be assigned the permissions. The account specified in the failover monitor configuration. Use the following procedure to assign the Write servicePrincipalName permission to a user or group: 1. Start Active Directory Users and Computers. 2. Select View, Advanced. 3. Locate the source's computer account. 4.
● ● If Exchange is clustered, the user running the Application Manager must be a member of the Cluster Administrators and local Administrator group for each of the source and target cluster nodes. If Exchange is clustered, it is highly recommended that the same cluster service account be used for both source and target nodes.
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.
For SQL, you should first configure all permissions as described in Application Manager Credentials. In addition, the user must have SQL Server System Administrator permission. In order to operate the Application Manager for setup and to manage failover and failback for SQL, the following permissions are required: ● ● The user must be assigned the System Administrator role on the SQL server in order to query and Administer SQL.
SharePoint 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. For SharePoint, you should first configure all permissions as described in Application Manager Credentials. In addition, the user must have the same permissions as are required for SQL. For more information, see SQL credentials.
Changing the account used to run the Storage Mirroring service By default, the Storage Mirroring service is configured to log on as the system account. If you want to select a specific account to run the service, use these instructions. If you are protecting full-server workloads, you cannot modify the account used Note: to run the Storage Mirroring service. Otherwise, the full-server protection will not function correctly. 1. Modify the user account that the Storage Mirroring service is using. a.
c. Right-click on the Administrators group on the right pane of the screen and select Add to Group. d. Click Add. e. Locate the domain account that you are using for the Storage Mirroring service. Select that account and click OK. f. Click OK to close the Administrators Properties dialog box. g. The domain account is now added to the local administrator group. Close the Computer Management window.
Configuring the Storage Mirroring service for Active Directory If you want to use Active Directory registration, the Storage Mirroring service must have privileges to modify Active Directory. There are two options for assigning the privileges. ● ● User account—Assign a user account to the Storage Mirroring service and assign Active Directory privileges to that user. Refer to your Windows reference guide for Active Directory privileges.
● Write All Properties ● Read Permissions 658 of 739
Utilities The following utilities can be used with the Application Manager. ● ● ● 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. Target Data Verification (TDV) utility—There are several options available in the Target Data Verification utility for performing a verification of the target data.
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\HP\Storage Mirroring \dfo.
● ● dnsservername—The name of the source domain/zone's primary DNS server (optional; local machine name will be used if missing) sourceFQDN—The source machine's Fully Qualified Domain Name (required for modify) ● sourceip—The source machine's IP address (required for modify) ● targetip—The target machine's IP address (required for modify) ● ● ● ● ● ● Options ● ● ● ● ● ● targetFQDN—The target machine's Fully Qualified Domain Name (required for modify on failback) recordtype—The type of DNS r
● ● ● ● ● ● sourceDN—The distinguished name of the source machine's computer account (CN=,DC=domain,DC=local). DFO will add a deny "Read All Properties" permission to the computer account on failover and remove the permission on failback for the trustees specified with the /trustee parameter. This prevents a source virtual server from being brought online in Windows 2008 prior to failback.
● 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.
dfo /setpassword mydomain.com\admin mypassword Stores the username (mydomain.com\admin) and password (mypassword) in the default credentials file (dfo_credentials.dat) Password Encryption Examples dfo /dnssrvname mydnsserver.mydomain.com /srcname mysource.mydomain.com /srcip 206.31.4.10 /tarip 210.11.12.13 /username mydomain.
b. Create a file called dnsback.txt that includes the following. update delete targetservername.fullyqualifieddoamin.com A update add sourceservername.fullyqualifieddomain.com 86400 A sourceserverIP send 6. Modify the .txt files appropriately with the source/target server names, IP addresses, and fully-qualified domain names. 7. Change the Storage Mirroring service on the target server to a domain account that has rights to modify BIND DNS. Stop and start the service to have it take effect.
Using the Target Data Verification (TDV) utility If you have not done so already, launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. There are several options available in the Target Data Verification utility for performing a verification of the target data.
/apptype SQL|EXCH —Select whether to verify SQL or Exchange data on the 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 Double-Take Admin local groups on the source and target servers.
/scriptpre prerestore (optional)—The script to run after the target Exchange services are stopped but before normal protection is resumed. The script should be located in the Storage Mirroring Recover folder on the target server. If there are spaces in the file name, enclose the script path in quotation marks.
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.exe /apptype EXCH /dnsdomain MYDOMAIN.
Description Used to run a test that verifies that the database on the target is viable for failover tdv > > > > [/port ] [/username ] [/password ] > Syntax [/addonsvc
/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.
/scriptpre prerestore (optional)—The script to run after the target SQL Server services are stopped but before normal protection is resumed. The script should be located in the Storage Mirroring Recover folder on the target server. If there are spaces in the file name, enclose the script path in quotation marks.
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 ] Examples 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.
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.
noRGconnectors—(Optional) Do not change the Routing Group connectors noexchangeab—(Optional) Do not fail back the ExchangeAB SPNs for Small Business Server noADreplication—(Optional) Do not force Active Directory replication of changes nopublicfolders—(Optional) Do not move the public folders onlypublicfolders—(Optional) Only move the public folders movehostspn—(Optional) Move the HOST SPN to/from the target instead of removing/adding it on the source o options_filename—(Optional) Allows you to pass in a fi
u username:password—(Optional) User with Active Directory permissions virtual new ip—(Optional) Update the addresses stored for HTTP, IMAP, and other virtual protocols to point to the target sever (applies to likenamed cluster failover) dc DC name:ip—(Optional) Specifies name or IP address of the domain controller to update ?—Displays the syntax of the Exchange Failover utility ??—Displays the syntax of the Exchange Failover utility along with brief descriptions of each option 676 of 739
exchfailover -failover -s Indy -t ExchSrvr_Bkup exchfailover -failover -s Indy -t ExchSrvr_Bkup -r exchfailover -failover -s Indy -t ExchSrvr_Bkup -r Sales:Indy_Sales Examples exchfailover -failover -s Indy -t ExchSrvr_Bkup -r Sales, Inside:Indy_Sales, Inside -r Sales, Outside:Indy_Sales, Outside exchfailover -failover -s Indy -t ExchSrvr_Bkup -r Sales:Indy_Sales -norus -u administrator:password exchfailover -failover -s Indy -t ExchSrvr_Bkup -o options_file.
Consoles There are various Storage Mirroring Recover consoles, many of which are being phased out over time. To help consolidate the consoles and help you locate the necessary workflows to complete your work, use the console called Storge Mirroring Console. To access this console, select Start, Programs, Storge Mirroring, Storge Mirroring Console. Select Get Started from the toolbar and then select the type of workload protection you want to establish. The appropriate workflow or console will then open.
Data workload consoles Data workloads can be managed through two clients. The Replication Console manages, monitors, and controls the replication set and connections. The Failover Control Center manages, monitors, and controls failover monitoring. ● Replication Console ● Failover Control Center Replication Console To open the Replication Console, click Get Started in the Storge Mirroring Console toolbar.
If you are logged in locally to the machine running the Replication Console, there will be no servers automatically populated in the Servers tree. You will have to manually insert each server.
2. If you have no access, the Logon dialog box will automatically appear. If you have monitor access or want to log on with a different username, right-click the machine name and select Logon. 3. Specify your Username, Password, Domain, and whether you want your password saved. 4. Click OK and verify your access by the resulting icon and log on again if necessary. When logging in, the user name, password, and domain are limited to 100 characters.
Description Access Granted This icon is a computer with a gear and it indicates the Storage Mirroring Recover security is set to administrator access. Administrator rights This icon is a computer with a magnifying glass and it indicates the Storage Mirroring Recover security is set to monitor only access. Monitor rights This icon is a lock and it indicates the Storage Mirroring Recover security is set to no access. No rights Icon 5.
The location of the new group that is created will depend on what was highlighted. If the root of the tree was highlighted, the new group will be created as a child of the root. If a group or server within a group was highlighted, the new group will be created as a child of that group. Name the newly inserted group with a unique name by typing over the default name and pressing Enter. This process is similar to naming a new folder in Windows Explorer.
● Insert a server into the desired group. Inserting an existing server to the tree will move the first occurrence to that new location. A Storage Mirroring Recover server will only appear once within the entire Replication Console tree. Servers cannot be placed into multiple groups. Inserting Servers If a machine is not displayed on the Replication Console, it can be manually inserted. This feature is useful for machines that are across a router or on a different network segment.
If Active Directory discovery is enabled on the Replication Console, those servers that have Active Directory advertisement enabled will automatically be repopulated back in the default Discovered Servers group. If Active Directory discovery is disabled on the Replication Console or for individual servers, servers will need to be manually inserted into the Replication Console.
1. Select View, Unhide Servers. 2. Select one or more servers by using Ctrl-click or Shift-click. You can also click Select All to select all of the servers in the list. 3. Click Unhide. Before moving a group that contains at least one subgroup with at least two hidden servers, you must unhide all of the servers. After the servers have been unhidden, move the group and then hide the servers again.
● Open Workspace—Open a previously saved workspace. Clearing maintained security credentials To remove cached credentials, select File, Options and select the Security tab. To remove the security credentials, enable Clear Cached Security Credentials and then click OK. Failover Control Center To open the Failover Control Center, select External Tools from the Storge Mirroring Console menu bar. Select Failover Control Center.
From the Failover Control Center, you can manage, monitor, and control failover for your Storage Mirroring Recover servers. The Failover Control Center displays a main window for monitoring failover activity. Control buttons to the right allow you to configure and manage your servers.
like obtaining the Time to Fail status from a target, or may be a general request, like determining which machines are running Storage Mirroring Recover. The rate at which these requests are made can be modified through the Failover Control Center refresh rate dialog box. Select Settings, Refresh Rate. The default update interval is one second.
Full-server workload console The Full-Server Failover Manager allows you to create your source and target connection, monitor your full-server workload protection, manage your full-server snapshots, and initiate full-server failover. The client is a simple interface with four numbered steps. Steps 1 and 2 for the source and target have to be completed before the other steps are available or the Protection Status is displayed.
Configuring the console refresh rate Select File, Options. By default, the main window of Full-Server Failover Manager will automatically update every five (5) seconds. If desired, you can modify the Refresh Interval. You can also refresh the main window manually by selecting File, Refresh. Configuring the level of detail to log Select File, Options. By default, Full-Server Failover Manager creates a log that maintains all processing information.
Clearing maintained security credentials Select File, Options. By default, Full-Server Failover Manager will save the user credentials supplied for each servers. If desired, you can enable Clear cached credentials on exit so they are not saved. You can also clear the user credentials manually by selecting File, Clear Cached Credentials.
Storage Mirroring Recover Application Manager Console Launch the Storage Mirroring Recover Application Manager by selecting Start, Programs, HP Storage Mirroring, Recover, Storage Mirroring Recover Application Manager. If you have not yet set up protection, the window will show the Welcome screen. When you select an application to protect in the Tasks area on the left pane, you will enter an application protection workflow.
You can launch the Storage Mirroring Recover Application Manager from the command line to open it in the following contexts: 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 /blackberry— Launches the Application Manager in the BlackBerry context dtam / /
1. In the Service Listen Port field, enter the value for the Storage Mirroring Recover port to be used for Application Manager communication. The default port is 6320. The Application Manager Service Listen Port must be the same as the Storage Note: Mirroring Recover Service Listen Port on both the source and target servers. You can also change the port through the Replication Console. 2.
5. Select the Enable verbose logging checkbox to have all user interactions with Application Manager logged to the dtam.verbose.log file (Default = selected). 6. Select the Always show protection details checkbox to have the Protection Details area on the Monitor tab expanded by default. 7. Select the Display statistics values in bytes checkbox if you always want to show the values on the Protection Details area on the Monitor tab values in bytes, rather than in MB, GB, or TB. 8.
● ● ● ● ● ● ● ● ● Enable/Disable Monitoring—Enable or disable failover monitoring for the source server Failover/Failback—Initiate manual failover or failback View source DFO log—Launch a viewer to examine the log file generated by the dfo.exe utility on the source server View source ExchFailover log (Exchange only)—Launch a viewer to examine the log file generated by the exchfailover.exe utility on the source server View target DFO log—Launch a viewer to examine the log file generated by the dfo.
Virtual workload consoles Use the following table to determine which console you need to launch to protect your virtual workload.
Storage Mirroring Recover for Virtual Infrastructure uses standard Windows-style controls. Enter information in fields, select options from drop-down menus, click buttons, and use menu options. After you have configured protection, you can select options in the left pane of Storage Mirroring Recover for Virtual Infrastructure to monitor and manage your protected virtual machines.
If you want to add, modify the password, or remove a VirtualCenter server, select Manage VirtualCenter servers in the left pane. The Manage VirtualCenter servers window will appear in the right pane. To remove a server, select the server, then click the Remove VirtualCenter server button. Adding a VirtualCenter server If you want to add a new VirtualCenter server, click the Add VirtualCenter server button. The Add VirtualCenter server window will appear in the right pane. 1.
3. In the Password field, enter the password that is associated with the user account. 4. Click Save to save the VirtualCenter credentials. Changing VirtualCenter server credentials If you want to change the credentials for a VirtualCenter server, select the server, then click the Configure VirtualCenter server button. The Set VirtualCenter server credentials window will appear in the right pane. Changes to the credentials will apply to all protection jobs that use this VirtualCenter server.
Managing ESX servers If you have not done so already, launch the Storage Mirroring Recover for Virtual Infrastructure console. When you click on the Manage ESX servers button, Storage Mirroring Recover for Virtual Infrastructure automatically scans to find ESX servers that are VMotion destination candidates for protected virtual machines, based upon SAN connectivity. You can view the Credentials Cached column to identify servers that need to have credentials entered.
1. In the VirtualCenter server field, select a VirtualCenter server that manages the ESX server you want to add. 2. In the IP address or DNS name field, enter the IP address or DNS name of the ESX server. Or, click the Browse button to browse VirtualCenter to locate a server. The Select ESX server window will appear.
3. Enter the IP address or DNS name for the new ESX server. 4. In the User name field, enter the user name for the account you will be using to log on to the ESX server. 5. In the Password field, enter the password that is associated with the user account. 6. Click Save to save the server credentials.
Select an account in the Credentials area, then click Add to add a username and password, or Edit to change existing credentials. The Set ESX server credentials dialog box will appear. Enter a Username and Password in the fields, then click OK. Storage Mirroring Recover for Virtual Infrastructure will attempt to authenticate the supplied credentials. When you are finished, click Done.
To configure access to the SMTP mail server to use for e-mail notification, click the Set up e-mail server button in the left pane. The Set up e-mail server window will appear. You should set up the e-mail server before creating a protection. Otherwise, you can set up the e-mail server during the protection configuration workflow by Note: clicking the Configure button on the Configure e-mail notifications window. For more information, see Setting e-mail notification options.
3. In the User name field, enter the user name for the account that will access the SMTP server. 4. In the Password field, enter the password that is associated with the user name. 5. When you are finished, click Save. If you choose to disable e-mail notification for Storage Mirroring Recover for Virtual Infrastructure after it has been configured, delete the server name in the SMTP server field, then click Save. Configuring advanced options Controlling protection jobs with scripts The startprotection.
Configuring the VirtualCenter operation timeout You can configure a single timeout value to be used for all VirtualCenter operations. By default, the value is 90 minutes. 1. Stop all protection jobs. 2. Change the default value of 90 minutes in the DefaultJob.xml file: 90 3. Restart your protection jobs.
9PM 6AM Optionally, you can set a protection job to remove all snapshots when going into hibernation. The RemoveAllSnapshotsOnHibernating parameter must be set to true for all snapshots to be removed.
● ● ● ● Manage ESX servers—Opens the Manage ESX Servers pane, where you can add, modify credentials, or remove an ESX server. Manage VirtualCenter servers—Opens the Manage VirtualCenter servers pane, where you can add, modify credentials, or remove a VirtualCenter server. Set up e-mail server—Opens the Set up e-mail server pane, where you can configure access to the SMTP mail server to use for e-mail notification.
Storage Mirroring Console overview Storage Mirroring Console allows you to manage all aspects of the process of protecting your servers with Storge Mirroring. With Storage Mirroring Console, you can: ● ● ● Configure protection for an entire physical or virtual source server with a Microsoft Hyper-V target server. Configure protection for virtual machines running on the Microsoft Hyper-V platform .
From the Home page, you can: ● ● ● ● Launch tasks—Click the links in the Tasks area on the right. View details about issues with connections—Select a connection in the Headlines area on the left, then click View. View information about servers—Click the links in the Servers Summary area on the left. View information about connections—Click the links in the Connections Summary area on the left. To begin using Storage Mirroring Console, click the Get Started button on the main toolbar.
You can also add servers by importing an .xml file that has been previously Note: created in Storage Mirroring Recover. For more information, see Importing servers. Warning! You must not add servers that are running Storage Mirroring version 5.0 to this version of the Storage Mirroring Console. To add servers, from the Home page, click the Add servers option under Tasks on the right pane. Adding servers manually 1. Server—Enter the name of the server to add to Storage Mirroring Console.
Note: You should only add Storge Mirroring source servers. Any other servers will show up in an error state. 2. User name—Enter the account that you want to use to access the specified server. 3. Password—Enter the password associated with the specified User name. 4. More Options—Click the arrow to enter additional information for a server (not typically necessary). ● ● Domain—Enter the domain associated with the specified User name.
2. Click Discover to search Active Directory for servers running Storage Mirroring Recover. 3. If you need to remove servers from the list of Servers to be added, highlight a server and click Remove. You can also remove all of them with the Remove All button. 4. When your list of Servers to be added is complete, click OK. You will automatically be taken to the Manage Servers page. Importing servers You can import a list of servers and credentials from an .
On the Manage Servers page, you can view, add, edit, or remove configuration information for servers that have been added to Storage Mirroring Console. To view the Manage Servers page, click the Manage Servers button on the main toolbar. Each server is displayed on the Manage Servers page. ● ● Information—The Manage Servers page displays information about servers. See the table Server Information for a description of what is displayed for each server.
Toolbar Button Description Remove Server—To remove a server from Storage Mirroring Console, select one or more servers, then click the Remove Server button. Provide Credentials—To change the login credentials, select one or more servers, then click Provide Credentials. The Provide Credentials window will appear. For more information about changing credentials, see Modifying credentials. View Server Events—To view events associated with a selected server, click the View Server Events button.
1. In the Monitoring interval field, enter the interval (in number of seconds) at which you want Storage Mirroring Console to poll the servers for updated information. 2. In the Default port (for XML web services protocol) field, enter the port number Storage Mirroring Console will use when sending requests to the servers. The default is 80. 3.
● Tools, Storge Mirroring Backup Console—Launch the Storage Mirroring Replicate console. You can also add other frequently-accessed application to the Tools menu. 1. To modify the list of utilities available from the Tools menu, select Tools, External Tools. The External Tools window will appear. 2. Click the New button to add a new tool. Or, select a tool in the Tools area to edit settings for an existing tool. 3. In the Name field, enter the name you want to use to identify the application or tool. 4.
8. To add or edit another tool, repeat steps 1-7. 9. Click OK. Modifying credentials If you have not done so already, launch the Storage Mirroring Console. To change credentials for a server, from the Manage Servers page, select a server, then click the Provide Credentials button . 1. Specify the credentials. ● ● ● User name—Enter the account that you want to use to access the specified server. Password—Enter the password associated with the specified User name.
Evaluations You may want to evaluate Storage Mirroring Recover before implementing it in your production environment. This is a good process for users who want to see, first-hand, the benefits that Storage Mirroring Recoverhas to offer. The evaluation processes walk you through a step-by-step process to assess the key Storage Mirroring Recover features. Select a link below based on the type of evaluation you would like to perform.
Evaluating data protection The following evaluation procedure has eleven tasks containing step-by-step instructions for evaluating the data protection functionality of Storage Mirroring Recover. Before starting this evaluation procedure, make sure you have reviewed the server requirements and that you have installed the software on both the source and target. Also, you should have approximately 500 MB to 1 GB of data on the source for testing.
machine. If the logon is not successful, the Logon dialog box will appear prompting for your security identification. When logging in, the user name, password, and domain are limited to 100 characters. 5. If you highlighted a target in the Replication Console, the target will already be selected. If it is not, select the Storage Mirroring Recover target. This is your backup server that will protect the source. Click Next to continue.
To view specific mirroring statistics that may be of interest, use the horizontal scroll bar at the bottom of the right pane of the Replication Console window to view the various columns. ● ● ● ● Sent (Bytes)—The total number of mirror and replication bytes that have been sent during this connection. Sent Mirror (Bytes)—The total number of mirror bytes only that have been sent during this connection.
2. Select four files from your source and record the file name, date, time, and file size for each file. 3. On your target, locate those same four files that you just identified on your source. The files on the target match the files on the source. 4. Back on your source, view the contents of one of your files contained in your replication set and note the file contents. 5. On your target, view that same file that you just viewed on the source.
Storage Mirroring Recover is waiting for additional changes to transmit. After replication is complete, you are ready to continue with the evaluation. 4. Verifying the data changes on the target Now that you have modified some of the files, you want to be sure that the file modifications were applied correctly.
Just like when you were monitoring the mirror and replication processes, you can monitor the verification process. Notice that the Mirror Status column changes to Verifying while the verification process occurs. When the verification is complete, Storage Mirroring Recover will have created a log file for you to review. 5. Wait until your Mirror Status has returned to Idle and then open the file DTVerify.log located in the Storage Mirroring Recover installation directory on your source.
● Application data—If you are protecting application data, for example a database application, you will need to use that application to test the integrity of the data and the files. Use the following instructions to test application data on the target. 1. In order to test the application data on the target, you will need to start the application on the target. But Storage Mirroring Recover requires applications to be in a standby mode in order to update files on the target.
5. Type in your source machine name and click OK. The Insert Source Machine dialog box will close and the Monitor Settings dialog box will be available for updating. This is where you configure failover monitoring. 6. Select the source to be monitored by marking the check box to the left of the source server name in the Names to Monitor tree. 7. By default, Failover Hostname is disabled.
The Active Directory account password cannot be blank. Click OK to return to the Monitor Settings dialog box. At this point, in terms of your evaluation, your failover configuration is complete because you will be using the default settings for the remaining options. But while you are viewing the Monitor Settings dialog box, notice the flexible configuration options available to you. 7.
You can minimize the Failover Control Center and, although it will not appear in your Windows taskbar, it will still be active and the failover icon will still appear Note: in the desktop icon tray. The Failover Control Center does not have to be running for failover to occur. Monitoring failover monitoring contains more information on the Failover Control Center visual indicators. 8. Simulating a failure To fully evaluate failover, you need to simulate a failure.
3. Repeat that process, modifying the other three files from earlier, but this time make the modifications on the target copy of the file. Save the changes. If desired, you can also test the target data as you did earlier. You can test user data using the associated application, and you can save the changes if desired. If you want to test application data, start the application services on the target, and test the application data by using clients to connect to the application.
5. You will be prompted to determine if you want to continue monitoring the source. Do not make any selections at this time. 6. At this time, you would connect the source to the network. For this evaluation, reconnect the network cable(s) on the source that you disconnected to simulate the failure. 7. After the source is online, select Stop in the Failover Control Center to indicate that you do not want to continue monitoring the source.
2. Identify the Original Source machine. This is your source machine where the data originally resided. 3. Select the Restore From machine. This is the target machine where the copy of the data is stored. 4. Replication Set contains the replication set information stored on the target machine (the machine in Restore From). If no replication sets are available, the list will be blank. Select the replication set that corresponds to the data that you need to restore. 5. Select the Restore To machine.
9. After the restoration is complete, disconnect the restoration connection. You can identify a restoration connection because it is enclosed in parenthesis ( ) and it has _Restore appended to the end of the replication set name. Once the restoration is complete, your evaluation is complete.
Evaluating full-server protection The following evaluation procedure has five tasks containing step-by-step instructions for evaluating the full-server protection functionality of Storage Mirroring Recover. Before starting this evaluation procedure, make sure you have reviewed the server requirements and that you have installed the software on both the source and target. Also, make sure that the target you select is compatible to stand-in as the source.
6. Double-click on any of the validation items to see details. You must correct any errors before you can enable protection. Depending on the error, you may be able to click Fix or Fix All and let Storage Mirroring Recover correct the problem for you. For those errors that Storage Mirroring Recover cannot correct automatically, you will need to modify the target to correct the error, or you can select a different target.
modifying existing files, creating new files, deleting files, and changing permissions and attributes. 1. On the source, browse through the directories and files. 2. Select four data files from your source and record the file name, date, time, and file size for each file. 3. On your target, locate those same four files that you just identified on your source. The files on the target match the files on the source. 4. Back on your source, view the contents of one of your data files and note the file contents.
controller was allowed to communicate with other production domain controllers. 1. To begin failover, click Failover. 2. If Storage Mirroring Recover determines there is a possibility that the data on the target is incomplete, you will be warned before failover begins. If you proceed with failover, the state of the source will be unknown until failover is complete.
