HP P6000 EVA Storage Replication Adapter Software for VMware vCenter SRM version 5.0 Administrator Guide This document provides information about the HP P6000 EVA Storage Adapter Software for VMware vCenter SRM version 5.0, requirements and procedures for installing it, and information for configuring the software. This document is intended for system administrators with knowledge of host hardware, HP P6000/EVA disk arrays, and the VMware Site Recovery Manager (SRM).
Legal and notice information © Copyright 2008, 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview of HP P6000 EVA SRA Software version 5.0 ........................... 7 Discovery of disk arrays and LUNs ................................................................................................ 7 Disk array discovery sequence ............................................................................................... 8 LUN discovery sequence ....................................................................................................... 8 Failover testing ..............
If the protected site has crashed and protected virtual machines fail to recover at the target site .......... Error messages ......................................................................................................................... SRM log .................................................................................................................................. SRA logs ....................................................................................................................
Figures 1 Discover arrays ......................................................................................................... 8 2 Discovery of replicated consistency groups/devices between an array pair ...................... 9 3 Using snapshots for recovery test .............................................................................. 10 4 HP P6000 EVA SRA Software version 5.0 architecture ................................................. 11 5 SRM zone ...........................................
Tables 1 HP P6000 EVA SRA Software version 5.0 error and warning messages ......................... 37 2 Document conventions .............................................................................................
1 Overview of HP P6000 EVA SRA Software version 5.0 HP P6000 EVA SRA Software version 5.0 is a Storage Replication Adapter (SRA) for use with VMware Site Recovery Manager (SRM). The SRA, developed by HP for P6000 and P6000/EVA storage arrays, enables SRM to work with HP P6000 Continuous Access Software array-based replication. HP P6000 EVA SRA Software version 5.
Remote vdisks are members of HP P6000 EVA storage systems and HP P6000/EVA data replication groups, and are replicated between protected and recovery HP P6000 EVA storage systems and HP P6000/EVAs using HP P6000 Continuous Access Software. Disk array discovery sequence Once the array manager has been added and configured from within VMware SRM, SRM calls the adapter to discover the arrays configured for with the SRA. SRM periodically calls the SRA to refresh array information.
3. 4. Data Replication Group information, including vdisk member information is discovered. For each replicated vdisk found on the protected array, HP P6000 EVA SRA Software version 5.0 gathers the following information: • Remote array ID • Remote vdisk name • Local presentation information • Host the LUN is presented to locally • ID assigned to host 5. 6. HP P6000 EVA SRA Software version 5.0 returns this information to SRM.
Figure 3 Using snapshots for recovery test . Failover recovery 1. During recovery plan execution, when SRM reaches the Prepare Storage step, the plan provides the HP P6000 EVA SRA Software version 5.0 with the DR Group and LUN information needed for failover. The information includes: • Recovery site storage array ID • DR group ID • Vdisk name • Recovery ESX server HBA ports (WWNs) for post-failover LUN presentation 2. HP P6000 EVA SRA Software version 5.
When Site Recovery Manager makes a request to HP P6000 EVA SRA Software version 5.0, the SRA communicates through the Storage Administration Portal for all operation.
Overview of HP P6000 EVA SRA Software version 5.
2 Configuring SRM, HP P6000/EVA, and HP P6000 EVA SRA Software version 5.0 This chapter summarizes the steps to set up SRM and HP P6000 EVA and HP P6000/EVA disk array for use with HP P6000 EVA SRA Software version 5.0. For detailed information on these steps, see the documents listed in Related information. Complete the following steps: 1. Set up P6000/EVA SAN environment with local and intersite link (ISL) zoning configurations. 2. Install HP P6000 EVA SRA Software version 5.0. 3.
• • • • Install licenses for HP P6000 Continuous Access Software and HP P6000 Business Copy Software Create vdisks for replicated datastores and RDMs. Add vdisks to data replication groups on the array. Create datastores using VMware vCenter.
NOTE: Snapclones, mirrorclones, and the ability to choose different disk group for clones are not currently supported with SRM or HP P6000 EVA SRA Software version 5.0. Creating vdisks for datastores You must create HP P6000 EVA virtual disks (vdisks) for VMware ESX datastores and raw device mappings (RDM). Create the vdisks on the protected HP P6000/EVA disk array, using HP P6000 Command View Software or HP Storage System Scripting Utility (SSSU) Command Line Interface.
Configuring array managers with HP Storage Administration Portal After installing HP P6000 EVA SRA Software version 5.0 on both SRA servers (protected site and recovery site), the installed SRA component, HP P6000 EVA SRA Software version 5.0 Storage Admin Portal must be configured at both sites.
1. Launch Storage Admin Portal from the Windows Start menu: Start > All Programs > Hewlett-Packard > HP P6000 EVA Storage Replication Adapter Software for VMware vCenter SRM version 5.0 -Storage Admin Portal > HP P6000 EVA Storage Replication Adapter Software for VMware vCenter SRM version 5.0 -Storage Admin Portal Figure 7 Storage Admin Portal . Login Name is admin and the password used to log in to Storage Administration Portal is the one set during SRA installation.
Figure 8 Launch Storage Admin Portal via web browser . 2. Once logged in, add an array manager from the main page by clicking the Add button on the left. Figure 9 Add an array manager . 18 Configuring SRM, HP P6000/EVA, and HP P6000 EVA SRA Software version 5.
3. Select HP P6000 Command View Software for the type of array management server and click Next. Figure 10 Select type of array management server . 4. Enter the HP P6000 Command View Software address and login credentials for the HP P6000 Command View Software used in your SRM environment. Typically you will configure two HP P6000 Command View Software servers (one per site). Figure 11 Enter HP P6000 Command View Software address .
5. Select both local and remote storage arrays being used in your SRM environment and click Finish. Figure 12 Select storage arrays . 6. 20 Repeat steps 2 through 5 and add the second array manager to the Storage Administration Portal. Configuring SRM, HP P6000/EVA, and HP P6000 EVA SRA Software version 5.
7. Repeat steps 1 through 6 on the second SRM server located in the other site. Note that the password for HP P6000 EVA SRA Software version 5.0 -Storage Admin Portal can be changed by running the Password Management Utility that is installed with the adapter. The Password Management Utility can be launched from the Windows Start menu: Start > All Programs > Hewlett-Packard > HP P6000 EVA Storage Replication Adapter Software for VMware vCenter SRM version 5.
2. Right-click the place holder for the protected site and select Add Array Manager to initiate the SRM array manager configuration wizard (see Figure 15). Figure 14 SRAs tab . Figure 15 Add Array Manager . 22 Configuring SRM, HP P6000/EVA, and HP P6000 EVA SRA Software version 5.
3. Make sure that the array manager type HP P6000 EVA Replication Adapter for VMware Site Recovery Manager appears in the SRA Type drop-down field and select it (see Figure 16). Figure 16 SRA type . HP P6000 EVA Storage Replication Adapter Software for VMware vCenter SRM version 5.
4. Enter HP P6000 EVA SRA Software version 5.0 connection parameters for the protected site.The IP address is the location where the Storage Administration Portal is configured, which is typically the same IP as the protected SRM server (see Figure 17). Figure 17 Enter IP address . 24 Configuring SRM, HP P6000/EVA, and HP P6000 EVA SRA Software version 5.
5. Once the SRA is successfully configured at the protected site, the configuration summary can be reviewed using the SRM GUI (see Figure 18). Figure 18 Review configuration summary . Create protection groups Protection groups (containing replicated virtual machines) fail over the storage and VMs to the recovery site during test and recovery. To create protection groups, follow the instructions in the VMware Site Recovery Manager Administration Guide.
Configuring SRM, HP P6000/EVA, and HP P6000 EVA SRA Software version 5.
3 Installing and removing HP P6000 EVA SRA Software version 5.0 This chapter explains how to install and configure HP P6000 EVA SRA Software version 5.0. IMPORTANT: A successful installation depends on using compatible versions of the OS and all installed software. For version requirements, see HP P6000 EVA SRA Software version 5.0 Release Notes. NOTE: If a version of the adapter earlier than 5.0 is installed, it must be uninstalled before installing the one described in this guide.
1. Download HP P6000 EVA SRA Software version 5.0 installation file from the HP web page (http://www.hp.com/go/storage/vmware) and save it in a temporary folder. 2. Browse to the temporary folder and extract HP P6000 EVA SRA Software version 5.0 installation files. 3. After the files are extracted, click HP P6000 Replication Adapter for VMware Site Recovery Manager.exe to start the installation. The installer window appears (see Figure 19). Figure 19 SRA installer . 4. Click Next.
10. Once the installer has finished, click Done to complete installation of the SRA. NOTE: After this step, an option will be available to view the release notes. NOTE: For SRM to detect the newly installed SRA, click Rescan SRAs in the SRA GUI under the SRAs tab within the Array Managers screen. Verifying the installation After HP P6000 EVA SRA Software version 5.0 is installed, it appears in the Windows Add or Remove Programs window. Figure 20 Verify installation .
Installing and removing HP P6000 EVA SRA Software version 5.
4 Recovery and failback Recovery Recovery occurs when an SRM recovery plan is configured with SRM protection groups that use replicated EVA/P6000 vdisks as a datastore is executed. A recovery plan can be used for DR or planned migration of VM between data centers. During normal operation, the replication path is from a protected site (local site) to a recovery site (remote site).
Recovery and failback
5 Troubleshooting HP P6000 EVA SRA Software version 5.0 NOTE: Error messages are logged to the SRM log files. The following problems and solutions are typical. HP P6000 EVA SRA Software version 5.0 does not install Solution: Make sure that SRM is installed. Ensure Windows User Account Controll (UAC) is switched off. Virtual machines do not start at recovery site after failover Causes: • The ESX recovery hosts are not configured with the correct HBA port WWN on the recovery P6000/EVA.
SRM environment is healthy, yet HP P6000 SRA Software version 5.0 is not operating as expected If HP P6000 Command View Software active management has been switched between management servers after initial Storage Administrator Portal configuration, HP recommends that you click Refresh from the SRM Array Managers window Array Pairs tab and Devices tab.
Figure 21 SRM menu . HP P6000 EVA Storage Replication Adapter Software for VMware vCenter SRM version 5.
Figure 22 Advanced Settings window . If the protected site has crashed and protected virtual machines fail to recover at the target site There may be instances where the Command View management servers have been configured such that the protection site Command View server is actively managing both protection and recovery site arrays (and the recovery site Command View server is passively managing both arrays).
that are present in the DR Group in question. DR Group comments are set and read by the SRA, and it left-over artifacts can confuse SRM. SRM log VMware provides a tool with SRM that gathers all SRM logs and saves them to the desktop. See SRM documentation for more detail. NOTE: • By default, logs roll over after reaching 5 MB. • The most recent Log File number is located in vmware-dr-index. SRA logs HP P6000 EVA SRA Software version 5.
GUI error message Description/corrective action Initialization of CV Client failed using IP address . The address or login credentials to the management host may be incorrect, preventing the adapter from connecting. Initialization of the Element Manager object failed. Connection to the HP P6000 Command View Software host could not be initialized. No test snapshots found.
GUI error message Description/corrective action Device DeviceName is not a member of a known consistency group. Ensure DeviceName is a member of a consistency group. None of the input initiator group IDs match up with any hosts visible to the storage array. Ensure ESX server EsxHostName has been zoned and configured correctly with storage array StorageName. Unpresent of existing snapshot failed. Ensure that snapshot is presented to the host. Delete of existing SRM snapshot failed.
GUI error message Description/corrective action Requested remote array was not found. Check array ID RemoteArrayID sent from SRM, ensure that valid array ID is sent. Requested consistency group was not found. Check consistency group ID ConsistencyGroupID sent from SRM; ensure that valid consistency group ID is sent. Requested target group was not found. Check target group ID TargetGroupID sent from SRM;, ensure that valid target group ID is sent. Requested target group has invalid disk IDs.
6 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
The following book is available on the VMware website: • VMware Site Recovery Manager Administration Guide NOTE: This document does not describe the operation of related products, including HP P6000 Continuous Access Software, HP P6000 Business Copy Software, HP Storage Software Scripting Utility, or VMware Site Recovery Manager. For information about these products, see the respective user guides. HP websites For additional information, see the following HP websites: • • • • http://www.hp.com http://www.
HP product documentation survey Are you the person who installs, maintains, or uses this HP storage product? If so, we would like to know more about your experience using the product documentation. If not, please pass this notice to the person who is responsible for these activities. Our goal is to provide you with documentation that makes our storage hardware and software products easy to install, operate, and maintain.
Support and other resources
A Third-party licenses This section contains licenses for the third-party software that is used in the product. Open Source Initiative OSI - The Artistic License:Licensing (NOTE: This license has been superseded by the Artistic License, Version 2.0.) Some versions of the artistic license contain the following clause: 8.
c) rename any non-standard executables so the names do not conflict with standard executables, which must also be provided, and provide a separate manual page for each non-standard executable that clearly documents how it differs from the Standard Version. d) make other distribution arrangements with the Copyright Holder. 4.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of a such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code.
b) accompany it with a written offer, valid for at least three years, to give any third party free (except for a nominal charge for the cost of distribution) a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Paragraphs 1 and 2 above; or, c) accompany it with the information you received as to where the corresponding source code may be obtained.
DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner.
distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third
or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
of the Copyright Holder as specified below. "Copyright Holder" is whoever is named in the copyright or copyrights for the package. "You" is you, if you're thinking about copying or distributing this Package. "Reasonable copying fee" is whatever you can justify on the basis of media cost, duplication charges, time of people involved, and so on. (You will not be required to justify it to the Copyright Holder, but only to the computing community at large as a market that must bear the fee.
d) make other distribution arrangements with the Copyright Holder. 5. You may charge a reasonable copying fee for any distribution of this Package. You may charge any fee you choose for support of this Package. You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own.
The license agreements of most software companies try to keep users at the mercy of those companies. By contrast, our General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. The General Public License applies to the Free Software Foundation's software and to any other program whose authors commit to using it. You can use it for your programs, too.
1 above, provided that you also do the following: a) cause the modified files to carry prominent notices stating that you changed the files and the date of any change; and b) cause the whole of any work that you distribute or publish, that in whole or in part contains the Program or any part thereof, either with or without modifications, to be licensed at no charge to all third parties under the terms of this General Public License (except that you may choose to grant warranty protection to some or all thir
copies, or rights to use copies, from you under this General Public License will not have their licenses terminated so long as such parties remain in full compliance. 5. By copying, distributing or modifying the Program (or any work based on the Program) you indicate your acceptance of this license to do so, and all its terms and conditions. 6.
Digest MD5 Artistic The "Artistic License" Preamble The intent of this document is to state the conditions under which a Package may be copied, such that the Copyright Holder maintains some semblance of artistic control over the development of the package, while giving the users of the package the right to use and distribute the Package in a more-or-less customary fashion, plus the right to make reasonable modifications.
site such as uunet.uu.net, or by allowing the Copyright Holder to include your modifications in the Standard Version of the Package. b) use the modified Package only within your corporation or organization. c) rename any non-standard executables so the names do not conflict with standard executables, which must also be provided, and provide a separate manual page for each non-standard executable that clearly documents how it differs from the Standard Version.
when no overt attempt is made to make this Package's interfaces visible to the end user of the commercial distribution. Such use shall not be construed as a distribution of this Package. 9. The name of the Copyright Holder may not be used to endorse or promote products derived from this software without specific prior written permission. 10.
The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License Agreement applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License.
Paragraphs 1 and 2 above; or, b) accompany it with a written offer, valid for at least three years, to give any third party free (except for a nominal charge for the cost of distribution) a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Paragraphs 1 and 2 above; or, c) accompany it with the information you received as to where the corresponding source code may be obtained.
NO WARRANTY 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. JBoss.
or that the operation of the Software Packages will be entirely error free or appear precisely as d in the accompanying documentation. This warranty extends only to the party that purchases the Servi pertaining to the Software Packages from Red Hat or a Red Hat authorized distributor. 4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, the re described below are accepted by Client as its only remedies.
a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JCRAFT, INC.
library. If the library is modified by someone else and passed on, we want its recipients to know that what they have is not the original version, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that companies distributing free software will individually obtain patent licenses, thus in effect transforming the program into proprietary software.
A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms.
application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole.
However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.
d) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it.
conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all.
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU.
LWP UserAgent license Artistic The "Artistic License" Preamble The intent of this document is to state the conditions under which a Package may be copied, such that the Copyright Holder maintains some semblance of artistic control over the development of the package, while giving the users of the package the right to use and distribute the Package in a more-or-less customary fashion, plus the right to make reasonable modifications.
a) place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or placing the modifications on a major archive site such as uunet.uu.net, or by allowing the Copyright Holder to include your modifications in the Standard Version of the Package. b) use the modified Package only within your corporation or organization.
regression tests for the language. 8. Aggregation of this Package with a commercial distribution is always permitted provided that the use of this Package is embedded; that is, when no overt attempt is made to make this Package's interfaces visible to the end user of the commercial distribution. Such use shall not be construed as a distribution of this Package. 9.
software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0.
Paragraphs 1 and 2 above provided that you also do one of the following: a) accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Paragraphs 1 and 2 above; or, b) accompany it with a written offer, valid for at least three years, to give any third party free (except for a nominal charge for the cost of distribution) a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Paragraphs 1 and 2 above
make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
OpenSSL license LICENSE ISSUES ============== The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED * OF THE POSSIBILITY OF SUCH DAMAGE. * ==================================================================== * * This product includes cryptographic software written by Eric Young * (eay@cryptsoft.com). This product includes software written by Tim * Hudson (tjh@cryptsoft.com).
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * The licence and distribution terms for any publicly available version or * derivative of this code cannot be changed. i.e. this code cannot simply be * copied and put under another distribution licence * [including the GNU Public Licence.
3. You may otherwise modify your copy of this Package in any way, provided that you insert a prominent notice in each changed file stating how and when you changed that file, and provided that you do at least ONE of the following: a) place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or placing the modifications on a major archive site such as uunet.uu.
languages) supplied by you and linked into this Package in order to emulate subroutines and variables of the language defined by this Package shall not be considered part of this Package, but are the equivalent of input as in Paragraph 6, provided these subroutines do not change the language in any way that would cause it to fail the regression tests for the language. 8.
(2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
derivative) on a volume of a storage or distribution medium does not bring the other work under the scope of these terms. 3.
8. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 9.
i) changes to the Program, and ii) additions to the Program; where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf.
a) it complies with the terms and conditions of this Agreement; and b) its license agreement: i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose; ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential dam
Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages. 5.
Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.
3. Distribution Obligations. * * * * 3.1 3.2 3.3 3.4 Application of License. The Modifications which You create or to which You contribute Availability of Source Code. Any Modification which You create or to which You contri Description of Modifications. You must cause all Covered Code to which You contribute Intellectual Property Matters. o (a) Third Party Claims. If Contributor has actual knowledge that a license under a t o (b) Contributor API's.
Trilead SSH license Copyright (c) 2007-2008 Trilead AG (http://www.trilead.com) All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: a.) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. b.
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The Java implementations of the AES, Blowfish and 3DES ciphers have been taken (and slightly modified) from the cryptography package released by "The Legion Of The Bouncy Castle". Their license states the following: Copyright (c) 2000 - 2004 The Legion Of The Bouncy Castle (http://www.bouncycastle.
"You" is you, if you're thinking about copying or distributing this Package. "Reasonable copying fee" is whatever you can justify on the basis of media cost, duplication charges, time of people involved, and so on. (You will not be required to justify it to the Copyright Holder, but only to the computing community at large as a market that must bear the fee.) "Freely Available" means that no fee is charged for the item itself, though there may be fees involved in handling the item.
Package. You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own. You may embed this Package's interpreter within an executable of yours (by linking); this shall be construed as a mere form of aggregation, provided that the complete Standard Version of the interpreter is so embedded.
General Public License applies to the Free Software Foundation's software and to any other program whose authors commit to using it. You can use it for your programs, too. When we speak of free software, we are referring to freedom, not price.
b) cause the whole of any work that you distribute or publish, that in whole or in part contains the Program or any part thereof, either with or without modifications, to be licensed at no charge to all third parties under the terms of this General Public License (except that you may choose to grant warranty protection to some or all third parties, at your option).
5. By copying, distributing or modifying the Program (or any work based on the Program) you indicate your acceptance of this license to do so, and all its terms and conditions. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
Copyright (c) 2009 Leonardo Rossetti motw.leo@gmail.com Licensed under the MIT license (http://www.opensource.org/licenses/mit-license.php) THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
VMware VI Java API license Copyright (c) 2008 VMware, Inc. All Rights Reserved. Copyright (c) 2009 Altor Networks. All Rights Reserved. Copyright (c) 2009 NetApp. All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
modified, or has been modified in accordance with the wishes of the Copyright Holder as specified below. "Copyright Holder" is whoever is named in the copyright or copyrights for the package. "You" is you, if you're thinking about copying or distributing this Package. "Reasonable copying fee" is whatever you can justify on the basis of media cost, duplication charges, time of people involved, and so on.
d) make other distribution arrangements with the Copyright Holder. 5. You may charge a reasonable copying fee for any distribution of this Package. You may charge any fee you choose for support of this Package. You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own.
The license agreements of most software companies try to keep users at the mercy of those companies. By contrast, our General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. The General Public License applies to the Free Software Foundation's software and to any other program whose authors commit to using it. You can use it for your programs, too.
it, and copy and distribute such modifications under the terms of Paragraph 1 above, provided that you also do the following: a) cause the modified files to carry prominent notices stating that you changed the files and the date of any change; and b) cause the whole of any work that you distribute or publish, that in whole or in part contains the Program or any part thereof, either with or without modifications, to be licensed at no charge to all third parties under the terms of this General Public License
the Program under this License. However, parties who have received copies, or rights to use copies, from you under this General Public License will not have their licenses terminated so long as such parties remain in full compliance. 5. By copying, distributing or modifying the Program (or any work based on the Program) you indicate your acceptance of this license to do so, and all its terms and conditions. 6.
zlib license ZLIB DATA COMPRESSION LIBRARY zlib 1.2.3 is a general purpose data compression library. All the code is thread safe. The data format used by the zlib library is described by RFCs (Request for Comments) 1950 to 1952 in the files http://www.ietf.org/rfc/rfc1950.txt (zlib format), rfc1951.txt (deflate format) and rfc1952.txt (gzip format). These documents are also available in other formats from ftp://ftp.uu.net/graphics/png/documents/zlib/zdoc-index.
Notes for some targets: - For Windows DLL versions, please see win32/DLL_FAQ.txt - For 64-bit Irix, deflate.c must be compiled without any optimization. With -O, one libpng test fails. The test works in 32 bit mode (with the -n32 compiler flag). The compiler bug has been reported to SGI. - zlib doesn't work with gcc 2.6.3 on a DEC 3000/300LX under OSF/1 2.1 it works when compiled with cc. - On Digital Unix 4.
entirely written by Jean-loup Gailly and Mark Adler; it does not include third-party code. If you redistribute modified sources, we would appreciate that you include in the file ChangeLog history information documenting your changes. Please read the FAQ for more information on the distribution of modified source versions.
Glossary This glossary defines acronyms and terms used in this guide or related to this product and is not a comprehensive glossary of computer terms. cleanup Clean up steps are performed after a recovery plan test. The steps begin executing after you have responded to the prompt displayed after the test completes. 1. Power off each recovered virtual machine 2. Replace recovered virtual machines with placeholders, preserving their identity and configuration information. 3.
Protected Site The datacenter containing the protected virtual machines from which data is being replicated to the recovery site. protection group A collection of virtual machines and templates. When you create a protection group, it initially contains only those virtual machines that store all of their files on one of the datastore groups associated with the protection group. RAID Redundant array of independent disks.
Index C contacting HP, 41 conventions document, 42 D document conventions, 42 documentation providing feedback, 43 related, 41 documentation, HP website, 41 R related documentation, 41 S Site Recovery Manager (SRM) discovery process, 7 Subscriber's Choice, HP, 41 T error messages, 33, 36 technical support HP, 41 technical support service locator website, 42 troubleshooting, 33 typographic conventions, 42 F W E Failback overview, 31 Failover overview, 31 Failover testing overview, 9 websites, 41 H
