I searched around to see if this topic has come up before, but didn't find much. Hopefully someone is willing to share some insights (much appreciated).
I have a DNN 4.7.0 site that I have been running for some time now, and am considering adding a second site. However, I suspect that the second portal might get moved on to a different physical server down the road. Because of this, I am leary of putting the new portal on my existing DNN installation.
Are there any reasons why I couldn't do a parallel installation of DNN on my server (i.e., two physical SQL database files and two physical installation of DNN on the same server)? My thinking was that if I had to move a portal to a new server, it would be as simple as detaching the database and moving the db files and DNN directory to the new server. Assuming the backend software was running, the migration would be relatively painless. However, if I have both portals running off of one DNN instance, moving just one of them to a new server becomes a bit tricky.
Bad idea? At the moment, I can't think of why, other than there could be somewhat higher overhead for running two portals on the server (that doesn't concern me much because neither site wil be high traffic).
One more quick one -- if a parallel installation is possible, is there any reason that the two installations should be the same version of DNN? Or can I keep my existing DNN 4.7 site and install a new 4.8.1 site as well?
Thanks!