FalconStor Recovery Agents User Guide

Transcription

1

2 FalconStor Recovery Agents User Guide FalconStor Software, Inc. 2 Huntington Quadrangle Melville, NY Phone: Fax: Web site: Copyright FalconStor Software. All Rights Reserved. FalconStor Software, IPStor, TimeMark, and TimeView are either registered trademarks or trademarks of FalconStor Software, Inc. in the United States and other countries. Windows is a registered trademark of Microsoft Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. FalconStor Software reserves the right to make changes in the information contained in this publication without prior notice. The reader should in all cases consult FalconStor Software to determine whether any such changes have been made

3 Recovery Agents User Guide Contents Introduction Terminology Message Recovery for Microsoft Exchange System requirements Install the software Recovery procedure on Microsoft Exchange Cleanup on Microsoft Exchange LaunchMRMEAsUser utility on Exchange Recovery procedure on Microsoft Exchange Cleanup on Microsoft Exchange Advanced features Mountpoint Options Trace log DiskSafe priority Start/stop Exchange Manual RSG recovery Mount single backup image Dismount RSG backup Restore from RSG backup image Message Recovery for Lotus Notes /Domino System requirements Install the software Change system settings Recovery Clean up Notes Advanced features Trace log DiskSafe priority Clean up TimeViews Manual recovery Database Recovery for Microsoft SQL Server System requirements Install the software The console The menus Add a new storage server Recovery Agents User Guide i

4 Contents Delete a storage server Modify storage server properties Configuration Configure global settings Configure the Snapshot Agent for Microsoft SQL Server Integration with DiskSafe DiskSafe priority Command line utility Transaction log backups Trace log Database recovery Restore your database Advanced restore options IntegrityTrac Terminology Supported platforms System requirements Install the software Console overview Configure global settings Sort events Search for events Storage servers Establish a connection with your storage server Add a new storage server Resolve the host name of a storage server Add credentials for a storage server Add a IntegrityTrac administrator in IPStor, NSS, or CDP Delete a storage server Application Hosts Remove Application Hosts Scripts Device mapping scripts Job scripts Properties Syntax for IntegrityTrac runtime module CSMap CSRun CSNotify.bat Create a diagnostic X-ray file Index Recovery Agents User Guide ii

5 Message Recovery for Microsoft SQL User Guide Introduction FalconStor s recovery agents offer recovery solutions for your database and messaging systems. FalconStor s Message Recovery for Microsoft Exchange (MRE), and Message Recovery for Lotus Notes/ Domino (MRN) expedites mailbox/message recovery by enabling IT administrators to quickly recover individual mailboxes from point-in-time snapshot images of their messaging server. FalconStor s Database Recovery for Microsoft SQL Server expedites database recovery by enabling IT administrators to quickly recover a database from point-intime snapshot images of their SQL database. This guide describes how to recover your data using the following products: Message Recovery for Microsoft Exchange Message Recovery for Lotus Notes/Domino Database Recovery for Microsoft SQL Server Recovery Agents User Guide 1

6 Introduction Terminology DiskSafe Group IMA Snapshot Snapshot Agent TimeMark TimeView A Continuous Data Protection (CDP) agent that runs on Windows hosts and provides complete volume-level data protection and rapid recovery in the event of a system crash or disk failure. It operates by mirroring local disks or partitions to a remote virtual disk and provides user-initiated recovery of files, folders, or entire volumes. Also referred to as Snapshot Group. Building on the snapshot technology, disks can be grouped into a group for snapshot synchronization purposes. Snapshots for all resources in a group are taken at the same time whenever a snapshot is triggered. It is recommended that you have your database and logs on separate disks. Putting them into a single group allows a snapshot to be taken of all resources at the same time. Intelligent Management Agent is a FalconStor software module that resides on the host machine and provides core services such as authentication, encryption, and management functions to FalconStor host agents (such as DiskSafe and FileSafe). A snapshot is a consistent point-in-time, frozen image of one or more data volumes. The Snapshot Agent for each recovery tool ensures transactional consistency and reliability. The Snapshot Agent for Microsoft SQL creates TimeMark snapshots to ensure database and application system data integrity. The Snapshot Agent for Microsoft Exchange and the The Snapshot Agent for Lotus Notes ensure transactional integrity by notifying the Exchange or Notes Server to quiet activity on the disk before a snapshot is taken. A TimeMark is a point-in-time image of any virtual drive or data volume. It is the result of taking a snapshot. Each TimeMark represents one backup image. A TimeView (a.k.a. Backup image) is a mountable TimeMark, It allows you to access files and directories from a TimeMark image without rolling back the entire volume. Recovery Agents User Guide 2

7 Message Recovery for Microsoft SQL User Guide Message Recovery for Microsoft Exchange Message Recovery for Exchange (MRE) version 3.0 works with IPStor to protect and recover Exchange databases that are stored on IPStor-managed disk. IPStor and TimeMark work in conjunction with the FalconStor Snapshot Agent for Microsoft Exchange to take scheduled point-in-time snapshot images of the Exchange databases that are stored on IPStor-managed disk. The Snapshot Agent gives the snapshot images point-in-time consistency and transactional integrity. Note: MRE version 3.0 no longer supports Exchange If you want to recover Exchange 2000, you will need to use MRE version 2.5. With Exchange 2007, can be recovered from any Recovery Storage Group (RSG) mounted mailbox. There is no need to use Exchange system tools to create an RSG or mailbox merge as was necessary with earlier versions. With Exchange 2003, if the server has local, direct-attached storage and you are using FalconStor DiskSafe to protect the Exchange databases, DiskSafe works directly with the Snapshot Agent for Microsoft Exchange to replicate point-in-time snapshot images to IPStor-managed disk. When needed, MRE enables administrators to mount the storage server s snapshot images so that mailboxes can be easily and quickly recovered from any protected Exchange Server in the same Exchange Administrative Group. The recovery procedure varies depending upon whether you are using Microsoft Exchange 2007, 2003 or Refer to Recovery procedure on Microsoft Exchange 2007 on page 6, Recovery procedure on Microsoft Exchange 2003 on page 15, or Advanced features on page 21. Microsoft Exchange 2007 With Exchange 2007, the administrator runs MRE on the local Exchange Server and can restore an individual mailbox or all mailboxes for a local or remote message store. MRE can be used to recover mailbox stores on multiple partitions of the same disk as well as partitions that do not include the first partition of a disk. Further filtering can be specified for recovering a certain date range of s or by specific subject, content, or entire level. Recovery Agents User Guide 3

8 Message Recovery for Microsoft Exchange Microsoft Exchange 2003 With Exchange 2003, the administrator runs MRE on the local Exchange Server and recovers individual mailboxes from any protected Exchange Server (local or remote) directly to the mailbox of the user who requested recovery. The user can then select what he or she needs. System requirements The following table outlines the requirements needed on the Exchange server: Supported Exchange Servers Version and Service Pack Information Microsoft Exchange 2003 No exchange packs are required. Supports stand-alone or multi-node Microsoft cluster Microsoft Exchange 2007 Windows 2003 (64-bit) Windows 2008 (64-bit) General Requirements Your Microsoft Exchange Server must have an IPStor SAN Client or FalconStor Intelligent Management Agent (IMA) installed. Your Microsoft Exchange Server must have the Snapshot Agent for Microsoft Exchange and the Snapshot Agent for Windows filesystems installed. FalconStor recommends that you have a minimum of two disks (one for the database and one for the logs) or a maximum of three disks/luns for the Exchange database and logs. The EDB and STM database files must be on the same disk/lun. In addition, Log and Sys should be on a single disk/ LUN or recovery will take longer. Recovery Agents User Guide 4

9 Message Recovery for Microsoft Exchange Install the software Best practice is to have the database and logs on separate disks. However, if you must keep both on one disk, Remote Recovery requires that the logs and system directory exist in either the first partition or in a unique subdirectory of a non-first partition Installation of MRE has the following requirements: MRE must be installed on an Exchange Server machine. You must be an administrator or have administrator privileges in order to install MRE. To install: 1. Insert the installation CD into your CD-ROM drive. 2. Select Install Products --> Install Host-Based Applications --> Install Message Recovery for Microsoft Exchange. 3. When prompted, enter your license keycode. The MRE license must be activated (registered with FalconStor). If your computer has an Internet connection, the license is activated as soon as you enter your keycode and click Next. However, if your Internet connection is temporarily down or if your computer has no Internet connection, your license will not be activated. You must activate your license within 30 days so that you can continue to use the software. If your Internet connection is temporarily down, your license will typically be activated automatically the next time you run MRE, assuming you have an Internet connection then. Or, you can add your license through the SAN Disk Manager (the utility that is installed with IMA). If your computer has no Internet connection, you must perform offline activation. Refer to your SAN Disk Manager User Guide for more information. 4. When done, click Finish. Recovery Agents User Guide 5

10 Message Recovery for Microsoft Exchange Recovery procedure on Microsoft Exchange 2007 This section describes how to recover messages from user mailboxes on Microsoft Exchange MRE includes an easy-to-use wizard that enables administrators to recover mailboxes from local Exchange 2007 servers and remote Exchange 2007 servers that are in the same Exchange Administrative Group. You must be a local administrator and a full Domain Exchange administrator in order to recover mailboxes. If you want to pre-configure MRE to launch from a non Exchange Domain Administrator user, refer to LaunchMRMEAsUser utility on Exchange 2007 on page 13. Be sure to log into Windows with the same account with which you are doing the recovery. 1. Launch the Message Recovery for Microsoft Exchange Console on the Exchange Server (Start menu --> Programs --> FalconStor --> Tools --> Message Recovery for Microsoft Exchange). 2. From the menu, select File --> Recover using a Recovery Storage Group. This launches the RSG recovery wizard. If you have previously recovered a mailbox store, it must be unmounted before you can continue. The wizard will prompt you to unmount it. 3. Enter the domain and user authentication information needed to log into the Exchange Server and access its Active Directory configuration. Root Domain Name - Exchange Server domain. Recovery Agents User Guide 6

11 Message Recovery for Microsoft Exchange Domain Server Name - Domain controller for the Active Directory tree. You must enter the server name, not an IP address. User Name/User Password - This login user must have rights to access and export Exchange Server objects such as, Storage Group objects, Mailbox objects, and Exchange users objects. Login User Domain - Domain for the user account specified above. After logging into the Active Directory Tree, a list of Mailbox stores will be available for selection as shown on the screen below. 4. Select the mailbox store you wish to recover. 5. Click the Create RSG tab if you have not already created a Recovery Storage Group. The Create Recovery Storage Group screen displays. 6. Enter the RSG name. 7. Once the RSG group has been created, click Next. Recovery Agents User Guide 7

12 Message Recovery for Microsoft Exchange The Mailbox Restore Selections screen displays. The Restore now radio button is selected by default. 8. Select the mailbox to restore from the drop down menu. 9. Select whether you want to merge the restored with your existing or copy the restored to a folder. If you choose to copy the to a folder, enter the folder name. Depending upon the size of the mailbox, the restore operation can take a while. If you would like to see the restore progress, check the Show restore output screen during restore checkbox. Click Mount the backup image only radio button if you will be using another utility to restore . Recovery Agents User Guide 8

13 Message Recovery for Microsoft Exchange 10. Select any appropriate options or filters for the restore. You can filter by date and by text contained in the subject or body. Each filter further restricts the selection. 11. Enter storage server login information. You need to log into the IPStor server which contains the TimeMarks for the mailboxes to be recovered. This can be a primary IPStor server or a replica IPStor server. If you are using IPStor version 4.5 or above, indicate the protocol to use. Recovery Agents User Guide 9

14 Message Recovery for Microsoft Exchange 12. If you are recovering from a remote Exchange Server, select the snapshot group that contains the mailbox to be recovered and select the appropriate SAN Resource used for the storage of each Exchange component. Recovery Agents User Guide 10

15 Message Recovery for Microsoft Exchange 13. Select the TimeMark from which you want to recover. It is recommended that you select a TimeMark indicated as quiescent. 14. Confirm all information and then click Finish to mount the TimeMark to the RSG. The TimeMark will be mounted using the next available drive letter(s) and to mountpoints if you are using the Mountpoint feature. Refer to Mountpoint Options on page 21 for additional information. Recovery Agents User Guide 11

16 Message Recovery for Microsoft Exchange Wait for the TimeView to mount. It may take a few minutes to complete this process. 15. Click Finish when you see a screen similar to the following: Cleanup on Microsoft Exchange 2007 Cleanup for Exchange 2007 includes removing the RSG mailbox and Group. The cleanup process occurs automatically when you start another recovery or exit the application. To run cleanup manually, select Tools > Advanced > Dismount RSG Backup image. Recovery Agents User Guide 12

17 LaunchMRMEAsUser utility on Exchange 2007 Message Recovery for Microsoft Exchange The LaunchMRMEAsUser utility allows Exchange Administrators to pre-configure MRME to launch with Exchange Domain rights from a lower level login. Parameters & Options Required Parameters -a[application] -x[application] Description If specified, the named application will be launched. If not specified, the default Message Recovery for Microsoft Exchange (MRME) application will be launched. Clears the saved user credentials for the named Application. If not specified, the default MRME application user credentials are cleared. Options -d<exchange Domain> -u<exchange Domain User> -p<exchange Domain User Password> -c<command Arguments> -z Silent mode -? Help If specified, the Exchange Domain is used for this run and saved for the next run of the specified application. If not specified, the previously saved Exchange Domain for the specified application is used. If specified, the Exchange Domain User is used for this run and saved for the next run of the specified application. If not specified, the previously saved Exchange Domain User for the specified application is used. If specified, the Exchange Domain User Password is used for this run, encrypted, and saved for the next run of the specified application. If not specified, the previously saved Exchange Domain User Password for the specified application is used. The application is launched with the specified command arguments. Recovery Agents User Guide 13

18 Message Recovery for Microsoft Exchange Usage Examples command LaunchMRMEAsUser Utility -a LaunchMRMEAsUser Utility -a - dexchdomain.com -uexchuser - pexchpassword LaunchMRMEAsUser Utility - ammc.exe -c"c:\rsg.msc" LLauncheMRMEAsUser -x result Launches "C:\Program Files <x86> \FalconStor\MRME\ExRecoverUI.exe" with the saved Exchange Domain User credentials for: "C\Program Files <x86>\falconstor\mrme\exrecoverui.exe" Launches "C:\Program Files <x86> \FalconStor\MRME\ExRecoverUI.exe" with the following user credentials: Domain:ExchDomain.com User:ExchUser Password:ExchPassword The ExchDomain.com, Exchuser, and ExchPassword are then encrypted and saved for future executions of "C:\Program Files <x84>\falconstor\mrme\exrecoverui.exe" Launches "mmc.exe c:\rsg.msc" with the saved Exchange Domain User Credentials for "mmc.exe" Clears the User Credentials for: "C:\Program Files <x86> \FalconStor\MRME\ExRecoverUI.exe" Recovery Agents User Guide 14

19 Message Recovery for Microsoft Exchange Recovery procedure on Microsoft Exchange 2003 Minimal configuration is required to make Message Recovery for Microsoft Exchange (MRE) work in your environment. MRE uses the Exchange Recovery Storage Group (RSG) to hold recovered data. Prior to recovery, you must create a RSG in your Exchange System Manager. Refer to the Recover Mailboxes on Microsoft Exchange 2003 chapter for details. MRE includes an easy-to-use wizard that enables administrators to recover mailboxes from local Exchange 2003 servers and remote Exchange 2003 servers that are in the same Exchange Administrative Group. You must be a local administrator and a full Exchange administrator in order to recover mailboxes. If you want to pre-configure MRE to launch from a non Exchange Domain Administrator user, refer to LaunchMRMEAsUser utility on Exchange 2007 on page 13. Be sure to log into Windows with the same account with which you are doing the recovery. 1. Launch the Message Recovery for Microsoft Exchange Console on the Exchange Server (Start menu --> Programs --> FalconStor --> Tools --> Message Recovery for Microsoft Exchange). 2. From the menu, select File --> Recover using a Recovery Storage Group. This launches the RSG recovery wizard. If you have previously recovered a mailbox store, it must be unmounted before you can continue. The wizard will prompt you to unmount it. Select Yes to automatically delete any previous backup image and proceed. Recovery Agents User Guide 15

20 Message Recovery for Microsoft Exchange 3. Enter the domain and user authentication information needed to log into the Exchange Server and access its Active Directory configuration. Root Domain Name - Exchange Server domain. Domain Server Name - Domain controller for the Active Directory tree. You must enter the server name, not an IP address. User Name/User Password - This login user must have rights to access and export Exchange Server objects such as, Storage Group objects, Mailbox objects, and Exchange users objects. Login User Domain - Domain for the user account specified above. After logging into the Active Directory Tree, a list of Mailbox stores will be available for selection. Recovery Agents User Guide 16

21 Message Recovery for Microsoft Exchange 4. Select the mailbox store where the mailbox to recover resides. Note: The RSG must have been pre-created for Exchange Enter the storage server login information. You need to log into the IPStor server which contains the TimeMarks for the mailboxes to be recovered. This can be a primary IPStor server or a replica IPStor server. If you are using IPStor version 4.5 or above, indicate the protocol to use. Recovery Agents User Guide 17

22 Message Recovery for Microsoft Exchange 6. If you are recovering from a remote Exchange Server, select the snapshot group that contains the mailbox to be recovered and select the appropriate SAN Resource used for the storage of each Exchange component. 7. Select the TimeMark from which you want to recover. It is recommended that you select a TimeMark indicated as quiescent Recovery Agents User Guide 18

23 Message Recovery for Microsoft Exchange 8. Confirm all information and then click Finish to mount the TimeMark to the RSG. The TimeMark will be mounted using the next available drive letters. Wait for the TimeView to mount. It will take a few minutes to complete this process. Recovery Agents User Guide 19

24 Message Recovery for Microsoft Exchange 9. Click Finish when you see a screen similar to the following: 10. Launch the Exchange System Manager. You can now see the recovered mailbox store under the RSG. If you do not see it, click F5 to refresh. 11. Right-click on the mailbox store and select Mount Store. Ignore the Exchange warning that appears as MRE has already validated the image. Click Yes to continue. 12. Click F5 to refresh the screen and see the recovered mailboxes listed beneath the mailbox store. 13. If your Exchange 2003 system has Service Pack 1 or later installed, expand the mailstor tree under the Recovery Storage Group, right-click on a mailbox in the right frame and select Exchange Tasks. If you are using a pre-service Pack 1 version of Exchange 2003, you must download the exmerge tool from Microsoft s web site. This tool allows you to extract mail from a selected mailbox into a PST file. 14. Follow the steps in the Exchange Task wizard to copy or merge the data from the recovered mailbox. Merging data adds items from the mounted TimeMark to the current mailbox. Duplicate items are not merged. If the recovered mailbox contains folders not present in the current mailbox, they will be created. Copying data copies all items from the recovered mailbox to a separate recovery location in the current mailbox. The contents of current folders will not be changed. 15. Have the user check the mailbox in his/her client (i.e. Microsoft Outlook). Recovery Agents User Guide 20

25 Message Recovery for Microsoft Exchange If the recovered mailbox was copied, there will be a folder called Recovered Data <date>. All of the recovered information can be found beneath this object. Cleanup on Microsoft Exchange 2003 Advanced features Mountpoint Options After you have finished recovering messages for one or more mailboxes, you should delete the recovered mailbox store from the RSG. To do this, right-click on the mailbox store and select Delete. If desired, you can also delete the RSG itself. When you exit MRE or start a new recovery wizard, you have the choice of deleting the existing TimeView that was mounted. If you choose Yes, MRE will disconnect the TimeView and delete it from the IPStor Server. While the TimeView is deleted, all of your TimeMarks are retained. This section describes the advanced features available in the Message Recovery for Microsoft Exchange (MRE) console. The mountpoint options feature allows you to select mount points instead of drive letters during message recovery. To select mountpoint options, select Options --> Mountpoint Options. Recovery Agents User Guide 21

26 Message Recovery for Microsoft Exchange Trace log The Trace log is a diagnostic tool used by your Technical Support team to help solve system problems. Each Trace log contains technical information about your system as well as system messages. You should not turn the Trace log on unless you are requested to do so by your Technical Support representative. To turn the Trace Log on, select Options --> Trace. To view the Trace Log, select View --> Log. Recovery Agents User Guide 22

27 Message Recovery for Microsoft Exchange DiskSafe priority Start/stop Exchange MRE enables recovery of Exchange 2003 mailboxes when the Exchange database is stored on IPStor-managed disk. With Exchange 2003, if the server has local, direct-attached storage, MRE enables recovery of Exchange mailboxes that have been replicated to IPStor-managed disk by DiskSafe. There may be instances where the Exchange database is stored on IPStormanaged disk AND DiskSafe is used to replicate data to another IPStor-managed disk. By default, MRE will assume that the IPStor-managed disk containing the primary Exchange database is used for TimeMarks. If this is not the case, you must tell MRE to use the DiskSafe replica disk. To do this, select Options --> DiskSafe Priority. You can start or stop Exchange services on the local Exchange Server from within the MRE. Note: The feature is not applicable for cluster servers. Manual RSG recovery To do this, select Tools --> Start Exchange (or Stop Exchange). MRE includes an easy-to-use wizard that enables administrators to recover mailboxes from local and remote Exchange 2003 servers. Refer to Recovery procedure on Microsoft Exchange 2003 for more information. However, there may be advanced configurations for which the wizard will be unable to automatically detect the logical resources containing the Exchange database. For example, if your Exchange system is not connected directly to the storage server that contains your backup images (such as a remote replica server), MRE will be unable to identify the logical resources and map the TimeMarks. For these types of configurations, MRE includes tools that let you manually log in to the storage server, manually select TimeMarks, and manually validate and mount the mailbox store to the RSG. To run a manual recovery: 1. Select Tools --> Advanced --> Mount RSG Group Backup Image or select Mount Single Backup Image if you have not used Snapshot Groups and your entire database, logs, and system directory are all on a single SAN disk. Log in to your storage server. Recovery Agents User Guide 23

28 Message Recovery for Microsoft Exchange Mount single backup image Enter the Exchange Server name and select the Snapshot Group that contains the mailbox to be recovered. Select the logical SAN Resource containing the database, select the corresponding database path, a drive letter for the RSG database, and select a TimeMark from the list. This mounts the TimeMark and assigns it to the Exchange Server. Select the logical SAN Resource containing the logs, select the corresponding log path, and select a drive letter for the RSG logs. You do not have to select a TimeMark for the logs because the Snapshot Group maintains a relationship between the TimeMark you selected for the database and the corresponding TimeMark for the logs. 2. Select Tools --> Advanced --> Validate RSG Group Backup Image. Select the RSG database path and RSG log path you entered in the first step and enter the corresponding logfile base name for the storage group. The system will then run a quick integrity check. 3. Select Tools --> Advanced --> Prepare RSG for Message Recovery. Enter the domain and user authentication information needed to log into the Exchange Server and access its Active Directory configuration. Select the mailbox store containing the mailbox to recover, enter the Exchange Server name, select the RSG, select the path for the RSG database and the corresponding stream (.stm) file. The recovery mailbox store will be created. 4. Launch the Exchange System Manager, mount the store, and use Exchange Tasks to copy or merge the data from the recovered mailbox. Dismount RSG backup The SSG and advanced RSG recovery wizards assume that you have used Snapshot Groups for your Exchange mailbox database and your Exchange mailbox log. If you have not used Snapshot Groups and your entire database, logs, and system directory are all on a single SAN disk, select Tools --> Advanced --> Mount Single Backup Image instead. Before you recover a new backup image, you will be prompted to delete any existing backup images.to delete the backup image manually, go to Tools -> Advanced -> Dismount RSG Group Backup. This option will also delete the RSG mailbox and group for Microsoft Exchange Recovery Agents User Guide 24

29 Message Recovery for Microsoft Exchange Restore from RSG backup image In the event a restore did not recover as expected, you may restore the backup image again if you have not deleted the image. To restore from a RSG backup image, go to Tools -> Advanced -> Restore from RSG Backup Image. The Exchange Server Login Information screen will display and you can rerun the recovery. This option is only available for Microsoft Exchange Recovery Agents User Guide 25

30 Message Recovery for Microsoft SQL User Guide Message Recovery for Lotus Notes /Domino Message Recovery for Lotus Notes/Domino (MRN) works to protect and restore Notes databases that are stored on IPStor -managed disks. IPStor and TimeMark work in conjunction with the FalconStor Snapshot Agent for Lotus Notes to take scheduled point-in-time snapshot images of the Notes databases that are stored on IPStor-managed disk. The Snapshot Agent gives the snapshot images point-in-time consistency and transactional integrity. If the server has local, direct-attached storage and you are using FalconStor DiskSafe to protect the Notes databases, DiskSafe works directly with the Snapshot Agent for Lotus Notes to replicate point-in-time snapshot images to IPStor-managed disk. When you need to recover a mailbox, MRN uses the Notes transaction log along with IPStor s snapshot images so that mailboxes can be easily and quickly recovered to any point in time. The administrator runs MRN on the local Notes Server and recovers individual mailboxes directly to the mailbox of the user who requested recovery. The user can then select what he or she needs. Recovery Agents User Guide 26

31 Message Recovery for Lotus Notes /Domino System requirements Lotus Notes Server MRN supports Lotus Notes version Your Lotus Notes Server must have an IPStor SAN Client or FalconStor Intelligent Management Agent (IMA) installed and should have the Snapshot Agent for Lotus Notes and the Snapshot Agent for Windows File System installed. Your Notes database file and transaction log should be on separate disks/ LUNs. IPStor Server Your IPStor Server must have TimeMark enabled. In the IPStor Console, you should create a group for your Notes mailbox database and your Notes mailbox log. Be sure to enable TimeMark for this group. This will keep your files in sync for recovery purposes. Refer to your IPStor User Guide for more information. Do not use any spaces in group names or for your device names. Remember that in order to recover user mailboxes with as much granularity as possible, you should configure TimeMark to regularly take point-in-time images of your Notes Server. We recommend taking at least one TimeMark per day. Install the software Installation of MRN has the following requirements: MRN has to be installed on a Notes Server machine. You must be an administrator or have administrator privileges in order to install MRN. To install: 1. Insert the installation CD into your CD-ROM drive. 2. Select Install Products --> Install Host-Based Applications --> Install Message Recovery for Lotus Notes. 3. When prompted, enter your license keycode. The MRN license must be activated (registered with FalconStor). If your computer has an Internet connection, the license is activated as soon as you enter your keycode and click Next. However, if your Internet connection is temporarily down or if your computer has no Internet connection, your license will not be activated. You must activate your license within 30 days so that you can continue to use the software. If your Internet connection is temporarily down, your license will typically be activated automatically the next time you run MRN, assuming you have an Internet connection then. Or, you can add your license through the SAN Disk Manager (the utility that is installed with IMA). Recovery Agents User Guide 27

32 Message Recovery for Lotus Notes /Domino Launch MRN If your computer has no Internet connection, you must perform offline activation. Refer to your SAN Disk Manager User Guide for more information. 4. When done, click Finish. This section explains how to launch MRN and change system settings. To start MRN select Start menu --> Programs --> FalconStor --> Tools --> Message Recovery for Lotus Notes Domino. The Console is displayed: A list of jobs that have been run previously is listed on the right side. To see more details about a job, highlight the job. By default, the last 20 jobs will be displayed. To change the number of jobs that are displayed, refer to the Change system settings section. The status of each job can be: Successful - Recovery was successful Cancelled - Cancelled by the user Failed - Recovery failed Recovery Agents User Guide 28

33 Message Recovery for Lotus Notes /Domino Change system settings To change system settings, highlight the Settings icon in the tree. Here you can change the number of jobs that will be listed on the main Console screen. You can also turn the system s Trace Log on or off. For more information about when you would turn the Trace Log on, refer to the Trace log section under Advanced features. Recovery Agents User Guide 29

34 Message Recovery for Lotus Notes /Domino Recovery MRN includes an easy-to-use wizard that enables administrators to recover mailboxes from a local Notes server. Using this wizard, you select the mailbox(es) you want to recover and the point in time to which you want to recover. MRN then automatically locates the correct TimeMark and, using the Notes transaction log, mounts a TimeView so that the data can be recovered. You must be a local administrator and a full Notes administrator in order to recover mailboxes. 1. Launch the MRN Console on the Notes Server. 2. From the menu, select File --> Automated Recovery. If you have previously recovered a mailbox, it must be unmounted before you can continue. The wizard will prompt you to unmount it. 3. Enter IPStor server login information. You need to log into the IPStor server which contains the TimeMarks for the mailboxes to be recovered. This can be a primary IPStor server or a replica IPStor server. This IPStor server must be a primary Lotus Notes machine. It cannot be a Lotus Notes replica machine (a machine to which Lotus Notes replicates data). The default Client Host Name comprises the SAN client machine name and the IMA host name in the format machine name[storage user login name]. Prior to IPStor 5.1, the Client Host Name was the machine name. Recovery Agents User Guide 30

35 Message Recovery for Lotus Notes /Domino 4. Select the mailbox(es) you want to recover. The path to the database is automatically selected for you. You can select multiple mailboxes to recover. Indicate if you want to generate a new replication ID for each recovered mailbox. If you generate a new replication ID, Notes will not replicate the mailbox. If you are only recovering specific items from the mailbox, you will want to generate a new replication ID because you do not want the older, recovered mailbox to overwrite the existing replica. If you are overwriting an entire mailbox, you may want to use the mailbox s existing ID so that Notes will replicate the data. Select a temporary location for the restored mailbox. Recovery Agents User Guide 31

36 Message Recovery for Lotus Notes /Domino 5. Select the point-in-time to which you want to recover. If you are trying to find a deleted , select a time prior to when the was deleted. You can either type in a specific time or you can pick a specific TimeMark. If you select a specific time, MRN will select the most appropriate TimeMark for you. 6. Confirm all information and then click Finish. Recovery Agents User Guide 32

37 Message Recovery for Lotus Notes /Domino It can take a few moments while the TimeView(s) are being mounted. 7. Click Finish when you see a screen similar to the following: Afterwards, there are several ways to get missing back to its owner. The administrator can open the NSF file into Notes and the whole NSF file or just the missing (s) back to its owner. The administrator can also share out the NSF file so that the owner can open the NSF file and the whole NSF file or just the missing (s) back to himself/herself. Clean up Notes When you exit MRN or start a new recovery wizard, you have the choice of deleting the existing TimeView that was mounted. If you choose Yes, MRN will delete it from the IPStor Server. While the TimeView is deleted, all of your TimeMarks are retained. Recovery Agents User Guide 33

38 Message Recovery for Lotus Notes /Domino Advanced features Trace log DiskSafe priority Clean up TimeViews This section describes the advanced features available in the Message Recovery for Lotus Notes /Domino (MRN) console. The Trace log is a diagnostic tool used by your Technical Support team to help solve system problems. Each Trace log contains technical information about your system as well as system messages. You should not turn the Trace log on unless you are requested to do so by your Technical Support representative. To turn the Trace Log on, highlight the Settings icon in the tree and select Trace On. To view the Trace Log, select View --> Log. MRN enables recovery of Notes mailboxes when the Notes database is stored on IPStor-managed disk. If the server has local, direct-attached storage, MRN enables recovery of Notes mailboxes that have been replicated to IPStor-managed disk by DiskSafe. There may be instances where the Notes database is stored on IPStor-managed disk AND DiskSafe is used to replicate data to another IPStor-managed disk. By default, MRN will assume that the IPStor-managed disk containing the primary Notes database is used for TimeMarks. If this is not the case, you must tell MRN to use the DiskSafe replica disk. To do this, select Options --> DiskSafe Priority. When you exit MRN or start a new recovery wizard, you have the choice of deleting the existing TimeView that was mounted. To manually delete the TimeView, select Tools --> Clean up TimeView. When you delete a TimeView, MRN deletes it from the IPStor Server. While the TimeView is deleted, all of your TimeMarks are retained. Recovery Agents User Guide 34

39 Message Recovery for Lotus Notes /Domino Manual recovery There are advanced configurations for which the wizard will be unable to automatically detect the logical resources containing the Notes database. For example, if your Notes system is not connected directly to the storage server that contains your backup images (such as a remote replica server), MRN will be unable to identify the logical resources and map the TimeMarks. For these types of configurations, MRN includes a tool that lets you manually log in to the storage server and manually select TimeMarks. To run a manual recovery: 1. Select Tools --> Advanced --> Manual Recovery. 2. Log in to your storage server. 3. Select the mailbox(es) you want to recover. Select the database file that contains the mailbox(es) to be recovered. Indicate if you want to generate a new replication ID for each recovered mailbox. If you generate a new replication ID, Notes will not replicate the mailbox. If you are only recovering specific items from the mailbox, you will want to generate a new replication ID because you do not want the older, recovered mailbox to overwrite the existing replica. If you are overwriting an entire mailbox, you may want to use the mailbox s existing ID so that Notes will replicate the data. Select a temporary location for the restored mailbox. 4. Select the disk that contains the Notes data directory and then select the TimeMark to which you want to recover. 5. Select the disk that contains the Notes log directory and then select the TimeMark to which you want to recover. 6. Select the point-in-time to which you want to recover. If you are trying to find a deleted , select a time prior to when the was deleted. 7. Confirm all information and then click Finish. 8. Click Finish when you see the Recovery completed successfully screen. Afterwards, there are several ways to get missing back to its owner. The administrator can open the NSF file into Notes and the whole NSF file or just the missing (s) back to its owner. The administrator can also share the NSF file so that the owner can open the NSF file and the whole NSF file or just the missing (s) back to himself/herself. Recovery Agents User Guide 35

40 Message Recovery for Microsoft SQL User Guide Database Recovery for Microsoft SQL Server FalconStor s Database Recovery for Microsoft SQL Server expedites database recovery by enabling IT administrators to quickly recover a database from point-intime snapshot images of their SQL database. The recovery method you will use depends upon the SQL recovery model that your database uses, Full Recovery Model" or Simple Recovery Model. The Full Recovery Model maintains the transaction log history, which records all changes to the database. For this reason, the Full Recovery Model" allows you to recover to any point in time, whereas the Simple Recovery Model" only allows you to roll back to the time of a scheduled TimeMark. Therefore, to take full advantage of this recovery too, at least one of your databases should be using the Full Recovery Model. This recovery tool integrates with your IPStor server to restore snapshot images of the SQL databases that are stored on IPStor-managed disks. IPStor TimeMarks work in conjunction with the Snapshot Agents to take scheduled snapshot images of the SQL databases. The Snapshot Agents give the snapshot images point-in-time consistency and transactional integrity. This recovery tool also integrates with DiskSafe to protect SQL databases that use local direct-attached storage. DiskSafe works directly with the Snapshot Agents to provide point-in-time snapshot images. Recovery Agents User Guide 36

41 Database Recovery for Microsoft SQL Server System requirements Database Recovery for Microsoft SQL supports the following: Microsoft SQL Server 2005 (32-bit and 64-bit) Microsoft SQL Server 2003 (32-bit and 64-bit) This recovery tool must be run on the SQL Server machine because certain configuration information is maintained during snapshots. Restoring to a different machine is not supported. The Intelligent Management Agent (IMA) must also be installed on the SQL Server. It is recommended that you have three disks if you will be performing transaction log backups. This will ensure the fastest possible restore. A separate disk should be used for each of the following: Database Transaction log Transaction log backups TimeMark must be enabled on your storage server. Remember that in order to recover your database with as much granularity as possible, you should configure TimeMark to regularly take point-in-time images of your server. The Snapshot Agent for Microsoft SQL Server and the Snapshot Agent for Windows file systems must be installed. In the storage server console, you must create a group for your SQL database, log, and backups. The group name cannot contain any spaces. TimeMark and Snapshot Notification must be enabled for your device group. This will keep your files in sync for recovery purposes. You must be an administrator or have administrator privileges in order to install and run this recovery tool. You should have a working knowledge of Microsoft SQL backup and restore processes prior to using this recovery tool. Recovery Agents User Guide 37

42 Database Recovery for Microsoft SQL Server Install the software To install Database Recovery for Microsoft SQL: 1. Insert the installation CD into your CD-ROM drive. If the setup utility does not start automatically, browse to the CD root directory and click setup.exe to launch the InstallShield wizard. 2. Read and accept the license agreement to continue installation. 3. Enter your user name and the name of your company. 4. Click Next to accept the default installation destination folder or browse to install to a different folder. 5. When prompted, enter your license keycode. 6. When done, click Finish. Recovery Agents User Guide 38

43 Database Recovery for Microsoft SQL Server The console To run the console as a standalone application, select Start --> Programs --> FalconStor --> Database Recovery for Microsoft SQL. An application window similar to the following appears: To access the console via Computer Management console, click Administrative Tools --> Computer Management, expand the Storage node in the left navigation pane, and click the Database Recovery for Microsoft SQL node. Note: This method of launching the console is not available if you are running the 32-bit version of this product on a 64-bit machine. The Console is divided into two panes. The left pane contains a navigation tree with nodes that you can click, expand, or collapse. The root node is the Database Recovery for Microsoft SQL node. When you highlight a node in the navigation tree, the right pane displays associated information. For example, when you highlight the Storage Servers node, the right pane displays information about your storage servers. Recovery Agents User Guide 39

44 Database Recovery for Microsoft SQL Server The menus If you display the Console through Computer Management, the menus at the top of the application window provide access to several functions that are common to all Microsoft Management Console-based applications, such as exiting the application. The common functions are available via the File, Action, View, Window, and Help menus. Functions that are specific to Database Recovery for Microsoft SQL typically appear in the Action menu. The Action menu is context-sensitive; the items that appear here change, depending on which node has focus. For example, when you click the Storage Servers node, the Action menu displays. You can also access Database Recovery for Microsoft SQL functions by right-clicking the elements on the screen. Add and connect storage servers The first time you start the application, the system will scan and import all storage servers identified by the IMA Client. These storage servers will be listed in the Database Recovery for Microsoft SQL Console. After your first backup, all backed up databases are listed. If you add a storage server directly in IMA, it will be imported into Database Recovery for Microsoft SQL the next time you click the Storage Servers node. If you add a server directly in Database Recovery for Microsoft SQL, the server will appear in both IMA and in Database Recovery for Microsoft SQL. Note: If a server is displayed with a red line, the server could be missing credentials or it could be offline. Check the Status field for more details. Add a new storage server If the server is missing credentials, you can add credentials on the server s properties page. Refer to If your server s status displays No Credentials, select the Authentication tab and right-click on the unauthenticated server and select Properties. on page 43 for more information. If you do not see your storage server displayed in the Servers list, you can add a new server. To add a server: 1. Navigate to Action --> New Storage Server from the main menu. Alternately, you can right-click on Storage Servers and select New Storage Server. Recovery Agents User Guide 40

45 Database Recovery for Microsoft SQL Server The Add Server screen displays. 2. Enter the following parameters: Server name - Enter the IP address or name (if resolvable) of the storage server. Windows Domain Authentication - (for iscsi Storage Servers) Indicate if you are using Windows domain authentication. You will have to enter the domain name. User name/password - Enter the user name and password that has administrative rights to the Storage Server Console. Protocols - Select which protocol(s) your Database Recovery for Microsoft SQL client uses. You must select at least one. If necessary, click the Advanced button for additional settings. Recovery Agents User Guide 41

46 Database Recovery for Microsoft SQL Server iscsi Advanced Settings - By default, the first detected iscsi HBA is utilized to communicate with the storage server. If no HBA is detected, the Microsoft iscsi Initiator is used. You can change the setting here. You can also specify the target portal IP address and port number to use for communicating with the storage server. Delete a storage server Fibre Channel Advanced Settings - By default, your storage server target ports and client initiator ports are set in an all-to-all configuration. If you want to use a specific client initiator port, select Enable specific Fibre Channel WWPN setting, click Add, type the appropriate WWPN, and click OK. You will also need to do this if the system cannot automatically detect your HBAs. If your storage server has two or more target ports and you want to use a specific target port, you will have to set this through the storage server console. 3. Click OK when done. Once the new server has been added, you can click Refresh to update the Servers list. You can delete a storage server that is no longer in use. To delete a storage server, right-click on the storage server and select Delete Storage Server. Recovery Agents User Guide 42

47 Database Recovery for Microsoft SQL Server Modify storage server properties You only need to modify storage server properties if a server displays with a red line through it or the server status displays No credentials. To modify storage server properties: 1. Right-click on the server name and select Properties. The Storage Server properties screen displays. The General tab displays the server name, IP address, storage server software, protocol, connection status, number of databases contained, as well as the last successful and failed snapshot date and time. The Authentication tab allows you to add credentials or authenticate using your user name and password. 2. If your server displays with a red line through it, click the Resolve button to resolve the host name. If the host name cannot be resolved, type in the IP address and select the Connect by Address checkbox. 3. If your server s status displays No Credentials, select the Authentication tab and right-click on the unauthenticated server and select Properties. Recovery Agents User Guide 43

48 Database Recovery for Microsoft SQL Server The server properties screen displays. 4. Enter a user name and password to log into the storage server. For iscsi Storage server, connect as your regular Windows administrative user. For storage server 5.0, you can connect as the root user or as another storage server administrator. For storage server 5.1, you must connect as an administrator. You cannot use the root user. 5. Click OK when done. Recovery Agents User Guide 44

49 Database Recovery for Microsoft SQL Server Configuration Configure global settings Your SQL database was configured for "Simple Recovery Model" or "Full Recovery Model" when it was initially set up. The recovery model your database is in dictates the recovery method you will use. The main difference between the two recovery models is the transaction log history. The transaction log records all changes to the database and plays an important role in backup and recovery. In order to benefit from all of the features provided with this Database Recovery for Microsoft SQL, at least one of your databases should be configured for the Full Recovery Model. Performing full database backups along with transaction log backups allows you to restore the database from the most recent full backup and then apply all the transaction log backups taken since the last full backup. This strategy is good for frequently modified databases and for those where you need to be able to recover data more frequently than the interval between full backups. This backup strategy also allows you to restore to a point in time before the end of the last transaction log backup. The global system settings are used to specify the transaction log backup policy and when to purge event history. To configure global settings: 1. Navigate to Action --> Global Settings from the main menu. Alternately, you can right-click on any node in the tree and select Global Settings. Recovery Agents User Guide 45

50 Database Recovery for Microsoft SQL Server The Recover Global Settings screen displays allowing you to configure your transaction log backup and purge policy settings as well as specify your log settings. 2. Set your Transaction Log Backups preferences using the parameters described below: Show transaction log list in the restore wizard dialogs - Allows you to add more detail to the restore wizard. If selected, a list of transaction logs is displayed during the restore process. Perform a transaction log backup for every snapshot - Backing up the database and the transaction logs is the most commonly used backup strategy because it offers a more granular and flexible recovery. This option is selected by default to perform a transaction log backup for every snapshot, creating a record of any database changes since the last full backup. Truncate transaction logs after they are backed up - Since the log files do use disk space if they are not removed by an administrator, you can select to truncate the transaction log files after you have completed the backup of all log files. You can configure the snapshot agent to back up the current transaction log using this option. Purge Policy - Allows you to specify the database transaction log purge policy. The selected purge policy options are applied immediately and are as follows: Purge when there are more than transaction logs per database Purge when transaction logs are older than days. Notes: If your transaction log backups are done on a storage server-managed disk, a copy of the transaction log backups are maintained in the storage server. Therefore, you can set a liberal purge policy. Your backups should take less than eight minutes. Due to the default timeout Recovery Agents User Guide 46

51 Database Recovery for Microsoft SQL Server for your storage server, the Snapshot may fail is the time is exceeded. 3. Configure your user log settings using the Log Settings tab. Errors and informational events can be found in the event viewer through the Computer Management console. Other events can be found in the program installation directory --> RecMSSQL.log file. The available settings are: Off - Only Actions are recorded to the log. This is the default setting. Low - Only Actions and Errors are recorded in the log. Medium - Actions, Errors, and Warnings are recorded in the log. High - Actions, Errors, Warnings, and Informational messages are recorded Trace - All messages are recorded in the log. The Trace log is a diagnostic tool used by your Technical Support team to help solve system problems. Each Trace log contains technical information about your system as well as system messages. You may be asked to turn the Trace log on by your Technical Support representative if you encounter a problem. The trace log file is located in the program installation directory. Trace log settings can be set to: Off - No logging. Low - Only Errors are recorded in the log. Medium - Errors and Warnings are recorded in the log. High - Errors, Warnings, and informational messages are recorded. Trace - All messages are recorded in the log. Recovery Agents User Guide 47

52 Configure the Snapshot Agent for Microsoft SQL Server Database Recovery for Microsoft SQL Server The Snapshot Agent for Microsoft SQL Server protects your Microsoft SQL Server database with full point-in-time consistency while still allowing full speed, continuous access to the database. Refer to the Snapshot Agents User Guide for additional information. To configure database options for the Snapshot Agent for Microsoft SQL Server: 1. From the main menu, navigate to Programs --> FalconStor --> Tools --> Snapshot Agent for Microsoft SQL Server. 2. Set the following parameters on the Database Options tab: Database: Select the database you are protecting. Database directory: The location of the database displays here. Transaction log directory: The location of the transaction log directory displays here. Storage server: The storage server name displays here. Transaction log backup directory: Select or browse to locate the transaction log backup directory. By default the transaction log directory is used. It is recommended that you use a separate disk to back up transaction logs. Transaction log backup directory: The agent can be configured to perform a transaction log backup - before the full snapshot backup. See information about this option in Configure global settings on page 45 Recovery Agents User Guide 48

53 Database Recovery for Microsoft SQL Server Integration with DiskSafe DiskSafe priority Database Recovery for Microsoft SQL can be used in conjunction with FalconStor DiskSafe. DiskSafe protects your Microsoft SQL servers (referred to as hosts) by copying the data to a mirror another local disk or a remote virtual disk managed by a storage server application. If you are using the DiskSafe application to backup your SQL server(s), the Database Recovery for Microsoft SQL tool can be used to recover your data. Database Recovery for Microsoft SQL enables recovery when the SQL database is stored on your storage server-managed disk. If the server has local, direct-attached storage, the recovery tool enables recovery of SQL database data that has been replicated to your storage server-managed disk by DiskSafe. There may be instances where the SQL database is stored on your storage servermanaged disk and DiskSafe is used to replicate data to another your storage servermanaged disk. If detected, the following message displays prompting you to select the source for the backup image to restore. By default, the Database Recovery for Microsoft SQL tool will assume that your storage server-managed disk containing the primary SQL database is used for TimeMarks. If this is not the case, you must notify the recovery tool to use the DiskSafe mirrored disk. Recovery Agents User Guide 49

54 Database Recovery for Microsoft SQL Server Command line utility Transaction log backups A command line recovery tool (fsssrest.exe) is included with your Database Recovery for Microsoft SQL installation allowing you to perform additional options. After a storage server snapshot, you can run this command, if needed, to back up the transaction log. To do this, use the following command: fsssrest -d <databasename> -tlb The advantage to using this command is that the date and time is recorded, making it easier to identify which transaction logs are needed during the restore. You can also schedule and perform Transaction log backups with other utilities in order to have more transaction log backups between the snapshots (full backups). You can run this command as needed, based on your backup schedule. The <databasename>.his file contains a list of all files from the time the application started and resides on the same disk as the specified transaction log disk. The <databasename>.his file looks similar to the following: dbtest.mdf dbtest log dbtest log dbtest log dbtest.mdf From this log file we can tell that a full backup was done, followed by three Transaction Log backups, and then another full backup. Recovery Agents User Guide 50

55 Database Recovery for Microsoft SQL Server Trace log To turn the Trace Log on and create a fstrace.log file, use the following command: fsssrest -t To create a fstrace.log file to another location or file name option (default): fsssrest -t "d:\fstrace.log The Trace Log is also available from the console. To create a fstrace.log file, select Options --> Trace. To view the Trace Log, select View --> Log. To view the Trace Log, select View --> Log Database recovery Restore your database After a database has crashed it is recommended that you initiate one last Transaction Log backup manually to capture the last possible moment before database crashed. Once your backups are in order, there are two restore scenarios to choose from: TimeView - restores the database image to a temporary location for validation prior to permanent rollback. TimeMark Rollback - restores a database image (snapshot) to the original location, permanently replacing the existing data. To restore your Microsoft SQL database: 1. Right-click on the database you plan to recover and select Restore. Recovery Agents User Guide 51

56 Database Recovery for Microsoft SQL Server The login screen displays. 2. Select the database name, storage server, and hostname and click Next. The devices are scanned and the Restore Database - Mode screen displays. 3. Select the restore mode. TimeView Restore - Temporarily restores a database to a temporary device so you can verify the recovery data before committing to a rollback. It is recommended that you select this option first. Recovery Agents User Guide 52

57 Database Recovery for Microsoft SQL Server Rollback TimeMark Restore - Permanently restores back to a previous state. TimeMark rollback is an irreversible process, replacing existing data with the selected restore data. It is recommended that you select TimeView Restore first to determine if the database can be restored to a good point in time. 4. Select any additional databases to restore. It is recommended that you restore all databases on the device. Selecting all databases on the device results in a quick disk swap. Otherwise, the system performs a file copy of the selected databases back to the original device when in rollback mode. 5. Select the restore method. You can choose from the following types of restore: Restore Full backup with transaction logs to a specific point in time. Restore Full backup from a snapshot (Advanced option). 6. If you selected to restore a full backup with transaction logs to a specific point in time, select the date and time for the restore. For information regarding advanced restore options, see Advanced restore options on page 55. Recovery Agents User Guide 53

58 Database Recovery for Microsoft SQL Server The Restore Database screen displays a list of what is being recovered. 7. Verify the list for recovery or modify the list using the add, delete, or move buttons. To include transaction logs that were not taken by this recovery tool, click Add and browse for the transaction logs to include with the recovery. if you have selected multiple databases, select each database and verify each list. 8. Click Next when you are ready to begin the restore process. If you have selected the TimeView restore, the temporary restore process begins and the data is restored to a temporary location. Verify the recovery data. Click Next to revert back and try another restore, or click Cancel to leave the devices in their current state and continue later. Once the recovery data has been verified, repeat the process selecting the Rollback TimeMark Restore option to permanently restore the database. Recovery Agents User Guide 54

59 Database Recovery for Microsoft SQL Server If you selected the permanent Rollback TimeMark Restore process, the data is restored to the original location. Advanced restore options Advanced restore options allow you to restore a full backup from a snapshot image. You can select the snapshot image from the list of available full backups. In addition, you can select the Restore to the time of the last scheduled transaction log backup checkbox to include all transaction logs. If you are using a different recovery tool to complete the restore, you may select the Use No Recovery option to keep the database in restore mode checkbox. Recovery Agents User Guide 55

60 ac IntegrityTrac IntegrityTrac is a validation tool that allows you to check the application data consistency of snapshots taken from Microsoft Exchange servers before using them for back up and recovery. IntegrityTrac allows you to off load application-specific image verification for those applications that require it (such as Microsoft Exchange) so that the production server is not impacted by the snapshot/backup process. This ensures data integrity so applications can have fast and transactionally consistent recovery IntegrityTrac can be run on a separate server, at any time, to check the validity of a TimeMark snapshot from the application s perspective. When possible, IntegrityTrac can even repair a snapshot using the application s own tools. IntegrityTrac can also be installed on the same machine as FalconStor HyperTrac Backup Accelerator so that the validation and backup can be performed on a single server. Terminology Checksum Integrity Scripts Snapshot TimeMark TimeView A checksum verifies whether a messaging system, database, or file system was successfully quiesced and whether snapshot data was correctly written. An integrity check sweeps snapshot data for errors. An integrity check is more comprehensive than a checksum and takes longer to complete. Scripts define the disks/devices that are mapped to the Application host machine from a storage server that are included in each snapshot. A snapshot is a consistent point-in-time, frozen image of one or more data volumes. A quiescent snapshot is one that used snapshot notification. With snapshot notification, the system notifies the host to quiet disk activity before the snapshot is taken. A TimeMark is a point-in-time image of any virtual disk or data volume. It is the result of taking a snapshot. Using FalconStor's Snapshot technology, TimeMarks track multiple virtual images of the same disk marked by "time". If you need to retrieve a deleted file or "undo" data corruption, you can recreate/restore the file instantly based on any of the existing TimeMarks. Each TimeMark represents one backup image. A TimeView (a.k.a. backup image) is a mountable TimeMark. It allows you to access files and directories by mounting a virtual drive as of a specific point-in-time, based on existing TimeMarks. The following is an overview of the steps required to begin using IntegrityTrac: 1. Install the IntegrityTrac software. Recovery Agents User Guide 56

61 IntegrityTrac Supported platforms System requirements Install the software Refer to Install the software for more information. 2. Connect to and authenticate each storage server. Refer to Storage server authentication for more information. 3. Create device mapping scripts and job scripts. Device mapping scripts define the disks/devices mapped to each Application host machine from a storage server. Job scripts enable you to drill down further into the mapped Application host disks to select that application data and log files that need to be verified. Information about creating scripts can be found in the Scripts section. IntegrityTrac supports the following operating systems: Microsoft Windows 2003 (64-bit) - Enterprise and Standard editions Microsoft Windows 2008 (64-bit) - Enterprise and Standard editions IntegrityTrac supports the following applications: Microsoft Exchange 2003 Microsoft Exchange 2007 IntegrityTrac supports the following applications: Microsoft Exchange 2003 Microsoft Exchange 2007 IntegrityTrac has the following requirements: FalconStor SAN Disk Manager must be installed on the machine where IntegrityTrac is being installed. If not detected, the installation process will install the correct version. You will need approximately 50 MB of available hard disk space for history and log files. You must be an administrator or have administrator privileges in order to install and run IntegrityTrac. To install: 1. Launch the installation media. If the setup utility does not start automatically, browse to the CD root directory and click setup.exe to launch the wizard. Recovery Agents User Guide 57

62 IntegrityTrac 2. Select Install Products --> Install Host-Based Applications --> Install IntegrityTrac. 3. Read and accept the license agreement to continue. 4. Determine if you want to accept the default installation destination folder or browse to install to a different location. By default, IntegrityTrac is installed to the following directory: \Program Files\Falconstor\IntegrityTrac 5. When prompted, enter your license key code. For new installations, your license must be activated (registered with FalconStor) within 30 days. If your computer has an Internet connection, the license is activated when you enter your key code and click Next. If your Internet connection is temporarily down, your license will typically be activated automatically the next time you run IntegrityTrac. If your computer does not have an Internet connection, you will need to perform offline activation. Refer to your SAN Disk Manager User Guide for more information. 6. When done, click Finish. Microsoft Exchange tools If you are using IntegrityTrac with Microsoft Exchange, you must copy the appropriate versions (they must match your version of Microsoft Exchange) of the following Exchange utilities to the root directory where IntegrityTrac is installed: ese.dll eseutil.exe jcb.dll. exchmem.dll exosal.dll Storage server authentication Since IntegrityTrac will be interacting with your FalconStor IPStor CDP, or NSS storage server to validate TimeMark snapshots, it needs to connect to the server without requiring a user to be present. For IPStor 5.1 or 6.0 (build 6086 or later), you need to create an administrator account for IntegrityTrac in the FalconStor Management Console that will be used to connect to each storage server. You cannot use the root user. To add an administrator in the FalconStor Management Console: 1. Launch the FalconStor Management Console (Start --> Programs --> IPStor Console). 2. Right-click on the server and select Accounts. Recovery Agents User Guide 58

63 IntegrityTrac Console overview 3. Click the Add button. 4. Enter a name in the Username field. You cannot use root as the Username. 5. Enter a password and then re-enter it in the Confirm Password field. The password is case sensitive. 6. Change the user type to IPStor Admin. 7. Click OK to save the information. To run the console as a standalone application, select Start --> Programs --> FalconStor --> IntegrityTrac. An application window similar to the following appears. The console is divided into two panes. The left pane contains a navigation tree with nodes that you can click, expand, or collapse. The root node is the IntegrityTrac node. When you highlight a node in the navigation tree, the right pane displays associated information. For example, when you highlight the Storage Servers node, the right pane displays information and status about your storage servers. Recovery Agents User Guide 59

64 IntegrityTrac For a quick view of system status, click on the IntegrityTrac node to see the status of all job scripts and Application hosts. Computer Management You can also access the console via the Computer Management Console. 1. Click Control Panel --> Administrative Tools --> Computer Management. 2. Expand the Storage node in the left navigation pane and expand the IntegrityTrac node. Menus Global settings Configure global settings IntegrityTrac functions appear in the Action menu. The Action menu is contextsensitive; the items that appear here change, depending on which node has focus. For example, when you click the Storage Servers node, the Action menu displays functions specific to storage servers. You can also access IntegrityTrac functions by right-clicking the nodes in the tree. If you display the console through Computer Management, the menus at the top of the application window provide access to several functions that are common to all Microsoft Management Console-based applications. The common functions are available via the File, View, Window, and Help menus. Global system settings are used to specify where to store important directories and when to purge event history. Configure your global settings to specify where to store your scripts. You can also specify your default mount directory and indicate your preferred purge policy. To configure global settings: 1. Right-click on any of the main nodes and select Global Settings. Recovery Agents User Guide 60

65 IntegrityTrac You can also select Global Settings from the Action menu. 2. Select the Script Directory tab to specify where to store your device mounting and job script files. 3. Select the Mount Directory tab to specify where the default mount directory will be stored. This is applicable only if IntegrityTrac is running from the host machine. 4. Select the Purge Policy tab to specify the policy for Event history. The selected purge policy options are applied immediately and are as follows: Purge when there are more than events per script. (default = 60) Purge when events are older than days (default = 30). Set this field to zero to ignore this option. Events A list of events are displayed when you highlight the Events node. (Note that all the events are also sent to the Windows Event Log.) Recovery Agents User Guide 61

66 IntegrityTrac The system shows the status when a script is created or imported and after a job is run. For each event, the system shows when it occurred, the storage server and script, the type of event, the operation performed, the status, and a description of the warning or error (if applicable). Status is marked by colored icons: Blue - Informational Yellow - Warning Red - Error Sort events Search for events Storage servers 1. To sort the events in alphabetical/numerical order, click on the heading of the appropriate column. 2. Click again if you want to reverse the order. 1. To search for a specific event or a range of events, select the search criteria in the first drop-down box. 2. Type all or part of what you want to find in the search field and click the Go button. Only the events that match your criteria will be displayed. 3. When you are finished, click the Clear Filter button and all events will be displayed. The first time you start IntegrityTrac, the system will scan and import all storage servers identified by the SAN Disk Manager (SDM) / Intelligent Management Agent (IMA) Client. These storage servers will be listed in the IntegrityTrac console and will need to be authenticated. Recovery Agents User Guide 62

67 IntegrityTrac If you add a storage server directly in SDM/IMA, it will be imported into IntegrityTrac the next time you click the Storage Servers node. If you add a server directly in IntegrityTrac, the server will appear in both SDM/IMA and in IntegrityTrac. Establish a connection with your storage server Add a new storage server Since IntegrityTrac will be interacting with your storage server, you will need to establish a connection to the server(s). You need to create an administrator account for IntegrityTrac in IPStor, NSS, or CDP that will be used to connect to each storage server. You cannot use the root user. If you do not see your storage server displayed in the Storage Servers list, you can manually add it. To do this: 1. Right-click on the Storage Servers node in the directory tree and select New Storage Server. Alternatively, you can select Action --> New Storage Server from the main menu. The Add Server screen displays. 2. Enter the following parameters: Server name - Enter the IP address or name (if resolvable) of the storage server. Windows Domain Authentication - Indicate if you are using Windows domain authentication. You will have to enter the domain name. User name/password - Enter the user name and password that you created for IntegrityTrac in the FalconStor Management Console. Recovery Agents User Guide 63

68 IntegrityTrac Protocols - Select which protocol(s) your IntegrityTrac client uses. You must select at least one. 3. If necessary, click the Advanced button next to a protocol for additional settings. iscsi Advanced Settings - By default, the first detected iscsi HBA is used to communicate with the storage server. If no HBA is detected, the Microsoft iscsi Initiator is used. You can select an adapter here. You can also specify the target portal IP address and port number to use for communicating with the storage server. Fibre Channel Advanced Settings - By default, your target ports and client initiator ports are set in an all-to-all configuration. If you want to use a specific client initiator port, select Enable specific Fibre Channel WWPN setting, click Add, type the appropriate WWPN, and click OK. You will also need to do this if the system cannot automatically detect your HBAs. If your storage server has two or more target ports and you want to use a specific target port, you will have to set this through the FalconStor Management Console. 4. Click OK when done. Recovery Agents User Guide 64

69 IntegrityTrac Once the new server has been added, you can click Refresh to update the Servers list. Resolve the host name of a storage server If a server is displayed with a red line through it, you may need to resolve the host name in order to bring the server online or it may be missing credentials. Follow the steps below to resolve the host name. Refer to the next section if the server is missing credentials. 1. Right-click on the server name and select Properties. The storage server properties screen is displayed. The General tab displays the server name, IP address, storage server software, protocol, connection status, number of databases contained, as well as the last successful and failed snapshot date and time. 2. Enter or confirm the IP address and click the Resolve button to resolve the host name. If you want to connect via IP address rather than host name, select the Connect by Address box. 3. Click OK when done. Recovery Agents User Guide 65

70 IntegrityTrac Add credentials for a storage server If a server is displayed with a red line through it, this might indicate that the server is missing credentials or is offline. Check the Status field to see if it displays No Credentials. Follow the steps below if the server is missing credentials. Refer to the previous section to resolve the host name and bring it online. 1. Right-click on the unauthenticated server and select Properties. The server properties screen displays. 2. Select the Authentication tab. The Authentication tab allows you to add credentials or authenticate using your user name and password. 3. Enter a user name and password to log into the storage server. 4. Click OK when done. Recovery Agents User Guide 66

71 IntegrityTrac Add a IntegrityTrac administrator in IPStor, NSS, or CDP Delete a storage server You must create an administrator account for IntegrityTrac in IPStor/NSS/CPD that will be used to connect to each storage server. You cannot use the root user. To add an administrator: 1. Launch the FalconStor Management Console (Start --> Programs --> FalconStor --> IPStor --> IPStor Console). 2. Right-click on the server and select Accounts. 3. Click the Add button. 4. Enter a name in the Username field. You cannot use root as the username. 5. Enter a password and then re-enter it in the Confirm Password field. The password is case sensitive. 6. Specify that this account is an IPStor Admin. 7. Click OK to save the information. You can delete a storage server that is no longer in use. To do this, right-click on the storage server in the IntegrityTrac console and select Delete Storage Server. Recovery Agents User Guide 67

72 IntegrityTrac Application Hosts Select the Application hosts with provisioned storage that have TimeMark Snapshots that will be verified by IntegrityTrac. This would be your Microsoft Exchange servers. To select an Application host: 1. Right-click on Application Hosts and choose Select Application Hosts. Alternatively, you can select Action --> Select Application Hosts from the main menu. Remove Application Hosts 2. Click the checkbox next to each host you want to select. If you need to remove an Application Host, you may do so as long as there is not a device mapping script associated with that host. To remove it: 1. Right-click on the host name and select Remove. Alternatively, you can highlight the host name and remove the host from the Action menu. 2. Click OK to confirm the host removal. Recovery Agents User Guide 68

73 IntegrityTrac Scripts Device mapping scripts IntegrityTrac uses script files to validate TimeMarks. There are two types of scripts used by IntegrityTrac: Device mapping scripts - Allow you to define the disks/devices mapped to each Application host machine from a storage server. Job scripts - Allow you to drill down further into the mapped Application host disks to select that application data and log files that need to be verified. The first step is to create your device mapping scripts. Once they are defined, you can create your job scripts. Device mapping scripts map devices to Application host machines. Each device mapping script stores information such as the storage server name, the Application host name, and all of the devices assigned to the Application host. Click on the Device Mapping Scripts node in the console to see a list of your device mapping scripts along with the associated Application host, storage server, device/ volume number, the number of runs, the number of failed runs, the date of the last run and the current status. Create a device mapping script To create a script: 1. Right-click on the Device Mapping Scripts node and select New Device Mapping Script. Alternatively, you can create a device mapping script by right-clicking on a storage server or application host. Recovery Agents User Guide 69

74 IntegrityTrac 2. Enter the basic information about this script. Script Name - Enter a unique name for this script. Storage Server - Select the storage server that provides devices to your host. This must be an authenticated server. If you initiated this wizard from a storage server node, this field will display that storage server and you will not be able to change it. Application Host - Select the host that the devices are mapped to. The host names are automatically filled in based upon the selected storage server. Local Machine Name - The local machine name is automatically populated. Recovery Agents User Guide 70

75 IntegrityTrac 3. Select the device(s) that are provisioned to the application host for the application data you want to verify. The list includes all devices from the selected storage server and indicates which options are enabled, if the device is a member of a group, and size. Devices must have TimeMark or Snapshot enabled or be a replica. If a device is in a group, you should select all devices in the group since a single TimeMark snapshot will be taken for the group. Recovery Agents User Guide 71

76 IntegrityTrac 4. Enter the names of the volumes that are on the devices that you want to mount to the specific mount point path. Click the Add button to add a volume to be mounted to a specific mount point directory or drive. 5. Confirm the newly created device mapping script is correct and click Finish. Recovery Agents User Guide 72

77 IntegrityTrac Modify a device mapping script There may be cases where you will want to change the host mapping of a device mapping script. Follow the steps below to modify device or volume names contained in a device mapping script: 1. Right-click on the script name and select Properties. 2. Select the Devices tab. 3. Click the Modify button. 4. Select or de-select the storage server devices to be associated with the script and click OK. Import device mapping scripts You can import a device mapping script or an entire directory of scripts created on another machine. If you import an entire directory, it will import all of the scripts from that directory. Recovery Agents User Guide 73

78 IntegrityTrac 1. Right-click on Device Mapping Scripts and select Import Device Mapping Script. 2. Click the Browse button to select the script directory or file to import. 3. Select one of the following import options: Move and Merge files - Moves the script and merges it onto the destination. The source is deleted when the import operation is finished. Copy and Merge files (default) - Copies the script and merges it onto the destination. The source remains intact. Move and Overwrite files - Replaces the destination script with that from the source. The source is deleted when the import operation is finished. Copy and Overwrite files - Replaces the destination script with that from the source. The source remains intact. 4. Click Finish. Run a device mapping script To run or test a device mapping script: Recovery Agents User Guide 74

79 IntegrityTrac 1. Right-click on a device mapping script and select Run Map Command. 2. Specify the following information and click Next: Snapshot - Select which Snapshot to use: Use latest Snapshot Use closest Snapshot to the specified time Use closest Snapshot before the specified time Use latest Quiescent Snapshot Protocol - Select iscsi or Fibre Channel Recovery Agents User Guide 75

80 IntegrityTrac 3. Specify the advanced command options and click Next. Output - Indicate how extensively the processing messages should be displayed on the screen. Output choices are: Verbose - (Default) All messages will display on the screen. Terse - Errors, warnings and highlighted action messages are displayed. Silent - No messages are displayed. Trace execution to IntegrityTrac.log - This option defaults to On. You can turn it off if you do not want trace information sent to the IntegrityTrac log file. Rescan Timeout - Indicates how many seconds to wait after a device rescan. Specify zero (0) to use the default timeout. Other - Specify other options here if the above options are not sufficient. Refer to the Syntax for IntegrityTrac runtime module section for more information about available options. Detect DiskSafe Mirror and flip disk signature to original signature - This option is selected by default. Recovery Agents User Guide 76

81 IntegrityTrac 4. Review the Map command information that has been generated and click Finish. Select Run Now to run the script immediately. To remove the device mapping script, right-click on the device mapping script from the console and select Run Remove Command to remove the mappings. Job scripts Once your device mapping scripts have been created, you can create Job scripts. Job scripts enable you to drill down further into the mapped Application host disks to select that application data and log files that need to be verified. For example, an Exchange Job Script would allow you to see the mapped devices and browse the devices to select database (edb and stm) files, log files, and the checkpoint files that need to be verified. Once created, job scripts can be edited and run from the IntegrityTrac menu. Job scripts can also be run from a DOS prompt, can be scheduled directly from the IntegrityTrac console, or from the Windows Scheduler. Job script creation and modification may be an ongoing process. As you acquire devices, you can update your job scripts as needed. Click on the Job Scripts node in the console to see a list of job scripts along with the associated application host, storage server, device/volume number, the number of runs, the number of failed runs, the date of the last run and the current status. To view more detailed general, statistical, or historical information about a specific job script, you can right-click on the job script and select Properties. Recovery Agents User Guide 77

82 IntegrityTrac Create a job script To create a job script: 1. Right-click on the Job Scripts node and select New Job Script The Create a Job Script wizard launches. You can also right-click on an existing device mapping script and select New Job Script. 2. Enter a unique Script Name. 3. Select the device mapping script that contain the device assignment for your application hosts. 4. Select the Application that has data on TimeMark Snapshots of the devices that will be verified and click Next. Microsoft Exchange 2003 Microsoft Exchange Select the Snapshot Criteria: Check Last N non-checksummed TimeMarks Check Last N non-verified TimeMarks Check Last N TimeMarks Recovery Agents User Guide 78

83 IntegrityTrac 6. If desired, specify options for this script. Snapshot Criteria - Indicate the snapshot schedule. You can select whether you want to: Check the last N non-checksummed TimeMarks Check the last N non-verified TimeMarks Check the last N TimeMarks N = the number of TimeMarks to check. Place the number in the field beside Snapshot Criteria. Action - Select one of the following: Verify Checksum - verify the data at the physical level. This is the default, Backups of Exchange only require that the data be checksummed before backup. Verify Integrity - verify the data at the logical level. Verify Checksum and Repair - verify the data at the physical level and fix any problems detected. Verify Integrity and Repair - Verify the data at the logical level and fix any problems detected Select if you want to update the snapshot with changes or repairs. (This is available with IPStor 6.0 and later.) Protocol - Select iscsi or Fibre Channel (FC). Output - Indicate how extensively the processing messages should be displayed on the screen. Output choices are: Recovery Agents User Guide 79

84 IntegrityTrac Verbose - (Default) All messages will display on the screen. Terse - Errors, warnings and highlighted action messages are displayed. Silent - No messages are displayed. Trace execution to IntegrityTrac.log - This option defaults to On. You can turn it off if you do not want trace information sent to the IntegrityTrac log file. Rescan Timeout - Indicates how many seconds to wait after a device rescan. Specify zero (0) to use the default timeout. Other - Specify other options here if the above options are not sufficient. Refer to the Syntax for IntegrityTrac runtime module section for more information about available options. The Mount Devices during Job Script Create to verify script checkbox is selected by default and is recommended. This process activates the device mapping script to mount the latest snapshot image locally so that you can select the application data and logs directly from the actual images. This ensures selection accuracy as well as the validity of the selected device mapping script. Recovery Agents User Guide 80

85 IntegrityTrac 7. Select the Application Path Type, the Volume Mapping, and enter the Path Directory or file. If you are using Exchange 2003, select one log directory, one checkpoint file (.chk), and n pairs of database/streaming (edb/stm) files contained within one Exchange storage group. If you are using Exchange 2007, select one log directory, one checkpoint file (.chk), and n database (edb) files contained within one Exchange storage group. 8. Confirm the information and click Finish. Note: Your job script contains the selected host name, device mapping script, the various application specific paths (such as edb file and log directory), the default snapshot criteria, actions and options to use during the job. Refer to Edit a job script for more information. The snapshot criteria and actions may be overridden when you run the job using CSRun. For more information, refer to CSRun. Edit a job script Each job script contains the selected host, device mapping script, and default verification actions, criteria, and options. You can edit a job file from the Properties screen in the IntegrityTrac console. Recovery Agents User Guide 81

86 IntegrityTrac Properties Run a job script To edit the properties of a job script: 1. Right-click on the job script and select Properties. The Properties dialog consists of the following tabs: General Schedule Options Application Paths, Snapshots History Some tabs are only informational. 2. Select the Options tab to edit any needed script options. 3. Click OK when you are done. To run a job script: 1. Right-click on a job script and select Run Job Script. Recovery Agents User Guide 82

87 IntegrityTrac Schedule a job script 2. Select if you want to override any job criteria, actions, starting points, or options. Or click OK to run the job script. IntegrityTrac allows you to schedule verification jobs directly from the console. The IntegrityTrac scheduler interface matches the Microsoft Windows Scheduler interface since it uses Windows scheduler to run the jobs. You can schedule when to run a job script by right-clicking on the job script and selecting Schedule. You can also launch the scheduler from the property pages for the job, or use the Windows Scheduler. 1. Select the frequency to run the job script and click OK. You can click the Advanced button to specify additional options such as an end date or repeat schedules. Recovery Agents User Guide 83

88 IntegrityTrac Syntax for IntegrityTrac runtime module CSMap CSMAP is an executable module that takes two sub-commands: map and remove, followed by a script name, in addition to the following options. Syntax: CSMap <map remove> <script file name> [options] Options: [[-c -cb -ca]{timestamp}] [-d -d5] [-e{type}] [[-l -nq] [-h#] [-i -m -p] [-k] [-r] [-s] [-t] [-u] [-w#] [-x] [-o] [-v -z] [-@df] [-@f]: Option Description -i Ignore volumes listed in the script file (reverse of m) -m Mount or unmount volumes listed in script. -n Always create new TimeMark for each device (reverse of l). -nq -o Turn log off. Always create new TimeMark with quiescent status equal to yes -c Use the TimeMark that is closest to the given timestamp.[yyyymmddhhmmss] -ca -cb Use the TimeMark that is closest but after the given timestamp.[yyyymmddhhmmss] Use the TimeMark that is closest but before the given timestamp.[yyyymmddhhmmss] -h Verify that the TimeMark is not older than #Hours (e.g. - h10) -p Proxy mode -d Use DynaPath v1.x -d5 Use DynaPath v5.x -k Remove drive letter for TimeView device (if applicable) -l Use the latest TimeMark -lq Use the latest TimeMark with quiescent status equal to yes (if available) -e Protocol - indicates which protocol is being used. (e.g. -e FC) Recovery Agents User Guide 84

89 IntegrityTrac Option Description -er -svm Indicates which protocol to use for standby. Skip calling Virtual Mount Utility -t Force re-attach of single device -r Remove old TimeMarks. -s Stop and restart SAN client. -u Flush volumes before unlock. -v Verbose mode. All messages are displayed onscreen. -w# Wait # seconds after device rescan (e.g. -w30) The default is 3 seconds. -x Remove mount point folders after unmount. -z Silent mode. No onscreen messages. -@df DiskSafe flip - revert to original disk signature -@f -@u Force to execute consecutive map or remove operations Update/persist TimeMark changes => Leave TimeView data. Recovery Agents User Guide 85

90 IntegrityTrac CSRun CSRun is an executable module that runs a job script. CSRun also tracks and synchronizes with other concurrent jobs so as not to collide with them. Syntax: CSRUN <job script name> [options] Options: [-a{action}] [-m{snapshot Criteria}] [-n{#snapshots}] [-u] [-c -cb -ca]{timestamp}] [-o] [-v -z]. Option Description -m Snapshot Criteria: 0 - Check latest snapshot 1 -.Check latest un-verified snapshot 2 - Check latest N snapshot 3 - Check latest N un-verified snapshot (Use -n to specify N snapshots.) -n # of Snapshots to verify -a Action {0 - Verify, 1 - Verify and Repair} -u Update Snapshot {0=No, 1=Yes} -c Use the TimeMark that is closest to the given timestamp.[yyyymmddhhmmss] -ca -cb -o Turn log off. Use the TimeMark that is closest but after the given timestamp.[yyyymmddhhmmss] Use the TimeMark that is closest but before the given timestamp.[yyyymmddhhmmss] -v Verbose mode. All messages are displayed onscreen. -z Silent mode. No onscreen messages. CSNotify.bat. After each job completes, CSNotify.bat is called with the following parameters to allow customized reporting.: Param1 - Job Name Param2- Error Value (0-success, else error #) Param3- Error String Recovery Agents User Guide 86

91 IntegrityTrac Param4 - Error File The CSNotify.bat file can be modified to send alerts or whatever for each IntegrityTrac job that is run. CSNotify.bat is located in the IntegrityTrac directory. Create a diagnostic X-ray file To capture information about your host into a file, create an X-ray by following the steps below: 1. Highlight IntegriryTrac in the root of the directory tree. 2. Right-click and select Take X-ray. The Create diagnostic X-ray screen displays. 3. Select the location where you want the X-ray file placed and click Finish. This procedure may take several minutes. Recovery Agents User Guide 87

92 Database Recovery for Microsoft SQL User Guide Index A Active Directory 7 Administrator 67 Advanced Fibre Channel settings 64 Advanced iscsi settings 63 Advanced restore options 55 Authentication 43, 66 Windows 58 B Backup image 2 Batch scripts 77 Create 78 Edit 81 Options 82 Pre/Post commands 81 Properties 82 Run 82 Set recovery order 81 Validate 81 C Checksum 56 Clean up TimeViews 33, 34 Cleanup 12, 21 Command line recovery tool 50 Computer Management Console 39, 59 Console 28, 59 Action menu 60 Job list 28 Launch 28 Menus 60 Windows Red line 40 Continuous Data Protection (CDP) 2 Copy mailbox 20 Credentials Add 66 adding 43 CSNotify.bat file 87 D Database recovery 51 Database Recovery for Microsoft SQL Server 1 Definitions 56 Device mapping scripts 69 Create 69 Import 73 Modify 73 Run 74 DiskSafe 2 DiskSafe priority 23, 34 E EDB database 4 Event history 61 Events 61 Search for 62 Sort 61 Exchange , 13 Exchange Tasks 20 F Fibre Channel Client initiator ports 64 IPStor target ports 64 fsssrest.exe 50 fstrace.log file 51 G Global Settings 45 Global settings 60 H Host scripts 69 Hosts Remove 68 Resolve name 64 Select 68 I Import device mapping scripts 73 Installation 5, 27, 38, 57 Integrity 56 IntegrityTrac administrator 67 Intelligent Management Agent (IMA) 2, 37 Introduction 1 IPStor 26 IPStor Server 27 iscsi initiator 63 Revcovery Agents User Guide i

93 Index J Job List 28 Status 28 K Keycode 58 L LaunchMRMEAsUser utility 13 License Activation 58 Licensing 5, 27, 38 Lotus Notes Server 27 M Mailbox Copy 20 Merge 20 Manual recovery 35 Manual RSG recovery 23 Menus 60 Merge mailbox 20 Message recovery for Exchange (MRE) 3 Message Recovery for Lotus Notes/ Domino (MRN) 1 Message Recovery for Microsoft Exchange (MRE) 1 Microsoft Exchange 2003 Cleanup 12, 21 Mirrored disk 49 Mount directory 61 N No Recovery option 55 O Output Silent 76, 80 Terse 76, 80 Verbose 76, 80 P Passwords Windows 58 Platforms supported 57 Properties Batch scripts 82 Device mapping scripts 73 Protocol iscsi or Fibre Channel 79 PST file 20 Purge policy 61 Q Quiescent snapshot 56 Quiescent TimeMark 11, 18 R Recovery How it works 3 Manual 35 Microsoft SQL Server database 36 Recovery Storage Group (RSG) 3 Remote Recovery 5 Replication ID 31, 35 Requirements Exchange Server 4 IPStor Server 27 Lotus Notes Server 27 Supported platforms 57 System 27, 57 Rescan timeout 76, 80 Resolve host name 64 Resolve the host name. 43 Rollback TimeMark Restore 53, 54 RSG Create 7 Delete 21 Manual recovery 23 Recovery wizard 6, 15 S Script directory 61 Scripts 56 Batch 77 Device mapping 69 Single backup image 24, 25 Snapshot 2, 56, 71 Quiescent 56 Snapshot Agent 2, 36 Snapshot Group 2 Snapshot notification 56 SSG Mount SSG Single Backup Image 23 Start/stop Exchange 23 STM database 4 Storage Server Revcovery Agents User Guide ii

94 Index Adding 40 Deleting 42 Properties 43 Storage servers Add 62 Add credentials 66 Advanced Fibre Channel settings 64 Advanced iscsi settings 63 Authentication 66 Delete 67 Establish connection 62 Properties 65 Protocols 63 Resolve host name 64 Server name 63 User name 63 Windows Domain Authentication 63 Supported platforms 57 System requirements 27, 57 System settings 29 Change 29 T Terminology 2, 56 TimeMark 2, 37, 56, 71 TimeMark Restore 52, 55 TimeView 2, 56 Cleanup 33 Trace information 76, 80 Trace log 22, 29, 34, 47 U User Log 47 W Windows Advanced Fibre Channel settings 42 Advanced iscsi settings 42 Authentication 58 Console Red line 40 X X-ray 87 Revcovery Agents User Guide iii