|
For TAA Tools, if you want a working license for the second system, you need to purchase a second license. But if you truly only us it for D/R, you can make the license for your first system work on the second for seven days. See: http://www.taatool.com/document/L_crtgrckey.htm Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 02/13/2006 01:04 cc PM Subject RE: Software Licensing for HA Please respond to systems Midrange Systems Technical Discussion <midrange-l@midra nge.com> Based on his later response I'd bet there's not a reason to have a HA solution if he cannot use those two packages. Software licensing fees are a valid reason to phase out a package. However I'd make double sure that any replacement package was not similarly affected. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 02/13/2006 12:46 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: Software Licensing for HA systems Question, Can you limp along with out those two packages for a short period while in DR mode? Are you implementation a HA system so you can move users to the backup system while upgrading the primary system ? Third, can you phase out these two packages? Christopher Bipes Information Services Director CrossCheck, Inc. 707.586.0551, ext. 1102 707.585.5700 FAX Chris.Bipes@xxxxxxxxxxxxxxx www.Cross-Check.com Notice of Confidentiality: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me by e-mail (by replying to this message) or telephone (noted above) and permanently delete the original and any copy of any e-mail and any printout thereof. Thank you for your cooperation with respect to this matter. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ron-Zimmerman@xxxxxxxxxxxxxxx Sent: Monday, February 13, 2006 8:56 AM To: Midrange Systems Technical Discussion Subject: Software Licensing for HA systems I would like to know the experience of others with their software licensing and how they have responded when they implemented an HA solution such as MIMIX, iTera's ECHO2, etc. As we have started preparing for implementing the ECHO2 solution, we contacted all of our software vendors about how we would deal having a second copy of their software on the HA system. What we have found is that the software vendors' policies range from allowing the second copy for no additional charge all the way to requiring what we consider to be an unreasonable additional fee. Our position with the vendors is that the second copy is only used as a disaster recovery backup and we will never be using more than one copy of the software at any one time, so we believe that anything more than a very nominal additional charge is unreasonable. We have two vendors who are asking/requiring a fee equal to 25% of the list price for the HA copy of their software which we believe is very excessive. I would like to hear the experience of others and how they have dealt with this situation when they implemented their HA systems. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.