Many thanks, Mike, good to know it's in use elsewhere. Anything I'm
missing in terms of the switching out frontends/enabling a new system,
or any gotchas I need to worry about apart from the licensing issues you
bring up?
Mike Pflugfelder wrote:
Peter,
I've had experience with the same setup. We have used SANs for
High Availability environments as well as Disaster Recovery as well. We
have used this in quite a few environments that want to be up all of the
time. We haven't ever tried to use different OS releases as the purpose
was to keep the system highly available or be back online as quickly as
possible. One of the advantages of a scenario like this is that you
don't need to purchase additional licenses for other servers. If your
application goes down for any reason, you fail the disks over to another
server and bring up the application from there. In other scenarios, you
either purchase hot-standby licenses at a percentage of the full price,
or purchase a small user license, then replace it with the full license
if you have a disaster situation.
Just my $0.02
Michael Pflugfelder | Systems Integrator | Keystone Information Systems
| 856-722-0700 | [EMAIL PROTECTED]
--
Peter Ivanick
Web Services and Instructional Technologies
School of Veterinary Medicine, University of Pennsylvania
Email: [EMAIL PROTECTED]
Phone: 215.573.2306 Fax: 215.573.8777
http://www.vet.upenn.edu/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
