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] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Ivanick Sent: Monday, January 23, 2006 10:40 AM To: u2-users@listserver.u2ug.org Subject: [U2] Hypothetical question about switching server frontends to SAN w/o reinstalling Universe Hola all - We've got our UniVerse installation (RH AS 3.5, U2 10.1.4) on a SAN partition, /usr/ibm is mounted entirely from there and that's where everything was installed to. On a hardware testing server, I had the opportunity to test out pointing an entirely different front-end system to that partition (well, a copy of it for testing) to see if U2 would come up, and it did indeed after I: 1) copied uv.rc, S999uv.rc, .uvhome & .unishared over to the new system 2) linked .uvlibs appropriately 3) restore spconfig & the whole spool directory from a backup 4) added the RPC port into /etc/services Is there anything I missed here that would be helpful and/or necessary to proper functioning? I'm looking at this as an extreme disaster recovery scenario possibility, but theoretically it could substantially ease upgrading the system as well (although ours is pretty recent so this likely wouldn't come up for some time) with minimal downtime. Thoughts/comments? Would OS differences matter at all here, i.e. if one was RH 3.5 64 bit and the next system coming up was 32 bit, or a jump from the 2.4 kernel to the 2.6 kernel (presuming the release of U2 supported the 2.6 kernel)? Thanks very much for any input. -- 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/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/