IBM SmartCloud Virtualized Server Recovery Customer User Guide Version 2, Release 1 SC27-4303-03
IBM SmartCloud Virtualized Server Recovery Customer User Guide Version 2, Release 1 SC27-4303-03
Notice Before using this information and the product it supports, read the information in “Notices” on page 87. First Edition (May 2014) This edition applies to version 2, release 1 of IBM SmartCloud Virtualized Server Recovery (product number 6948-16D) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents Figures . . . . . . . . . . . . . . . v Tables . . . . . . . . . . . . . . . vii Recovering a Reserved Resource Virtual Machine Service Level System . . . . . . . . . . Recovering a Reserved Resource Server . . . . 38 . 39 Changes from IBM SmartCloud VSR, 2.0 to 2.1. . . . . . . . . . . . . . . . ix Appendix A. Frequently Asked Questions . . . . . . . . . . . . . 41 Chapter 1. Introduction . . . . . . . . 1 Appendix B. Troubleshooting: Warning and Error Messages . . . . . . . . .
iv IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. IBM SmartCloud VSR High-Level Schematic VSR Bandwidth Estimator . . . . . . . Bandwidth Calculated . . . . . . . . VSR Web Portal Login . . . . . . . . Reset Password Prompt . . . . . . . Password Reset Not Possible, Contact POD Admin . . . . . . . . . . . . . VSR Management . . . . . . . . . VSR Version (Sample) . . . . . . . . File Downloads . . . . . . . . . . File Utilities . . . . . . . . . . .
vi IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Tables 1. 2. 3. Standard VSR User Account Types by Function 1 Downloads: Windows, Red Hat 5, Cent OS 5 and OEL 5 (Standard Kernel) . . . . . . 19 Downloads: Red Hat 6, Cent OS 6 and OEL 6 (Standard Kernel), Oracle 5/6 Enterprise Linux (Kernel 2.6.39). . . . . . . . . . . . 20 © Copyright IBM Corp. 2014 4. 5. 6. 7. Downloads: SUSE 11, AIX. . . . File Utilities . . . . . . . . Site Option Settings . . . . . . Disaster Recovery Method Options. . . . . . . . . . . . . . . . .
viii IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Changes from IBM SmartCloud VSR, 2.0 to 2.1 Changes to VSR from VSR 2.0 to 2.1 are described in the following categories: v “Major Core System Features and Changes” v “User Interface Features” v “Software Bug Fixes” Major Core System Features and Changes 1. The AIX interface has been significantly improved as follows: v DR Testing/Live Recovery can now automatically create an LPAR for itself. Restriction: VSR customers must not name their LPARs using all of the characters allowed.
x IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Chapter 1. Introduction IBM® SmartCloud Virtualized Server Recovery (VSR) is the unique business continuity solution that protects critical Windows-, AIX®-, and Linux-based servers in real time. VSR protection allows an entire business server, its operating system, installed applications and other software components, to be quickly recovered and hosted from an IBM Recovery Center. About this Document This document is the IBM SmartCloud Virtualized Server Recovery Customer Administrator Guide.
Table 1. Standard VSR User Account Types by Function (continued) Maintenance Account User Restricted User User can access Downloads U U U User can access Reports U U U User can edit Site Options U X X Category Function Reporting System Cred Service Description A high-level description of the IBM SmartCloud VSR service follows in this section. Figure 1. IBM SmartCloud VSR High-Level Schematic Customers connect to IBM BCRS with their own network structures.
Over the network, customers can access the VSR portal. From the portal, customers can utilize their VSR solution. The VSR customer in the user role or the IBM system administrator (acting in the customer's behalf) can perform Recoveries. See “Logging in to the VSR Web Portal” on page 13. Service Levels IBM offers three service levels of the IBM SmartCloud VSR.
Setup This procedure applies only to the Shared Resource Virtual Machine and Reserved Resource Virtual Machine service level offerings. After signing the contract, the IBM VSR Customer performs the following tasks: Before you begin IBM SmartCloud Virtualized Server Recovery has the following prerequisites: v See: “Supported Operating Systems” on page 11. v See: “Supported Internet Browsers” on page 11.
Before you begin Optionally, before embarking on replication, calculate the following estimates: 1. The time duration required for replication to complete 2. The percentage of your bandwidth that VSR consumes during ongoing replication. Use the IBM Bandwidth & Replication requirement estimation tool to make these calculations: See IBM Synchronization and Bandwidth Estimator. http://www-935.ibm.
3. VSR presents the following pop-up message: Important: This action will place live machines onto your network with the same networking configuration as your original systems. Please confirm: is this the action you wish to perform? The options are OK to confirm the recovery and Cancel to abort the request. 4. After the customer clicks OK on the pop-up message, the customer's recovery begins. a. The VSR system suspends the customer's replication. b.
When using a Layer 2 extension, the recovery server is, practically speaking, on the same LAN as the source. And this presents a dilemma: if you place two machines with the same IP address on the same LAN, neither functions properly. To avoid this collision of IP addresses, VSR powers off the recovery server, then boots the production server.
Estimating the Bandwidth Required for VSR Service IBM SmartCloud VSR bandwidth requirements differ for each partner, based on various aspects. The bandwidth made available for disaster recovery must address existing bandwidth available, network resource type, user activity, as well as unique disaster recovery strategy requirements. About this task The IBM SmartCloud VSR Bandwidth Estimator is provided at no charge and without any guarantees. Actual results may vary.
current environment in the course of a day hour, minute, or second. The value is expressed in terabytes, gigabytes, megabytes, or kilobytes. Gross bandwidth available for replication Indicate one of the following network types available for replication activity: DS1/T1 Digital service hierarchy level 1 network, offering up to a maximum channel capacity of 1.544 Mb/s. DS2 Digital service hierarchy level 2 network. Offering one 6.
Figure 3. Bandwidth Calculated 2. Click the button labeled Calculate. Results Time to complete first replication The calculated result shown in hours. This is the estimated amount of time that VSR requires to replicate all of your data to the IBM Recovery Center. Your data must be fully replicated before VSR can recover your servers. Network bandwidth required to maintain synchronization The calculated result shown as a percentage.
IBM pSeries servers Implementations of the IBM SmartCloud Virtualized Server Recovery VSR Replication Client are tested for use with IBM pSeries servers. Note: For additional information, see Chapter 3, “Downloads and Utilities,” on page 17.
12 IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Chapter 2. Reaching the VSR Web Portal Your local IBM BCRS representative supplies you with a UserID, password, and the URL for the VSR portal. Access the VSR Web Portal using any of the “Supported Internet Browsers” on page 11 with which it has been extensively tested. VSR Web Portals are hosted at URLs using the following naming convention: XXnn-vsr.bcrs-vaults.ibm.com XX Represents the applicable two-letter country code.
credentials are valid entries, the VSR Web Portal grants the user access and loads. Depending on the POD (Point of Delivery) used, Selectable languages include the following: v English v Japanese v German v Simplified Chinese v French v Korean v Italian v Hindi v Spanish v Portuguese (Brazil) v Portuguese (Portugal) Note: a. If the user leaves the VSR portal open without any action performed for twenty (20) minutes, the session times out.
Figure 6. Password Reset Not Possible, Contact POD Admin c. VSR emails your new password to the address you provided. If either the email address or your answer to the Secret question is missing or incorrect, VSR does not send email to you containing your new password. In either case, VSR returns a message similar to that communicated in Figure 6. Accordingly, contact your local IBM BCRS VSR administrator for assistance. Figure 7. VSR Management 3. The VSR Web Portal displays Figure 7.
Recovery functionality is accessible from this pane for either a Server Group or Server. This provides for speed of usage during an actual failover invocation. Initially, the VSR Replication Portal presents no sites or servers in your tree view. This is because they have not yet been added to the system. Note: Icon Meaning The silver server icon in the tree view indicates a server protected at the Shared Resource Virtual Machine service level.
Chapter 3. Downloads and Utilities There are installable VSR Replication Client software packages, documentation, and failback ISO images associated with the VSR service. You can download any of these items from the VSR main menu's File Downloads page by clicking Downloads. Identify the applicable release-dependent documentation containing detailed instructions for installing the VSR Replication Client and the correct Replication Client Installer by its VSR release and OS.
Figure 9.
Figure 10. File Utilities The following files, documents, and images are available for download: Table 2.
Table 3. Downloads: Red Hat 6, Cent OS 6 and OEL 6 (Standard Kernel), Oracle 5/6 Enterprise Linux (Kernel 2.6.39) Downloads OS Replication Client Installers User Guide Documents (PDF format) ISO Images 32-bit Replication Client Installer (Standard Kernel) Red Hat 6 Cent OS 6 OEL 6 Std Kernel Download 32-bit Replication Client Installer 64-bit Replication Client Installer (Standard Kernel) Download 64-bit Replication Client Installer 32-bit Replication Client Installer (Kernel 2.6.
Table 4. Downloads: SUSE 11, AIX Downloads OS User Guide Documents (PDF format) Replication Client Installers ISO Images 64-bit Replication Client Installer (SUSE11 SP1) SUSE 11 Download 64-bit Replication Client InstallerDownload 32-bit Replication Client Installer 64-bit Replication Client Installer (SUSE11 SP2) AIX 5.2/5.3 Replication Client Installer Download AIX 5.2/5.3 Replication Client Installer See IBM SmartCloud Virtualized Server Recovery: User Guide. Failback ISO Images AIX 6.
Software Prerequisites There are no prerequisites for installing the VSR Replication Client onto a server. It runs without any external libraries or applications on all VSR-supported versions of Windows and Linux. It is important that your subscribed server is able to establish a transmission control protocol/internet protocol (TCP/IP) connection to the IBM SmartCloud solution. See your IBM System Administrator for information about establishing the necessary connection.
Chapter 4. DR Test, Verify, Report, Cleanup, and Recover Cycle This section summarizes the process through which VSR cycles through disaster recovery testing, verification, reporting, cleanup, and recovery. 1. Perform the Disaster Recovery Test. 2. Verify that the Disaster Recovery Test completed successfully. v Feedback is relatively immediate when you perform a Disaster Recovery Test for the particular case at hand.
24 IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Chapter 5. Setting Site Options and Server Groups Use this section to edit the credentials of sites to which you have access under VSR protection. About this task To adjust Site Option Settings: 1. Click the Settings > Site Options buttons in the left column of the screen. 2. Use the drop-down button in the Site: field and click the button labeled Select Site. Figure 11. Site Options Site Selection 3.
Procedure 1. Complete the Site Options, Site Groups section as follows: In the Site Groups section groups can be added and removed as required. The use of groups allows tasks to be performed on all group members. Figure 13. Site Options, Site Groups 2. Complete the Site Options, Group Mappings section as follows: Using the Group Mappings section, you are able to select a group for each protected server. Figure 14. Site Options, Group Mappings 3.
In the Notification Emails section addresses can be added and removed as required. Addresses entered will receive emails alerting them of events and changes made on this site. Figure 16. Site Options, Notification Emails 5. Click the Save Configuration button to save and implement the settings recorded. Chapter 5.
28 IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Chapter 6. Accessing System Statistics The VSR Management selection facilitates access to customer statistics. About this task Click VSR Management > Statistics on the VSR main menu to access statistics of the following types: v Customer Statistics: – Site Specific SAN Statistics: (See step 1) – Server Statistics: (See step 2 on page 30) – Replication History (RPO) Statistics: (See step 3 on page 31) Figure 17. VSR Statistics The interface is illustrated in Figure 17. Procedure 1.
Figure 18. VSR SAN Statistics v As required, on the subsequent screen, click the drop-down arrow associated with the Site: field to change the target site. v Click the button labeled Apply Filter to produce a report analogous to that illustrated in Figure 18. v Alternately, click Back to Statistics Selection to return to Figure 17 on page 29. Figure 19. Customer Statistics: Server Statistics 2.
Figure 20. VSR Server Statistics v As required, on the subsequent screen, click either drop-down arrow associated with the Site: or System Type: fields to change the target site or system type. v Click the button labeled Apply to produce a report analogous to that illustrated in Figure 20. v Alternately, click Back to Statistics Selection to return to Figure 17 on page 29. 3.
Figure 21. VSR Replication History (RPO) Statistics v Click the button labeled Show Statistics to produce a report analogous to that illustrated in Figure 21. 4. Click VSR Management > Statistics in the VSR main menu to return to Figure 17 on page 29.
Chapter 7. Performing a Disaster Recovery When an interruption or disaster affects one or more of your critical systems, use the VSR service. It creates a virtual machine in the VSR solution infrastructure that effectively behaves and operates precisely as the original. This process is called recovery. Before you begin Perform disaster recovery only after you conduct testing and it has ended successfully, completed verification, and any required cleanup.
Figure 22. Live Server Recovery 3. Complete the filter, as required. For each site listed in detail, a combination of either of the following mutually exclusive text statement types appear, as warranted. When Live Recovery is possible... When Live Recovery is not possible...
v The silver server icon ( ) in the tree view indicates a server protected at the Shared Resource Virtual Machine service level. 5. Click the down arrow associated with the Point In Time and make a selection. There are two basic options: Realtime Target Volume a. Default option. To recover your server to the most recent possible working condition, click the down arrow associated with the Point In Time drop-down menu. Then, select Realtime Target Volume.
taken before an incident occurred. Each represents a snapshot of the main volume for that server on a different date, at a different time. The Shared Resource Virtual Machine service level stores 24 such snapshots daily while the Reserved Resource Virtual Machine service level stores 96 daily. (No PIT Data Loaded For Server) VSR displays this option when there is no PIT data loaded for the server to recover. The Realtime Target Volume is the only option in such cases.
7. When the VSR Replication Client completes the recovery, the following screen displays: Figure 26. Live Server Recovery, Completed Essentially, the same following screen displays for Linux systems when the VSR Replication Client completes the recovery. Figure 27. Live Server Recovery, Linux Completed When you see this screen, the VSR Replication Client is finished creating your server as a virtual machine in the VSR environment.
2. Periodic Disaster Recovery Testing follows that cleanup. For more information, see: v Chapter 4, “DR Test, Verify, Report, Cleanup, and Recover Cycle,” on page 23 3. As required: Perform a Failback. Recovering a Server Group Servers that are grouped can be recovered as a group. Before you begin v Review information about creating a group. v Recovery follows successful testing, test reporting, verification, and cleanup. See Chapter 4, “DR Test, Verify, Report, Cleanup, and Recover Cycle,” on page 23.
When upgraded from Shared Resource Virtual Machine service level, servers covered under Reserved Resource Virtual Machine service offer options and benefits. This recovery method is the only method associated with the Reserved Resource Virtual Machine service level. Recovering a Reserved Resource Server Recovery at the Reserved Resource Virtual Machine service level in this manner is similar to recovery at the Shared Resource Virtual Machine service level.
Figure 29. Reserved Resource Server, Live Recovery Note: For details on selecting a particular point in time when recovering a server protected at the Reserved Resource Service Level, see Chapter 7, “Performing a Disaster Recovery,” on page 33, Figure 23 on page 35, 4. Recovery proceeds in a manner similar to Chapter 7, “Performing a Disaster Recovery,” on page 33. What to do next 1. Manual cleanup of the system following a VSR Disaster Recovery is imperative.
Appendix A. Frequently Asked Questions 1. How much CPU resource does the VSR replication software client consume? From 1 to 3 percent. This is significantly better than other replication client software CPU resource consumption. 2.
6. How does the VSR system communicate with a customer's servers? There are two communications channels between a customer's sites and IBM's VSR infrastructure. The first is the replication connection, which is an OSI Layer 3 connection maintained by the replication software. The second is the OSI Layer 2 LAN extension used during failovers to enable customers' users to connect with IBM's recovery servers. Both channels may be encrypted at the customer's option. 7.
10. My company uses a version of Windows that is tied to and came bundled with hardware. Do I need a separate Windows license when failing over to the IBM recovery system? The likely answer is "yes". Ask your software provider for definitive answers. According to the IBM SOW, software license costs are solely the responsibility of VSR customers. 11. Does VSR support 32-bit RHEL? Yes, VSR supports 32-bit RHEL as of VSR v1.6. Appendix A.
44 IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Appendix B. Troubleshooting: Warning and Error Messages IBM SmartCloud Virtualized Server Recovery issues a number of informational, warning, and error messages. 1. During Automatic Configuration of a new system the Failed to communicate with server message is displayed. Probable Cause 1: The Replication agent is not installed on the system for Auto Configuration. Probable Solution 1: Install the Replication agent. Probable Cause 2: The Replication agent is installed but the services are not started.
2. Internet browser ... cannot display the web page. Probable Cause: You are entering an incorrect URL. Probable Solution: Enter the correct URL. If the issue persists contact your IBM Support representative. 3. Server Name Does not Display in the Recovery Screen under VSR Management. Probable Cause 1: Your user account does not have the correct privilege to view the server.
Probable Solution 1: Login with a user account that has the appropriate permissions. Probable Cause 2: Your server is not protected. Probable Solution 2: The system requires protection. Contact your IBM Support representative to confirm your contractual agreement. 4. SocketException: A connection attempt failed because... ...the connected party did not properly respond after a period of time, or established connection failed because connected host failed to respond nn.nnn.nn.
Probable Cause: The user ID being used is logged in using another session. Probable Solution: Wait for the session to time-out. The default time before an abandoned session times out is 20 minutes. 6. VSR Portal login page displays Username/Password invalid. Probable Cause: Username or password is incorrect. Probable Solution: Confirm that the caps lock is in the correct state, that you have the correct username, and that you are typing the correct case-sensitive password.
8. Failed to Connect to Remote Server. Probable Cause: The web portal is unable to connect to the VSR system or the system is unable to connect to its main database. Probable Solution: Wait for the VSR system or the main database to come back online. 9. Your session has timed out. Probable Cause: The VSR portal was left open without any action for 20 minutes. Probable Solution: Click the Login button to access the portal again. Appendix B.
50 IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Appendix C. Failback in Detail This detail of the failback procedure proceeds from redirection located in a previous chapter. About this task See “Failback” on page 6 for steps preceding those detailed in this appendix. Procedure 1. Proceeding from “Failback” on page 6, step 6 on page 7, VSR presents Figure 30. Figure 30. Intel PRO/1000 MT Connection Found 2. As illustrated in Figure 31 on page 52, use the radio buttons to select the appropriate failback OS type: Windows or Linux. © Copyright IBM Corp.
Figure 31. Select Windows or Linux OS Note: When Linux is selected, and Set IP is pushed, diskpart runs and clears the existing volumes. 3. Click the button labeled Set IP Address Manually as illustrated in Figure 31. Set a static IP address. VSR requires a static IP address to add to the NAT table in order to perform failback.
Figure 32. Obtain an IP Address Automatically 4. As illustrated in Figure 32, click the button labeled Obtain an IP address automatically to toggle to the static entry. Appendix C.
Figure 33. Specify and Customer Failback Address 5. As illustrated in Figure 33, input an address for the customer failback network on the IP Settings tab, click Apply, then click OK.
Figure 34. Identify IP 6. Click the button labeled Identify IP as illustrated in Figure 34. If the IP address you entered does not appear, click Next. If it still does not appear, return to set address and verify the entry. Then, click OK and then Next, again, on this screen. 7. In the empty field below Identify IP, enter the NAT address for the failback. This is the address that the replication server requires in order to locate the failback disks presented as iSCSI. Appendix C.
Figure 35. Set Partitions 8. Click the button labeled Set. When ready, click Set Partitions as illustrated in Figure 35. You do not need to Enable iSCSI disks. This occurs automatically. The button labeled Enable iSCSI disks is intended for manual troubleshooting.
Figure 36. Initialize the disk 9. Once the partition manager appears, initialize the disk(s). To do so, make your selection from the menu and click OK as illustrated in Figure 36. Appendix C.
Figure 37. All disk(s) must be equal to or larger than the original being failed back 10. All disk(s) must be equal to or larger than the original source disk that is being failed back. For Linux, you can exit the window now. The disk only needs to be initialized.
Figure 38. Windows: Create a simple volume 11. For Windows, create a simple volume. To do so, click New Simple Volume... on the menu illustrated in Figure 38. Appendix C.
Figure 39. New Simple Volume Wizard 12. This launches a New Simple Volume Wizard as illustrated in Figure 39. Click Next.
Figure 40. Set size to match the partition 13. Set the size to match the partition in the field labeled Simple volume size in MB: as illustrated in Figure 40. Appendix C.
Figure 41. Not necessary to assign a drive 14. On the next screen, illustrated in Figure 41, it is not necessary to assign the drive. Click Next.
Figure 42. Not necessary to format disk 15. The disk does not need to be formatted on the subsequent screen illustrated in Figure 42. Click Next. Appendix C.
Figure 43. Complete New Simple Volume Wizard 16. Click Finish as illustrated in Figure 43 to complete the New Simple Volume Wizard.
Figure 44. Close Disk Management Window 17. Close the Disk Management window. Appendix C.
Figure 45. Start Failback 18. Click the button labeled Start Failback on the screen illustrated in Figure 45.
Figure 46. Return to portal and initiate failback 19. As illustrated in Figure 46, once prompted, return to the portal and initiate failback. Appendix C.
Figure 47. Stop Failback 20. Failback runs. 21. Once completed, when you log into the portal VSR informs you by prompt that failback is ready to be completed. 22. Click the button in the VSR portal to complete failback. Once VSR indicates that failback is complete, return to the booted ISO. Note: Do not click Stop Failback as illustrated in Figure 47 until you complete step 22. 23. After you choose to complete failback in the VSR portal, click Stop Failback.
Figure 48. Complete Failback Note: If failing back to dissimilar hardware where a special driver (RAID or NIC) needs to be injected before restarting, click the Import Driver button, and follow that process. 24. Click Complete Failback as illustrated in Figure 48. This initializes the disks, and sets the bootable volume. 25. Once the completion step finishes, remove or dismount the CD, and then click Reboot. Appendix C.
Figure 49. Reboot Now 26. When these actions complete successfully, the failed back system boots to the OS. 27. Disconnect the failed over system from the network at this time to avoid an IP conflict.
Appendix D. Accessibility Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use software products successfully.
72 IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Glossary The terms in this glossary are defined as they pertain to IBM SmartCloud Virtualized Server Recovery documentation. If you do not find the term you need, refer to the IBM Software Glossary on the Web at this address: http://www.ibm.com/ibm/terminology/. You can also refer to the IBM Dictionary of Computing, New York: McGraw-Hill, 1994. Numerics 10 Gb/s LAN. Local Area Network, offering up to a maximum channel capacity of 10 Gb/s. 100 Gb/s LAN.
cluster. A group of computers, linked and working together to form, in some respects, a single computer. The components of a cluster are usually connected to each other through fast local area networks. Clusters are usually deployed to achieve better performance, availability, and cost efficiency than a single computer of comparable speed or availability. Cluster - Configuration File Creator.
D – Add Volumes to an Existing Server – Configure Grouped Systems – Protect a Microsoft Windows 2008 Cluster – Configure a Microsoft Windows 2008 Cluster v Create a Reserved Resource Server v Create a Reserved Resource Server Group v Perform a Disaster Recovery Test v Manage Disaster Recovery Test Machines v Test an Reserved Resource Server v Test a VSR Server Group v Report Disaster Recovery Test Results – Run a Report – Set Report Schedules v Perform a Disaster Recovery v Recover a Server Group v Recover
E • H Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators centrally manage and automate the assignment of Internet Protocol (IP) addresses in an organization's network. Using the Internet Protocol, each machine that can connect to the Internet needs a unique IP address, which is assigned when an Internet connection is created for a specific computer.
I • M Hypertext Transfer Protocol (HTTP). A networking protocol for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web. Hypertext Transfer Protocol Secure (HTTPS). A combination of the Hypertext Transfer Protocol (HTTP) with SSL/TLS protocol to provide encrypted communication and secure identification of a network web server.
N • R Master Boot Record (MBR). The very first section of data on the hard drive. It holds the start up program and information about each primary or extended partition on that drive. It also has a flag to indicate if a partition is active/bootable. MBR. See Master Boot Record (MBR). Microsoft Cluster Server (MSCS).
S Recovery point objective (RPO). The acceptable amount of data loss measured in time. The recovery point objective is the point in time to which you must recover data as defined by your organization. Recovery time objective (RTO). Recovery time objective (RTO). The maximum tolerable length of time that a computer, system, network, or application can typically be down (until system boot start) after a failure or disaster occurs.
SAN. See storage area network (SAN). scheduled report. A report that comes out at a predetermined time. scorecard grid. A system used to mark areas to be replicated when a disrupted network is later restored. Secure Sockets Layer (SSL). A cryptographic protocol that provides communication security over the Internet. It encrypts the segments of network connections above the Transport Layer, using asymmetric cryptography for privacy and a keyed message authentication code for message reliability.
T • V Synchronization & Bandwidth Estimator. A tool that allows the IBM SmartCloud VSR customer to plan bandwidth requirements based on existing bandwidth available, network resource type, end user activity, and unique disaster recovery strategy requirements. T T1. Data transfer system that transfers digital signals at 1.544 megabits per second. See Digital Signal 1. T3. See level 3 T-carrier. TLS. See Transport Layer Security (TLS). Tivoli® Service Request Manager® (SRM).
W • X represents. In most virtual storage systems a metadata mapping table is held which translates the incoming (virtual) disk identifier, and LBA (logical block addressing) to a physical disk identifier and LBA. Virtual Machine (VM). A tightly isolated software container that can run its own operating systems and applications as if it were a physical computer.
Index Numerics Business Continuity and Resiliency Services (BCRS) 2 Business Continuity Resiliency Services (BCRS) 73 10 Gb/s LAN 9, 73 100 Gb/s LAN 73 100 Mb/s LAN 9 20 minute session 14 32-bit Windows 2003 22 Windows 2008 22 32-bit RHEL support 43 32-bit VSR Replication Client 17 64-bit Red Hat Enterprise Linux 22 Windows 2003 22 Windows 2008 22 64-bit VSR Replication Client 17 C calculate bandwidth requirement 10 cannot display the web page 45 CentOS 11 change screen settings 71 changes for time unit,
G K GeoTrust certificate 76 German language 14 Germany 14 global site license arrangement Gold-Level server recovery 38 gold-level server recovery 76 Google Chrome 11, 13 graphical user interfaces 71 guest OS 76 GUI 71 Korea 14 Korean language 41 H hardware 10 hardware bundled with Windows 43 Hindi language 14 how VSR works 3, 4 HTML 76 HTML format 71 HTTP 76 HTTPS 76 Hypertext Markup Language (HTML) 76 Hypertext Transfer Protocol (HTTP) 77 Hypertext Transfer Protocol Secure (HTTPS) 77 hypervisor 77 I
recovery time objective 3 Recovery time objective (RTO) 79 Red Hat Enterprise Linux (RHEL) 79 Red Hat Enterprise Linux 4 64-bit 11 Red Hat Enterprise Linux 5 64-bit 11 Red Hat Replication Client 17 replication 2, 5 replication agent 79 replication client 17, 79 replication ensemble 79 replication server 79 replication servers 2 replication suspended 6 report DR test results 23 reporting 2 reports 2 reserved resource 13 reserved resource server 38 reserved resource server, initiating 38 reserved resource ser
web-based front end 1 who should use this document 1 Windows 2008 recovery fails 48 Windows bundled with hardware 43 Windows cluster 82 Windows OEM 11 Windows Replication Client 17 Windows Server 2003 11 32-bit version 11 64-bit version 11 Windows Server 2008 11 Windows Server 2008 R2 32-bit version 11 64-bit version 11 Windows Server 2012 11 Windows Storage Server 11 X XML 86 82 IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
90 IBM SmartCloud Virtualized Server Recovery: Customer User Guide
Product Number: 6948-16D Printed in USA SC27-4303-03
