Here's my interpretation of the license: If the heartbeat is done outside of Universe, then it's considered "cold". If the heartbeat is done inside of Universe, therefore requiring that Universe be running, it's considered "hot".
-Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Augusto Alonso Sent: Thursday, October 14, 2010 8:38 AM To: U2 Users List Subject: Re: [U2] Cloud UniVerse Hi all. I have a doubt about this. What happens if I have this scenario: - 2 linux boxes with universe installed. Both the same license, but only the active server has Universe started. - a unique shared hard disk that holds my DataBase. - In case of shutdown of the active server, the heartbeat software takes the control and starts Universe on the standby server. According to the fact that "the Program has not been started", it should be considered "Cold". But according to the fact that I am using a software called "heartbeat", shuld it be considered "Hot"? Does anybody know wich is the right consideration? Thanks -- Augusto Alonso Alonso Director de Sistemas QUITER SERVICIOS CENTRALES Zoco Gran Santander, 1ª planta - 39011 Santander - España Telf: +34 902233323 - Fax: +34 902234280 AVISO LEGAL: Este mensaje contiene información destinada exclusivamente al usuario de destino, pudiendo contener información confidencial o protegida legalmente. Si, por un error de envío o transmisión, ha recibido este mensaje y usted no es el destinatario del mismo, por favor, notifique de este hecho al remitente y no use, informe, distribuya, imprima, copie o difunda este mensaje bajo ningún medio . Cualquier opinión en él contenida, es exclusiva de su autor y no representa necesariamente la opinión de Quiter Servicios Centrales. LEGAL WARNING: This e-mail and any attachment, contain information intended solely for the addressee and may contain confidential information or legally protected data. If you are not the intended recipient, please notify the sender and do not use, disclose, distribute, copy, print or rely on this e-mail under any circumstances. The views and opinions expressed are the author´s own and do not necessarily reflect those of Quiter Servicios Centrales. 2010/10/7 Bill Brutzman <[email protected]> > The following is what I received from RS... > > License Types > Rocket U2 offers several types of disaster recovery licenses as described > in this document: Backup (Cold, Warm, Standby, and Hot). Primary licenses > and Hot Backup licenses are interchangeable. License types cannot be changed > after initial licensing. > > Cold > A copy of the Program may be stored for backup purposes on a machine as > long as the Program has not been started. There is no additional charge for > this copy. > > Warm > A copy of the Program may reside for backup purposes on a machine. It may > be started, but is "idling", and is not doing any work of any kind. There is > no additional charge for this copy. > > Standby > A copy of the Program may reside for backup purposes on a machine. It may > be started but may not be doing work. A Standby license provides for rapid > failover and can mirror data, update files, and synchronize programs, data > or other resources as well as periodic failover testing. It cannot be used > for production, development, solution testing, program maintenance, > reporting or other operational uses. A Standby license is currently > available at a 75% off the SRP (except U2.NET which has a different > pricing structure) and must mirror the primary license in number of users, > features, and maintenance status. A Standby license cannot be converted, > consolidated or distributed to a non-Standby license. Applicable ISV > contract discounts apply. > > Hot > A copy of the Program may reside for backup purposes on a machine. It may > be started, and is doing work. However, this Program must be ordered, and > there is a charge for this copy. > "Doing work", includes, for example, production, development, program > maintenance, and testing. It also could include other activities such as > mirroring of transactions, updating of files, synchronization of programs, > data or other resources (for example, active linking with another machine, > program, database or other resource, and so on), or any activity or > configurations that would allow an active hot switch or other synchronized > switch over between programs, databases, or other resources to occur. > In the case of a program or system configuration that is designed to > support a high availability environment by using various techniques (e.g. > duplexing, mirroring of files or transactions, maintaining a "heartbeat", > active linking with another machine, program, data base or other resource, > etc.), the program is considered to be doing work in both the "hot" and > "standby" situations and a use authorization is required and a charge > applies. > A scheduled hardware outage, such as preventive maintenance or installation > of upgrades, is not considered a backup situation. However, the same > guidelines apply. In addition, the outage should not be scheduled during > peak (e.g. end-of-month) processing times if the program has a > capacity-based charging metric and the secondary machine has more capacity > than the primary machine. > A Hot backup license is equivalent to a production license. > > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
